bouldersoundguy
Well-known member
Loopback test shows they DON'T line up perfectly.
It is definitely record latency. I'll leave the solution to those who know the software.
Loopback test shows they DON'T line up perfectly.
Just to be clear, you shouldn't be using either of these.
I used the latency correction in the advanced options that said "Correct for Record Latency".
It should!! I wonder why it isn't.1. So why doesn't Cubase automatically correct latency?
Not sure2. Surely when I use my other input it will be 10ms out because my audacity loopback test test proved I get different values for different line ins.
There is a loopback test in the panel I described earlier. Cubase gets latency data from the ASIO driver. It should be using it to determine the offset and it should be automatic. Unless you have something turned off or selecting the wrong driver, it should be working and you shouldn't have to even think about it.3. How does Cubase "know" the latency? Is it definitely correct or an estimation? Could I do a loopback test in Cubase and get a better result?
Well, that gets subjective. lol4. How can it be such a simple resolution considering millions of forums posts are dedicated to solving it?
Hi,
Been looking round to try and work this one out, and there seems to be no definite answer other than reduce latency with faster hardware from the start. However...
I'm running a Lexicon Alpha into my laptop (i3, 8GB RAM) which is running Cubase (I've just switched from Audacity). Audacity used a latency correction that re positioned the track after the recording.
In Cubase, under device management it tells me latency is 36.077ms. Because I use hardware monitoring through the Lexicon which is no latency (or very low) does this not mean I can just correct latency is Cubase by exactly 36.077ms for every track I do? Why isn't this the standard answer, it seems too simple for latency to be such a huge issue!
What have I missed? (and how would I do this in Cubase 5 LE?)
Thanks!