Forum
    • Categories
    • Register
    • Login

    Latency issues..

    Scheduled Pinned Locked Moved General Questions
    4 Posts 3 Posters 1.0k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      Jeetender
      last edited by

      I made a vst everything works fine, but when i open that vst into any daw like flstudio/live/reaper/reason it gives out latency.. how do i compensate the latency automatically?

      dannytaurusD J 2 Replies Last reply Reply Quote 0
      • dannytaurusD
        dannytaurus @Jeetender
        last edited by dannytaurus

        @Jeetender You can use setLatencySamples() to report the latency amount to the host, so it can compensate.

        https://docs.hise.dev/scripting/scripting-api/engine/index.html#setlatencysamples

        However, I think the tool to measure the latency of your plugin is currently broken.

        Tools > Check latency of signal chain

        https://forum.hise.audio/topic/14245/check-latency-broken-on-latest-develop-build?_=1783032811243

        HISE dev latest / super.engineering + Claude Fable / Figma + Affinity
        Meat Beats: https://meatbeats.com
        Klippr Video: https://klippr.video

        1 Reply Last reply Reply Quote 0
        • J
          Jeetender @Jeetender
          last edited by

          @Jeetender said in Latency issues..:

          I made a vst everything works fine, but when i open that vst into any daw like flstudio/live/reaper/reason it gives out latency.. how do i compensate the latency automatically?

          i did try this.. but nothing worked, BUT i had a dynamic module in the end of the chain, which had a limiter, i removed it and then the latency was gone after compiling the vst..

          ustkU 1 Reply Last reply Reply Quote 1
          • ustkU
            ustk @Jeetender
            last edited by

            @Jeetender That is strange. Didn't you see the latency reported in the DAW?

            Removing the module that causes latency is not a viable solution. Once you know the latency of your plugin, you should just be able to report it to the DAW with this method.

            So it's not an "in plugin compensation" but telling the DAW "hey, I introduce this amount of latency, please compensate for me" (in which "this amount" is your job to determine)

            Hise made me an F5 dude, any other app just suffers...

            1 Reply Last reply Reply Quote 0
            • First post
              Last post

            27

            Online

            2.5k

            Users

            13.9k

            Topics

            121.0k

            Posts