Midi clock in stand alone mode

[AndreasFranke]

Fun fact. Try to get VST plugins inside of a Plugin Host module in sync to anything inside of the standalone. Will not work at all, because they only can sync to the global tempo which is given by the standalone it self and this can not be synced from any external source.

What VM clock you are trying to use and what parameter you are trying to in the VST Host? I have just started to test using the VM Arpeggiator clock routed to the DCO-106's Arpeggiator Sync parameter [vst3 version]. The DCO-106's arpeggiator seems to be responding to the VM Arpeggiator's clock, but I haven't yet wired in a second source directly to the VM Arpeggiator.

That doesn't work because it just seems to be modulating the rate of the DCO-106's internal arpeggiator.

VM Standalone running on a notebook should be synced to a Midi clock from another computer. Setting up a MIDI-In and MIDI-Clock Divider like described above works fine with all VM modules you like to sync with it. But if you maybe want to host some special VST inside a VST-Host module, that also has to be in sync (Delay, a special VST sequencer module, whatever you can imagine for this case), it can't be synced to the MIDI-In/MIDI-Clock Divider setup. Instead of this, the VST will always be synced to the fixed tempo of the standalone application.

A simple example:
External timing send via MIDI-Clock is 80 bpm, the global tempo of the standalone is 120 by default. You have added a sequencer module to the MIDI-In/MIDI-Clock Divider combo like described above in this thread. Now the sequencer runs at 80 bpm as you expected. Now add a VST delay into the VST Host, set it up to run in sync to the standalone, voila it will run at 120 bpm, not 80 as wanted and it also will not sync to a send MIDI-Clock if you send one into the VST-Host MIDI-In connector.