Program Changes in Native Instruments

[David Loving]

I like using Native Instruments' Kontakt 5.  I use either a digital piano or a controller to play NI keyboard sounds as a standalone in live performance.  Native Instruments lets one assemble a "multi", a group of sounds: Tonewheel B3, a piano, Wurli, Rhodes, Clav, etc.   I use a Korg Nano to send commands for drawbars, percussion, Leslie, etc for NI's B3.   Most of the Korg's duties involve the B3 program. and a knob sends volume commands for all the instruments in the multi.   I can program a knob on the KorgNano through the NI scripts to change from instrument to instrument in the NI Multi; a program change.    I'll have usb cables from the keyboard (PX330, or Alesis Q88) to the laptop, from the KorgNano controller to the laptop, from the laptop to a Presonus audio interface.  I use a Belkin device to plug in 3 usb into two slots on the MacBook Pro laptop.   The Alesis Q88 will send program changes to the NI Multi  - changing instruments as needed.   The PX330 will not send program changes, so I use the Korg, velcroed to the PX330.   I'd like to buy a PX5s mainly for the improved sounds and action.  I'd also like to be able to send program changes like the Korg Nano does.  Will the PX5s  do this?

[Display Name]

Hi David. The PX-5S functions make a great master keyboard controller and will send program changes via MIDI with no problem. You can also program the 6 sliders and 4 knobs to send MIDI CC messages to control parameters in your virtual instrument.  

[David Loving]

So it will replace the Korg,  and I can use the "learn midi" in NI to correspond to controls in the PX5s, one of which will act just like the knob on my KorgNano to send "program change" commands to the NI multi?

[Brad Saucier]

Yes.  Actually you can go a step further with the PX5s.  It allows the user to define what CC# the sliders and knobs are sending.  You can also disable the control sliders and knobs from affecting the internal sounds of the PX5 or they can do both at the same time.  It's pretty versatile. 

[David Loving]

Way cool.  That's what I need.  Thanks

[Display Name]

I make a "blank" stage setting and name it after the softsynth or iPad app I want to control. Then I map all the controls to the synth and save it. That way all you need to do is call up that Stage Setting when you want to use that particular VST / app.  

[Joe Muscara]

There's one itty bitty caveat I've run into doing this kind of thing.

 

Some Stage Settings don't have MIDI CCs set to some of the controls, usually the knobs. If you start with one of those, you'll have to map the CCs to the knobs. If you follow Scott's advice about creating a blank Stage Setting and use that, you should be fine.

 

I tend to start with an existing Stage Setting so I've gotten caught by this a few times.