NKS Quality Control

JesterMgee

So it's a given that when users make NKS presets there will be issues with the quality/consistency of things like tagging, often making a bit of a mess and it's sometimes difficult to pick up on this especially given the broken way the tagging in KK works these days (not removing old unused/inaccurate tags even after being fixed)

However, there are some mistakes I often see in official NKS libraries which are suppose to go through some kind of quality control I would think. Just a quick few examples off the bat:

Example 1: Native Instruments Hybrid Keys:

There should not be a "Pads" character

Example 2: Native Instruments Hybrid Keys:

Again, should not be a "Piano" character and no such character / type exists for just "Keys".

Example 3: Native Instruments Hybrid Keys (again and again...):

Synth should be "Synthetic" tho personally i would love to have seen Synthetic as just Synth but meh... Plucks should just be Pluck...

Whoever checked/compiled Hybrid Keys must have done so at 4:58 on a Friday afternoon.

Example 4: Native instruments MassiveX

Sweeps & Swells is a category, not a Type

"Best of"?

Example 5: Arturia

The lower case "release" places this in a new tag

Example 6: KV331 Synthmaster

"Top" is not a tag I know of...

Nor is Lick...

That is just a quick example, there are more examples but CBF going through everything and I notice this during the cleanup of my own mistakes in tagging which are evident in the tags displayed.

Just thought I would bring this up since it may be showing a drop in quality control when it comes to checking these libraries, and it's honestly not a huge task given the official NKS pool is still pretty small. Anyone who actually sues it and looks in the NKS tag browser will see the mistakes for sure.

Another one that is already known but still irksome is this:

Vagus

So I have two points on this:

1) top is actually a character used in a few libaries, the latest one I have outside of Synthmaster, is Audierre Zone.

2) I would actually advise NI to utilze the community more to beta test 3rd party for NKS compatibility, and structure. I've contacted three or four 3rd party manufacturers with basic issues such as missing previews (sometimes, entire instruments), missing or unencoded .nkis for fully NKS compatible libraries in the last 12 months (Try loading Init- Lunaris 2 in KK or Maschine, for instance.)

While I appreciate there's actually a good outflow of NKS compatible instruments at present, if they're all going thourgh an approval process with one or two people on a small team, there's a very easy way to fix the issues with tagging, and those I've mentioned above; just get some community members to beta test them in return for NFR codes (which NI can produce unlimited quantities of as zero cost). Presto, much bigger compatibility testing team.

One further thing to add.

NKS FX - there is no logical reason to not have previews for FX that are NKS compatible. Having tested this, it's a software choce not to play previews for NKS FX plugins - it wouldn't be too difficult to export these previews from a DAW (I've done it), to showcase how each FX preset sounds; the preview just isn't played by KK/Maschine.

There is still so much unfulfilled potential in this format.

JesterMgee

"Top" means nothing to me and is not part of the NKS tagging standard as I have understood, never seen it used on anything since the last 1.5 tagging update was rolled out, what does "Top" even mean?

Personally, FX previews would be a waste of time IMO. I know some will say "at least you get a sense of the effect" but not ion context. Effects are usually quick to load because they are smaller in size and dont need to buffer samples and such so to load an effect takes as much time as it does to listen to a 4 second preview and can be done easily while a project plays. That's how I usually work, tho I dont use FX within KK at all, works out to be WAY more efficient in resources and usability having FX loaded onto tracks direct as cores can be better assigned and you can have both the instrument + effect open, something not possible in KK.

Main point is some of the review process that should happen appears to not be happening lately. Trying to clean tagging to find I cannot fix the ones that are in official files is a little annoying.

Eight4aWish

I agree with everything you say here. I find it frustrating that NI don’t follow the precedents they set for themselves. “Best of” really annoys. I copy the offending NI presets into the user folder for re tagging. I also routinely rebuild the database to get rid of the tags made redundant by this. I have toyed with exploring using AI to listen in and suggest tags for new presets. The available AI products that do auto tagging based on sound analysis (as opposed to reading the file names of samples) seem to struggle outside of drum samples so I am guessing this might not work well enough - certainly no match for the ears of Freelance SoundLabs.