VST clock sync

Apr 11, 2013 at 7:25pm

VST clock sync

Hey all,

The last topic I could find related to mine is 5 years old. Is it yet possible to send clock information to a vst~ object for beat-dependent delays, etc.? The vst~ documentation does not say.

#67667
Apr 15, 2013 at 11:44am

You have to include a transport object in your patch, and turn the transport on. That will automagically make your plugins hosted within vst~ sync to the same tempo specified by the transport object.

#243452
May 25, 2013 at 1:42am

What about named [transport] object. As I know Max may have more ‘timing streams’ at once. Is any option to relate timing from named [transport] to particular [vst~] object. Global transport extra in just a patch with unnamed instance of [transport]. Any clues?

#250648
May 25, 2013 at 10:08pm

That’s an interesting question. It would be cool if [vst~] had an @transport argument.
I don’t have access to multiple tempo-sensitive vst plugins now but I guess that [vst~] will not reliably synchronize to any particular [transport] if there’s more than one active.
One workaround might be to not use [transport] but instead send MIDI ticks direct into [vst~]. I am also not sure how [vst~] parses time–is it at the standard MIDI 24 ticks/beat or the Max 480 ppq or something else?
The patch here takes a BPM, translates it to MS per tick @ 24 ticks/beat, then sends “248″ (the MIDI “tick” 11111000) at that rate. I don’t know if that will work though.

– Pasted Max Patch, click to expand. –
#250691
May 26, 2013 at 10:33am

Oops. put the Real-Time stop message in the wrong place. Should be here:

– Pasted Max Patch, click to expand. –
#250719
May 26, 2013 at 3:05pm

I’ve tried this before and the main problem is that [vst~] need midievent with at last two arguments. RealTime MIDI Msgs are without arguments. It does not working neither if I send midievent with 2 args (the second 0 or whatever). Timing in [vst~] is a little out of control. The good plugin to test is TAL-FilterII (Togu Audio Line) its envelope driven filter and is free.
Adding @transport to [vst~] will be nice :)

#250746
May 26, 2013 at 3:58pm

Yes. Posting feature request.

#250751
May 26, 2013 at 5:56pm

> Timing in [vst~] is a little out of control.

What exactly do you mean, inaccuracy (jitter) or latency?

#250758
May 27, 2013 at 10:10pm

Neither. Just that I can’t use MIDI Real Time messages and rely on global transport. I did not tested time synced [vst~] for phase/jitter/latency problems since I’m interested in being “out of sync” :-).

BTW: 32Bit’s question about the internal timing resolution of plugin and it’s host [vst~] is important too. Does [vst~] take tempo value from [transport] and send it to plugin or just send real time msgs in right intervals?

#250877

You must be logged in to reply to this topic.