Hi Everyone, I'm using Sonar Professional. I recently picked up an older Korg NanonKontrol
for a couple bucks to see how well it worked before I went out and got a nicer surface controller.
But, it doesn't seem to work at all.
Sonar shows the device installed as an input, and has power.
I've also downloaded and installed the software for it and read the manual.
I'm sure I've done soemething wrong but can't figure out what it is.
 
Any help would be appreciated.
 
Gary

To check it is configured right, delete all control surface plug-ins from Sonar preferences and try to record a midi track with nanokontrol as input. Press buttons, move sliders, etc. Is something recorded?
 
If yes (otherwise you have problems with drivers / windows MIDI devices, not Sonar specific and "popular"). NanoKontrol has "Mackie" and "Midi" mode, switchable on device (see manual). You need correct mode for particular control surface plug-in in Sonar. Simpler to start with "Generic surface" and MIDI mode (see sonar reference guide how to configure).

Thanks, I will try that.

If this is the original NanoKontrol (9 channels, with fader, pan and two buttons on each channel), you will need to go in and set up each channel. It is a bit of a pain, but once you get the hang of it, it progresses quickly. The nice thing is you can select what you want each button in each channel to be (for instance, you can make the top button a channel record, and the bottom button mute - it really is your choice). The other thing is that it gives you 4 scenes, for a total of 36 channels. Mine controller was white with blue trim, and since I have trouble working with multiples of 9, i used a fine tip marker to identify the other three channels, based on the scene (so channel 1 is also channel 10, 19 and 28).
 
Hope that helps.

MandolinPicker
If this is the original NanoKontrol (9 channels, with fader, pan and two buttons on each channel), you will need to go in and set up each channel. It is a bit of a pain, but once you get the hang of it, it progresses quickly. The nice thing is you can select what you want each button in each channel to be (for instance, you can make the top button a channel record, and the bottom button mute - it really is your choice). The other thing is that it gives you 4 scenes, for a total of 36 channels. Mine controller was white with blue trim, and since I have trouble working with multiples of 9, i used a fine tip marker to identify the other three channels, based on the scene (so channel 1 is also channel 10, 19 and 28).
 
Hope that helps.

If someone really wants to spend time for NanoKontrol, there is AZ Controller. I don not claim that is easy, but I am available to help. Just to mention some (far from all possible) advantages (for NanoKontrol2, but some apply for 2 buttons version as well):
* LEDs can indicate current situation
* a "shift" modifier (and more if required) can be defined, to extend the number of controlled parameters (f.e. +3 buttons pro strip, like "select/echo/automation arm", still with correct real-time LED feedback)
* controlled strips range can be arbitrary set, including buses (f.e. 8 tracks + 1 bus)
* faders and knobs can be used in different modes, in addition to usual "absolute" and "catch", there are "instant" with non linear curves and "endless emulation" with arbitrary precision (with "shift" it is possible to combine modes, f.e. "instant convex" for coarse and "endless fine" for precise adjustments)

I have one of the older NanoKontrollers. Picked it up on a M/F stupid deal of the day as I was having problems with a Behringer BCF2000 I had at the time.  Had to manually set it up in Sonar and got everything set except (I think) fast forward.  I still have it but don't use it as I bought a new Behringer X-Touch.
 
This is an old setup procedure, may still work. 
http://untidymusic.com/midi/setting-up-nanokontrol-sonar
 

@Fireberd - nice tutorial! - 
 
One questionthough... why did you use ACT for transport control? I'm sure there's an option on the  generic surface for GLobal parameters - whats different about this approach?

I didn't use that tutorial, I used a different one (that I can't find now).  But, I just did what the tutorial instructed and it worked.  I think I tried or at least looked at the other options and didn't find anything that would work until I found the instructions on the web.  It took a little time with all the manual programming. 

Elffin
@Fireberd - nice tutorial! - 
 
One questionthough... why did you use ACT for transport control? I'm sure there's an option on the  generic surface for GLobal parameters - whats different about this approach?

That approach (with 2 plug-ins) is looking for troubles in case there are any MIDI tracks with "Omni" input in the project. F.e. all assignments from Generic Surface (Notes, CC) will leak into MIDI track. If by bad luck some CC is interpreted withing Soft/HW Syth, you get (normally invisible) sound change. I mean you play life/record piano and has decided to lower drum volume with corresponding fader... and you change the sound of the piano. I have not checked recently, may be already fixed (but unlikely). Also prior 2017.1, having 2 CS plug-ins was the killer for ACT Learn. I mean Sonars was corrupting the mapping file every time it was saving that file.