Korg Nanokontrol Vs Nanokontrol2
Roxine Denison
I 've bought a Korg Nano kontrol 2, which I want to use in Premiere for easier audio control. I've set the support control service in preference. But nothing happen when I press any key in the nano kontrol 2 (actually the same when using in Audition).
I had a Korg Nanokontrol that I used in the past, and I remember having to select the "Mackie" interface. Premiere Pro doesn't list Korg as an option, but it does list Mackie. Please let us know if this helps.
We are editing the sound track on a feature and mouse and keyboard can be useful but I prefer an external mixer for such task, especially as I can use the various audio plug in for compression, delays and so on included in the software.
think i have found a solution to your problem. in premiere pro if you set device class as mackie, the type as mackie control the input and output device as the Nano kontrol. Then un plug the device, hold down the set and reverse button, plug it in whilst still holding down the buttons, the reverse button then should flash a couple of times and it should now work in premiere pro, for me the channel panner works smoothly, the transport controls work, the solo/mute and record buttons work and the volume slider work as well as all the LED lights on the control surface.
I'm considering picking up a nanokontrol2 for premiere- so let me know here if this winds up working for you: Have you tried to right click on the audio mixer panel and select: toggle control surface mixer mode? That opens the audio clip mixer in which you'd have to click the little keyframe button for the clip you wish to mix on and then hit play and slide the nanokontrol fader- when you hit stop, conceivably the keyframes will be there? Let me know if this works. thanks
I recently bought both the Korg nanoKONTROL 2 (usb only) and the nanoKONTROL Studio (usb and bluetooth), neither of which can I get to work with any DAWs (eg Cubasis (IOS), Cubase LE 11, GarageBand, NanoStudio).
Not only have I read the manuals, the forums and called Korg (pretty useless and only managed to get through the once), I got no reply at all from Steinberg.
I have worked with software and hardware for over 35 years and never wasted so much time.
I discovered in one posting that Korg uses a proprietary USB cable but that it looks to be identical to any run of the mill cable - can that really be true? If so, how do I know that the ones which came in my boxes are the right ones (i.e. not those from returned items?).
What a fiasco.
I see many, many posts of people having issues with recent Korg products and that is shameful from a company of that stature in the industry.
But with yours its as easy as downloading korg app. Then controller will be in aum. Then see if cable works. Heard also about the cables but not sure if it means its different for sending data when customising controller vs using controller. Every cable has worked when customising. Theres were sure to be a cable thats for charging a torch. Vapouriser. Ps4 controller etc but could be true what you are saying. I think with the nanokey ( yours is nanokontrol ) maybe theres more functionality when using BT vs wired? Or maybe that were just the arps. Maybe scenes though.
With the kontrol studio. Will be noodling but with sequencers and tweaking. Controller will be close. Will seem good to have 16 volumes and 16 mutes and solo. Like a mixer. Shame about no cue monitoring but mixer style will be good. Any other additional mutes and solo will be with the left buttons near the circle jogwheel. With a 2nd ipad dedicated for a couple of synths. The only prob is if you solo these synths. You would be soloing both synths ( if they are a stereo input in another aum ) but thats fixed with x 2 volumes mapped to another controller. Volume off when you you solo the other. So it seems that a wired connection ( if everything works ) would be better for use with both ipads.
I have both the nK2 and nKS and they both work fine with all my iPads. Both usb through ACC and nanoKontrol Studio via bt as well. All you do is just map them however you please in AUM and you're good to go. Tried Studio recently with CB3.3 and mapping worked as well although they don't have a factory profile for nanoKontrol Studio but just nanoKontrol 2 unfortunately.
I make it a rule now a) not to buy anything which has a micro usb to communicate and b) to fit the gear that I already have using micro usb with magnetic-end cables, so I can leave the usb doohickey itself. permanently in place to avoid stressing the ridiculously fragile micro usb connection.
@sdclee tons of people (including myself for the NanoKEY Studio) use these with iOS and all the hosts you mention. I can only speculate you may inadvertently be using a charging only USB cable. I've never needed to use a special cable from Korg with the NKS, but there are USB cables that don't carry data and are good only for charging devices.
Regardless of the USB situation, you should be able to use the NKS with Bluetooth. You have to go through the Bluetooth connection dialog every time you reconnect the device. You do not go through the normal Bluetooth device connection. You go through either the Korg BLE Midi app, or the host's Bluetooth MIDI dialog. I you did manage to "pair" the device through iOS Settings > Bluetooth, tell iOS to forget that connection before using the BLE Midi dialog to connect.
Since you bought these recently, I kind of doubt that you need to update any firmware, but it's possible. That's always a good thing to try because a year or more back there were problems with the Korg products after an iOS update.
Thanks for the replies - I didn't get notifications so I'll look into my settings. I was more interested in Cubase on the iMac than Cubasis on IOS even though I use both. I guess I was just unlucky but I think it's a very sad state of affairs when huge companies have no phone support (which I'd be prepared to pay for) and those which don't even reply to emails or form submissions (thanks for nothing Steinberg).
Once I'd read about the dedicated USB cable (true or false who knows) I gave up. I was using Korg's BT connectivity btw.
Anyhow, I've sent them back and moved on to more productive areas.
The Korg nanoKEY Studio (BT) I bought a few months ago worked straight out of the box so that was really the spur to purchase the other two products. Am I the only one who finds their naming completely and utterly confusing? Drives me crazy.
Appreciated - Cheers.
So I was kinda expecting a pain to set this up, but got it working with AUM seamlessly. The transport controls, sliders, button and knobs all mapped and working. Instead of using the Korg editor app to change the CC values I just used the AUM learn functionality to map the sliders and buttons etc. Cool!
I can confirm that the NK2 is a great DAW controller for Cubasis 3.3. Just set it up as a Mackie controller in CB settings and hold Set + Rewind when you connect the controller (I made this mode default with editor software). I used many different USB cables. I think only I once had a cable that seemed to be for charging only.
That's good to know but I would want it primarily for Cubase LE 11 on the iMac with Cubasis (IOS) with as a secondary use.
Anyway, it has gone back now so I'll have to wait until such time that someone can provide me definitive setup for Cubase LE 11, in which case I might consider buying one again (but not right now as I've just spent the money on a volca mix and volca 2x2 stand instead).
Hi all, I am operating a Pd 0.43.4-extended version into a macOS Mojave 10.14.6 64-bit . I tried to plug NanoKONTROL2 KORG following this patch & instructions -leo/pure-data-korg-nanokontrol-2 fixed the broken links to the abstractions, but the entry signals from the NK2 Korg are not recognized, only the potentiometers (and not accurately), but no slider nor buttons..
I wonder if any other had the same issue and succesfully solved, or if any clue about 64-bit or Pd version being the potential issue...
Ps: My Nk2 is detected and works on MaxMSP7, so I guess the Nk2 nor port comm are the issue...
The patches are very simple control routing. There are no executable objects apart from [ctlin] so it will all run in Vanilla if that is necessary.
I understand that in later 64-bit OSX no 32-bit executables will run. Maybe that is not the case for 10.14.6 if you have extended (32-bit only) running?
@Maelstorm posted this 10 years ago. Very pretty, and maybe still valid....... nano2.pd although the [ctlin] numbers are different and so have probably changed from the original NanoKontrol.
That should be easy to change though.
David.
2 -"Maybe that is not the case for 10.14.6 if you have extended (32-bit only) running?" I can do run other patches and even the ones which serial communicate with my Arduino, etc.. but I am blocked with this one (I also upgraded MacOS almost at the same time as starting this tryouts.. that's why I am suspicious of this)
@hybridoa I was thinking maybe a factory reset of the NanoKontrol, or a reset of whatever its driver might have changed for its setup.
If the data is not arriving into Pd the problem is elsewhere I think.
The Data "jumping" I have seen elsewhere on this forum and others....... along with some other Midi weirdness from the NanoKontrol2.
For other Midi controllers it really depends what you want to do. For DAW or lighting console work the BCF2000 is a good cheap option, because it can be more accurate (NRPN) and has motorised faders....... but midi controller setup is far more complex than it first seems and can be a steep learning curve unless the software you are using has built in templates for its setup.
Sysex is difficult in Pd....... anything can be done of course...... and because we are building very bespoke systems from scratch there really is very little plug'n'play available.
David.