Jump to content
FJ Lamela

plugin total added latency???

Recommended Posts

 

Hello and thanks to all member of this forum.

My question is simple.

There is any way to know how much latency added the  total plugins  in the project?.

Thanks.

Share this post


Link to post
Share on other sites

in general, you need to know the "maximum" or "largest" latency which is used by the DAW to then set it across the board so everything plays in sync.

image.thumb.png.1f575dd8769cbc025935db2944709663.png

so if i have only a single track with 5 plugins and none of the other tracks have anything on them, all the tracks will use the latency reported from that one track to set the overall latency so everything plays as expected. e.g. if that one track plugins add 10ms of latency, then all other tracks will be delayed by 10ms so all tracks are playing at the same time. (this is a simplification since internally i'm sure exactly what is happening but the effective results is the same).

note that # of buffers used, as well as the sample rate will dictate the overall latency of the chain.

image.png.79eab86d23c6665f3d5b3727d5376090.png

CbB has a button "PDC" (plugin delay compensation) which if you turn it off will (should?) remove the compensation added based on what CbB determined based on the latency reported by the plugins etc.  this (to me) should identify which track has the most because it will be out of sync.

so you'd want to measure the latency of the tracks (or busses) to see which one has the most, and then how much latency that track (or buss) has. one way (manually) would be to use something like https://www.voxengo.com/product/latencydelay/ and pick a track with nothing else on it and adjust the time/samples until it aligns with the longest track. or try out https://www.kvraudio.com/product/vst-plugin-analyser-by-christian-budde

some references on internal latency in a DAW:

https://www.macprovideo.com/article/recording-and-production/understanding-plug-in-delay-compensation

https://help.ableton.com/hc/en-us/articles/360010545559-How-Latency-Works

https://www.16sounds.com/blog/zero-latency-plugins/

 

Edited by Glenn Stanton
  • Like 4

Share this post


Link to post
Share on other sites

Thanks for the info.

Anothers daws,show you the latency added by the plugins in a easy way,next to bpm or sample rate (for example).

Calculate manually with voxengo or similar is so hard and have so sense to me.

I think is so ease put Pdc (number)at some position in the screen by the daw.

Share this post


Link to post
Share on other sites

yeah, it would be nice to have the full latency total for a given track and by plugin in a small display or metric popup... hmmmm

  • Great Idea 2

Share this post


Link to post
Share on other sites

Dumb question: For mixing, why should I care as long as PDC is working? What am I missing? I think it would be nice to know what it is but I don't understand a need to know. Thanks.

  • Great Idea 1

Share this post


Link to post
Share on other sites
13 hours ago, Glenn Stanton said:

Yeah, it would be nice to have the full latency total for a given track and by plugin in a small display or metric popup... hmmmm

Like Cubase does for its console strips?

  • Like 1

Share this post


Link to post
Share on other sites

and maybe some estimate of the CPU usage for the plugins/synths so we could get the first suggestion from our DAW what plugins to freeze first, not that it's crucial but could be handy... sorry for off topic

Share this post


Link to post
Share on other sites
On 2/21/2021 at 1:36 PM, Bill Phillips said:

Dumb question: For mixing, why should I care as long as PDC is working? What am I missing? I think it would be nice to know what it is but I don't understand a need to know. Thanks.

Sometimes knowing it can be useful if you are recording (traking)for example a guitar or a vocalist and there is a plugin that is introducing a lot of delay in the chain. Or for example when you have to play a vst synthesizer in real time and some included effect causes a lot of delay in the chain, you can change it for a lighter one.

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites
1 hour ago, FJ Lamela said:

Sometimes knowing it can be useful if you are recording (traking)for example a guitar or a vocalist and there is a plugin that is introducing a lot of delay in the chain. Or for example when you have to play a vst synthesizer in real time and some included effect causes a lot of delay in the chain, you can change it for a lighter one.

Thanks. Makes sense.

  • Thanks 1

Share this post


Link to post
Share on other sites
On 2/21/2021 at 4:36 AM, Bill Phillips said:

Dumb question: For mixing, why should I care as long as PDC is working? What am I missing? I think it would be nice to know what it is but I don't understand a need to know. Thanks.

No, not for mixing.

One of the reasons other DAWs report latency numbers is that certain other DAWs didn't use to have PDC, requiring the user to figure how much compensation was needed. Cakewalk was among first to make PDC a standard feature on an affordable DAW, instead of a premium feature you paid extra for.

 

  • Like 3
  • Thanks 1
  • Sad 1

Share this post


Link to post
Share on other sites
10 hours ago, bitflipper said:

No, not for mixing.

One of the reasons other DAWs report latency numbers is that certain other DAWs didn't use to have PDC, requiring the user to figure how much compensation was needed. Cakewalk was among first to make PDC a standard feature on an affordable DAW, instead of a premium feature you paid extra for.

 

Bingo! Thanks for the refresher. That's what I was thinking. Cakewalk was the first, or near the first, for so many important features and functions!

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×
×
  • Create New...