Hi there,
I recently purchased a Korg nanoKONTROL Studio device to use with Cubase 13. I’m wanting to be able to use the faders as CC controls for expression and vibrato when writing for orchestral instruments, however whenever I move the sliders, they only control the volume of the corresponding track, i.e fader 1 controls track 1’s volume, fader 2 controls track 2’s volume etc.
I put the device in assignable mode rather than in Cubase Mode as I thought this might have something to do with it, but even after I mapped the CC channel’s in the Korg Editor and restarted Cubase it was still performing the same way.
Does it have anything to do with Cubase 13 not recognising it as a MIDI remote? When I tried to add it I could only add the nanoKONTROL or nanoKONTROL2 and so I have it currently set up as a Mackie controller…
I tried to create a midi remote by creating a custom layout using the model of the nanoKONTROL Studio and got everything to work, even the pots as quick controls, however when I try and use the faders for CC, they are still only changing the track volume.
It looks like you are using the device in Mackie Control Mode, and you set Mackie Control in Cubase (Studio > Studio Setup > Remote Devices). If you do so, you don’t use the device as plain MIDI Controller, you use it as a DAW Controller to control Cubase instead.
Thanks for the tip, I removed it as a Mackie Control and have placed the nanoKONTROL Studio in setup mode and it is now no longer controlling the track volume. However, when I try and assign it a CC the faders don’t seem to communicate with the DAW anymore.
If I just map them and leave them as their default mapping they work fine, i.e if I leave fader 1 as CC#2 and fader 2 as CC#3 then I can use them perfectly, but when I make fader 1 CC#1 and fader 2 CC#11 they seem to no longer communicate with Cubase. All other faders will work if I don’t try and assign them.
However, the MIDI indicator in the bottom right hand corner still lights up when I move the fade so it’s still getting an input, it just won’t map it to what I want.
Open Studio > Studio Setup > MIDI Ports Setup. On the nanoKONTROL Studio Input, click on the Monitor icon. The Monitor window opens and you can monitor incoming data on this given MIDI Input. Now, you can inspect, if Cubase receives CC1 from the hardware.
Make sure, you are not using MIDI CC1 in the Quick Controls or any other Remote Device, which would filter the MIDI CC1 out, please.
I’ve got it all working now! I worked out that I hadn’t written the scene data from the Korg Kontrol Editor to the actual unit. Once I did this I had to remap the midi remote in cubase to make sure it all matched up, but I got there!
Sorry I can’t help much on this, except to say I don’t think so…
But you would be very kind to summarize your findings here, once you have a satisfying stable solution, for those (like me ) who are considering this device.
The only way would be to make a custom settings. Assign the Jog Wheel to the message, Mackie Control expects for the wheel (i.e. MIDI CC60) and all other controls to the message Mackie Control doesn’t use at all (Mackie Control is using MIDI CCs 16-23 and lots of MIDI Notes).
Very nice Mackie Control MIDI Messages overview is available here.
Or write MIDI Remote script just for the Jog Wheel MIDI CC.
) who are considering this device.