Windows 10
Cubase Pro 12
Kontakt 6 v6.7.1

I have more weird issues with my nanoKONTROL Studio in Assignable mode.

After MUCH hassle and hours spent searching for any information on google (there is none) on how to set the nanoKONTROL Studio to control the Expression, Vibrato and Dynamics of the Spitefire range of Kontakt library's, I have figured some things out all except two...

Sending midi cc 21 to knontakt and recording the movements of the Modulation (Dynamics), Expression and Vibrato faders as I manipulate them with the nano studio.

The CC 21 Issue.
I can assign every other cc number to kontakt but no matter what I do the nanoKONTROL Studio will not send CC 21.

I have tried clicking on the Vibrato control, deleting its current assignment (cc 21), and then clicking Learn Midi, this works for ANY other number except CC 21
My kontrol Studio is definitely assignable mode and after changing the Studios CC Assignments in the Korg software, I chose "Write Scene".

Start Cubase, create a new project, insert an instance of Kontakt, load any Spitefire Strings library and the nanoKONTROL Studio Fader 1 sends CC 1 to Modulation (Dynamics), Fader 2 sends CC 11 to Expression but Fader 3 does nothing, nada...

Spitefire use the same CC numbers across all of their library's
1 Modulation (Dynamics)
11 Expression
21 Vibrato
Is there something that I am missing?

The Recording the CC Data issue.
In my project I insert an instance of Kontakt, and then Spitefire Studio Strings.
I write some notes in Cubase's Piano roll, play it back to make sure Kontakt is out putting sound.
In the main window, I make sure that the midi/instument track is highlighted/selected, in Kontakt I click on the library so that it has focus, then I click on Kontakts "write automation" button, start the track playing and move the nanoStudios faders.

It should record my automation but it does not..

Driving me mad, bloody bonkers?

It really should not be this hard to get answers especially from a world famous brand like Korg but I can honestly say that their UK support are the worst I have ever come across in 30 years of music production.

 

1.) Korg makes a program where you can edit the CC values.

Customize the nanoKONTROL Studio perfectly with the KORG KONTROL Editor.

The included "KORG KONTROL Editor" software can be used to assign the appropriate MIDI
messages to the faders, knobs and buttons for effective control of the desired functions.

DOWNLOAD: nanoKONTROL2/KORG KONTROL Editor2.0.9
www.korg.com/us/support/download/software/0/159/1354/

2.) [This tip is from another korg product, maybe it will help]:

Hi everybody finally I found it! I can use first fader as mod wheel, second fader as vibrato, third fader as expression etc. I want to help you. It was really simple. You dont need to assign faders, knobs or use different xml etc. First we need to donwload Korg editor to select our cc numbers which we want.

 

I've just tried it and (maybe) succeeded, without editor shenanigans; but it's quite fiddly, counter-intuitive and nonsensical. Wouldn't work controlling CC directly. Had to use QC. Ignore the QC on the inspector, and setup ur NK to control quick controls 1-8 in MIDI remote. Then go to Kontakt, and click on the (tiny) QC icon (top right). This should let you "learn" the controls you want to assign, within Kontakt? Honestly, not clear at all! Also: setting takeover to "jump" seems to smooth out the jitter a bit.

 

Last edited: Apr 20, 2022

Hi again BEAT

Sorry I should have said that I have the Korg Kontrol Editor and I used it
to place my nano Studio in to Assignable and change the fader CC's to those
which Spitefire uses...

 

You would have to try working with CC21 either in a different DAW or with a different
plugin to rule out a fault in the Korg hardware/software.

MIDI CC List – Most Common Parameters

• 1 = Modulation wheel
• 2 = Breath Control
• 7 = Volume
• 10 = Pan
• 11 = Expression
• 64 = Sustain Pedal (on/off)
• 65 = Portamento (on/off)
• 71 = Resonance (filter)
• 74 = Frequency Cutoff (filter)

NOTE: There is no standard CC value for Vibrato Amount or Vibrato Speed.
Sometimes you can assign them (and other CC mappings) yourself in the software instrument you use.
https://professionalcomposers.com/midi-cc-list/

MIDI Control Change Messages – Continuous Controllers
https://nickfever.com/Music/midi-cc-list

MIDI CC Chart for Spitfire Audio Libraries --> CC21 ?!
https://spitfireaudio.zendesk.com/h...18-MIDI-CC-Chart-for-Spitfire-Audio-Libraries

How do I reassign a fader on the Spitfire interface?
https://spitfireaudio.zendesk.com/h...I-reassign-a-fader-on-the-Spitfire-interface-

 

Last edited: Apr 20, 2022

How do I reassign a fader on the Spitfire interface?

• 2 years ago
  
• Updated

All faders on the Spitfire GUI can be assigned to a CC value of your choice. If you have a MIDI Controller you can customise these parameters to your own preference.

1) With a library interface open, find the fader you would like to re-assign. In this example, we will reassign Vibrato from CC#21 to CC#71.

2) Right click the fader on the interface.



3) You'll see that by default Vibrato is assigned to CC#21. First choose Remove MIDI Automation to unassign CC#21.

Following this, you can reassign the fader by selecting Learn MIDI CC# Automation.



4) It may seem as though the nothing is happening, however if you move the controller that you want to use you'll find that the fader will automatically reassign to that value.

 

I agree, the whole thing is counter-intuitive and Korgs UK Support simply told me to read the manual !!!!!!!!
which I have done cover to cover and it is of no use.

Searching youtube gave a few posts with users saying that Korg is of no use at all and nearly all relate to using nano studio in Logic....

I am going to go and give your quick contols suggestion a try, thanks for that/

 

If a control is assigned in the midi remote control (via the editor), it is no longer available to normal midi tracks, indeed only through the QC if you assigned those.
One time my mod wheel got stuck in the midi remote and it disappeared for normal use.

 

Do you have a Midikyboard ? You can also use your midi keyboard to assign CC21 to the modwheel or amother Knobs and Slider.

 

Midi CC Logic Issue? [Solved]

The plugin can only see the controller's value when it moves, so if there's no movement at the start of a region then the dynamics slider should just stay wherever it was left by the last change, e.g. by a previously-played region, or your moving the controller. If you start playback between two regions, then Logic will replay the earlier region's last controller change, so you'll start with dynamics wherever that earlier region left it... that is, as long as MIDI chase is enabled: "Project Settings", "MIDI" in the menu, "Chase" tab, "Control Changes" section, "0-15" checkbox (assuming modwheel is assigned to dynamics.)

If it's the first region in a track, then you still get whatever dynamics was last set to, but this can be a bit hard to predict: sometimes it'll be the value from whatever region was last played in full, but sometimes it'll be zero because Logic sends a reset, including modulation=0, when playback stops inside a region. You can disable this reset by checking 'no reset' in the track's inspector, but the start value will still depend on what you last played, so I don't find this helps much with consistency.

Best solutions I've found so far are: (1) adding a short empty region to the start of the track, to set initial values for expression, dynamics, vibrato, etc. As long as MIDI chase is working, any notes on the track will get those values until I add some controller changes - especially useful if I'm trying out regions dragged in from a different instrument, say. (2) If I'm recording, I also briefly wiggle the controllers as soon as I hit record, to lay down initial values. (3) Otherwise, I do what you do, and draw in an initial value!

https://community.spitfireaudio.com/discussion/1390/midi-cc-logic-issue-solved