They will come back in sync after one play/stop cycle. DP of course cannot update its latency compensation during playback. If you play both instruments live - they will not be delay compensated of course. Only for playback tracks.
-
hmmm...starting and stopping doesn't make any difference, same drift. Outside of the latency compensation box in DP is there something else that I need to do?
-
I am not a DP guy, but if DP does not listen to the proper AU events, it might be that it cannot update latency compensation in realtime. A re-instantiation of the plugin, or reset of the audio engine might be needed. Most proper sequencers have the ability to update this information in realtime, like Logic, Cubase, Nuendo...
-
-
I spoke with MOTU and they said that as long as the latency compensation is working internally with DP than it shouldn't be anything on their side.
I loaded identical patches into 4 instances of K3, one loaded in DP, 1 in Bidule (in rewire mode) and 2 loaded into 2 different VE PRO instances with buffer settings of 0 and 2X. The internal and the Bidule tracks play back tightly synced but when compared to the K3 instance in DP, the VE PRO instances are both out of sync, the effect with the 0 buffer instance is slight but noticeable and the difference with the 2X buffer instance is very noticeable. If I put DP into multi-record and enable the MIDI tracks for the internal DP instance and both of the VE PRO instances, the latency is identical whether it is triggered from my keyboard or played back in DP after several start/stop cycles.
-
I though the thread title was referring to latency compensation, I'll start a new one.