Using MidiMap from the API in m4l

[asha.dan]

I have a midi remote script that changes the midi assignment of my controller dynamically. That is, if I send a certain note my CC's get mapped to one track's parameters, if I push another note then they get mapped to another tracks parameters etc. It does this using the Live.MidiMap class in the API.

Now I have M4L and want to do the same thing, effectively porting my remote script over. But I can't see how to access the MidiMap functions in max
... anyone know how?

Cheers,

Dan

[bulo]

You don't need to access midi map with m4l, You have to directly access the path of the parameters you want to control.
I think this device will help you:
http://www.maxforlive.com/library/device.php?id=262

[asha.dan]

Thanks for the reply, sorry to take so long getting back on this.

Yeah I understand the idea, and can observe and set the appropriate parameters from Max as in that example. I am accessing those objects to show various parameters in a single window. Its just much more complicated than how I did it in python using Live.MidiMap to swap the midi control over and observe/set the parameters.

Oh well... the cost of getting those nice dials onscreen

D

[S4racen]

I'd look at investing the time in getting the dials as a floating window as well that way you can always see what you're controlling if the focus of Ableton changes...

Cheers
D

[asha.dan]

Yes that's what I bought Max to do initially. And have been successful in showing the dials, just not in changing the mapping dynamically.I tried for a while and decided in the end to just map the dials to the appropriate parameters, but leave the parameter mapping changes in the Python code at the moment. Too much hassle to redo it all, and it seemed to me that its easy to loose the responsiveness of the controller routing midi all over the place (probably due to my inexperience with max).

I'll revisit it all once I have a little more Max under my belt perhaps.

Cheers,

Dan

[amounra93]

You'll do better leaving stuff in Python that can stay there. It is much more responsive. You can, however, use the m4l access to the API to gather information to display in those windows you're talking about. Have a look at my LCD project....I found some ways to forward the parameter information from functions in Python over to m4l. Check my blog.

Cheers.

[asha.dan]

Thanks I'll have a look over the weekend. I agree that Python is much more responsive too.

I have managed to get my patch set up to display all the parameters I want in a floating window... but as a first attempt its all a bit spaghetti-like in there

D