Kontakt 6 - any rumors about release?

Sampler and Sampling discussion (techniques, tips and tricks, etc.)
Post Reply New Topic
RELATED
PRODUCTS
Kontakt$299.00Buy

Post

jancivil wrote:I would've expected the NI Heavyocity would have Host Automation set up in the nkis.
I don’t have a NI keyboard, so useless.
If you have to ask, you can't afford the answer

Post

Is it possible that NI overdue anniversary celebration will take place at the NAMM 2018 on January 25?
Then release Kontakt 6, Absynth 6 and Massive 2 and include them in Komplete 12?

I must be dreaming. :(

Post

Kalamata Kid wrote:Is it possible that NI overdue anniversary celebration will take place at the NAMM 2018 on January 25?
Then release Kontakt 6, Absynth 6 and Massive 2 and include them in Komplete 12?

I must be dreaming. :(
Apparently I was dreaming as I just had a nightmare that I was wrong. :scared: :roll:
13 days to NAMM! :hyper:
Will they have the Komplete giveaway as they did in 2017?
https://www.kvraudio.com/news/kvr-givea ... e-11-36031

Post

Kalamata Kid wrote:
Kalamata Kid wrote:Is it possible that NI overdue anniversary celebration will take place at the NAMM 2018 on January 25?
Then release Kontakt 6, Absynth 6 and Massive 2 and include them in Komplete 12?

I must be dreaming. :(
Apparently I was dreaming as I just had a nightmare that I was wrong. :scared: :roll:
13 days to NAMM! :hyper:
Will they have the Komplete giveaway as they did in 2017?
https://www.kvraudio.com/news/kvr-givea ... e-11-36031
That was a KVR thing, not an NI thing. NI dont do NAMM.
An idiot on Set Theory:
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."

Post

Oh, too bad!
Will cancel my plans to go to the NAMM. :lol:

Post

whyterabbyt wrote:That was a KVR thing, not an NI thing. NI dont do NAMM.
I kinda hope that changes now that NAMM has become dedicated to making Software.NAMM a success.

Post

SJ_Digriz wrote:
jancivil wrote:I would've expected the NI Heavyocity would have Host Automation set up in the nkis.
I don’t have a NI keyboard, so useless.
I don't either. I write automation in Cubase from VE Pro's automation mapping, where it is much better when a Kontakt instrument has it all spelled out in advance; it shows up in the dialog with a name by '000' etc.

This currently means I will not do a lot of instruments in a multi, rather there is a consistency to SonicCouture for instance when you load single .nkis. I know the drill. They end up occupying earliest empty slot if loading more than one, of course. I can get by but it will obviously be much nicer to work from a template of controllers both CC and Host.

Post

jancivil wrote:
SJ_Digriz wrote: I can get by but it will obviously be much nicer to work from a template of controllers both CC and Host.
I just won't work this way without the mapping template. It is a purposefully unnecessary obfuscation done to NOT support other systems. Kind of pisses me off actually. To the point that I was considering the K2-88 if it came out, but this mess puts me off enough to go elsewhere.
If you have to ask, you can't afford the answer

Post

Kalamata Kid wrote:Is it possible that NI overdue anniversary celebration will take place at the NAMM 2018 on January 25?
Then release Kontakt 6, Absynth 6 and Massive 2 and include them in Komplete 12?

I must be dreaming. :(
It looks like my prediction record stays at 100%. :lol:

Post

jancivil wrote:This currently means I will not do a lot of instruments in a multi, rather there is a consistency to SonicCouture for instance when you load single .nkis. I know the drill. They end up occupying earliest empty slot if loading more than one, of course.
In Kontakt, go to Options->Load/Import->Unwind automation IDs for additionally loaded patches, make sure that's enabled. Then any patch loaded after the first one in a multi will have its automation slots starting after the last slot taken by the previously loaded patch.

SJ_Digriz wrote:It is a purposefully unnecessary obfuscation done to NOT support other systems. Kind of pisses me off actually.
Actually, it's not. There are other plugins out there that have very similar host automation management. When you have a gazillion parameters like Kontakt can have, you cannot simply assign them automatically an automation slot, because very soon you'll end up with a jungle of automation parameters nobody would save you from. This is why they give you 512 slots and you fill them however you want.

They also added possibility to assign scripted parameters to automation slots automatically via KSP, which is now a requirement for all libraries that are NKS approved. So things are getting better in this regard. For older products, though, editing scripts would be the only way.


I wouldn't hold my breath for any sort of save/load host automation templates, though. Looks like scripting is the solution that NI offers in this regard.

Post

EvilDragon wrote:
jancivil wrote:This currently means I will not do a lot of instruments in a multi, rather there is a consistency to SonicCouture for instance when you load single .nkis. I know the drill. They end up occupying earliest empty slot if loading more than one, of course.
In Kontakt, go to Options->Load/Import->Unwind automation IDs for additionally loaded patches, make sure that's enabled. Then any patch loaded after the first one in a multi will have its automation slots starting after the last slot taken by the previously loaded patch.

SJ_Digriz wrote:It is a purposefully unnecessary obfuscation done to NOT support other systems. Kind of pisses me off actually.
Actually, it's not. There are other plugins out there that have very similar host automation management. When you have a gazillion parameters like Kontakt can have, you cannot simply assign them automatically an automation slot, because very soon you'll end up with a jungle of automation parameters nobody would save you from. This is why they give you 512 slots and you fill them however you want.

They also added possibility to assign scripted parameters to automation slots automatically via KSP, which is now a requirement for all libraries that are NKS approved. So things are getting better in this regard. For older products, though, editing scripts would be the only way.


I wouldn't hold my breath for any sort of save/load host automation templates, though. Looks like scripting is the solution that NI offers in this regard.
you aren't following. If they exposed the 8 controls as CC, then I can permanently map a controller to those CCs just like using the hardware. As far as I can tell you can't do that. So, it's useless. Halion allows you to drop any parameter into a QC slot. The QC itself has a control value. The sound designer can assign whatever they want to those controls, and a user can default a controller to those values.
If you have to ask, you can't afford the answer

Post

Actually, I think you may have combined two conversations.
My comment was in regards to Komplete Kontrol as a plugin. With a KK Keyboard, the 8 controls are automatically mapped to whatever plugin resides in the preset in those slots. You hit page, and your 8 controls are still mapped to whatever parameters are in the slot. You as the user, don't have to map unless you want to.

With the plugin standalone, I don't see a way to do this same static mapping of controller to slot. I still have to go through the same process as if I wasn't using KK. So to me, KK gives me nothing but another messy plugin to map out, preset by preset, page by page.
If you have to ask, you can't afford the answer

Post

EvilDragon wrote:
jancivil wrote:This currently means I will not do a lot of instruments in a multi, rather there is a consistency to SonicCouture for instance when you load single .nkis. I know the drill. They end up occupying earliest empty slot if loading more than one, of course.
In Kontakt, go to Options->Load/Import->Unwind automation IDs for additionally loaded patches, make sure that's enabled. Then any patch loaded after the first one in a multi will have its automation slots starting after the last slot taken by the previously loaded patch.
That's what I meant to type, 'earliest empty slot' needs qualifying 'after the last one filled...'
Thanks for the reply.

We need a template sort of paradigm. For instance: I just loaded an instrument with a number of parameters I may automate. I have a certain consistency where I remember most of the slots. Here I'm doing it all, one by one manually which gets old fast.

I don't know the pitfalls of coding that. But its time has been here for years now afaic.

Post

That's what I'm saying, templates for automation slots are unlikely to happen because this is handled via scripting now...

Post

I saw you mention that but I don't know how to use it.

Case scenario: an instrument made before SonicCouture made their things with Host Automation loaded. So I want to cut down on the diddling sort of work this is, as I usually want to see '000 = Frequency; 001 = Resonance; 002 = Envelope; 003 = Velocity et cetera. And it loads with 'Automation' blank, unlike post-2010 libraries or whenever it was.

Template. :shrug: I reckon you know what you're talking about which means I'm not likely to spend time lobbying them but this is kind of basic as far as I understand anything. It would seem like to me they have something which works as a template since it's consistent with every library.

Post Reply

Return to “Samplers, Sampling & Sample Libraries”