Korg NanoKontrol 2 and Fairlight in DaVinci Resolve


I bought a Korg NanoKontrol 2 to use with Fairlight in DaVinci Resolve.

I can get all the controls to work except the fader controls, which is ironic, as these were the reason that I bought the machine in the first place.

I am a total newbie when it comes to MIDI. I have created a project in Bome MIDI Translator Pro, but all that I have done is connect the Nanokontrol to the Translator input, and Fairlight to the Translator output. This has already had the effect of making the pan controls much less sensitive, and thereby useable, but obviously, has not resolved(sorry!) the issue of the faders.

I saw it written that Fairlight requires a 'Touch and Release' command when the faders are operated, but that the Korg does not supply this command. please could you explain this in terms that a total newbie would understand?



Indeed the Korg NanoKontrol2 does not send touch and release as I discovered a few months ago. The below project file simulates that behavior for the Korg NanoKontrol2 (and many other controllers that have partial Mackie Simulation).

The solution involves the following:

  1. Set up the project aliases for your My Controller to Korg NanoKontrol2 and output alias Davinci Resolve to Bome MIDI Translator Virtual 1 Port (In Davinci resolve this should be set as BMT1)
  2. Set up a default project path from My Controller to Davinci Resolve. This will allow all messages from your controller to pass through to the application
  3. Set up 3 translators. Fader Touch, Fader Release, and Timer

The first translator (Fader Touch) looks for any fader movement from your controller and sends a “fader touch” message for that fader to your application. Davinci resolve requires this to move faders.

The second translator (Start Fader Release) looks for the same incoming message and starts a One-shot timer for 500ms (1/2 second), called “Start Fader Release”

The third translator is the actual Fader Release timer and when it completes, will send a Fader Release message for the appropriate fader to the application.

So as long as you are moving a fader, the touch messages are also sent to your application. When you stop moving the fader, the release message is sent after 500 milliseconds.

There are rules in each translator that handle the calculations on which fader is being moved and which touch message to send.

I use the global variable ga to indicate which fader is being touched. The timeout period of 500ms is controlled in the variable gb.

I set the global variable gb at project start and if I hit my computer <ESC> Key. This is done within the INIT preset.

Please find the attached.

Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist



Super, yes, I didn’t really focus on LED feedback.

I did notice however that if I send a touch, it keeps sending it over and over as you move the fader. If you set up a variable like gc and set it to 1 when you move a fader and then set it to 0 when the timer executes you can put in a rule to look and see if gc is a one and not resend fader touch if it is already set. This will reduce fader touch traffic.

At the beginning of your fader touch, you would put
if gc==1 then exit rules, skip outgoing action

Toward the end of the same transator you would out

then in your timer rules you would put


And that way you only get 1 fader touch message until the timer trips with fader release.


Hi Steve, Thank you very much. The faders now work fine. It has turned the Korg from an expensive doorstop, to an inexpensive, and very useful tool. The only mod that I have made is to open Bome Virtual Port 1, and route it to nanoKONTROL2 1 CTRL. This, I believe, has given me back the LEDs, such as the tranport, solo, and mute, which did not light up originally.