Korg Nanokontrol 2 in Bitwig

[Ultrabra]

Just moving over to Bitwig from Cubase ... going mostly well but ... cannot work out the set up for using my Korg Nanocontrol 2 in CC mode.

Can anyone guide me to the correct steps to get this working.

Thanks

[u-u-u]

What do you mean with CC mode?

I have a Nanokontrol 2 and used it together with Bitwig but together with a controller script. There is one in the controller script list inside Bitwig Studio which you can select - but this sets the Nanocontrol into native mode (which is you want to avoid?)

What do you want to achieve with CC mode? If you just want to directly record MIDI CC you probably could select the Generic -> MIDI Keyboard (or maybe the Generic -> Controller) script in the Controller settings.

[Ultrabra]

Thanks for the reply.

I want to use the Nanocontrol2 to control Midi CC-related function on my virtual instruments - eg CC1 dynamics, CC11 expression. When plugging in the Nanocontrol whilst holding down Cycle+Set this put the Nanocontrol in CC mode (at least in Cubase).

[u-u-u]

Ah ok, I would have to be at home to try to find a solution. Haven't used my NK2 for some time now although I used it to get into controller scripting back then by observing the stock script that comes with Bitwig Studio

Basically I see 2 ways

1. Find a way to get the CC messages on a separate note input for the CC mode which then can be used to directly record MIDI CC data on a track
   • setup the NK2 to use different MIDI channels in CC mode vs in native mode. Then adjust the controller script so that it offers a note input for incoming cc messages on the CC-mode MIDI channel. (You can filter MIDI messages in the controller script)
   • Or does the NK2 send on a different MIDI port in CC mode? That would make things easier because then you just could select a different (Generic) controller script for the CC-mode port.
2. Use Bitwig's MIDI CC device. Put it in front of the VST you want to control. Then you can use the stock NK2 controller script to control the selected device (e.g. that MIDI CC device) in device mode. You even can give meaningful names to the MIDI CC knobs on the device. If you want to route the NK2 to the same VST permanently, you can pin the currently selected MIDI CC device for the NK2 so that it always points to that MIDI CC device.

Personally I'd go for method 2 because it doesn't involve any scripting and let's you avoid switching to CC mode completely.

[Ultrabra]

Oh, that's good! It worked using the Method 2 above. But .. i didn't quite get your last part - I would like that every time I launch Kontakt (for example) that the Midi CC setting is there ready ---- is that what you meant by "route the NK2 to the same VST permanently"? ---- where do I /how do I do the "pinning"?

Thanks

[u-u-u]

I would like that every time I launch Kontakt (for example) that the Midi CC setting is there ready ---- is that what you meant by "route the NK2 to the same VST permanently"?

Not 100%. Unfortunately VST devices don't have a Note FX slot in Bitwig. Because you'll always need that MIDI CC device in front of the VST device. Therefore you'd have to put Kontakt into a Chain device - and put the MIDI CC device there as well. Save a Chain device preset. And everytime you want to use Kontakt - you have to call up that Chain device preset again. Then I'd also recommend to add a remote control page for the Chain device which contains all knobs you need from the MIDI CC device.

Oh, that's good! It worked using the Method 2 above. But .. i didn't quite get your last part - I would like that every time I launch Kontakt (for example) that the Midi CC setting is there ready ---- is that what you meant by "route the NK2 to the same VST permanently"? ---- where do I /how do I do the "pinning"?

Go to the "Studio I/O panel" (the left/right arrow icon at the bottom right). If you correctly loaded the standard NK2 controller script, you should see a section for the NK2 script with the currently selected device which you then can pin.
Select the MIDI CC (or the Chain) device and pin it. But if you have multiple of these Kontakt / Chain setups on multiple channels you might not want that because I think it's convenient to always have the NK2 mapped to the cursor device on the currently selected track.

[Ultrabra]

Thank you for your detailed help. I did make a "Chain device" for this, and I can select it for a new track and everything comes up ... but the Nanokontrol didn't work on that one, did not change the CCs.

Can just be my lack of knowledge of Bitwig, but it does sound like way too complicated process for what I need.

Does the Nanokontrol2 in its CC mode not work with Bitwig?

[u-u-u]

Thank you for your detailed help. I did make a "Chain device" for this, and I can select it for a new track and everything comes up ... but the Nanokontrol didn't work on that one, did not change the CCs.

Now I could finally try it at home. The nanoKONTROL2 script is very old so it uses an API function that only works with the "primary" (aka instrument) device on each track but not the selected device.

I attached a modified control script which you can try out:

• Just put it inside your user control script folder. On Windows that's under
  "C:\Users\<username>\Documents\Bitwig Studio\Controller Scripts"
• I renamed it to "nanoKONTROL2 (manipulated)" so this is how you should find it in the settings dialog
• The change is that in device mode the script now always uses the cursor device (the one that you selected last on a track) instead of the primary device
• inside the code I left the changed (actually just 2) lines as comments - in case you want to know more

Using that script you should be able to use a Chain setup like this:

MIDI CC Chain.png

(as long as you have selected the Chain device its remote knobs should have that little color indicator to show that they are currently controlled by the nK2 - which has to be in device mode (press the Cycle button))

Does the Nanokontrol2 in its CC mode not work with Bitwig?

CC mode worked for me like this and I could record CC automation to a track:

1. Pressing Cycle+Set while plugging in the nK2
2. In Bitwig, add "Generic" -> "MIDI Keyboard" as control script
3. select the nanoKONTROL 2 ("nanoKONTROL2 1 SLIDER/KNOB") as MIDI input for that script
4. Arm record (or just arm automation write)
5. select a note track (with input set to "All ins") -> should be armed automatically (or arm manually if you set it differently in the settings)
6. press play and move the faders on the nK2 -> records automation
7. If you don't see the automation, unfold the automation lanes on the track (this requires 2 steps: 1. automation lane button on the track head 2. the star icon inside the track automation area to show all automation lanes).

[Ultrabra]

Ah, thanks - now the NK2 is working fine. I had previously selected "Controller" and not "Midi Keyboard". (It also works with "Keyboard + 8 Device Knobs").

I'll check out that script - big thanks for sending it - I'll need to swap the function of the NK2 though to test it (from CC to device mode) which can be a bit of a pain in normal usage. Maybe its time to upgrade from NK2 to a better controller which would perform both tasks automatically, does it exist?

One small extra question - in Bitwig, do I see the recorded CC data only in the automation lanes (in Cubase it shows in Piano Roll too)

[u-u-u]

I'll check out that script - big thanks for sending it - I'll need to swap the function of the NK2 though to test it (from CC to device mode) which can be a bit of a pain in normal usage.

That's why I probably would go for the Native mode + MIDI CC device solution and skip the CC mode. My perspective is that the modern standard is that I have high-res parameters for everything in Bitwig Studio. But many plugins and hardware devices still do need CCs (hopefully only until they support MIDI 2.0 or another hi-res protocol - except for legacy plugins and vintage hardware of course). So MIDI CC device helps to wrap this old-school tech inside the modern Bitwig environment until something better comes around the corner.

One small extra question - in Bitwig, do I see the recorded CC data only in the automation lanes (in Cubase it shows in Piano Roll too)

You can show automation (also CC automation) below the piano roll when you switch to the Edit Panel Layout (Shift + Tab). On the other layouts (Arrange & Mix) you can only have one of both at the time.