@Marsdy said:
I have a long standing issue with VE Pro latency in Pro Tools. It seems to have persisted in the Apple Silicon Native versions of VE Pro/Pro Tools.
I've been able to lower Pro Tools' buffer quite considerably since moving to Apple Silicon and the performance is super impressive. Similarly, I've been able to lower the buffer setting of the VE Pro AAX plugin to "1 Buffer". This gives me a Pro Tools System Deal of 3.33ms/160 samples
The problem occurs when adding more instances of VE Pro. Adding one particular instance, (my woodwinds with a mixture of Kontakt 7 and Synchron Player,) increases the latency to 14ms/672 Samples. I can't see any difference in this instance, either in the VE Pro plugin or in VE Pro Server compared to the other instances.
Currently there are fiveVE Pro instances in my Pro Tools session and its just this one Woodwinds instance that causes the problem.
Any ideas as to why this is happening?
Hi,
Synchronized versions of Synchron libraries add additional 512 samples of latency because of impulse response reverb. By default, plugin latency compensation is enabled in Vepro settings and additional latency will be reported to Pro Tools and Pro Tools will compensate by adding 512 samples to your base latency. In Vepro server you can see latency on bottom right of the screen (number between tempo and cpu usage).
If you have only one Synchron present with additional latency - whole instance will report latency and your whole ProTools session will compensate.
To test this, open only one instance and one Synchron. Load Big Bang Orchestra 2 - you will se 0 reported latency and ProTools compensate for base latency only. Now load Epic Orchestra 2 / 01 Appassionata strigns and you'll see 512 samples of reported latency and Pro Tools will compensate. Now go to MIX tab of Appassionata strings patch and click small wave icon on Reverb section of the Strings channel and open Edit Impulse Response window. Now click remove on bottom left. Once IR is removed you will see latency drops to 0 and Pro Tools go back to base latency (audio buffer multiplied by selected vepro buffers).
So, all this is completely normal behavior and show that both Vepro and PT are working OK and compensate latency as it should. If extra 512 samplesnof latency is unacceptable for you - there are workarounds (with some downsides) but it's too long to write here...
Hope this helps,
Regards,
Suad