mapping higher midi channels to live.text from lemur menu objects
Jun 25 2013 | 3:21 pm
Hello,
I'm mapping parameters on my m4l device to my lemur skin in Ableton. I have many mappings and am now up to midi channels 2 and 3. When I map a lemur menu box to a live.text box on these higher midi channels the live.text boxes do not respond to the lemur menu box.
Any ideas?
Thanks,
~Ben Salomon
- Jun 25 2013 | 3:24 pmHere are some screenshots:max recognizes the lemur menus, so i don't think its a problem with the lemur object. you can see my midi mappings in ableton, and here is a shot of my lemur skin.
- Jun 25 2013 | 3:26 pmableton support said that "Unfortunately while Max for Live can deal with different MIDI channels, Ableton Live only will only receive MIDI using MIDI channel 1." and to post this on the forums.
- Jun 25 2013 | 6:04 pmFor the following I am going to assume that you are talking about live.menu objects, not live.text.Ableton support's got it wrong; you can off course midi map with all 16 channels. (The mfl device can only *output* one midi channels, that's where the confusion must've come from).I just set up a simple mfl device with a live.menu in it, and successfully mapped it to channel 2, then 4, 8 and 16. So they do work.I do have one thing that might have caused a problem; could you check that the midi map mode is absolute? If it somehow senses it to be relative in some weird way you would end up with problems.
- Jun 26 2013 | 3:41 pmhaha, yeah... live.menu, not live.text sorry, woops.
- Jun 26 2013 | 3:52 pmthanks for your suggestions wetterberg. I checked, and all menus are in absolute... so i'm still kind of stuck. I wonder if its the lemur application, or ableton. anyone else have any ideas?
- Jun 26 2013 | 4:57 pmYour Max patch in the picture uses midi input from a Live track which means that you get channel 1 only. But midi mapping is something different as explained in the manual, chapter 'Midi and Key Remote Control'.
