The other option is to change the Controller's preset so it sends #7 from the fader that was previously sending #21. In this situation, it's expected that you're going to use the software to "re-map" the incoming values (21, 22, 23) to be #7 on a channel per channel basis. even though the GM standard states that volume should be 7 and pan should be 10. And the knobs may send CC#41, 42, 43, etc. Usually, controller keyboards just use some random consecutive numbers - so for example, if you have 8 faders, they'll send CC# 21, 22, 23, etc. So you have two options when a situation like this comes up, and those are basically change the value of the fader on the controller so it sends CC#7, or change something in the software so that whatever number does come in when you move that fader, it "interprets" it as CC#7. However, it may not be set up from the factory to send CC#7 on the first fader for example. This means GB *might* recognize all of the defined ones, or it may only recognize the more popular ones. The others were left undefined so manufacturers could make devices do other things for those numbers.īut not all software follows the General MIDI standard. Less than half of the 128 numbers are defined IIRC. General MIDI defines some portion of 128 CC#s 0 CC#1 is Modulation, CC#7 is Volume, CC#10 is Pan, CC#64 is Sustain Pedal, etc. So if you send a CC#7 message from your controller (0-127 range as you move the fader sending that CC#) it will make the volume of the selected track go up and down. GB TMK doesn't have "set" MIDI values it receives to affect things that are beyond "standard fare".įor example, the General MIDI standard sets Volume as CC#7.
0 kommentar(er)
