Many of us have submitted a tech note to MOTU regarding this. A fellow at MOTU named Lorne said that he will look into it.
-
So then if we leave the VEP server plugin at zero buffers, it should compensate correctly?
I just did a test where I set the VEP plugin latency to zero buffers, but set the MOTU hardware buffer to 1024. I then recorded the audio output of some snare drum hits coming off my slave-- both dry and running through Altiverb. Everything lined up. Changing the buffer setting to anything other than zero is what causes the problem, as Martin is suggesting.
-
At Zero buffers, there is no latency to compensate for!
CPU usage will be a bit higher with 0 latency though, but since the CPU time is yielded back to the scheduler while waiting for data from the VEPro process, the CPU usage is only virtual - adding more plugins in DP should be possible without any noticable increase in total CPU. That being said, processing graph of host of course also comes into play. If plugins and effects are chained after the VEPro plugin, DP has to wait for the VEPro data before continuing with further processing, making this virtual load real :)
-
There is nothing we can do about this unfortunately. DP simply refuses to update the latency of instrument AU's, even though we report the changes properly. MOTU has to implement latency compensation for instrument AU's in DP for this to work as it currently only seems to compensate for effect plugins. I've put a latency display (in samples and ms) on the VE Pro plugin's editor for the next update though, so compensating manually will at least be easier to accomplish until MOTU fixes this.
-
Hello Karel. Thank you for the info. Are you and your team 'directly' in contact with MOTU about this? I suspect you folks are going to have to work together to figure it out. (Our contact there indicates that VSL is the only company with this problem.) I am sure you can get it going if you work together. :)
-
Hi, When do you plan update VEP which this implementation? I was just about swiching to the VEP instead of Bidule mainly couse of that I had to add some many soundshifting plugins for midi tracks which was a horror and now it seems it doesn't work here as well. Would be grateful for info about approximate time of this update. Is day or weeks matter? Thanks.
-
Oops forgot to mention a few posts back... Karel and Martin et al. The "0" latency setting inside VEP idea, wont work when using event input as it adds another buffer. SO yuo dont end up in time then. We have to have the functionality of 'event input' and the fix for the delay comp for our major scores. Thanks again for helping us all get to the bottom of this.
-
-
Hello Martin,
thank you very much for keeping us updated on the progress and for this cool new.
If MOTU keeps up with their NAMM announcement (DP8 in March!) it seems like we're gonna stop dealing with latency inconsistency in a matter of days.
Time for upgrading to VEP5!!! ;-)
Cheers
Arceo
P.S.
Since you got in contact with MOTU, did you two cope with the Event Plugin/No Bounce to Disc issue? Are you (or are you aware if MOTU team is) working on a solution even for this hick up? Thanks again.
-
Karel - will the VEP update help with Logic as well? I'm having the exact same issue and have to manually move my bounced waves every time I render midi to audio within Logic. Thank you for your help
-
Yes plugin latency compensation in Logic is set to ALL. My VEP instances in logic have 2 Buffers. If I turn the VEP buffers off my CPU goes really high.
-