manually mapping midi controls

[ashtarchris]

Does anyone know any ways to manual map midi controls in ableton?

Specifically I am trying to map different midi control messages from a lemur to ableton. When mapping x-y functions I've noticed that it's difficult for ableton to choose the right controller.

It would be a lot easier to manually enter control messages in the midi mappings rather than using auto mapping.

Complex structures are very difficult to map, such as step sequencers and bouncing balls.

Is there a way to create new mappings manual without having to click on the destination and play the signal from the midi device?

It is driving me crazy to map out complicated lemur templates.

Please Help!


thanks

chris

[chapelier fou]

It is still impossible...
SO.......
+1!

[Geezus]

Does anyone know any ways to manual map midi controls in ableton?

Specifically I am trying to map different midi control messages from a lemur to ableton. When mapping x-y functions I've noticed that it's difficult for ableton to choose the right controller.

It would be a lot easier to manually enter control messages in the midi mappings rather than using auto mapping.

Complex structures are very difficult to map, such as step sequencers and bouncing balls.

Is there a way to create new mappings manual without having to click on the destination and play the signal from the midi device?

It is driving me crazy to map out complicated lemur templates.

Please Help!


thanks

chris

I dont have a lemur but I think a way around this would be to create a specific lemur template JUST for mapping controls and your main template that actually has the controls you want on them.

i.e., say you have a lemur template with an x-y pad that you want to map to ableton controls. Instead of trying to map it via the x-y pad itself, have a second lemur template with nobs or faders that route the SAME MIDI cc messages and map THOSE controls, then switch back to the template with the x-y pad and jam out. since they are both sending the same midi cc mesages, it should be interchangable. use one template for routing midi ccs and another for actually playing them.

[djgroovy]

I dont have a lemur but I think a way around this would be to create a specific lemur template JUST for mapping controls and your main template that actually has the controls you want on them.

i.e., say you have a lemur template with an x-y pad that you want to map to ableton controls. Instead of trying to map it via the x-y pad itself, have a second lemur template with nobs or faders that route the SAME MIDI cc messages and map THOSE controls, then switch back to the template with the x-y pad and jam out. since they are both sending the same midi cc mesages, it should be interchangable. use one template for routing midi ccs and another for actually playing them.

Good idea mate. I have the same problem mapping the xy in my novation, gotta try that.

[siliconarc]

here's a tip i got from mike at trackteamaudio for mapping a multi-cc:

go into map mode and map a control. it will appear in the midi mappings page to the left. now click on the new mapping in the list and hit 'undo' to go back through the other cc's. really useful for mapping multitouch, xy controls etc.

[JuSchu]

+1

i'm controlling live also with glovePIE. there i'm typing the CCs also with the computer-keyboard. it would be a better workflow, when i don't have to switch always between the pc and the controller.

and i have anyway a real complex midi-setup without glovepie.

[kcp]

here's a tip i got from mike at trackteamaudio for mapping a multi-cc:

go into map mode and map a control. it will appear in the midi mappings page to the left. now click on the new mapping in the list and hit 'undo' to go back through the other cc's. really useful for mapping multitouch, xy controls etc.

When I hit 'undo' the new mapping disappears from the list and I'm back where I started.

[siliconarc]

what are you trying to map? works fine here with my padkontrol's xy and my edirol's dual-cc fader. this only works with multi-output controllers; XY controller, multitouch screen, accelerometer etc. once a cc is mapped (the last cc received from the controller), 'undo'ing basically goes backwards through all the previous cc's that have been sent from that one device. you'll see the cc numbers change in the midi mappings list.