It seems to me that some CC numbers will be ignored by GP.
Sending test MIDI data via: Reaper → LoopBe30 → Select it as Device in Rig Manager
Documentation’s not mentioning anything to watch out for.
Can someone check/confirm if this is reproducible?
Situation 1:
Setup Rig Manager to listen for your device (in my case Reaper into LoopBe30).
Create a MIDI Control Alias.
Double Click it to learn.
Send a CC with number in between 120-127.
My observation: Rig Manager will not detect/assign these.
Situation 2:
Setup Rig Manager to listen for your device (in my case Reaper into LoopBe30).
Create a MIDI Control Alias.
Double Click it to learn.
Send a CC with number=32.
It should be mapped now.
Assign the Alias to a knob.
Send CC32 values.
My observation: CC 32 messages seem to be discarded.
Reading about CC 120-127 in general, these seem to be reserved for special actions sometimes. Is this the case with GP too? This should be documented then, or better, display a warning when user is trying to assign a reserved CC number.
The CC 32 leaves me scratching my head. I cannot believe it doesn’t work, but as soon as I switch to a different CC, it works as expected. No filtering is set up and rig manager correctly detects the incoming CC 32.
CC0 and CC32 are the Select Bank MSB/LSB messages (extending the program change message) and in general are not available for normal use since GP itself responds to those messages.
If you must use those particular messages for something else (why?) then you can intercept those CC messages via a Gig Script and and reinject them into the system with some other CC number.
I remembered I did something like that which preserves CC0 and CC32 involved in Program Changes Bank Selects and converts others (I still don’t know if it works ):
To use MIDI controllers, one needs to know or have access to the MIDI conventions.
Keep this document to hand, so that you can quickly understand why you may encounter problems when using certain codes, as well as finding other information.