First of all, thank you for your incredible work on Overbridge! It’s an amazing tool that allows for deep integration with DAWs and external software.
Currently, Overbridge provides access to a wide range of MIDI data, such as velocity changes and trigger presses, filters-amps-fx changes in real-time. However, I’ve noticed that sequencer data is not transmitted via MIDI.
For example, if I manually press a trigger, Overbridge sends the corresponding MIDI data, including velocity. But if I place triggers within the sequencer and play the sequence back, this data does not appear in the MIDI stream. This means that external software, such as TouchDesigner, cannot access crucial sequencer-triggered events, which are essential for audio-reactive visuals and automation.
Would it be possible to include sequencer-triggered MIDI data in Overbridge’s output? This would significantly enhance its integration with visual and generative systems like TouchDesigner.
The elektron sequencer does not output midi for audio tracks so unfortunately overbridge is not the culprit. To my understanding, button presses and knob turning are interpreted as a controller behavior.
I believe that the workaround is to copy your track data to a midi track and send the midi track out to the external device. I think what you’re requesting is a great idea, but I suspect an update to overbridge will not update the behavior, if I’m understanding you correctly.
Yes, it will use a midi track if you have to work around the behavior, but that’s what they’re there for is so that you can use them if you choose to.
If that’s not what you’re trying to do though, you can always subimit an overbridge or other feature request to elektron directly to feature-request@elektron.se
Thanks for your reply! Yes, you understood me correctly, and I just discovered that MIDI machines do transmit this information.
However, it would be really great if audio tracks could also send this data. In a live performance, this limitation can create some confusion, and there’s a risk of accidentally disabling the wrong track.
I’ll try reaching out to the developers via email as well—big thanks for the recommendation