NKS Development Discussion

Rikk Show

Here are NKS for some freebie FXs. All made in Windows with VST3 plugin.

Bassline_RoyalComp_StudioRack.zip

Royal Compressor - currently free at AudioDeluxe with a purchase.

Waves StudioRack, free VST3 fx host (Really a must have with parallel and mid/side processing, 8 macros)

Bassline - a new plugin that generates side harmonics while keeping the original bass mono

Rikk Show

By the way, the above NKSs have NICE graphics, like this:

Rikk Show

https://community.native-instruments.com/discussion/comment/38595#Comment_38595

Hmm, yeah. Don't know why. And I checked I have the latest version installed on Windows. Those presets have Bass, Pad etc in the name so it is OK, I'll just leave it as is.

The save to NKS only exists in Diva VST2, I tried to see if Diva VST3 would do it properly, but the function wasn't there...

Christos Adamos

All LABS in VST3

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

Fixed some incorrect mappings and previews. Tags importing from database and some fixes applied too

Kymeia

https://community.native-instruments.com/discussion/comment/38655#Comment_38655

I know - and at the moment even if it could they would still open in the VST2 :( U-he are aware of it, but need our patience letting them deal with it, they are working on many things at the moment

jggorman

So am I understanding this correctly?

1. The plugin that opens can be changed by changing the uuid in the nksf preset files.
2. Even if the above is true, it is useless because the parameter IDs get mismatched and the preset files does not work properly.
3. The above is only true is unless the author of the plug programs the plugin for VST2 to VST3 migration.

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.

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)