NI wants users to get into their ecosystem and stay there. Yes, it is not friendly to projects created without KK or to non-NKS plugins (including all the native devices in any DAW, not just Logic). Super cumbersome when introducing the M32 to any project that has been created previously (and what if you move to a different controller at a later date.? )
I have to let this all sink in before I even try to formulate an opinion. This method seems very invasive, for lack of a better word, and super cumbersome when introducing the M32 to any project that has been created previously (and what if you move to a different controller at a later date.? ) As some have pointed out, I kind of get the sinking feeling that weaving Komplete into my workflow can be potentially hazardous.Wow. So I guess if you have a project your'e already working on, before you got the NI-controller, you have to then delete the synth you've been using, put KK in it's place and then find it through their GUI. NI's method is such an anachronistic concept that the thought never even entered my mind. Soooo.basically I've been tearing my hair out for three days, to discover that it was working all along. I was thinking you only needed to do this when working with Kontakt content, and that otherwise the "wrapper" would wrap around the whole of Logic, just kind of running in the back ground. You "just" have to open Komplete Kontrol as the Instrument on each and every track - and then go through that pretty non-inviting menu system to reach the instrument you want to use. I haven't done anything more custom yet as I don't need to (I have those things covered by my own bespoke controller system), and the A49 works great in combination with that. Other than the regular MIDI functions, you can in "Track" mode control volumes/pans, control the transport and location, change tracks etc and it's a nice little unit. The A49 works pretty nicely as a controller for Logic. I can go into the various reasons why, but basically I don't use it. Komplete Kontrol is, from my point of view, on the Mac, a clunky under-delivering system, and having tried it for a bit, realised it (and the whole concept) just doesn't work at all for my needs. (They go through all of this in the setup instructions.)
I find that often the plugin lost contact with the keyboard and required a manual reselection more often than it should.) Once the plugin is running, you have more options and the full keyboard functionality should be there. Once here, you have the control surface working, but to use the full system, you need to load the Komplete Kontrol plugin, and make sure it's *connected* to your keyboard (there's a little icon to show whether the keyboard is connected). Once this is done, you can quit the app, and go back to Logic. So quit Logic, run the app, and make sure the keyboard is seen (it should happen automatically, but you might need to give it some help). You need to run Komplete Kontrol the app as the standalone app *at least once* before it will work in your DAW. Once mine was seen, I've had no problems with it.įor the OP - it seems like the keyboard *is* recognised, as you have transport functions working - so that's good. Try a few times, and Logic will I'm sure eventually see it and add it as a control surface.
Unplug and replug the keyboard, both when Logic isn't, and is, running.
Run Logic, with and without the keyboard connected, with and with Komplete Kontrol running Running Komplete Kontrol, and making sure the keyboard is seen You might need to futz around a little to get it going.
I did have a little trouble initially getting it seen by Logic as a control surface. I have an A49 as my "right next to the computer" keyboard, but it's essentially exactly the same as the M32.