123 control change problem
Posted: 04 Feb 2012 00:00
Hello everybody -
I am currently working on a Max for Live patch to be controlled by Lemur on iPad. I have 8 multisliders on the same channel, taking up all CCs for that channel, 0-127.
I am having trouble, however, with CC 123. This apparently is used as an "all notes off" control change, and as a result, it is silencing all incoming midinotes in my patch, when in fact, I need it to just deliver velocity information.
I've noticed that it's not particularly the architecture of my patch - if I try to individually assign the MIDI of the 123 slider, it simply will not do it. I also notice that, when running it through MAX/MSP, midiparse will report the 123 control change, but there is no value change associated with it (it just reports 123, value 0).
I'm wondering if other people have run into this problem, and if there is an easy workaround.
It occurred to me that I could just put the last multislider on a different channel, but for some reason, MAX/MSP and midiparse aren't recognizing the individual MIDI channels (i.e. midiparse reports channel 1 for EVERYTHING). Ableton Live can discern the different channels coming from Lemur, so perhaps there is a MAX/MSP setting that I am missing? Fixing this problem seems to be the easiest solution, but I have no idea why MAX/MSP isn't recognizing the channels!
Obviously, OSC would be ideal, but I've found that my iPad's IP address is constantly changing. If I used MAX/MSP in live performance, that might not be an issue, but I use Live and would rather just use MIDI than having to keep MAX/MSP open as well.
Any thoughts? Thanks!
Sincerely,
Drew
I am currently working on a Max for Live patch to be controlled by Lemur on iPad. I have 8 multisliders on the same channel, taking up all CCs for that channel, 0-127.
I am having trouble, however, with CC 123. This apparently is used as an "all notes off" control change, and as a result, it is silencing all incoming midinotes in my patch, when in fact, I need it to just deliver velocity information.
I've noticed that it's not particularly the architecture of my patch - if I try to individually assign the MIDI of the 123 slider, it simply will not do it. I also notice that, when running it through MAX/MSP, midiparse will report the 123 control change, but there is no value change associated with it (it just reports 123, value 0).
I'm wondering if other people have run into this problem, and if there is an easy workaround.
It occurred to me that I could just put the last multislider on a different channel, but for some reason, MAX/MSP and midiparse aren't recognizing the individual MIDI channels (i.e. midiparse reports channel 1 for EVERYTHING). Ableton Live can discern the different channels coming from Lemur, so perhaps there is a MAX/MSP setting that I am missing? Fixing this problem seems to be the easiest solution, but I have no idea why MAX/MSP isn't recognizing the channels!
Obviously, OSC would be ideal, but I've found that my iPad's IP address is constantly changing. If I used MAX/MSP in live performance, that might not be an issue, but I use Live and would rather just use MIDI than having to keep MAX/MSP open as well.
Any thoughts? Thanks!
Sincerely,
Drew