Sad state of Native Instruments

[egbert101]

The real one.

[martinjuenke]

The real one.

Vurt coming from the barber?

[El°HYM]

Affirmative. I exist. Did some great stuff in the past two hours.

You are not real Urs, admit it, you are a robo bot from the future

[martiu]

Affirmative. I exist. Did some great stuff in the past two hours.

You are not real Urs, admit it, you are a robo bot from the future

. . . . .

[cptgone]

yes of course. have owned it forever. since day 1. anyway.. yes it's great. all the things in it.

I just wanted to elaborate the point you were making, for the benefit of others.

[Urs]

The real one.

That's Lars. I'm a lot more ursome!

[EdwardGivens]

“U(h)bik ... Safe when taken as directed.”

- Philip K Dick

[Echoes in the Attic]

So is it true that in order to use the new features of mk3 keyboards like grouped parameter pages, that you need the vendor sdk? Can you not create your own mappings this way? Freelance sounds, who have lots of nks bundles for sale, have said they can't use the new features without the sdk.

Bumping this ahead of nonsense chatter. Was there an actual MK3 thread?

[dune_rave]

sad state of NI:
How's that possible soniccharge appears with this new AI related genopatch feature, and not NI? why is there no tool in Massive X?
Anyway, RP resurrects Albino3, so the money i dont spend for NI stuff, will go to Albino3 and Synplant2.

[GeneralQ]

I think all DAW and VST development has slowed down…the market has been saturated for some time and most people probably already have enough stuff to last a lifetime. Unless someone does something really interesting or new I just can’t see the need to buy much of anything anymore, and NI are at the opposite end of interesting and new…

Part of that is that the market is to hard to satisfy. People are not happy if a synth with a few new features comes out that can do some interesting stuff the other synth can't. It needs to have all the features that other synths have PLUS new features. Which I find weird. It's like people want to use only one synth for every task and replace their current main synth with a new one, instead of using different synths for different tools.
I use Kick2 for Kicks, polyplex for the rest of the drums, Serum or Spire for unison sounds, serum spire or vital as basic synths because they have a fast workflow, Phaseplant or serum for wavetable based stuff, vital for it's spectral warp modes, ana2 or super8 for analog sounds, dx7v for fm sounds, and Massivex for more obscure sounddesign that involves comb filters, feedback loops or the frequency alteration that the anima module does (which I really like), phaseplant for ganular etc...

I like massiveX because it added something cool and new to my toolbox that I previously didn't have. But many people seem to dismiss it because it doesn't have feature A or B.

MassiveX is the only non purely Fm synth besides phaseplant that has the option to tune oscillators in ratios. It has some cool physical modeling capabilities. It has a lot of FM capabilities which works great in combination with the fully modular routing. The feedback loop also allows for some cool stuff that other synths can not do.

[noiseboyuk]

People are not happy if a synth with a few new features comes out that can do some interesting stuff the other synth can't. It needs to have all the features that other synths have PLUS new features. Which I find weird. It's like people want to use only one synth for every task and replace their current main synth with a new one, instead of using different synths for different tools.

This is a very good point. I don't like Massive X because of the sound, but that's just me.

[Urs]

So is it true that in order to use the new features of mk3 keyboards like grouped parameter pages, that you need the vendor sdk? Can you not create your own mappings this way? Freelance sounds, who have lots of nks bundles for sale, have said they can't use the new features without the sdk.

Bumping this ahead of nonsense chatter. Was there an actual MK3 thread?

NKS1 presets still work, and will work, with mappings grouped in pages. Such that anyone can create NKS presets for any VST3 plug-in, with any mapping they find useful.

The new group feature in NKS2 only works if the plug-in supports it. I guess that's because there's a lot of meta information about the parameters and stuff involved. It's not meant to be for tweaking a patch during performance, it's meant to make the plug-in as thoroughly programmable as possible. So here, yes the developer of the plug-in needs the SDK and all that.

[EvilDragon]

Or, in case of Kontakt content, NKS2 parameter pages are now generated from KSP scripts directly (and can be modified at runtime, which is huge). So yeah, for Freelance Soundlabs this will not really be accessible in the same way NKS1 pages are.

[spacepluk]

Time for NKS2 wrappers? hehe

[Echoes in the Attic]

So is it true that in order to use the new features of mk3 keyboards like grouped parameter pages, that you need the vendor sdk? Can you not create your own mappings this way? Freelance sounds, who have lots of nks bundles for sale, have said they can't use the new features without the sdk.

Bumping this ahead of nonsense chatter. Was there an actual MK3 thread?

NKS1 presets still work, and will work, with mappings grouped in pages. Such that anyone can create NKS presets for any VST3 plug-in, with any mapping they find useful.

The new group feature in NKS2 only works if the plug-in supports it. I guess that's because there's a lot of meta information about the parameters and stuff involved. It's not meant to be for tweaking a patch during performance, it's meant to make the plug-in as thoroughly programmable as possible. So here, yes the developer of the plug-in needs the SDK and all that.

I see thanks! Sounds like the nks2 best features will really only be for those plugins fully supporting it. That's too bad. I don't see why we couldn't just group parameter pages in the komplete kontrol software, independent of parameter meta data. Disappointing.