How do you account for round trip latency?

Home › Forums › Products › Rackmount › How do you account for round trip latency?

Viewing 6 reply threads
  • Author
    Posts
    • February 27, 2023 at 9:58 pm #169436
      joeydego
      Participant

      Anyone on the air with an H9000 and studio one? How do you account for RTL? I use pipeline and ping the H9000 in bypass and its usually between 50 and 100 samples, but this does not account for the RTL which is usually considerably longer, resulting in ghosted hits. On a reverb algo with pre dalay and a snare drum, if I dial in the pre delay to match the latency # I see in pipeline (after pinging), its perfect.

    • February 28, 2023 at 2:38 pm #169457
      tbskoglund
      Moderator
      Eventide Staff

      Can you elaborate when you say “this does not account for the RTL”? The audio is being sent from the DAW out of the interface, through the H9000, and back to the DAW via the interface. What additional latency is there? If you are using the Pipeline plug-in, all of this latency should be accounted for when you ping the FX Chain.

      I don’t have Studio One to test this, but I just set up a similar test using Logic’s Audio I/O plug-in and the latency compensation seems to be working correctly. I can ping the plug-in and it will report various sample latency’s depending on my algorithm configurations. Once the latency is configured, the audio will sound correctly compensated. If I am using a reverb plug-in that has pre-delay, the pre-delay will introduce an additional delay before the sound is processed by the reverb.

      It sounds like perhaps the Pipeline delay compensation isn’t working correctly.

       

    • February 28, 2023 at 4:14 pm #169458
      joeydego
      Participant

      Ok here are a couple screenshots showing the plugin shows 2 numbers. 1 sample and 45.63ms of RTL. Pinging the device gives these numbers. What is S1 accounting for? A single sample (nothing) or 45.63ms? I’m hearing doubling thru only my eventide stuff so I’m guessing pipeline, S1 and my interfaces are acting normally.

      Attachments:
      You must be logged in to view attached files.
    • February 28, 2023 at 4:14 pm #169460
      joeydego
      Participant

      Here’s my interfaces current RTL

      Attachments:
      You must be logged in to view attached files.
    • February 28, 2023 at 4:33 pm #169463
      tbskoglund
      Moderator
      Eventide Staff

      Thanks for this info.

      Looking at those screenshots, it seems that Pipeline is just reporting the latency of the interface, which doesn’t make sense to me.

      Are you sure that instance of Pipeline is configured to send audio to/from the H9000? It should be reporting more latency being introduced by the H9000. You should also be getting a different latency amount depending on how your algorithms are configured: https://cdn.eventideaudio.com/manuals/h9000/2.0/content/setup/DAWLatencyCompensation.html#content-setup-dawlatencycompensation–page-root

      What happens when you ping another piece of outboard gear?

    • February 28, 2023 at 5:25 pm #169465
      joeydego
      Participant

      Im sorry I should have been specific and a little neater about this last post. THAT instance of pipeline was on an analog compressor. There is no latency so naturally, thats what it reports, 1 sample. Sometimes zero. On my 9000, I get anywhere between 30 something and 120 samples or so per algo, depending adat or analog. Now, 120 samples at 48k is maybe 3ms. This doesnt account for my entire RTL which you can see is in the dozens of ms at this high buffer. How does the DAW/Interface/Eventide sync this up so it’s in phase to a sample level? Does the RTL not matter?

    • March 1, 2023 at 10:15 am #169470
      tbskoglund
      Moderator
      Eventide Staff

      Thanks for clarifying that.

      The H9000 does not do any latency compensation or syncing etc, all of that must be done in the DAW.

      Looking into the Pipeline plug-in a bit further, it seems that the ms readout in the top left always displays the round-trip latency of the interface, regardless of what hardware is connected. It looks like when you ping the hardware, it will add that additional latency to the round-trip latency. The latency sample amounts you have reported from the H9000 seem correct.

      If you click the little wrench icon in Pipeline, that will display both waveforms and you can line them up manually if the auto button isn’t working (but the auto button should do this correctly for you) – https://youtu.be/6cKMcxpaIFk?t=431

       

  • Author
    Posts
Viewing 6 reply threads
  • You must be logged in to reply to this topic.