Native Instruments NKS Support

[Svama]

Hi folks,

are you using daw/plugin controllers? Sometimes I prefer them about mouse use.
The NI NKS works pretty well for me for recording automations.
Does it make sense to add NKS to some Melda plugins?

Greets

[MeldaProduction]

Hi Svama,

we have already been discussing that with NI, and I'm afraid the answer is no, the NKS thing is so limited that it is nearly impossible to implement here I'm afraid.

[Svama]

No problem, thanks for reply

[Svama]

Hi Vojtech, do you have any good suggestion for your plugins to handle with a controller?

[MeldaProduction]

What do you mean exactly?

[Svama]

What daw/plugin/midi controller would you use to handle your plugins. Something with fast and easy mapping. The NI Komplete Kontrol has the lightning information above the keys and the endless rotaries. Using a mouse isn’t comfortable (drawing or riding a knob). With a mouse you can handle just one parameter and it’s not a good workflow in general. I’d like to write automation for multiple parameters at once.

[jmg8]

Which DAW do you use?

[Svama]

Reaper 5

[aMUSEd]

I did make an attempt at mapping MPowerSynth to NKS, the template is shared in the NKS User Library. I just mapped the macros, oscs filters and envelopes though. The problem with mapping Melda plugins, especially the complex ones, is partly the sheer number of params to potentially map, but also the fact that the complex Melda plugins also have an additional 'device' layer - each device with its own individual set of params - makes it very hard. For something like MSF for example, you would have to create a template for each device, and since users are constantly adding new devices, it would mean a lot of work to keep up, and if you imported presets too these would also need mapping depending on the device they are based on.

I would suggest sticking to minimal mappings of things like macros, that way you can still control multiple params at once, but avoid the complication of trying to map everything.

[Distorted Horizon]

I would suggest sticking to minimal mappings of things like macros, that way you can still control multiple params at once, but avoid the complication of trying to map everything.

I was just going to say that maybe the easiest way would be to map dem macros

[Svama]

Thanks. I’ve read about the problems in your posts from 2017.
I personally don’t need to map every single parameter. Doesn’t make sense too me. I’m often happy with 8-16 mappings. Otherwise you will be lost. Just the simple stuff, like hpf, but I still prefer using rotaries over automation recording by mouse.

[MeldaProduction]

I'd then figure out which MIDI controllers NKI uses and just map them to whatever you need using MIDI settings, should be pretty simple. Plus, if you right click on a multiparameter (CTRL + ALT + right click on the easy screen), there's Attach MIDI controller option.

[DarkStar]

I looked around for details of the NKS MIDI implementation, as I had a similar idea, but could not find any.

[MeldaProduction]

I'd say, just learn it. Attach a multiparameter, touch the controller, done.

[ALBurk]

Picking up this thread again.

Many of your plugins now have "easy" interface available. Consider why you added such a feature. Ask yourself if that same reasoning would not also apply to an NKS implementation that mirrors the easy interface you already created.

Many musicians and producers are married to the larger platform that they work in every day. Users like me generally do not need "every capability" of *any* plugin, and generally use macros that meet most of their needs. I own some Melda plugins but haven't invested in any more because I almost never use them - they do not fit my workflow very well, if at all. Adding NKS mirrors of your easy interfaces would make them more accessible to me, and might even draw me in to exploring the deeper capabilities since they are loaded on the track anyway.

I sometimes wonder how many others think about such things. And if so, if they find their workflows are similar in this respect.