Latency of Cakewalk Plugs

When I buy plugs for use with Sonar I try and find out what the latency will be. I have no idea what kind of latency Sonar's plugs have and I'm wondering if anyone else knows. I love the way Waves posts those specs, so maybe this will be a feature request.
 
Do Pro Channel modules have zero latency?

There are occasional posts about Cakewalk-included plugins and which ones add enough latency to be unable to be effectively used during tracking, but I have never seen a complete list in any of those.
 
I guess I would look at descriptions of each suspect plugin in the Sonar documentation, and  then I also have a general sense that plugins that are in the Convoluted Reverb category likely add too much latency for use in tracking, just by the nature of what they do in their processing for the effect.
 
Many 3rd-party plugins post latency values on their websites, and that really helps.  I am shortly going to embark on several large-scale projects, and one of my by-products from that will be that I will start and retain a Word document that lists each of my plugins by category, vendor, name, description, and notes, with some sort of marking/note to indicate which ones are not to be used during tracking.  If and when I get enough of that finished, I will likely publish it here in the forums, for others to copy/paste into their own lists.
 
Bob Bone
 

In your quest for identifying latencies, be aware that many plugins have variable latency, a category that includes those most notorious for long latencies. Remember that what causes latency in a plugin is buffering. If a plugin offers a buffer size option then there is no single number that represents that plugin's latency. If an equalizer offers a choice between minimum phase and linear phase operation, then it, too, has no single latency number. Plugins with multiple modules (e.g. Ozone) will have variable latency depending on which modules are enabled. 
 
Latencies can be measured, IIRC, by Christian Budde's VST Analyzer. If you're not familiar with that tool, google it - it's a free download. Unfortunately, VST Analyzer could not load 64-bit plugins last time I checked. However, if you have the 32-bit version of a plugin available, even if it's not registered in SONAR, you can test that instead and whatever latency you measure for it will be the same as for the 64-bit version.

I was aware that all plugs have some sort of overhead. What fascinates me is that Waves lists the latency by platform and recording frequency plus some plugs have less latency when recording at 96k than 44k or 48k. That's got me wondering if ALL plugs have less latency at 96k. So far it's not consistent.
 
I'm shopping for a Quad Curve replacement and want something very similar. THe Waves H-EQ is very similar to the Quad Curve but has some latency at 48K recording. I only use multi-band plugs and limiters for mixing. Same for reverb.

Right ... it's also sometimes a factor in making a mix, without the FX, whatever it is, the sound isn't right, and it is extremely difficult to imagine a future improvement while working without it. 

I have more than a few songs done on a multi and then imported into Sonar. I have one of those songs re-recorded from scratch in Sonar. I can't do much with his imported stuff, it's already got the effects. At least in Sonar, it goes in dry and I can tune sims all day long til I find THE one! And Nectar works best on a dry vocal so far as well. I am glad the little 2i2 has no latency issues at all. He can hear what he needs to, and I get a nice dry signal to work with!

ampfixer
I was aware that all plugs have some sort of overhead. What fascinates me is that Waves lists the latency by platform and recording frequency plus some plugs have less latency when recording at 96k than 44k or 48k. That's got me wondering if ALL plugs have less latency at 96k. So far it's not consistent.
 

Computers do not think of buffers as time/delay/latency they think of buffers as a number of bytes of data that is stored prior to being processed. If a buffer is a certain size (bytes) then whenever you fill it with more data delivered at a higher number of bytes/second it will fill in a shorter time. The  effect of this is that if a plugin has a fixed size buffer and you use a higher sample rate the delay caused by that buffer in msec will be shorter. A given buffer will fill at 44.1K in about twice (96/44.1=2.17687) the time it will fill at 96K, introducing a latency of about half as long (time) at 96K as at 44.1K. Some programs may be designed so that they have buffers that vary in size depending on the demand, and there are other factors aside from buffer size that introduce delays, so observing such a simple relationship for all plugins is not likely.

ampfixer
I was aware that all plugs have some sort of overhead.

 
However keep in mind that "overhead" is not the same as latency. It is perfectly possible for a plugin to use a lot of CPU but have zero latency. Or to use almost no CPU but add a lot of latency.