Komplete 13 Select
Cora Synder
Hello, I have no idea how cubase select the bank to determine in what order the channel tracks will be linked to my 8 knobs on my m32
I setup the m32 like the tutorials instructed
But for some reason, the white line that is to the left of the track does not represent at all the order in which my 8 knobs are assigned to the mix faders
Have you both tried to use the MIDI Remote feature ? Maybe there are already existing scripts for the m32 device : I think that there is a post from @steve which gives the link where you can check that.
@bensmir.hbs : even with a six months delay, there is still a Selected track category in the actions available in the Functions browser of the MR Mapping Assistant. You should be able to find what is needed in it.
However, Komplete 14 select does give you a strong set of assets in your toolkit to spark new ideas and take your tracks to the finish line, along with a nice selection of effects and instruments to boot. You can get all the details on Komplete 14 Select here.
As part of the Native Instruments merger with iZotope a little over 2 years ago, we are now starting to see the fruition of this companionship with the inclusion of Ozone 10 inside the 3 uppermost bundles of Komplete 14.
A new version of KK from a month ago, claiming to bring M1 compatibility, prohibits Battery 4, Reaktor and some instruments that require the Reaktor envelope from loading. These instruments will be M1 compatible in Q1 2023... The NI response is to start Logic via Rosetta in the interim. Furthermore, some NI hardware like the Kontrol M32 and Maschine Mikro (I own these) will also act sporadically if you run Logic in Universal M1 mode - essentially there seems to be an issue with the OSC Driver/App. This means when you choose to run Logic in Universal M1 mode - because maybe you're not planning to use Battery or Reaktor - you'll still have issues with the Logic integration from your NI hardware.
I'm no expert, but this seems odd. I'm told to run Logic via Rosetta, so I can run an M1 compatible version of Komplete Kontrol, that doesn't seem to support Logic integration from NI Kontrol M32 hardware? Confused yet?
Yesterday, NI release a free instrument 'Hypha'. I download it, install it via Native Access. I start KK in standalone mode, select Hypha and get "Cannot load Plugin" message. Clearly nothing to do with Logic. Thanks for nothing!
During the install, I notice a new version of Komplete Kontrol v 2.8.1 released a few days ago, and a new version of Maschine 2 so I install them optimistically. I reboot. Even after this, the problems with loading 'Hypha' persist.
It would seem, to use Komplete Kontrol in Logic, you must check the switch to run Logic via Rosetta (as much as I hate this). Second, in order to have stable NI hardware integration with Logic, it must start via Rosetta, even if you're NOT running any NI instruments or software in your project. Yetch!
I can't seem to get a straight answer from NI on the optimal configuration. What version of KK works? Why is running Logic via Rosetta necessary for the Kontrol M32 Logic integration? Is anybody else having these issue?
One thing that makes the whole thing doubly confusing for us to troubleshoot is that at some point Logic started to have a AUCompatibilityHostingService - which is basically a Rosetta AU Wrapper. So even if you have Intel only plugins they will open when running Logic native. That's why we think stuff is native when behind the scenes it gets wrapped. The stability of this wrapper is kind of bad in my experience. I will definitely get crashes.
On top of that I think sometimes that wrapper opens the Intel version of a plugin even though the native version is also included in the component. Perhaps some misconfiguration on the plugin side... or who knows...
It's a transition and like last time 16 years ago (wow...) it will take a little time. Probably longer this time because in 2016 a lot of developers knew how to write for the x86 architecture already and could more easily adjust their IDEs whereas now if they are not a mainly Mac developer (like NI is or very much appears to be...) they actually have to do much more work and we're seeing the consequences of it. I don't even know if you can in fact develop at all for Apple Silicon on Windows.
One more cool thing in Unify is that when saving a custom preset, you can save one which has the instrument as Komplete Kontrol, and within Komplete Kontrol you can have Kontakt, and a Kontact instrument already loaded. In just a click of the Unify preset name the patch comes up and your Komplete Kontrol keyboard lights up according to the patch in Kontakt. So that's amazing!
This feature request is to have some way in Unify to be able to activate whichever Komplete Kontrol layer you need to by clicking on the layer so that the lights and control knobs talk to Komplete Kontrol based on that activated layer.
One of the limitations of Komplete Kontrol is it does not allow for layers. The same issue occurs when layering in a DAW. Only one layer can be actively controlled by the knobs at a time. To switch which layer is active you will need to select the layer in Unify and open the editor for KK. There should be a little piano icon at the top. Click it to activate and this layer should now become the new controllable layer.
Layering will still play all layers with the keyboard, but KK allows only a single active instance (controllable with the knobs) at a time and they don't make it easy to switch without some manual intervention.
So in a DAW (not Unify), if you create four tracks with four separate KK instances, you can only open the GUI for one instance at a time? How do you set which one is connected to the controller knobs/lights?
When using Komplete Kontrol within a DAW, selecting the track SHOULD switch to the new instance of KK. All knobs/lights will relate to the KK instance on that track. That is how it works with the KK host-integrated DAWs such as Ableton (I forget the others). It's super slick and works very well. Within Unify, it should work the same way. If a Unify patch contains a single KK instance, then the KK keyboard knobs should control just that one instance. I wish I could verify this to be sure. I may not be able to check this out until Monday night. But I feel this is how it has worked for me within Unify.
The issue comes when attempting to layer multiple instances of KK in a single track. This is similar to layering multiple instances in a Unify patch, which I think might be the original question. Only a single instance can be the "active" instance at a time. Unfortunately, even clicking on a layer in your DAW or within a Unify layer will not make it active. You have to actually enter the KK instance (edit), and along the top will be a little keyboard icon. You must click on that to tell the system "this is the layer I want to be active on my KK keyboard". Then the knobs/lights will relate to the newly selected instance. This has been a long running request to allow KK to handle multiple layers.
But...this is a BIG benefit of Unify and was one of the first things I tried out when I got Unify. You can define the 8 macro knobs to control specific parts of each layer. For example, you can define Macro 1 to control filter cutoff for what is on layer 1. Macro 2 can control an overdrive for layer 1. Macro 3 can control a parameter (or more) on layer 2. And so on. You can then save this as a USER preset in Komplete Kontrol. This is not quite the same as the pre-defined knob controls Native Instruments has provided, but it does allow you to control parameters across the layers, up to a maximum of the 8 Unify macro knobs. For me, and many others, this is the solution we have found to give us the ability to control multiple KK layers with knobs. This does not resolve any issues with lights, though. If you want to see lights for keyboard splits, you will still need to manually set which instance you want to be active.
Once Unify adds more macro knobs, the amount of control over the layers will increase, allowing for even more in-depth control over the separate layers. I highly recommend if anyone is having problems with Komplete Kontrol's handling of layers, to check out Unify as a solution.
...Unfortunately, even clicking on a layer in your DAW or within a Unify layer will not make it active. You have to actually enter the KK instance (edit), and along the top will be a little keyboard icon. You must click on that to tell the system "this is the layer I want to be active on my KK keyboard". Then the knobs/lights will relate to the newly selected instance.
So you're saying there's a manual way to choose which KK instance connects to the keyboard lights/knobs, and some kind of magic programming trick that NI-blessed apps can do, to effectively click that "little keyboard icon" for you at appropriate times.
Yes, you can manually select which KK instance is given lights/knobs control. I'll explain that below in the Unify section. NI has also provided scripts (using OSC) to integrate with a given DAW. The website states the following DAWs: Logic Pro X, Ableton Live, Cubase, Nuendo, and GarageBand. These nicely integrate with the KK keyboards for editing, mixing, and transport controls. I know there is a user made script for some partial integration with FL Studio. And someone has created a Linux driver for the KK S-series keyboard to access some nice features NI has hidden.
Using Ableton Live, yes, as you switch tracks, it will automatically swap knob/light control on the keyboard to match the KK instance on the selected track. Perhaps this is accomplished through the provided scripts. The scripts are compiled python, and there is no published NI API.