Midi Bus
under review
Nickstomp
I want to be able to create a midi bus and have the possibility to redirect the out of plugins and of buttons to it and from then send it to midi destinations
For example currently in my template I have 8 buttons that sends note messages to digistix
If I want to change the destination to another plugin I have to edit my template and change it to another plugin (16 times)
Would be easier to have a midi bus in my project and send the output of the buttons to that bus and from the buss then add midi plugins into it so I can quickly switch between multiple applications fire example
Anthony Westbrook
I made entire keyboards in the DCompose layout (what the Striso uses). It’s an incredibly space efficient layout. I wanted to be able to switch between audio units, but currently I can only pick one, then (thankfully) I can change presets within that one unit. I would love to share my keyboard layouts with the community, but I don’t think anyone’s going to just give it a try when they’d have to change the destination of 48+ buttons.
To be clear, MIDI bus is one solution to this. If a better solution exists, it has my vote.
F
Forest
also ran into this problem and fully agree.
E
Eric Raymond
Would this be an abstraction for midi outputs that serves a role similar to what Control Groups do for midi inputs?
Catherder
Please implement this soon. This functionality is essential for a quick and easy MIDI configuration, or when you want to share projects. And it should not be too complicated to implement. My suggestion would be a very simple one: Let's have a dummy MIDI interface (or call it "MIDI thru") that can be used for a MIDI track or as destination from other MIDI tracks.
ultracello
under review