I was just wondering how people are transferring pattern data from their DAW+OB setups into the machines? For use on stage this would be great! Especially interested to hear how automation can be transferred to plocks on the patterns.
Naturally there are limits on how complex DAW+OB schemes can be transferred (the data must be translatable to the internal sequencer limits ie. no duplicate time signatures per track etc)
Also, How to do the opposite? ie. I have a pattern on the machine with plocks and I want to export/import it into my DAW+OB?
I hope Elektron is thinking about how to properly implement this facet of overbridge. It would make the circle complete! I would imagine getting the note data to be relatively straightforward, but plocks are such a big part of elektron sequencing that there really should be a way to get that transferred across OB/standalone as well (within limitations of course)
Only way I could get the midi clips from Live to A4 was to use an External Midi set to USB A4 and use the A4 global midi channel. If you set the External Midi to VST (the standard OB setting), it doesn’t work or at least I couldn’t get it to work that way.
BTW, you can still keep the system USB setting to OB only mode for this to work. I thought the A4 USB MIDI got disabled when you choose OB only USB mode but that’s not the case. The A4 USB MIDI is still active.
As far as automation, I haven’t really tried transferring the DAW automation to A4. I’ve been creating clips in Live and just transfer the notes then do the p-locking on the A4.
And going from A4 back to DAW doesn’t work since A4 doesn’t send any MIDI data out.
Yeah, damn, I forgot these boxes do not send MIDI out. So only solution would be for Elektron to introduce a “import syx” feature to the OB system, so that one could import sysex backupped data to the OB plugin, and even this would require manual juggling of midi files on the DAW end
In any case, at least being able to dump pattern data from OB+DAW (within limitations) should be made possible in the future, somehow. MIDI note data is not sufficient, some level of automation transferrability should be possible. Perhaps this could be a project for a skilled M4L patch coder?