Vienna Symphonic Library Forum
Forum Statistics

204,051 users have contributed to 43,358 threads and 259,683 posts.

In the past 24 hours, we have 8 new thread(s), 22 new post(s) and 53 new user(s).

  • Pro Tools not recognizing correct delay from Vienna plugins

    I'm having an issue that I've never had before, running Pro Tools 2020 and VEP 6 on my MacPro late 2013, 128GB of RAM on Mojave. I recently expanded my template and have lots of instances on my local Vienna template, about 19 instances, (besides the ones on my server). Everything worked fine for a few days, but all of a sudden, every Pro Tools session I opened that used that template was sounding out of sync. After much trial and error, I finally noticed Pro Tools was not recognizing the right amount of delay for some of my Vienna plugins, so delay compensation was compensating some tracks incorrectly. Instead of showing the right amount of delay corresponding to the number of buffers used for each Vienna plugin (none = 0; 1 buffer = 1024; 2 buffers = 2048, etc...) it was only showing 16 samples of delay for some of my plugins, regardless of how many buffers I had selected in them. The only way to get things back in sync is to change the number of buffers for each problematic plugin. I can change to any number, and even go back to the original number, I just have to make a change, then Pro Tools will "wake up" and actually start reading the correct delay from that plugin, although it does still add that 16 to it... so if I change the buffer to none it shows 16 instead of 0, changing to 1 makes it 1040, 2 buffers makes it 2062, etc... so, it's not really the precise delay amount, but at least it makes things playback in sync again. The problem is still annoying though since it happens every time I open a session with that template. The problem is with a few specific instances in Vienna, I tried creating new tracks with new plugins in Pro Tools, or even connecting those same plugins to different instances, it happens every time I connect a plugin in Pro Tools to certain VEP instances and I can't figure out why.

    Anyone ever ran into this? 

    Thanks