Device Details

makes perfect sense :)

thx for the device.

Thanks for your comment.

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.

Wow! This device is very useful to me for one specific usage: It allows me to root CC messages from any MIDI controller to Serum VSTi.

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

@imacactus Thx for your feedback!
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. :)

This device seems to be broken in Live 11.1...

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?

@aiotea Sorry for the inconvenience.
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!

I realized M4L devices shall bypass messages or audio signals via routing I/O when inactive.
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.

Excellent and works.

I wish I could accept CC from other tracks but I'm unable to do that.

Is this a limitation of Live itself?

@magwa101 Thanks for your comment!

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.

Hi there,

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

Also, this seems to crash Ableton when it's placed in a group!

Tom

@Tom Thanks for your feedback!

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.

@Tom, Ableton have fixed issues around routing that could cause crashes. It may solve to update Live to 11.2.
https://www.ableton.com/ja/release-notes/live-11/

Hello

Very usefull device.
It could be great to have the same in midi device (for routing in midi effect rack for example)

@naerliona, thanks for your feedback!!
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.

Hello
Than you for your response.
You mean that this device can only be a max audio effect and not be a max midi effect ?

@naerliona Exactly, it is a limitation of M4L.

Is there anyway you could make this so I could midi map the input and output to a knob?

Sorry, but it is too complicate to map the selection of list for MIDI I/O or channel (types).
It may be useful if there are multiple I/O and some mappable switches?
Thanks for your feedback.

nvm, I forgot again that a M4L device cannot have multiple MIDI I/O…

is there any way to make similiar device that pulls midi from midi effects? and route to tracks?

@saus
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.

@saus
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.

Hello, thank you for this device! Actually very useful but I might encounter a bug (Win, Live 12). The device works for me only when "MIDI From" is set to "Pre FX". Any idea what's causing this issue? And a little feature request: would it be possible to add a "here" button to route the track where the device belongs (like Audio ADSR)? Thank you.

@distantnoise
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!

Wonderful device, and solves a problem that I have - when used on computer!

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

Thanks for your feedback, Damie!

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.

Hello.

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!!

This is so useful, it lets you have two VST instruments on the same track, with one sending MIDI to the other.

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!

Thanks, MrD, I did not realize the benefit of routing within one track.
Also, Push 3 would play the track if it's okay to freeze.

@zman818
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.