Why do most 3rd Party libraries don't link parameters to host automation?

Why do most 3rd Party libraries don't link parameters to host automation?

I have some 3rd party percussion libraries and it's daunting to link each instrument to host automation! :|

 

Because a lot of developers aren't acquainted with the scripting method necessary to do it, since it's not documented.

 

You don't even need to use scripting for that. All you need to do is load Kontakt into a host and drag the host id to parameters and save the patch. The instrument will recall with the host automation in place.

 

No, i meant linking parameters of each instrument to 001,002...or the midi CCs before they sell it to public.

:|

If it's like this then I wont see automatically on the komplete kontrol S screen since I have to manually connect 001,002..etc

So Komplete Kontrol S is mapped or should I say the 001,002,003,004...etc are mapped automatically for Komplete products but not for 3rd party libraries


Business as usual i see!~

 

But lets say for example, a percussion library with about 200 nki, so meaning I have to link each parameter of each nki instrument just to SEE it on the Kontrol S or even Maschine...Daunting Much!~

So I hope 3rd party developers now are mapping each nki they produce since we have NI Hardware like Kontrol S and Maschine Studio now.

 

Don't expect all 3rd party libraries to conform to Kontrol S keyboards, as it likely won't ever happen...

 

I understood, my reply was that it does not require scripting and the library developers could set this up for users easily. I agree and wish more library developers would be conscious of this. Especially with Komplete Kontrol and Maschine around. Makes the user experience much better. This would also help with other controllers like Push and various DAW controllers etc.

 

It does require scripting, at least for host automation parameters. For MIDI CC automation, it can be done manually as it's written into the NKI...

 

I just did it with no scripting and the instrument recalled with the host parameter in place. Of course you have to be running Kontakt as a plugin when you assign the automation to a knob and save the instrument for this to work. It may seem like a lot of work for the Developer to assign this for libraries with lots of presets and it is if the presets are already there. However, when starting from scratch, most presets are made from a base instrument as a starting point. Once you setup the automation parameters for the initial instruments, any presets you derive from that will have the automation in place.

Even in the case of having to update existing instruments, it can still be done once especially on libraries with minimal presets and not make the end user have to do it. It adds value to the product.

It would also be nice if developers of non player libraries would add a bank name to all the patches so they are easy to sort in KK and Maschine. Adding a general type tag would help too as Maschine and KK picks these tags up.

 

Well I hope when Kontakt 6 comes out, it can do the auto-assigning for 3rd party libraries when it comes out because there's no use getting komplete kontrol S when one of main purpose of the kontrol S knobs is to assign it to any kontakt powered instrument, isn't it? oe do i smell some kind of controlled NI komplete products only environment?

 

With the snapshots option in the latest version of Kontakt you don't need lots of nki's for the same instrument anymore. Just map one and save a snapshot for other settings.That being said, is there a standard list for CC channels somewhere?

 

what do you mean? How do I do that?

So if I have an instrument called Bells.nki and within the same folder has Bells1.nki, Bells2.nki, and etc... means I only need to open Bells.nki and map it once then save a snapshot???

 

You can't import Bells1.nki in Bells.nki but you can use different settings of Bells.nki as a snapshot in Bells.nki.
So if you like Bells2 and it uses the same samples and FX modules as Bells then you can manually tweak Bells into Bells2 and then save it as snapshot Bells2.

 

That of course won't work if Bells1 has different samples than Bells2...

 

and FX modules. I noticed the snapshots won't replace modules either.