Quote:
Originally Posted by
A Fak
β‘οΈ
I agree about the TDM version and needing to set the buffer as low as possible to get a fair comparison but not so with the UAD. The Plugin in question is as equivalent as 2 plugins can be on two different platforms so whether it does or doesnβt upsample is irrelevant because if it does it will on both platforms and if it doesnβt then that would allow the UAD to run more instances because it doesn't need to upsample.
This is absolutely not true. Let's say for instance that you are running both the UAD version and the native version in Logic running at 48KHz. If you load the UAD version, as that plugin upsamples, it will use more dsp than the native version as the native version does not upsample. If the UAD version is doing 4x upsampling, that would be the equivalent to running the native version at 192KHz.
Quote:
Originally Posted by
A Fak
β‘οΈ
But the buffer setting is an interesting though. Correct me if im wrong but really to be equivalent (leaving TDM out) you would have to set the buffer much higher to match what the inherent latency the UAD causes? Iβm not sure what it is but itβs definitely much higher than 32 or 64 samples.
You are confusing the UAD with TDM. If you are running UAD on a native system, it uses the same amount of sample buffer that the host is set to. So, if Logic is set to a buffer of 128, then the UAD plugins have a latency of 128 samples. Using UAD on a TDM is slightly more problematic as apparently UAD has issues with Pro Tools' delay compensation. That's a separate issue.
But my main point on the latency is this. If you are going to compare Pro Tools to Native, you have to take into account the latency. Pro Tools has lower latency than native systems, which means it is running at a buffer < 32 samples. So to do an equivalent comparison between TDM and native, one would have to run the host at a buffer of 32 (the lowest native equivalent) to try and simulate the same dsp usage.