Latency........????

Can someone explain to me what influence has the latency from each channel to my mixdown?
The question is, do the tracks line up when i mixdown so everything is tight? I’m trying to find in google topics about this but it is not clear to me…
Anyone please…???

Hi,

Yes, Cubase takes care about the plug-in delay compensation automatically.

Yes of course. Latency only matters during live tracking. What soundcard do you have? What settings is it at?
If you want a soundcard with very low latency then… It does not get better than an RME Baby face pro (for usb)
Any universal Audio product will else deliver great results.

Also make sure your asio guard is on and set to at least low. That is in studio setup under vst audio settings. Here is mine
I can run my UAD arrow at 64 or 128 buffer size (using Cubase’s asio guard on normal setting, and I have no popping or clicks. I have a good amount of VST effects and instruments running as well)

I also have a pretty good computer. So that helps.

Thank you both for the answers.

Even during live tracking latency mainly needs to be low if you are MONITORING WHAT YOU ARE RECORDING through Cubase. For example, if you are playing a MIDI controller to a HALion VST Instrument, or recording a guitar or vocal that is being processed and monitored within the DAW. If you are recording a guitar and monitoring the guitar from your amp, for example, Cubase compensates for that latency.

I have no issues with latency at all. I monitor through cubase. Live track with vocals, guitars, vst instruments etc. It’s virtually undetectable.

Same here. I am just saying monitoring through the DAW is when one really NEEDS low latency. It’s not as important when monitoring directly.

Thank you guys for the answers BUT the question was about the plugin latencies not the ASIO latency. Anyway thank you.

Same idea. If you are just mixing, it doesn’t matter. Cubase keeps everything tight. If you are recording live and monitoring through one of those plug-ins (a reverb or pitch correct, for example) and it has high latency, then you will notice the delay and it may be difficult to perform. That is why, as a rule, don’t monitor through high latency plug-ins while monitoring a recording.
The total ASIO latency is made up of several latencies. The audio interface conversions plus anything inside the DAW such as plug-ins.

The lower the latency of your soundcard, the lower the latency in your plugins. I do not notice any latency with the RME babyface PRO when I am under 128 buffers. Same goes for the UAD arrow. I do not notice ANY latency.

No you have to add plugin latency to asio/interface latency.
Cubase 10, now has the ability to show plugin latency.
So no need to guess anymore, plugin latency can be shown right in the mixer channel.

Hey, i have a problem with latency on Cubase 10.5 with RME UCX. Buffer is 48 samples, and with standalone application there is no latency at all, but within Cubase its virtually unplayable. Every driver is up to date, every setting has been checked…

the latency is determined by each and single plugin you use.

You pick the “setup windows layout” in the Mixer - check to show latency, this will give you the total latency on each channel going into the stereo output.

As you can tell on my picture “Little Alterboy” gives me 51 ms alone on 1 channel while the next channel with 3 plugins gives a total of 11,8 ms

I have plugins that give more than 200 ms so this is just how things are. Some developers care about low latency, some not so much.

What “standalone application” are you talking about?
In Cubase disable all Plugins (Disable, not bypass - also the ones in Control room)

The answer to the original question is: The latency in cubase and interfaces etc has absolutely NO influence on your mixdown. All tracks will line up perfectly. So as far as mixdown is concerned you simply forget the term at all. Cubase handles it.

Neural DSP Archetype Plini. Tried to open only that in Cubase project and it still has latency when monitoring through Cubase. No latency in Studio One or Standalone mode…

hi
yes you need a big computer to run plugings at 64 samples without clic and pops in cubase…
but even at 64 samples you have 5.079+3.515 milisecond so at 44 khz you will have 370 samples of recording shift latency .
i have an old computer lga 775 qx6850 8 go ssd sata 2 windows 7 x64
and i’am working at 512 samples. but not with cubase.
with samplitude and protools hd tdm.
in samplitude you have the same option “record shift” maned offset recording in samplitude.
in protools hd i can make working maybe 10 big plugins at 64 samples buffersize.
but when i use protools alone a have latency and when i use samplitude or cubase alone …it only work at 1024 samples . to much latency for playing plugins in realtime.
so i use samplitude at 1024 sample asio direct monitoring and protools hd at 64/128 samples.
now i will explain you how i resolve the latency problems of plugins when you record in realtime with a vst or rtas on insert.
first i record a click track in samplitude.
after i record this click track passing throught protools plugins into samplitude.
then i see the latency of protools plugins.
for example guitar rig rtas at 128 samples buffer protools do 459 samples of latency.
so i put 512 samples in the recording offset and 53 samples in the time adjuster plugins of protools.
why ? because every plugins have diferrent latency in protools.
when i use a tdm plugin i have only 130 samples latency then i put 382 samples in the time adjuster of protools 382+130=512 .
now i can use all the existing plugins (vst/rtas/tdm/aax) measuring and compensate the latency of every plugins with samplitude adjusting them with time adjuter and i can record my guitare basse drums voices with plugins and without any latency in samplitude !!!
you can maybe do the same with cubase alone .
first disable asio direct monitoring (because it disable vst plugins)
2 disable adjust for record latency.
3 put a global value in record shift (higher than the plugins who do the bigiest latency)
4 disable vst latency compensation.
5 record and audio click track
passing it in your plugins
6 see the difference - the 512 samples of recording shift= track delay latency
7 adjust the difference in the option track delay of cubase.
i think it will work
i cannot make running plugins under 512 samples in cubase .
but 512 samples is quite when you record guitar rig for example.
if you want be more precise you have to hear your guitare through a real amps and switch the signal in the same time to the plugins. (for hearing the real time signal)
you maybe have bad suprise with asio guard because 23.220 millisecond is maybe 1024 samples latency !
if it so disable it ! because at 1024 samples you cannot play guitar rig in realtime…
cubase is to big ! samplitude is light powerfull and easy and quite for little computer.
that’s why now i use samplitude for recording audio and midi and protools hd for plugins and instrument played by samplitude midi tracks.
best regards