I am just as interested as you in making sure that the correct information is reflected on a forum like this.
Can we please get past the inference that I do not understand the concept of various plugin formats, latency etc., and that I do not know how to read. The majority of people who frequent these forums generally have a decent level of knowledge on the topics involved.
In terms of the UAD-1 plugins being VST plugins using a wrapper, the delay is due to the large amount of processing latency on hardware-based plugins...not the fact that it is a wrapper. The wrapper is not exactly a CPU hog.
Quote: |
FXpansion claim that the adaptor code uses next to no CPU power, so the plug-ins should be nearly as efficient as in a native VST host like Cubase
|
Quote: |
What is latency, and how does Pro Tools deal with latency? Latency occurs on a UAD-1 plugin because the audio travels from the application to the UAD-1 card and back. Pro Tools HD has plug-in delay compensation (PDC), and this takes care of the latency.
|
Also, when Nuendo/Cubase refer to having full plugin latency compensation, they are referring to any plugin that is compatible with the system (VST or DX, VST<->DX wrappers, ). You don't have to preface it with "it works, except for when.... or as long as you don't exceed the buffer..., or unless you are using 3rd party hardware FX cards you will have full delay compensation...". I have never seen any reference to "full plugin delay compensation" not being exactly what is says it is.
RTAS is proprietary, so FXpansion had to pay for access to the plugin specification. I can't see a reason that they could not have implemented a function to transfer the reported VST plugin latency through to Pro Tools LE (unless Digidesign wouldn't allow it) .
Quote: |
There is the problem of latency in these systems which Pro Tools can't adjust for automatically, but it can at least report the delay time (as with TDM plug-ins), allowing you to nudge audio to compensate.
|
There is a version of the FXpansion adapter that is "optimized" for the UAD-1, so it is fully compatible. They do not say..."PTLE does not have PDC for VST wrappers"....they say "PTLE does not have Plugin Delay Compensation".
Quote: |
Does it add any latency? Not of itself - it's the same as regular RTAS plug-ins in that regard. Certain VST plug-ins, especially those running on DSP cards, do add latency. Pro Tools TDM/HD automatically compensates for this latency ("Automatic PDC"); Pro Tools LE and M-Powered do not. However, you can easily view the total latency in the Pro Tools mixer and compensate for it manually.
|
They also do not say that "Protools will compensate for the delay so long as the buffer size is large enough to cover the delay"...they say "always use our handy delay compensation plugin because "PTLE does not have Plugin Delay Compensation".
I find the "PDC is a given" argument a little hard to swallow as most DAW makers are so competitive with their feature lists these days that they list even the most insignificant ones, but hey you never know...
I have repeatedly pointed you to several sources that have stated that Pro Tools does not have full plugin delay compensation like other DAWs. I'm still waiting for another source from you, other than yourself, to support your claim. If Digidesign doesn't want to market the fact that they have it, they would at least have a support document somewhere stating that they do. Please give me a link.
This is Digi's tech support response from a DUC thread:
Quote: |
Just want to make sure this is clear.. Pro Tools LE DOES compensate for host-based plug-ins using the CPU for processing by way of the HW buffer. That point seemed to be getting muddled in the disucssion of latencies introduced by 3rd-party hardware accelerators (which are not compensated for as noted above).
|
http://duc.digidesign.com/showflat.php?Cat=&Number=85903 2&page=&view=&sb=5&o=&vc=1
There was no response that I could find to a question about host-based plugins that exceed the buffer limitation.
From the PT7 Ref Guide:
Quote: |
Delay that Exceeds the Compensation Limit
When the total delay on a track exceeds the amount of compensation available, Pro Tools applies the maximum available compensation, and displays the delay information in red (in the Delay Compensation View) for any tracks that cannot be fully compensated. The Delay Compensation indicator in the Edit window also turns red to indicate that the track delay exceeds the Delay Compensation limit. In this case, you need to bypass the track’s reported delay
|
There doesn't seem to be any reference to..or need for, a similar function in SX3 that I can find.
So the question is.....
Does PTLE implement PDC in a way that is different than other Native DAWs, and therefore is limited by the buffer, and cannot claim
full PDC support?
If you can prove that the delay compensation in Pro Tools LE is implemented in the same fashion as other DAWs, and that they will all "fail" at some point due to a similar audio buffer issue, then we will all be grateful. I have yet to read or personally experience a delay compensation problem with SX3, no matter how many (or what type) of plugins I use.
AS many potential PTLE customers will be looking at options like the UAD-1 and Powercore to create a "Poor Man's PTHD system", I think that it is reasonable to point out that PTLE does not compensate for delays with these products.
Also, in case I skimmed over it, please explain the different implementations of PDC in PTLE and PTHD. It's in LE but you just can't enable and disable it. Could you see some potential problems with this scenario?
From the PT7 Plugins Guide:
Quote: |
The TDM version of Maxim introduces 1028 samples of delay at 48 kHz into any processed signal. The RTAS version of Maxim introduces 1024 samples of delay. These delays will increase proportionally at higher sample rates. To preserve phase synchronicity between multiple audio sources when Maxim is only applied to one of these sources, use Delay Compensation (Pro Tools 6.4 and higher only), or the DigiRack Time Adjuster plug-in to compensate.
|
Is PDC already on (because you can't switch it on in LE). Or if it exceeds your buffer size, do you use the time adjuster plugin for this in PTLE?
Personally I like the SX3 concept of having full PDC on all the time (that you don't even have to think about), and only hitting the Constrain Delay (PDC off) button if I need to when recording.
Hopefully some of the of the more "techy programmer" types will read this and will shed some light on this.
Please let me know what you find out in your experiment.
JL