- Type
- Audio Effect
- Author
- h1data
- Version
- 1.2.0
- License
- None
- Live version
- 11.0.5
- Max version
- 8.1.11
- Downloads
- 3,316
- Updated
- 2024-12-03
Description
Routing MIDI I/O in audio tracks for audio effect devices or plugins which have MIDI input.
Changes in version 1.2.0 (November 29, 2024)
- Added `Route Here` button to route the track where the device belongs.
Changes in version 1.1.0 (May 19, 2022)
- Added "Send" button to switch if the device sends MIDI messages to the selected output.
- Added LED indicators to monitor incoming/outgoing MIDI messages.
Comments (35)
thx for the device.
Btw, your latest device is superb!
I have just made a simple enveloper for my own demand, but no need to make a complex one. :)
I hope more devices which have extra audio/midi I/O would come.
Why do such thing you ask ? Well because that's how Serum works when it comes to changing current preset using CC :)
The other "native" alternative was to allow track to listen MIDI from "All Ins" but I found that quite dangerous
I don't have Serum, but I swear you can add MIDI input of external devices to VSTi with empty MIDI tracks.
However, this device can route without extra tracks. :)
I put 2 on a midi track and route to 2 other tracks (to plugins that are controlled by midi). The device keeps routing the midi to both tracks, even if I turn the device off. Also, it can trigger the track that it's not assigned to (while the other instance assigned to that track is turned off).
Does anyone else have this problem?
Confirmed the device routes MIDI messages when the device is inactive.
I tried to stop routing while the device is disabled, however,
the inactive device seems to pass through MIDI messages like THRU.
It is necessary to coordinate with Ableton or C74 to fix this issue.
In old school way, you can use MIDI tracks without instruments;
that never output MIDI messages while inactive.
Thanks for your feedback!
Imagine deactivating an effect device in a normal MIDI/audio chain,
the device does send messages or audio signals to the next device in the chain.
To stop sending messages to routed output, I added a button instead of disabling the device.
@aiotea, I'm glad if I hear it works.
I wish I could accept CC from other tracks but I'm unable to do that.
Is this a limitation of Live itself?
I swear the device can route CC messages too. (confirmed on Win and Mac)
Could you explain the situation you have?
From/To audio/MIDI track, external controllers, or MIDI effect, etc.
The best way is to share your sample Live set somehow.
Is there a version of this that can send midi to multiple sources? Say if you use midi triggered sidechain within a plugin and you don't want to have to have an instance of this per sidechain plugin
Tom
Tom
Sorry but an M4L device can have only one pair of MIDI I/O,
thus you have to put multiple instances for routing to multi plugins.
I checked in grouped MIDI/Audio tracks but could not reproduce the situation.
A possible problem is routing to other tracks of the same group may cause a loop.
https://www.ableton.com/ja/release-notes/live-11/
Very usefull device.
It could be great to have the same in midi device (for routing in midi effect rack for example)
Sorry but MIDI I/O in MIDI effect devices are not routable since they are fixed to Live.
I think it makes sense if this device can be put in MIDI effect racks.
Than you for your response.
You mean that this device can only be a max audio effect and not be a max midi effect ?
It may be useful if there are multiple I/O and some mappable switches?
Thanks for your feedback.
I'm sure you can route from Post Fx of a MIDI effect by this device;
choose a track from upper pull-down menu then you can find Pre FX or Post FX of MIDI effect in the 2nd pull-down menu.
Well, I might take your question in the wrong way.
If you want a MIDI Effect M4L like this device,
it is not possible as mentioned on 'December 03 2022' above.
Thanks for your feedback!
If you choose 'Post Fx' of the track you place MIDI router itself, it makes an infinite loop and would not work.
Thus you should select 'Pre Fx' if you select the track where MIDI router belongs.
And yes, I should have added 'here' button, but I cannot remember what inhibited it.
Stay tuned!
Unfortunately, the midi routing disappear when I transfer the project to Push 3 standalone, and currently there is no way to route from standalone.
The only option that appears is "Send On/OFF'
.
Is it possible to add routing options when used in Push 3 Standalone mode? Sincerely Thanks
Sorry to say, but this device has no compatibility with Push 3 Standalone.
This device uses a non-standard way for routing and it might prevent it from working in Push.
M4L devices have limitations in Push 3 according to the article below.
https://help.ableton.com/hc/en-us/articles/8506527153308-Push-standalone-Max-for-Live-Device-Compatibility
I remember it worked at the release of Push 3 but features like I/O routing and parameter mappings
are no longer available while updating. (maybe around the release of Live 12)
Alternatively, you can route MIDI I/O with empty (no instruments) MIDI tracks.
This device provides the feature without extra tracks.
Love the device. Used it to solve a midi routing issue that a few people were looking to solve (https://forum.ableton.com/viewtopic.php?t=234735#p1829907)
I did run into one minor issue. If I create an instrument rack with your MidiRouter present in each chain, and then I save out the instrument rack as a preset, when I load the preset back in the' Midi To' values in the MidiRouter get reset back to 'none'. Is this is a limitation of the process, or is there some way you can think of that the Midi Out values can be saved/loaded as part of the preset?
Thanks!!
For example, i have Cthulhu first, then MIDI router, then Serum hosted inside Patchwork audio (not synth) plugin, so i can trigger Serum from Cthulhu's arp. This means i can freeze the track, which wouldn't be possible with a seperate track for the arp. Many thanks!
Also, Push 3 would play the track if it's okay to freeze.
I am so sorry for skipping your comment.
I swear I check every notification from maxforlive.com,
but sometimes new comments are not shown on the page when I receive the mail...
Also, I thank you for sharing this device in the forum. :)
The routing selections of track/channel would not be saved in presets of racks.
Those are not saved as usual parameters but as routing info of the MIDIRouter itself
because the lists of tracks/channels are changed dynamically.
The selection could be outside of racks such as other tracks or
external MIDI equipment, therefore It would be only saved within Live sets.
For 'MIDI From', we can decide the specific input because there is only one input for a track (PreFx).
For 'MIDI To', however, there are multiple options:
- the input of the track (when a MIDI track) (your request)
- an instrument such as Serum (one of the most standard cases I assume)
- the output of the track (when it's a MIDI track and has no instrument)
- one of the audio effect VSTs with MIDI input. (the original demand for myself)
I want to hear other use cases and opinions from users here.
I don't know much about Multipass and other plugins, however,
I assume 'Route Here' for 'MIDI To' would route to the instrument on the MIDI track for your case.
In addition to the post on May 27 2025, if you use an Instrument Rack for multiple instruments,
it would be harder to predict where to route.
Again, the device cannot route to multiple outputs.
This is a limitation of Max for Live devices.