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
123 control change problem
Re: 123 control change problem
Hi
I would suggest that you check out a list of Standard MIDI CC's to avoid further issues . . .
CC's above 120 are used as Channel Mode messages (most send 0 as data) and it's best to avoid using them except for their purpose. . .
There are other ones up there that will cause issues - as well as all the various standard CC's below 100 that can also cause issues. . .
Midiparse (in Max) should report the channel properly - if it says it is getting Ch 1 then that is what it is seeing . . .
Whether it reports differently from within Live, I'm not sure but think it should be the same - will check . . .
Re: iPad IP address - you could always set it statically to avoid the constant changing . . .
Imho, OSC would be better to use, even with Live - Why do you think you would ned to keep Max open to do this . . .
Cheers
MM
I would suggest that you check out a list of Standard MIDI CC's to avoid further issues . . .
CC's above 120 are used as Channel Mode messages (most send 0 as data) and it's best to avoid using them except for their purpose. . .
There are other ones up there that will cause issues - as well as all the various standard CC's below 100 that can also cause issues. . .
Midiparse (in Max) should report the channel properly - if it says it is getting Ch 1 then that is what it is seeing . . .
Whether it reports differently from within Live, I'm not sure but think it should be the same - will check . . .
Re: iPad IP address - you could always set it statically to avoid the constant changing . . .
Imho, OSC would be better to use, even with Live - Why do you think you would ned to keep Max open to do this . . .
Cheers
MM
iMac 2.8G i7 12G 10.6.8/10.7.2, Legacy Dexter/Lemur, Liine Lemur/iPad2, KMI SoftStep, 12Step & QuNeo , B-Controls, Mackie C4 etc
MaxMSP, Live Suite, Native Instrument stuff, etc Modified Virtual Guitar System etc All Projects/Modules © CC-BY-NC-SA[*][/b]
MaxMSP, Live Suite, Native Instrument stuff, etc Modified Virtual Guitar System etc All Projects/Modules © CC-BY-NC-SA[*][/b]
Re: 123 control change problem
Thank you so much for your response. I'm a newbie to Lemur (and the possibility of something other than MIDI).
Honestly, it was my understanding that Live does not have native support for OSC - I know that there are various ways to get OSC into the program, but I'd be curious to know what's the most efficient. Perhaps a MAX patch with the udpreceive object?
The one thing that I have I come to rely on in Live is the quick and easy MIDI map. Every session is so different, I'm curious to know how quickly things can be mapped to various controls in Live if you're bypassing MIDI altogether? Any other insights you have would be helpful.
I'm definitely not opposed to using OSC as I understand it's a more fluid protocol, I just don't know enough about it (and can't seem to find too too much writing about its inner-workings).
Thanks again!
Drew
Honestly, it was my understanding that Live does not have native support for OSC - I know that there are various ways to get OSC into the program, but I'd be curious to know what's the most efficient. Perhaps a MAX patch with the udpreceive object?
The one thing that I have I come to rely on in Live is the quick and easy MIDI map. Every session is so different, I'm curious to know how quickly things can be mapped to various controls in Live if you're bypassing MIDI altogether? Any other insights you have would be helpful.
I'm definitely not opposed to using OSC as I understand it's a more fluid protocol, I just don't know enough about it (and can't seem to find too too much writing about its inner-workings).
Thanks again!
Drew
Re: 123 control change problem
By the way, I further investigated the midiparse issue. It seems that Ableton is reading the correct channel. MAX/MSP reads the correct channel if I'm using it as a standalone application. Somehow, though, the translation between Ableton's MIDI in on the MIDI track and the MIDI effect in Max for Live is getting screwed up. Hmmm... not sure about how to deal with this one. If anybody's seen this and knows of a solution, let me know. I think I'll head over to the MAX/MSP forums and look there.