KORG nanoKONTROL 4 Mixxx

Hello Guys,

I’ve just finished the mapping for my Korg nanoKONTROL with the basic functions.
It doesn’t have any advanced features… maybe for the next version.

What You get:

[]nanoKONTROL Scene data file[/]
[]nanoKONTROL Mapping for Mixxx (xml)[/]
[]A nice skin for your controller[/]

I hope you can enjoy it, and that this came part of the final release of Mixxx 1.9.0 :sunglasses:

Last, I want to thank the developers for this GREAT piece of software!!!

Merry X-Mas to all :smiley:

EDIT: This configuration is now part of Mixxx since version 1.11.0

nanoKONTROL-4-Mixxx_v2.zip (26.6 KB)

Nice work - will try this tonight! Will have a think about what could be done using the scene switching button too!


The problem with the scenes is that when you switch them, the korg dosn’t keep the status of the contollers once you return to the previous one :frowning:

I think it should be better to find the way to configure one button (maybe the REC one) as a shift, to use with the other controlles and gain more functions.

Don’t have much experience with Javascript yet - I’m from a C++ and VB dabbling background. Is there any way the values could be written to persistent global variables?

Oh hang on - I’ve realised what you mean: what happens if a control gets moved ‘in’ another scene - there’s no way to get it back to what it was in the previous scene. Faders anyway. But the rotaries are endless aren’t they [writing without it in front of me] and the buttons would be OK so how about variable for these and just don’t touch faders :slight_smile: !

Well, I don’t have any experience at all of JS. But the explanation and examples are in the Wiki, so I hope I’ll get into something… it’s not rocket science, right?
Here is another contribution from the user Puddy that is using scenes. Have to take a look to the config/js files.

Yes, as the nano doesn’t have motorized sliders (like a Nord Keyboard) or endless knobs (like the APC40), there is a physical problem on changing “scenes”.
Besides, the buttons configured as “toggle” (they remain light when you press them), reset when you change scenes.
AFAIK the nano doesn’t have a MIDI-IN, so you cant reset the button previous status. Please, let me know if I’m wrong on this!!!

A combination of keys/buttons con the controller will allow us to reach more functions.

Thanks for your support!!

Actually, each button can be configured for toggle or temporary operation in the editor.

The only buttons configured as “Toggle” are the Headphone monitors (deck A & B) and the user assignable F1 and F2 buttons.
Rest of the buttons were left default.

Well… it didn’t get into mixxx 1.9 :cry:

Maybe in the next release :smiley:

I’m having trouble getting the kontrol to sync with mixxx. not only is there no response when i move a slider or turn a knob but after a little bit mixxx freezes and i have to force close it. I am running 10.6 and have all of my drivers up to date. I am also running mixxx 1.9.

I saw a similar post to this one but it was a few versions old and i thought maybe the problem had been fixed. I’ve deleted and re-pasted the midi files as well as deleted and re assigned the midi mappings for the kontrol but still nothing. thanks!

Hey epoxi,

I dropped the ball on this, really sorry! Getting it in the next 1.9.x release would be good. How do you suggest we package it? I assume the mapping doesn’t just work if you don’t have the Korg scene file loaded? Maybe we need to add a way for a mapping that’s loaded to pop-up an informational dialog to let the user know that they need to do something before it’ll work. Otherwise we’ll get a bunch of people being like “The NanoKontrol mapping doesn’t work”.

I think we should make a wiki page for the nanoKontrol – somewhere where people can download the PDF and the scene file. The mapping XML can ship with Mixxx, but we don’t have a good way to point people at the PDF and Korg file, since it will be installed somewhere crazy like C:\Program Files… or /usr/share/mixxx/res/midi/ etc. What do you think?



You’re absolutely right. I didn’t think about the Korg scene file! Without it, some buttons are not going to work properly.

The pop-up dialog sounds great. I could tell the user where the required files are (URL or docs directory). The wiki page is not a bad idea at all! Found that there’s already a Hardware Compatibility Matrix (mixxx.org/wiki/doku.php/hardware_compatibility).

The second option is to leave the scene “as Korg’s default”, and remapping the controller in Mixxx. This way, we’ll swap some buttons from “toggle” to “button” loosing the lightened effect when pressed. Maybe this is best from a plug’n’play point of view :wink:


You should put the scene file and mapping in a zip and upload to the forum. I want to try this out.

Just look at the first post :unamused:

haha, sorry, stupid post.

Thanks for your work!!!

Hi guys,

Has there been an update to this? I also have trouble with the files. The data is written on the nanoKontrol and the xml is copied to Mixxx’s midi folder, but nothing happens when I try to use the nanoKontrol. Please help.


Hey BB,

Check first if the nano is correctly detected by your sytem. Use the config wizard for that.
It should work.
Then you must select the template fromthe drop down


Anyone using this mapping on a Mac Book - it works perfectly on my Windows laptop but cannot get it to work on the Mac, which has a much higher spec and would make for an in the box gigging solution!

Any thoughts or tips to get it working most welcome.

Many thanks!

DId you install the Mac OSX USB-driver for the Korg NanoKontrol?

Thanks Jus - working perfectly now. :slight_smile:

I just added this preset to Mixxx 1.11.0 with the warning in the description that you should download the scene file from the forums and load it. Thanks ePoxi!