Feature Request(?): MIDI Clock & MMC support in Standalone mode

Post Reply
Koshdukai
Posts: 6
Joined: Sat Jan 19, 2019 12:34 am

Sat Jan 19, 2019 12:50 am

I'm trying VM as standalone and it doesn't seem to be "listening" to any of the MIDI input ports regarding MIDI Clock and/or MMC msgs/cmds.

Can't find any dedicated MIDI Clock port input setting nor something that would allow me to set which port to listen to MIDI Clock as source.
Also looked for MIDI->Sync Utility modules but there's no such thing either, so...

Is this (still) not supported or am I forgetting something?

Obviously, I've used the Transport's Sync out -> Sync Divider -> Drum Trigger Sequencer's Clock In with EXT on, as a test and it works but ignores any external MIDI Clock source(s) I throw at it.
I think it's also ignoring MMC Play/Stop commands.

Basically, my issue is: How do I (clock) sync (slave) Voltage Modular (in Standalone mode) with other devices ?


PS: ...and could we please have the "Active MIDI inputs" section a bit taller please? When having *A LOT* of devices/ports, it's kind of a pain to go through them in a 2 line height based list :/

Thank you ^_^
Cherry Dan
Site Admin
Posts: 84
Joined: Fri Jul 27, 2018 5:36 pm

Fri Jan 25, 2019 2:02 am

Koshdukai wrote:
Sat Jan 19, 2019 12:50 am
Obviously, I've used the Transport's Sync out -> Sync Divider -> Drum Trigger Sequencer's Clock In with EXT on, as a test and it works but ignores any external MIDI Clock source(s) I throw at it.
I think it's also ignoring MMC Play/Stop commands.
A MIDI Clock to Sync module is a very good idea, we'll definitely consider that.

You should be able to map MMC commands to control anything you'd like. Just select the MIDI tab, click "MIDI Learn", press the sequencer Play button, and send an MMC Play command to Voltage Modular. It should map the MIDI MMC command to the Play button of your sequencer. There are no "automatic" mappings in VM, as you may have many sequencers going in a single patch, and only want certain ones to respond.

Thanks,
Dan
Koshdukai
Posts: 6
Joined: Sat Jan 19, 2019 12:34 am

Sat Feb 02, 2019 9:21 pm

Cherry Dan wrote:
Fri Jan 25, 2019 2:02 am
Koshdukai wrote:
Sat Jan 19, 2019 12:50 am
Obviously, I've used the Transport's Sync out -> Sync Divider -> Drum Trigger Sequencer's Clock In with EXT on, as a test and it works but ignores any external MIDI Clock source(s) I throw at it.
I think it's also ignoring MMC Play/Stop commands.
A MIDI Clock to Sync module is a very good idea, we'll definitely consider that.

You should be able to map MMC commands to control anything you'd like. Just select the MIDI tab, click "MIDI Learn", press the sequencer Play button, and send an MMC Play command to Voltage Modular. It should map the MIDI MMC command to the Play button of your sequencer. There are no "automatic" mappings in VM, as you may have many sequencers going in a single patch, and only want certain ones to respond.
A MIDI Clock to Sync module would be useful and nice to have, when dealing with multiple Clock sources, but proper MIDI Clock (+MMC!) support through the main Transport when VM is in Standalone is (IMHO) obviously expected to work, just like it works when inside a DAW.

It doesn't make any sense (IMHO) to have a "dead" main Transport: Play, Stop and a useless static internal Sync Out when running VM in Standalone mode.
I thought VM would behave like many MIDI Clock+MMC aware hardware (Drum machines, Sequencers, etc) when in Standalone, "listening" to incoming MIDI Clock (if present), just like it does when "inside" a DAW, "listening" to the DAW's own Play/Stop and Sync signals.

Also, when trying to MIDI Learn a Sequencer Start or Stop button while having MIDI Clock msgs incoming, it'll learn either a mixed SysEx phrase (Song position + Start, for example) or it'll simply map itself to F8, so... not a usable solution... meaning, Universal Real Time SysEx messages may need to be ignored when using MIDI Learn, I think.
Post Reply