Promidi Posted October 9 Share Posted October 9 Like any controller number, CC numbers can be anything you would like them to be. Most synths have a MIDI learn function where you can map any controller nunber to any parameter. This is totally up to the synth. Not all synths allow this. (perversely, Native Instrument's Massive X does not) However, there is a Roland General MIDI (and Yamaha XG) standard where certain controller numbers are assigned specific functions. For instance, CC7 is usually volume, CC10 is usually Pan, CC 72 is usually release time, CC73 is usually attack time, CC123 > 127 usually stops any notes if they are still sounding (for what ever reason)..... and so on. However, synths are under no obligation to follow these standards. It just so happens that Rapture Pro does. The way to test is to insert a Simple Instrument Track (SIT). Then in the Piano Roll View (PRV), insert some long notes (about a whole note). Then insert a CC123 > 127 followed by a CC123 > 0 somewhere under those notes. If your synth goes silent when the CC123 > 127 is encountered, then that synth does indeed respond to the CC123 > 127 MIDI event. 1 Link to comment Share on other sites More sharing options...
Wojtek Stecyszyn Posted October 10 Share Posted October 10 Thank you for this info. I still don't understand how to "insert CC123" and other CC. Its totally new topic for me. I need to google it out. Link to comment Share on other sites More sharing options...
Promidi Posted October 10 Share Posted October 10 41 minutes ago, Wojtek Stecyszyn said: Thank you for this info. I still don't understand how to "insert CC123" and other CC. Its totally new topic for me. I need to google it out. Insert cc123.mp4 1 1 Link to comment Share on other sites More sharing options...
Wojtek Stecyszyn Posted October 10 Share Posted October 10 Ahh it is this then. Ok, I see now Thank you Well, I did exactly this and no, this instrument (Looptrack from Gospel Producers) do not respond to this command. But I have found a trick that can kill the samples - changing presets or sounds/instrument within one VST. In case of Looptrack its just changing the sample bank - super easy. Its not a great solution, but it works. Nevertheless I wish Cakewalk had a global and permanent kill button build in Link to comment Share on other sites More sharing options...
Promidi Posted October 10 Share Posted October 10 What about issuing a CC7 > 0. Mind you, the plugin will technically still be playing the sample, just at a volume of zero (this is assuming Looptrack responds to CC7 events) Link to comment Share on other sites More sharing options...
Wojtek Stecyszyn Posted October 10 Share Posted October 10 Nope. This VST instrument does not respond to CC events. I tried it on other instrument (Cakewalks electric piano) and it worked on both: CC7 and CC123 so Im doing it right. Its just this Looptrack. Anyway, thanks. I learned something today 1 Link to comment Share on other sites More sharing options...
mettelus Posted October 10 Share Posted October 10 1 hour ago, Wojtek Stecyszyn said: Nope. This VST instrument does not respond to CC events. This would be worth submitting feedback to the developer on if you like it and want to keep using it. Many complex VST(i)s have a Panic button in the VST GUI itself, but the Panic button inside the host (any host) is going to try to the same routine Cakewalk is doing. If the VST doesn't accept that input, there is no way to control it externally. The host is doing its job (and no way to make it better), but the VST is in its "own little world." Side note: some VST(i)s have that kill switch hard coded to a specific MIDI note, but I couldn't find any documentation on Loop Track. 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now