Robin Koek

I have noticed that once one makes a midi mapping in the Max editor window in a Max4Live device using the midi learn functionality introduced in Max 8, that after saving the device and running it in Live the mapping is gone, it seems to clash with the midi management/storage of the DAW. Is there a way of preserving the mapping or is the only work-around to add the specific control/input to the gui of the M4L device and map while running in Ableton?

Secondly I tried to work around this with a [ctlin] in conjunction with a [midiinfo] which receives a 'controllers' message listing all midi ctl inputs. While this is working perfectly inside Max listing the device I am looking for, allowing me to restrict the input of the ctlin object to this physical input device, once running inside Ableton Live, the midiinfo does not display the full list of midi control inputs once triggered but only the device name of the M4L instrument itself is listed as ports. Is there a way to still get the whole overview of connected midi devices while running inside a Max4Live device? And secondly is it possible to restrict a ctlin object to specific midi device while running inside an M4L? As currently it is a-specific so it is just responding to any cc message on the midi channel, including cc automation in clips etc, which conflicts with the controller messages.

Any work-arounds would be appreciated and illuminating insights in this matter of midi architecture traversing between Max and Max4Live.

Secondly I tried to work around this with a [ctlin] in conjunction with a [midiinfo] which receives a 'controllers' message listing all midi ctl inputs. While this is working perfectly inside Max listing the device I am looking for, allowing me to restrict the input of the ctlin object to this physical input device, once running inside Ableton Live, the midiinfo does not display the full list of midi control inputs once triggered but only the device name of the M4L instrument itself is listed as ports. Is there a way to still get the whole overview of connected midi devices while running inside a Max4Live device? And secondly is it possible to restrict a ctlin object to specific midi device while running inside an M4L? As currently it is a-specific so it is just responding to any cc message on the midi channel, including cc automation in clips etc, which conflicts with the controller messages.

 Any work-arounds would be appreciated and illuminating insights in this matter of midi architecture traversing between Max and Max4Live.

Dear all,
a two-folded question. 
I have noticed that once one makes a midi mapping in the Max editor window in a Max4Live device using the 

preserve-midi-mapping-restrict-midi-input-in-m4l

For anyone stumbling on this topic in the future. I have found a solution myself and would like to share it:

David Butler has developed a set of externals under the name of [imp.midi] which target exactly the limitation described above and extend existing midi input objects to list all ports available even while running as a M4L device.

https://www.theimpersonalstereo.com/max-externals

Yeah this is the only solution since M4l doesn't support referencing midi ports. The only ports that are available in m4l device are the the ones of the specific track that the device is loaded in.

Beware though that imp.midi needs to be tackled in order to work with the max native midi objects or else it gives errors in the midi out. For example you can't use the midiparse object directly.

Yeah this is the only solution since M4l doesn't support referencing midi ports. The only ports that are available in m4l device are the the ones of the specific track that the device is loaded in.
Beware though that imp.midi needs to be tackled in order to work with the max native midi objects or else it gives errors in the midi out. For example you can't use the midiparse object directly.

Preserve midi mapping / restrict midi input in M4L