NKS User Library

JesterMgee

Basically.

Its the PLID not the UUID that needs to change and it’s no longer a simple 8 byte number it’s a sequence of different numbers I assume because it’s a container with multiple targets. It actually has the VST2 and VST3 calls now in the PLID and it is possible to make it open either VST2 or 3 if they exist but the control IDs completely differ from VST2 and 3 so a whole new map has to be created. Also, some VST3 plugins I tested just don’t load the preset data when you use it from VST2 and some just crash so it’s all over the shop with issues that in some cases will need all the NKS to be redone

EDIT: Well the info I gave above is how it was when I was testing the Beta and developing tools. I did hundreds of tests and had things loading just fine by simply updating the PLID, sure controls were an issue but the actual preset would load.

Now, I have discovered none of that works. They appear to have changed something in the last few Betas which now causes none of what I have done to work, presets load the VST but are now not loading the actual data. I may know what this problem is but this will take many more hours to test and at the moment I seriously CBF looking at it. Might take a few weeks off trying to even test this ***** at the moment, it's got me pretty miffed and considering boycotting all my updates now.

Kymeia

https://community.native-instruments.com/discussion/comment/4468#Comment_4468

I found these seem to have lost sync with the params in the latest versions - not sure if this is a consequence of VST3 migration, or something else.

Anyway if anyone finds the originals above are not working in the new KK and Maschine, particularly using the VST3s, I have posted fixes here (basically just remade all the templates - the images can be used from the above Dropbox - however I also fixed the database files):

https://www.dropbox.com/s/52idaarqngec88b/Valhalla%20DSP%20VST3%20fixed.zip?dl=0

https://www.dropbox.com/s/1e7ua6fnf2lrhwa/valhalla%20dsp%20dist_database.zip?dl=0

This is ONLY for use with the VST3 versions

Rikk Show

Anyone making new NKS:

PLEASE state if they were done/tested with the VST3.

Anyone holding a repository please make a directive with VST3 verified NKS files.

This would be super useful.

JesterMgee

For now, I would simply suggest unless something specifically states it is VST3 it is not.

My site for instance states on every page VST2 so that is simple. I will then update this as I work through each and every plugin that it works with VST3.

Next problem: Just because something is VST3 does not magically mean it works on macOS, still needs to be M1 compatible after that and that is the devs area.

Kymeia

https://community.native-instruments.com/discussion/comment/38737#Comment_38737

Already have

Mercury

https://community.native-instruments.com/discussion/comment/37809#Comment_37809

This one is VST3 😀

Sunborn

Hello!

Is there a way (or is someone capable to re-program it) for the PresetMagician to read VST3?

Thank you

Kymeia

https://community.native-instruments.com/discussion/comment/38771#Comment_38771

Problem is even if it could it's Windows only and it's Mac users who are having most of the problems.

Kymeia

https://community.native-instruments.com/discussion/comment/2058#Comment_2058

I have created an update for F'em that has some mapping for params (too many to map everything realistically so I stuck to macros, XYs and a few basic ones). More importantly I have updated this to the VST3 version and converted all the presets you created to VST3 as well so do I have your permission to re upload this as this is building on your work? (I always intended this forum thread to promote collaboration though)

Planning to do the same for Biotek 2 if that is OK but I need to make a new template for that first and I've already made one for Imagine VST3 so will update the presets for that too if you are OK with this

I’ve found that Tracktion plugins do support migration of presets but params are not 100% aligned between the VST2 and VST3 versions (developers are not always careful to match them up) so the VST3 NKS versions can only be used with the VST3 plugins (but the VST2 can now be deleted anyway unless needed for other hosts)

Kymeia

OK Imagine VST3 and Biotek 2 VST3 are done too - just waiting for the OK to upload (Imagine will still need Rosetta on Mac as it's not Apple Silicon native yet but the Tracktion plugins are)

Kymeia

With Eight4aWish's kind permission I have created updated NKS packs for Biotek 2, F'em and Imagine VST3 versions merging my VST3 templates with their NKS presets and previews. Imagine I had already created a pack for (that was already in the VST3 folder in the NKS User Library) but without all the NKS factory presets but Eight4aWish had generated some but without a param map template and for the VST2 version - so I used my existing VST3 template to update their presets to VST3 adding the param mapping as well.

Done the same for F'em and Biotek 2, they are all in the VST3 folder in the NKS User Library here (along with many other VST3 plugins):

https://www.dropbox.com/sh/kg8m3y7boy4mssy/AADsX-4nuV8k1Z4z3k4rrPFha?dl=0

So these have factory presets with mapped params, previews, basic tagging, image thumbnails (some by each of us), and database integration files.

Note these are VST3 only and will not display params properly with the VST2 (at least not the Tracktion ones). Also Imagine is not Apple Silicon Native yet so will still need Rosetta, but the Tracktion plugins are

Also if you are running Komplete Kontrol using Rosetta mode remember to delete the VST2 plugin versions otherwise it will still try and load these with the VST2 which won't work properly - the whole point of these is so the VST2 is no longer needed for use in Komplete Kontrol or Maschine

Nice to collaborate on stuff like this for the benefit of the community :) Cheers

Christos Adamos

https://community.native-instruments.com/discussion/comment/39053#Comment_39053

Great! Thanks Kymeia and Eight4aWish

In case you want to put the Spitfire Audio LABS from VST3 in to your collection here are

https://1drv.ms/u/s%21AjOHJOPYHiuQiIsWrPC714mV_ihMYA?e=dWuPRZ

also I would like you to know that I am now working with factory presets for Abyss, Novum, Opsix, and Wavestate just to avoid double work

Kymeia

Thanks will do later - I don’t have Abyss but made templates you can use for Novum, Wavestate and opsix if you want

Christos Adamos

https://community.native-instruments.com/discussion/comment/39099#Comment_39099

Yes. All these (except Abyss) will be converted based on your templates. Thanks

Kymeia

Great nice to know they are being used. I have also made some presets for OPSix of my own if you want to include them