Hi there,
Just wanted to ask when it will be possible to add multiple MIDI Clock destinations.
Because there is only one destination that can be set, I needed to buy the CME H4MIDI WC to be able to have it for my synths and other gear. However, this is not the best workaround.
This should be one of the top features that you can select multiple MIDI clock destinations on a system like this (as it does on DAWs, MainStage, Cantabile, Camelot).
When will you release it for VST Live?
For others: Why do you need this? - seriously I was asked this today. I know - but better from you as well.
There are lots of sources in the internet, like on Wikipedia explaining what MIDI (beat) Clock does MIDI beat clock - Wikipedia
Mainly it’s needed to keep Arpeggiators, LFO tempo, Delays etc. in sync.
Hi @Matze_Keys ,
We (@CliveJ and me) know what MIDI clock does , the only question why do you need it for multiple destinations? 
One destination for a midi interface that has 5 pin midi out that will daisy chain to the pedals, keyboards etc, and another for the lights software (EMU) that outputs synced DMX to the fixtures through a usb interface without 5 pin midi.
Why don’t you ? 
I have mentioned it already in my thread start. Anyway, I will answer it more precisely.
It is needed to have VST Live as MIDI Clock Source (Master) and need to provide this to my external synths + other gear (Kemper, Delay etc.) as Slaves (destination).
However, it is not satisfying using Midi Thru or something because of the following reasons:
I want to use MIDI clock from VST Live. I would need to use MIDI 3 - BUT in this case only the external sources gets the clock, not the Montage.
When I set MIDI 1 - the Montage gets it, but not the external synths.
There are 2 Kempers that are connected to MIDI via Ch1 and Ch2 on MONTAGE M MIDI 3 - but works only when I use the MIDI via USB in the Montage. I can give program changes, CC and so on via this interface
Nord Lead A1 only has MIDI In/Out - no thru - only soft thru - and this provides only one MIDI channel, which is not enough.
In Cubase I use the Project Synchronisation Setup, and this works fantastic
As a workaround you can use Virtual MIDI. Set MIDI Clock Output in preferences to a Virtual MIDI port. And then create global layers for every MIDI Output with this Virtual MIDI as Input.
As a workaround you can use Virtual MIDI. Set MIDI Clock Output in preferences to a Virtual MIDI port. And then create global layers for every MIDI Output with this Virtual MIDI as Input.
This idea sounded really good to me! And I immediately tried it - would be a great workaround. However, unfortunately it doesn’t work. Only one device receives the MIDI Clock 
I have set the Global layers to VM 3:
unblocked Clock on both layers:
But only one works.
The second layer have input vm in 3 on channel 11, try setting it to channel 1 like the first lauyer (output channel where you need it if it’11)
Does it matter? I thought MIDI clock was channel agnostic. But then again….
I could not test it, as I have only one MIDI port. But I would suggest to keep channel to “any” on in- and output.
This has been discussed two years ago…
Unfortunately, the workaround is not useable as only one destination receives the MIDI clock (the first layer which uses the VM port).
I suppose there are many users who need this feature.
@Falfango @CliveJ @ciro1983811 Changed to Any, but only works on the first layer (or when this device is not available, the next layer which uses the VM port). Same with using the same channel on both layers.
