Is there a way, in Sonar, to see the delay compensation value (in # of samples) that is going on "under the hood" with Sonar's PDC?

I believe the plugin itself determines how much compensation is needed and reports it to Sonar and then Sonar uses this to provide necessary compensation. Sonar does not specifically have a way of showing this to the user. However, many manuals or help files for plugins may have a note about latency in them. Some plugins (like PerfectSpace) have there own latency settings so you could look at this also. Any plugin with a "look ahead" parameter is also giving you an idea of how much latency is introduced also since looking ahead means delaying processing that needs to be compensated for.

I have a related question. I have, on occaision, had Ozone 3 on my Master bus FX, while tracking. The reason for this is I had already progressed to the stage of mixing but still needed to bring in a few more finishing tracks, change-up some leads, etc. (and in this case using the Ozone limiter while mixing). I seem to recall that Ozone's default PDC setting does not match its actual insertion delay. It occurs to me that this could foul-up the timing tightness for those tracks added while Ozone is inserted on the playback. Has anyone run into this? Any good solutions, other than deleting Ozone from the Master bus? Anyone had consistant success getting the Ozone PDC value set so that the loopback timing alignment behaves properly?

Oops. Accidental post.