This is something I never really came up to before but is causing me issues and I wont to check if its normal and/or can be changed.
Currently if I am monitor two tracks with the same input, if one track has a plugin that has latency, only that track will have compensation the other doesn’t meaning there is a delay between the two tracks. Once recorded its fine but it means I am monitoring with weird phase issues at best and a slapback delay at worse. I don’t care if I am forced to have more overall latency as long as they are equal. If i wanted no latency Id use the constrain delay compensation button, Its really annoying if I want to record say a DI and Bass Amp sim at the same time and listen to the mix and any of the processing has different latency (which is common when doing overdubs). Also makes me wonder if then Id be playing out of time of other tracks if monitoring isn’t keeping up with the latency of other tracks.
Hi,
Yes, this is how all DAWs work. The signal has to arrived first, then you can process it. You cannot shift the life (monitored) signal ahead (what latency compensation really is under the hood), because the signal arrives now.
I understand that I just thought the monitor would add minimum latency to match the other latency or at worst have an option where it applies uniform latency across all channels which is how I thought it used to work (if say you had a huge latency on a drum track, all tracks would have latency when monitored) which is why constrain latency exists, otherwise what is the point of constrain latency compensation if other tracks latency don’t add to the latency of the monitor channels, it should just turn them off the channels that you are monitoring instead of all channels?
The work around I have is using M utility to match the latency and report that to cubase which then adds that latency to that track, only works if plugins are reporting latency correctly though (otherwise its a guessing game).
I also thought of latency compensation was to match all the latencies together not necessarily process them ahead of time which you can’t do in real time but you can still match latency in real time it just requires delaying everything until they match the biggest latency. This is how it works in live consoles (not all of them have it) which obviously can’t travel ahead in time either.
Hi,
In this case, you couldn’t play in sync with the background music (other tracks), because the background would be delayed (significantly in this case).
use the ‘constrain delay compensation’ button when recording to get round the difference between the 2 channels, or any channel with a latent plugin more than your audio buffer size. Or use Zero latency plugins when tracking.
M
Hi,
Be aware, this will bypass plug-ins with latency. That means, you will get different sound on the given track.
You can switch some plug-ins into the “Live” mode to avoid the latency.
This is one of the reasons why a number of audio interfaces give you the option of direct monitoring. As fast as computers are nowadays, they don’t yet possess the ability to travel back in time.
Can’t you just put the same plug on both tracks but bypass the one on the di?