Hi folks,
I'm using sonar 8.5 64 bits,  as next versions have not been adapted for the blind.
Is there any reason why midi CC#100 would be ignored by this version of sonar, when all other controllers work fine.
Thanks for your help,
best,

Are you perhaps trying to assign CC100 to a synth's control? That probably wouldn't work, because CC100 has a defined purpose.
 
CC100 is normally not used alone, but rather in conjunction with CC101. Together, they represent a 16-bit value. It could be that SONAR might require CC100 to be followed by CC101, even if the latter contains a zero. CC100 followed by anything other than CC101 might be treated as an incomplete command. Just a guess.
 
Also, some RPNs require a third and possibly a fourth MIDI message for the data, making the entire message 3 or 4 bytes long. In other words, the CC100/CC101 combination specifies which parameter you want to change, but may not actually do anything unless followed by the parameter's value. 
 
 

Hi bitflipper ,
that's a good thought. I use a trumpet bank in Kontakt by www.samplemodeling.com , which I highly recommend, that uses this particular CC for loading different kinds of trumpet mutes. I can of course reassigned this controller, but it's a long job because I have to do it for each of their presets, I was looking for a simpler solution.
But I guess it's a sonar limitation. For Samplemodeling banks, it seems CC#100 is considered a standard MIDI controller, which is not the case for sonar.
Thanks for your help anyway.
Regards,

Hay Bitflipper or anyone else,
could you tell me which range of midi controllers I can use safely in sonar? Is it from 01 to 99, and are above considered as special-purpose controllers?
Thanks for your help,
best regards,

These CCs are officially "unassigned":
14,15
20-31
85-90
I usually start with CC20.