I am having trouble setting up my BCF2000 to work with my Receptor. i do have some controls working just fine, but I dont understand how to assign the right cc values to the coordinating nrpn values. Here is what is working and perhaps you can tell me why.
BCf2000 is sending out CC 30.
Receptor is hearing it and making changes to B0 63 00 B0 62 1A
How can i deduce cc 30 from B0 63 00 B0 62 1A ???
If someone can offer me a solution it would help out tremendously. My BCF2000 asks for cc values not full nrpn values, so i need to figure out how to assign the right cc to get it to work right for me.
can someone also tell me the advantages of having the cc messages routed to the plug in as seen in the setup menu of the receptor, verses not doing it?
Thanks
Do you understand NRPN?? Then i need your help !!!!
-
- KVRist
- 269 posts since 23 May, 2008 from Lake Stevens, WA, USA
Dr. Oates, I think this is explained in the Receptor manual in the section titled, "Editing Plugin Parameters with MIDI NRPN Messages", particularly sub-section "NRPN Details."
I'm no expert on this, but it looks like this may be what you're looking for.
Good luck!
I'm no expert on this, but it looks like this may be what you're looking for.
Good luck!
-
- KVRist
- Topic Starter
- 35 posts since 3 May, 2007
Your exactly right, and it raises a new question. WHERE ARE THE PARAMETER NUMBERS FOUND? here is what the manuals says.
"To select the plugin parameter you want to change, you will need to translate the parameter number into a pair of MSB and LSB values, then add an offset to the MSB value. The formula for calculating the MSB and LSB values are as follows:
MSB = Parameter Number / 128
LSB = Parameter Number - (MSB x 128)
EXAMPLE 1: To control parameter 537 of a plugin:
MSB = 537 / 128 = 4
LSB = 537 - (4 x 128) = 25
My question is, in their example that used 537... where did they get 537 from.... where would i find parameter numbers? They inda of assume that they are right there for you to see.... what am I missing?
"To select the plugin parameter you want to change, you will need to translate the parameter number into a pair of MSB and LSB values, then add an offset to the MSB value. The formula for calculating the MSB and LSB values are as follows:
MSB = Parameter Number / 128
LSB = Parameter Number - (MSB x 128)
EXAMPLE 1: To control parameter 537 of a plugin:
MSB = 537 / 128 = 4
LSB = 537 - (4 x 128) = 25
My question is, in their example that used 537... where did they get 537 from.... where would i find parameter numbers? They inda of assume that they are right there for you to see.... what am I missing?
-
- KVRer
- 10 posts since 10 Aug, 2009
Hi-
From what I understand, The "route midi CCs to source plugin" option allows CCs to pass through the Receptors filter and go straight to the plugins. The disadvantage of this is that you can no longer control the mixer without using the front panel or receptor remote viewer.
I think CC 30 is reserved by the Receptor for controlling a parameter that is manually assigned to the front panel (specifically the 15th one). Maybe you have already done this and that is why you are seeing that parameter changing?
You can avoid NRPN altogether by just assigning parameters to the front panel and controlling them with CCs 16-31 (pg. 113 in the manual).
Also it is possible to use up to 47 different CC messages for a source plugin (so long as that plugin allows you to map out its CC assignments internally). You can do this without ticking "route midi CCs to source plugin".
For example, you can assign 16 parameters to the front panel (which are controlled by CCs 16-31), then midi learn other parameters within the plugin to any CC that Receptor doesn't filter out.
I went through all the CCs and found that you can send the following:
1-5, 9, 11, 33-37, 41, 43, 64-71, 100-101, 118-119, 122, 124-127
The rest are reserved by the Receptor for controlling the mixer and other functions. Anyway this method works because in most cases you have plenty of control and don't need to send NRPN.
Hope this helps.
From what I understand, The "route midi CCs to source plugin" option allows CCs to pass through the Receptors filter and go straight to the plugins. The disadvantage of this is that you can no longer control the mixer without using the front panel or receptor remote viewer.
I think CC 30 is reserved by the Receptor for controlling a parameter that is manually assigned to the front panel (specifically the 15th one). Maybe you have already done this and that is why you are seeing that parameter changing?
You can avoid NRPN altogether by just assigning parameters to the front panel and controlling them with CCs 16-31 (pg. 113 in the manual).
Also it is possible to use up to 47 different CC messages for a source plugin (so long as that plugin allows you to map out its CC assignments internally). You can do this without ticking "route midi CCs to source plugin".
For example, you can assign 16 parameters to the front panel (which are controlled by CCs 16-31), then midi learn other parameters within the plugin to any CC that Receptor doesn't filter out.
I went through all the CCs and found that you can send the following:
1-5, 9, 11, 33-37, 41, 43, 64-71, 100-101, 118-119, 122, 124-127
The rest are reserved by the Receptor for controlling the mixer and other functions. Anyway this method works because in most cases you have plenty of control and don't need to send NRPN.
Hope this helps.
-
- KVRist
- 197 posts since 23 Jan, 2006 from Ontario, Canada
Yes, you need to read the manual - several times!
The essence is that Receptor reserves some CC numbers for the mixer, but all others pass through to plugins.
In addition, some CC numbers map to the front panel controls, which in turn are mapped (by default, or by you) to some parameters in plugins.
The third layer is the long "B0" style numbers (like B0 63 00 B0 62 1A). Every parameter of every plugin is represented by these, and you can see them all by using the Receptor interface "faceless" mode - also described in the manual!
By using the B0 style command strings, you don't need to turn on "route midi CCs to source plugin", so the mixer will still be fully controllable.
The essence is that Receptor reserves some CC numbers for the mixer, but all others pass through to plugins.
In addition, some CC numbers map to the front panel controls, which in turn are mapped (by default, or by you) to some parameters in plugins.
The third layer is the long "B0" style numbers (like B0 63 00 B0 62 1A). Every parameter of every plugin is represented by these, and you can see them all by using the Receptor interface "faceless" mode - also described in the manual!
By using the B0 style command strings, you don't need to turn on "route midi CCs to source plugin", so the mixer will still be fully controllable.
Greg Holmes
Retailer: Acoustic Image, BassLab, Muse Receptor, MIDIjet, Rayzoon Jamstix, and more...
http://www.ghservices.com/
http://www.gregholmes.com/
Retailer: Acoustic Image, BassLab, Muse Receptor, MIDIjet, Rayzoon Jamstix, and more...
http://www.ghservices.com/
http://www.gregholmes.com/
-
- KVRist
- Topic Starter
- 35 posts since 3 May, 2007
okifinoki.... THANK YOU!!! I read through the manual and figured out how to assign to the front panel, so i tried it with i think cc 16... didnt work. Now I know why. The manual just seems so random at times. Teaching you how to find MSB and LSB for a parameter number that the darn machine doesn't even tell you. Anyway.... i can live without NRPN values... plus the BCF2000 doesn't exactly make using nrpn as easy as cc. Probably need to read that manual a few more times as well. Thank you all for the help. I will be implementing shortly, if this doesnt solve it nothing will.... And Thank you for the list of USABLE CC #. It will be taped to my mixer for reference.
-
- KVRer
- 10 posts since 10 Aug, 2009
No problem, glad to help 
Also keep in mind you that for FX plugins you can only assign 4 parameters so for those you may need to bust out some NRPN.
But yeah the manual explains how to read the hex values and if you need help down the road feel free to shoot me a PM.
Also keep in mind you that for FX plugins you can only assign 4 parameters so for those you may need to bust out some NRPN.
But yeah the manual explains how to read the hex values and if you need help down the road feel free to shoot me a PM.
-
- KVRist
- 38 posts since 28 Aug, 2008
okifinoki wrote:No problem, glad to help
Also keep in mind you that for FX plugins you can only assign 4 parameters so for those you may need to bust out some NRPN.
But yeah the manual explains how to read the hex values and if you need help down the road feel free to shoot me a PM.
On this - is there any way to control more that 4 parameters? Furthermore, I assign which parameters I want to control using those little blue boxers up the top of the screen. This leads to a problem that if I assign that 1 through to 4, then they have to stay there. If I open the same fx (say guitar rig) on another channel, and move them to where I want them for that channel, they seem to move for the original channel - ruining my set up. Any thoughts on that? Am I making sense?
-
- KVRer
- 10 posts since 10 Aug, 2009
Yes that makes sense. Unfortunately changing the order of assigned fx parameters affects all instances of that plugin. Once they are set you pretty much have to leave them alone, so pick the four most important. If your controller can send NRPN messages you can control more than four.