just to add..
It's not working 100% here.. but at a low enough buffer, it works decently..
At a higher buffer, it's unusable..
~J
189,693 users have contributed to 42,668 threads and 256,812 posts.
In the past 24 hours, we have 1 new thread(s), 4 new post(s) and 48 new user(s).
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!
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.