timrfrench61

planetearth

Anderton

Actually, I doubt it's a bug in X2. I tried using the nanoKontrol2 as an emulated Mackie Control in Sonar X2, Studio One Pro 2.5, Ableton Live 8, Acid Pro 7, and Vegas 10. It didn't work with any of them, yet other Mackie Control emulations (e.g., Samson Graphite) work with all of them. It could be that I'm not using the proper DAW control mode (the "hold down set marker + something else" thing), but shouldn't a Mackie Control emulation be the same, regardless of what DAW you use?
I'm using a 64-bit system, so maybe that's the issue.

That is surprising, actually. And yes, you'd think emulation should be the same, regardless of the DAW mode. All I know is that I re-installed X1 (without so much as disconnecting the controller that didn't work with X2), and voila! It worked flawlessly as soon as I opened X1 for the first time. I didn't even have to configure it. Admittedly, some of X1's entries were probably still in the Registry; Revo Uninstaller doesn't remove everything. Still, it's nice when things just work.
 
Frankly, between this latest "wrinkle" and X2 using much more RAM...and not being "supported" with or updated for Windows XP/32-bit OSes, I've gone back to X1 until I can afford a new PC. I like what X2 appeared to offer, but there were too many problems.
 
Thanks for trying, Craig, and good luck with your Kontrol/controllers. (I can't imagine the amount of hardware and software you must troubleshoot each month in your work. It's a wonder you get anything done at all!)
 
Steve
 

Steve, have you ever run 2 nanoKONTROL2 units successfully in X1? I have been trying to getting in X2 on Win7 and get 1 working but not 2 (and I keep seeing Corrupted Korg drivers in the Korg Delete Driver utility so I still have plenty of troubleshooting).
 
Glad I found this discussion.

No, I haven't run 2 nanoKontrol2 controllers in X1. But make sure you have the latest drivers for it/them, and that you've applied the firmware update. These steps won't necessarily fix the problem you're having, but they can't hurt.
 
You might also want to remove all traces of the Kontrol2 from Windows' Device Manager. The best way to do this is to make sure you're showing all of the "non-present" devices. (You'll be surprised what shows up when you view everything that's accumulated in there.) Simply choosing "View / Show hidden devices" in Device Manager isn't enough.
 
A quick Google search for "show non-present devices windows 7" will give you the steps you need to display basically everything that's ever been connected to your PC. You can safely delete any "ghosted" Kontrol2 entries--after you've uninstalled the driver and disconnected the controller. Then you'll have a relatively clean Registry, and you can re-install the latest driver.
 
Good luck!

Yes I have 3 of the korg nano faders working properly on x2. I had to hit the korg forum to find out that there is a 10 midi device limit in win7
I then had to run the korg uninstaller and deselect the unused midi devices to get it under the 10 device limit. After this Sonar X2 found the midi controllers and I was able to map them using the generic cakewalk controller mapping. But yes they do indeed work with X2.

http://www.korgforums.com/forum/phpBB2/viewtopic.php?t=63238&highlight=device+limit

I hope this helps

I'd head over to the korg forum and check on the 10 midi devices limit for Win7. This one stumped me for days. I had to run the korg uninstaller and uninstall the empty midi devices to get it under the 10 limit. I now have 3 of them running fine in X2a for 24 tracks of physical fader mixing.

redbarchetta


Hi bandso,

I want to make sure we are on the same page here.... When I say faders, I'm talking about the individual faders on the unit itself.  From your last post, it would lead me to believe when 'you' say faders, you're referring to a fader as a whole unit. 

Which if you're stringing three of them together for a total of 24 individual faders?  Hey, that's really slick.

I don't know about 24 faders--I can barely tell the difference between these non-numbered faders when I'm looking at this thing in a dimly lit room. Multiply that confusion by 3 and you're going to find yourself hitting "Undo" quite a bit!

Ok I made a crap cell phone video and posted it to youtube.
http://www.youtube.com/watch?v=Tr7TBB8TrTU

This isn't a tutorial or anything, it's just a quick video to show that these will indeed work with x2a. First I show the x2a build and then I move my hands on the controller and show the fader movement within sonar. Then I go on to perss some buttons, panning, transport...ect... 

A couple of quick notes.

I had to start the kontrollers in "CC" mode not mackie.

Once they were found properly by sonar's midi devices I had to assign them as a generic cakewalk controller.
Then you "build" the generic controller controller preferences map. Once you have the map set up for one kontroller, it's pretty easy to assign the second controller to faders 9-16 and the third to 7-24

I'm really hoping I'll get some time in the near future to do some kind of a tutorial on the setup of these units because they are really fun. Until then I'd check out youtube.com for tutorials on using ACT and Sonar's midi "learn" feature. Once I learned some about that, I was able to tinker around and get it working as a generic controller.  I used the learn button on the generic cakewalk controller preferences to map volume/panning/etc to faders/buttons 1-8.
 
Good luck guys, I really feel your pain on this one as I had all of the install issues that everyone else had. I just wish I had more to offer right now as help, because the video really isn't any.