NKS Development Discussion

I think you've hit the QA nail on the head @JesterMgee

To use videogames as an example (experience, rather than random), 80% of public beta testers will offer feature requests. 10% won't offer any feedback. 5% will complain it doesn't do what they expect and stop playing after 30 minutes, 3% will never take part, and 2% will offer some feedback.

On a closed beta, these numbers go down massively.

If we apply that same logic to an even smaller audience for music technology product, that's going to be a lot of people not giving any feedback whatsoever.

Amazing. Thank you.

It's not straightforward or even proven to work on every library but it's what I have as a start.

It requires basically taking the newer info from a NKS preset saved as VST3 and injecting that into existing presets. This means taking plugin ID and also a new control map with new control IDs since most plugins it seems will differ here. This info needs to be unpacked from the NKS files and repacked again but this only updates the call to the plugin and it's not a given that the plugin data will work with certain plugins.

In some tests I have done it is working (Spectrasonics for instance) but there may be some that wont work which in that case I will need to basically re-rip all presets again and retag. If it comes to that I will code something that will at least take the tag info from existing files and inject that into new files so all I will need to do is re-run the ripping scripts for the plugins then update their info from existing but it's never that simple.

Rest assured tho I am working on solutions and have a number of fallback ideas to make things work.

Ok now im in Team Rosetta Forever! :D 🤠

Thank you for your answer and your thoughts. And I know this Problem from Apple, its a never ending Game of changes...

Yep, there was hope that there was some kind of magical way to have VST3 plugins automatically just slot in place when VST2 was not available and this almost seemed possible.... However then I discovered the impossible problem that almost all instruments appeared to show completely different ID values for the same control between VST2/3 so even if it opens, the controls all don't work.

I still believe something is wrong there since every 3rd party plugin is doing the same but apparently this is explained as (paraphrased) "developers have not done the VST2/3 migration correctly so users need to contact developers"

In any case, not something we can simply hope will change, have to do what we always do and just press on and get things done.

Yeah there's gonna be a lot of additional work in many different ways. I've finally built a new blazing fast PC after 10 years so now have 3 workhorses to do processing and automated tagging (tho juggling most plugins that offer just 2 licenses is a bit of a challenge) so I have spent the time in the Beta just testing various different ways of carrying the data (mostly tagging) over from VST2/3. Some libraries can be easily converted, some need new templates and can then be converted and others need to be completely ripped and hopefully tagged using the existing tagging.... Oh how I hate the manual tag process, that's the main part that requires manual work if the plugins don't contain enough info to script tagging.

New Labs "Gaelic Voices"

Converted with VST3 plugin version and now works flawlessly, so i decide to reconvert all LABS in VST3 but it will takes me some days.

https://1drv.ms/u/s!AjOHJOPYHiuQiIp9b3G6ZBcg40QVKg?e=dkM8Yx

It depends on how you want to use the KK. I believe there is no wrong or right way, it just different ways to use it. For me it's very useful to have all the presets with previews especially for quite heavy plugins like Kontakt. On the other hand many times i use it as a sound design tool and i create my own presets. Of course i'm very happy too for the VST3 upgrade and i believe more cool things coming soon!