dfwaudio

Hello. I'm new to this forum and hope somebody can help.

It's a question about max4live but i don't know where to post this, if not here, because ableton forum isn't very helpful. (sorry for my english)

I'm reconfiguring my apc40 and also apc40 mkII for a lighting controller/step sequencer for ableton.

One of my major problems is the reinitialization of my patch after midi, key or button mapping in ableton. Maybe somebody know an observer message or something to get a bang after coming back from mapping?

Hello. I'm new to this forum and hope somebody can help.
It's a question about max4live but i don't know where to post this, if not here, be

max4live-device-initialization-after-midi-mapping

so when you assign a midi controller in Live to an object in your M4L device, the patch is "reinitialized"? are you using live objects? not sure what you mean by "reinitialization"

so when you assign a midi controller in Live to an object in your M4L device, the patch is "reinitialized"? are you using live objects? not sure what you mean by "reinitialization"
please post an example


I remapped some buttons from my apc40 via m4l.

I disconnected them from standard mapping (Mute and Crossfadebuttons) and assigned other functions. In my case: set_notes commands.

After hitting the blue midi map button 2 times, the apc40 initializes the standard configuration and my m4l patch doesn't work anymore. I have to turn it off and on again. So i need a bang after coming back from midi mapping to reinitialize the custom mapping. live.thisdevice, loadbang etc. doesn't work because there is no output when i close the mapping overlay.

Yes... there are a lot of live objects in this patch.

Thanks for your answer.
I remapped some buttons from my apc40 via m4l.
I disconnected them from standard mapping (Mute and Crossfadebuttons) and assigned other functions. In my case: set_notes commands.
After hitting the blue midi map button 2 times, the apc40 initializes the standard configuration and my m4l patch doesn't work anymore. I have to turn it off and on again. So i need a bang after coming back from midi mapping to reinitialize the custom mapping. live.thisdevice, loadbang etc. doesn't work because there is no output when i close the mapping overlay.
Yes... there are a lot of live objects in this patch.

there is no entry about the midi mapping mode in the Live API so I doubt this is possible

Can't you disable the control surface in Live's midi preferences and still get midi in your M4L device? If not, you could totally turn it off and run Max in parallel, sending midi to live. 

Or you could do a little max API patch that automatically turn it on and off every now and then.

ah OK
there is no entry about the midi mapping mode in the Live API so I doubt this is possible
Can't you disable the control surface in Live's midi preferences and still get midi in your M4L device? If not, you could totally turn it off and run Max in parallel, sending midi to live. 
Or you could do a little max API patch that automatically turn it on and off every now and then.
hope this helps!


Yeah... thats my problem. Think I read the whole API and LOM already :)

I also need some mappings from standard config... so it's not possible for me to turn it totally off.

Automatic turn off and on is too unspecific i think. And also there are a lot of commands with every init so it really would have impact on performance.

Thanks a lot for your reply, now i know it's not possible at this time.

Yeah... thats my problem. Think I read the whole API and LOM already :)
I also need some mappings from standard config... so it's not possible for me to turn it totally off.
Automatic turn off and on is too unspecific i think. And also there are a lot of commands with every init so it really would have impact on performance.

Max4Live device initialization after midi mapping