Nanokontrol2 Logic Pro X
Ashely Wolfgram
I recently purchased the Korg NanoKontrol2 control surface to control my Logic Pro tracks in DAW mode. However, I am struggling in order to use it in the "DAW" mode instead of the "CC" mode. The transport buttons are working fine. However none of the individual channel strip buttons including the fader, knob, solo, mute and arm button are working for the individual tracks. As per Korg manual, by default it is supposed to control a set of 8 tracks, and it is shown by a white line marker beside the tracks.
Also, have you tried deleting and re-establishing connection to it in Logic Pro X? Please read this article for more: -control.net/community/threads/trying-to-set-up-korg-nanokontrol-studio-w-logic-pro-x.92716/
Thanks so much for your response! Actually I installed the plugin that you mentioned, but it did not help. Even I uninstalled and reinstalled it as per the Korg documentation provided with the plugin software.
I also followed the steps mentioned in your community forum link, like resetting the device etc, without any luck! Only way it is working is by choosing "Mackie Control". However, the track buttons are not working in this scenario to navigate between individual tracks.
Thanks once again for the help! However being a complete novice to the control surface assignment and "learn mode", I find the link to be too fuzzy. Just tried by going into learn mode and pressing the Nanokontrol "left" and "right" track button and the "up" and "down" arrow key button in the track area. However it messed up the existing track assignments.
I must say a "BIG THANK YOU!" to you! Thanks so much! I followed the steps as you mentioned and it solved the issue completely. Feeling so happy! Now am able to navigate through the tracks as well as use the track slider/knobs to control the track parameters.
I am using Behringer since month and I like it.
I started with vjoy and freebie. This solution simply emulates keystrokes, even the rotary knobs, all keyboard events in simulator can be assigned to 80 knobs.
This solution is not very flexible if you want to have some logic, e. g. Fast press on the rotary does something else as a slow press. Different mappings per plane are not possible.
Next solution was AAO, the Autor is very helpful and busy here in this forum. This solution is more flexible. You may program logic. The so to say disadvantage is you must hunt for simconnect events. Some are easy to find some not, some are not really working. These problems have nothing to do with the AAO solution.
The third solution I tried was a python script found on github. -touch-Mini-Fs2020. Also very flexible, different plane settings. In the meantime this is my favourite. You need a little bit, but not much, python and coding to setup your favourite settings. Here also you have the problem to hunt for simconnect events. Try and error. Some people offer there configs here in the forum. For all three solutions a lot of G1000, g3000 buttons are missing. We all wait for the group andpage buttons. This visual cues are not useful or better meaningful. Most rotary buttons you will use for NAV, Com Radios or Altitude or Vertical Speed.
I decided to go with Axis and Ohs (AAO) because of the flexibility it offers. Oliver is very active with the Sim community and has already contacted me on using the rotary encoders with his product. Another advantage is you configure/bind all the controller inputs through AAO and no need to go through brain dead MSFS2020 controller settings page.
the HTML variables live outside the legacy simulator variable&event logic. They are not accessible with SimConnect. You need a WASM module running inside the sim to operate them. Which is what comes with AAO V2, plus a scanner to read the existing HVars (and LVars) from your simulator. They can change at any time, and every MSFS update can bring new ones.
I purchased Korg's NanoKontrol2 to use with Cakewalk CdB as a simple control surface for recording my practice sessions. Basically, I got tired of using my mouse and keyboard to control the application's faders and transport controls. After a few missteps at getting the controller to sync up with Cakewalk, I finally got it to work as designed. And I gotta say, this controller works quite well due to it's simplicity.
First, I did a lot of research around control surfaces, MIDI controllers, Mackie controllers, and how they can be integrated into your workflow with ACT, AZ, CdB's General MIDI controller, Mackie. We're talking hours and hours and hours.
My baseline was trying to get my M-Audio Oxygen 61 mkIV to work as a controller. It took even more hours to figure out how to map it with ACT (AZ was a bit too complicated) to get it to work. I ended up using the MIDI Learn function by right-clicking whatever fader, button, rotary to enable the Remote function. That worked well enough. I swapped out the Pan control for Gain, and even got the master fader to work without much hassle.
The only thing about the Oxygen 61 is that it takes up a lot of desktop space. That's why, after a lot more research, I settled on the NanoKontrol2. It's small, simple to setup with the Mackie controller (I'm using msmcleod's Mackie controllers) once you update your PC to Windows 10 S1H2.
1. Update Windows 10 to S1H2 update. Don't even try to start using the controller without doing this first. If you don't, have a couple bottles of aspirin on hand. Be sure to restart your machine after the update is installed. Don't install the driver until after you've done this.
4. Once your machine is up and running, open the Unistall Korg USB-MIDI Device utility from the Windows Start menu. No. We're not going to uninstall the driver. We're going to make sure that the NanoKontrol2 is listed in the first 10 MIDI ports (MIDI0 through 9). If it's not, it's most likely listed in the next ten. If the controller doesn't show up in the first 10 slots, you'll have to remove one device from one of the slots. This video explains what I'm talking about:
7. Go to Control Surfaces and add a new MIDI controller by clicking the funky yellow button in the upper right-hand side of the Preferences screen. Select Mackie Controller or MMcL Mackie Control #1, if you installed it. Associate the NanoKontrol2 with the controller's input/output ports and click OK.
8. Create a new project and insert a new track or two or three or whatever. Test the controller on whatever track you want. If you want to use the Master bus, hold down the Cycle button and press the right Track button. To go back to a track, hold down Cycle and press the left Track button.
There you go. Keep in mind that my needs are simple as I'm just recording practice sessions and not doing much in the way of production. At some point I'll figure out how to control T-Racks5 plugins and the like as well as VSTi. But that's for a later day. I'll probably get another NanoKontrol2 for that purpose.
Original Mackie Control ( -pro-and-xt-pro) has many non-strip buttons (on the right side of strip controls).
What these buttons are sending is fixed, but what they supposed to do is particular DAW dependent. There are overlays for each DAW, f.e. -mcu-midi-controllers/lexan-overlay/g-10000205 (note there is a separate Cakewalk overlay).
Mackie "compatible" devices (NanoKontrol2, Studiologic SL Mixface, etc.) do NOT have all buttons the original device has. They have decided which buttons are most important in particular DAW. "Cubase mode" in Cakewalk surface plug-in tries to use Cubase layout for Mackie Control. So "most important for Cubase" buttons are likely mapped to the corresponding functions in Cakewalk.
Original device has motorized faders, encoders and strip displays. Tiny (but in SL Mixface case not really cheap...) "compatible" devices have finite knobs and not motorized short faders. So not only big part of foreseen functionality is not possible at all, what is controllable does not work as foreseen by design. Motorized faders and encoders are always "at correct position", finite controls are not.
I mean if you want quickly mix 8 track project by adjusting the volume and pan (and only that), especially if the intention to do this live, SL Mixface will do the trick.
If you want control one instrument in a time (MIDI learn inside instrument, rarely switching between instruments), SL Mixface can help as well.
For anything else there are better options, even for the same money and size.
After doing some more research (and talking with Sweetwater some more) I settled on a Korg nanoKONTROL Studio Mobile MIDI Control Surface. Got it for $161 including tax. I'm hoping I didn't screw myself. What is your opinion on this unit? From what I can tell, I should be able to access more than just volume and pan. Am I right?
Note that with any controller you can use "not official" AZ Controller way. By that you can control whatever is theoretically possible in Cakewalk, for example switching the controller between DAW, plug-in dynamic mapping and MIDI learn in VSTi from the controller itself, assigning arbitrary functions to all controls and combinations, etc. But since I don't have this device there is no ready to use preset.
93ddb68554