Retreiving the Midi map

I am a little confused at what you are asking. In terms of devices it is dynamic and can control whatever device is selected. You can change the logic of that with M4L. if you want to get the device parameters there are objects to do that with the Live Api.

Most of these object start with," M4L.api."

If you give me a little more info on what you are trying to do then i can give you more assistance. Please give me the end result of what you are trying to accomplish.

Mike

Hi,

First, thank you for the fast reply!

I'll try to be clearer, but I think I need some sleep :)

So, the problem : I find it hard to see what each device knobs (on the APC40) do on a given device. I need to turn each knobs and look at the screen to see which parameter is affected.

What I'm trying to do : Have a M4L patch that somehow can read this hardcoded mapping and show me an exact replica of the device control section on the APC40, with the addition of the name of the parameter over each knobs.
A bit like a cheap, software version of the Novation Zero SL's LCD screen.

I hope it's better :P

Hi Mate,

I'm sure someone on the ableton forum printed a list of the standard functionality, can't find it at the moment though.....

Sorry

D

tecknoize wrote (on Tue, 02/23/2010 - 07:31)

I've spent the night trying to figure this one out.
Basically what I would like to get is the parameters' name of the appointed device that are currently under control by the APC40.
In other words, I would like know which knobs control which parameters, like Bank 1 -> Knob 1 -> Filter Cutoff, etc.

----

I too would like to find out how to do this. I would like to programatically retrieve the names of any parameters mapped to a MIDI control surface. To be able to produce a list very similar to that shown in the "MIDI Mappings" view.

I.e:

MIDI Channel 1, CC 2, is mapped to "Live.Song.Song.tracks[0].devices[0].parameters[0]" ("1-Audio"|"Auto Filter"), parameter name "Device on", parameter value=1.0

Hi guys,

I've managed to retreive the mapping of the APC40 by decompiling and looking at the python code inside /Resources/MIDI Remote Scripts/APC40. When using Max For Live and dealing with control surfaces, you're basically calling that API.

However, this is only the built-in mapping, so If I remap a control with the normal midi mapping, my max patch doesn't show it.

@anonymous, I'm not sure you can retrieve what's in the midi mappings view, unless you're using a control surface. As far as I can tell, you cannot go directly to the midi map. You need to pass through a control surface object and look at its mapping. Easier said than done when there's absolutely no documentation.

FYI, I've been using http://www.depython.net/ for decompiling the pyc files.