KVR Audio

EvilDragon · Post by **EvilDragon** » Mon May 30, 2016 7:25 am

SJ_Digriz wrote:
EvilDragon wrote:There are already ways to do that via scripting, but it has to be done by the developers...
I think his point is that it would be nice to make it so users can do it. I know I get frustrated with having to go patch by patch on stuff like Gravity

Yeah, I know... For the time being, it's best to nag the developer about NKS compatibility, which demands automation slots to be used in order to assign parameter pages for Maschine/Komplete Kontrol.

SJ_Digriz · Post by **SJ_Digriz** » Mon May 30, 2016 12:28 pm

EvilDragon wrote:
SJ_Digriz wrote:
EvilDragon wrote:There are already ways to do that via scripting, but it has to be done by the developers...
I think his point is that it would be nice to make it so users can do it. I know I get frustrated with having to go patch by patch on stuff like Gravity
Yeah, I know... For the time being, it's best to nag the developer about NKS compatibility, which demands automation slots to be used in order to assign parameter pages for Maschine/Komplete Kontrol.

NKS support doesn't do any good for those that don't use NKS keyboards.

What we need is for KK to have CC assignable to each knob with a knob bank select on Bank Select Message, instead of CC for the param controlled by the knob. That would solve my problem completely.

EvilDragon · Post by **EvilDragon** » Mon May 30, 2016 2:19 pm

While NKS doesn't have FULL benefit for non-NKS keyboard users, it is mandatory for the developer to assign automation slots in order to get parameter pages done. That in essence allows direct control via host automation, for all NKIs in the library - it's the rule.

It is probably going to be NI's preferred way of going forward as Kontakt becomes more developer-centric.

Now I don't see what difference does Bank Select make - it's a CC in and of itself (CC#0).

SJ_Digriz · Post by **SJ_Digriz** » Mon May 30, 2016 3:08 pm

EvilDragon wrote:While NKS doesn't have FULL benefit for non-NKS keyboard users, it is mandatory for the developer to assign automation slots in order to get parameter pages done. That in essence allows direct control via host automation, for all NKIs in the library - it's the rule.

It is probably going to be NI's preferred way of going forward as Kontakt becomes more developer-centric.

Now I don't see what difference does Bank Select make - it's a CC in and of itself (CC#0).

It would be way simpler if the 8 knobs always responded to the same CC. The parameter assignment to the knobs would work the same. But, I'd never have to mess with my controller once I set the 8 CC. Then you could bank to the pages. Whatever page was loaded would respond to my 8 controllers without having to change the CC. It would be vastly simpler for the user. Of course that would make it so we didn't need one of those keyboards. As it stands KK is useless to me.

SJ_Digriz · Post by **SJ_Digriz** » Mon May 30, 2016 3:20 pm

EvilDragon · Post by **EvilDragon** » Mon May 30, 2016 4:48 pm

I don't think that's going to happen for Kontakt, honestly.

SJ_Digriz · Post by **SJ_Digriz** » Mon May 30, 2016 4:58 pm

EvilDragon wrote:I don't think that's going to happen for Kontakt, honestly.

Oh I don't expect it either. It would allow integration to other controllers too easy.

It's just the better way to do it from a user perspective.

SJ_Digriz · Post by **SJ_Digriz** » Mon May 30, 2016 5:00 pm

When the marketing came out with the "map any control to the knobs and page through the assignments" I almost wet my pants. Then I realized that it doesn't work any different than assigning works now, other than vendors can pre-decide mappings for you.

gorgorsan · Post by **gorgorsan** » Sun Jun 12, 2016 5:46 pm

EvilDragon, please let me know if Kontakt 6 will still be compatible with old Kontakt 2 or even Kompakt libraries like this one:

https://www.kvraudio.com/product/artist ... st-service

Thank you sir!

EvilDragon · Post by **EvilDragon** » Sun Jun 12, 2016 5:58 pm

Of course, NI is big on backwards compatibility, so that goes without question.

loachm · Post by **loachm** » Mon Jun 13, 2016 9:50 am

gorgorsan wrote:EvilDragon, please let me know if Kontakt 6 will still be compatible with old Kontakt 2 or even Kompakt libraries like this one:

https://www.kvraudio.com/product/artist ... st-service

Thank you sir!

...all these old Kompakt libraries are based on Kontakt 1.5 and as long as NI don't change a thing in Kontakt's core architecture these will work. However, libraries from the early days of KSP like NI's own Kontakt Experience will have some scripts that probably won't work. I'm sure ED can tell more about it, but listing what old KSP commands aren't in use any longer or have been reworked would probably be overkill. So, as a general advice, I'd stay away from libraries with scripting that have been release on K2 (probably even some on K3)...

EvilDragon · Post by **EvilDragon** » Mon Jun 13, 2016 9:59 am

Scripts will also work - it's a part of backwards compatibility. Any old commands are still retained and can still be used.

spinettim · Post by **spinettim** » Mon Jun 13, 2016 1:57 pm

I really hope that NI jumps on the vst3 wagon this year. Retro compatibility for me means that if I installed kontakt 6 and I load an old project made with K5, I don't have to do anything to listen to my song properly. And I don't need to keep K5 in my system too! But this is just a dream, I know...

EvilDragon · Post by **EvilDragon** » Mon Jun 13, 2016 2:49 pm

That only works for Kontakt on Mac with AU plugin format...

Ogopogo · Post by **Ogopogo** » Tue Aug 02, 2016 8:40 am

EvilDragon wrote:Pretty much. K11 is not coming out without Kontakt 6 in it.

Lies!

So how's it coming?

Kontakt 6 - any rumors about release?