Midi Volume Control With CC #11
-
- KVRist
- 45 posts since 30 Jul, 2007
I use receptor live, and often need to layer multiple vst's, controlling them by assigning each vst to the same midi channel on the receptor. Both of my keyboard controllers (Yamaha S80 and Roland A-37) send volume control only on midi cc# 11, and not #7. Therefore I have trouble controlling the volume of most vst's. Some vst's such as B4 have a CC learn mode that solves the issue. Most do not. A simple solution would be a vst fx that I could insert into each mixer fx channel that can learn and respond to volume control on midi cc #11. Is there anything out there that could be put to this use without coloring the sound?
-
- KVRist
- 82 posts since 15 Apr, 2007
Hi, dudegruvy:
This was exactly the question I had a while back. You can see the thread here:
http://www.kvraudio.com/forum/viewtopic ... highlight=
Basically you have two choices: Use a MidiSolutions MidiMapper to map CC#11 to CC#14 on channel 16 to control Receptor's output volume, or use the handy little plug-in designed and kindly provided to us by our good friend Greg Holmes. The link to the plug-in is on Greg Holmes' entry in the thread.
The plug-in works great. Only problem is it uses two mixer channels per VSTi. This is explained in the thread. MidiMapper also works well, but requires an extra box hanging off the back of your Receptor. I currently rely on the wonderful plug-in from our Mr. Holmes.
Hope this helps.
K.
This was exactly the question I had a while back. You can see the thread here:
http://www.kvraudio.com/forum/viewtopic ... highlight=
Basically you have two choices: Use a MidiSolutions MidiMapper to map CC#11 to CC#14 on channel 16 to control Receptor's output volume, or use the handy little plug-in designed and kindly provided to us by our good friend Greg Holmes. The link to the plug-in is on Greg Holmes' entry in the thread.
The plug-in works great. Only problem is it uses two mixer channels per VSTi. This is explained in the thread. MidiMapper also works well, but requires an extra box hanging off the back of your Receptor. I currently rely on the wonderful plug-in from our Mr. Holmes.
Hope this helps.
K.
-
- KVRian
- 524 posts since 25 Aug, 2005
Just have to agree with okikahuna - it's a great plug in, works very well, thanks again, Greg...
-
- KVRist
- 197 posts since 23 Jan, 2006 from Ontario, Canada
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
- 45 posts since 30 Jul, 2007
Thanks guys. I ordered the Midi Event Processor from Midi Solutions, which seems to do lots of other things to help my contollers work with a receptor.
http://www.midisolutions.com/prodevp.htm
I already own their Midi Merger, which lets me plug 2 keyboards into the receptor, allowing me to have have a piano action and synth action keyboard together for live work. I am surprised that more folks are not talking about these issues, which have to be solved in order to use the recptor in a live performance.
http://www.midisolutions.com/prodevp.htm
I already own their Midi Merger, which lets me plug 2 keyboards into the receptor, allowing me to have have a piano action and synth action keyboard together for live work. I am surprised that more folks are not talking about these issues, which have to be solved in order to use the recptor in a live performance.
-
- KVRist
- 82 posts since 15 Apr, 2007
The midi mapper will also solve at least one other problem that the plug-in won't: That is that many plug-ins hard-map CC#11 to something like oscilator 2 tuning (ie Imposcar) and the Receptor seems to allow CC#11 to get to the plug- ins regardless of the setting of the "send midi ccs to plug-ins" switch. My solution used to be to set to set the midi mapper to block CC#11 on channel 1, as well as convert it to CC#14 on channel 16. Now, I've just stopped using those plug-ins and I research the issue before buying new ones.
All of the whining on this issue seems to have been done by only a handful of people, including myself, which surprises me as well. As much as I would like direct install, this is a bigger issue to me because it prevents me from using plug ins that already install right now. Many plug-ins I would most like to use would be pretty much unusable live if I can't map CCs (ie the Stradivari violin). I'm hoping that improved midi mapping may be in Receptor's future.
K.
All of the whining on this issue seems to have been done by only a handful of people, including myself, which surprises me as well. As much as I would like direct install, this is a bigger issue to me because it prevents me from using plug ins that already install right now. Many plug-ins I would most like to use would be pretty much unusable live if I can't map CCs (ie the Stradivari violin). I'm hoping that improved midi mapping may be in Receptor's future.
K.
-
- KVRist
- Topic Starter
- 45 posts since 30 Jul, 2007
I'm a little confused about the above post concerning mapping cc#11 with the Midi Event Processor.
The user manual for the Event Processor seems to say that I can convert all incoming cc#11 messages on any midi channel to CC#7, which should solve the problem of controlling volume for all Receptor vst's. My experiments with the receptor have allowed me to control volume on any plugin by using the "send midi cc's to Plug-ins" switch, and then sending volume control on cc#7. Am I missing something?
The user manual for the Event Processor seems to say that I can convert all incoming cc#11 messages on any midi channel to CC#7, which should solve the problem of controlling volume for all Receptor vst's. My experiments with the receptor have allowed me to control volume on any plugin by using the "send midi cc's to Plug-ins" switch, and then sending volume control on cc#7. Am I missing something?
-
- KVRist
- 82 posts since 15 Apr, 2007
No, I don't think you are missing anything. It sounds like your approach should work just fine. I just did it a different way, changing CC#11 to CC#14 on channel 16 to control the volume of the output channel, because I was doing this before the "route midi CCs to plug-ins" option appeared.
The only issue with doing it your way might be gain staging: if you are controlling the levels of the source plug-ins, you will have to be sure that you don't overload anything before an attenuator when you are at full volume. So, a question would be, is it possible for a VSTi at full gain to overload prior to reaching the mixer channel attenuator? Let us know what you find out.
K.
The only issue with doing it your way might be gain staging: if you are controlling the levels of the source plug-ins, you will have to be sure that you don't overload anything before an attenuator when you are at full volume. So, a question would be, is it possible for a VSTi at full gain to overload prior to reaching the mixer channel attenuator? Let us know what you find out.
K.