NKS Requests

Just added these. I don't have the first couple vaults but I have most of them:

already looking into it….

I've done a full library but you can check out the template I created in the demo.

Nothing from Serum 1 would carry over so I had to do everything from scratch, tho because the preset names for the "Serum 1 Factory Library" in V2 match V1 I was able to migrate all the tagging over that I did from V1 so that saved a chunk of time.

Took a few hours of playing with Serum 2 to figure out the new lay of the controls. While I am quite familiar with S1, S2 is more than just a new osc and more macros and mod options. A lot of controls are multi-purpose and the whole FX section is now not automatable like the old version, rather you have to right-click and enable automation which it appears only 16 slots are available for that so it's not possible to even map FX On/Off controls sadly.

Anyway, this was a very late night, few hours sleep, 6 hour work day and then another 8 hours to dig into this one.

I have that one here, basically almost all UVI is done:

I have created many NKS presets for serum over the years as my user collection grew. Now that serum 2 is out, I was hoping I'd still be able to access these user libraries within serum 2 and it is great that it allows you to browse serum 1 + all my user libraries inside Serum 2 and the tags are pretty much all still there. However, the NKS user libraries i made only work for serum 1, I tried moving the NKS user files to serum 2's NKS user library location and that obviously didn't work. So basically… if i want to use all my NKS serum 1 user libraries I made INSIDE serum 2….I'd have to recreate all those NKS user libraries using serum 2…right? Unless there's an easier way to do it, I'm just going to leave each library separate haha

Serum 2 is really cool though! Might just comp that Freelance Soundlab serum 2 NKS library still!

The format of Serum 2 is different from Serum 1 so external saved files in DAWs (and NKS which is the same "snapshot" data that a DAW uses when you save a project with a plugin) isnt compatible. There is far more to making a file open in a different plugin than just moving folders. You have to change the PluginID (PLID) and a VST3 header ID within each preset file to the new plugin and even a test on that, the presets do not load.

Basically, it has to be done from scratch again, very often the case with any plugin that changes the physical name of the plugin, and I have had to redo many libraries over the years which is a lot of hours to spend.