As I wrote earlier, VEP reports latency properly to the sequencer. It does however rely upon the host sequencer being able to adjust the latency compensation of plugins dynamically. It might simply be that DP lacks this feature.
-
Hello Martin. By "dynamically" do you mean prior to, or during playback? Or are you talking about 'per instantiation' ? Perhaps a specific type of example can help us to follow what you are explaining??? I can say that all the rest of our plugs on our 12 rigs DP have compensated fine the past 3+ years or so, excepting for a bug here or there on a specific plug. And we have tons of plugs, VI's etc. :)
-
-
Hi Martin,
Thanks for getting involved in this. I understand your explanation of the problem. However, I can't help but feeling that this explanation is the equivalent of saying that the software is incompatible. I wouldn't be so critical if this were a minor inconvenience, however I think most musicians would say that having perfect time is not some added luxury feature, but a requirement. I also wouldn't be so critical if I was forewarned about this issue.
Thanks for your attention. I hope this gets resolved with haste.
As a P.S. to DP users: this issue can be alleviated (albeit painstakingly) by adding a MIDI time shift plugin to each MIDI track, and shifting the timing earlier by the correct number of samples. For those of you with hundreds of tracks... have fun with that!
-
Thank you Martin. We have several plugs that I know of, that change their latency to DP depending upon what buttons are toggled within them. And they work as soon as you stop/start DP. And you can have 3 of the same plug in a session with differing settings. That to me, seems like what VEPro does. So I imagine it is quite possible to fix. BTW . can you have someone start monitoring and participating in this thread over at motunation. I think it would help us all out alot. http://www.motunation.com/forum/viewtopic.php?f=26&t=49430&sid=327c9a59dc218f35c893bec1752c8e4d
-
We just did an experiment here with the Vienna Suite Convolution Reverb, which reports latency changes to DP in the exact same way as Vienna Ensemble Pro does. Here, latency compensation is updated and works as it should after a stop/play cycle, just as expected. My suspicion therefore remains, that DP doesn't respond to property change events for kAudioUnitProperty_Latency with AU instruments.
-
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.