Hi all - I’ve been on my own plugin-preset-to-vstpreset journey for the past few months. Great to find I’m not the one! (Although regrettably I’m an Ableton user - sorry about that.)
@m.c I’m very interested to learn more about your NKSx to vstpreset converter. (I’m a programmer so I’m happy to get into the weeds!) Currently, like some others, I’ve been using a fairly crude automated approach - load the plugin to the first preset, write a script that clicks ‘next’ and reads the preset name with OCR, then saves to Ableton. But a lot of plugin interfaces don’t play nice with that approach, so when you mentioned 15 minutes to convert 65,000 presets that definitely piqued my interest…
Hi there, just to be clear I was talking only about the NKSf format. And this means that you have to have your third party plugins in this format. If you have such files already, I can contact you with a pm and share some snippets, no problem
I ended up having quite good success with an automated ‘mouse clicker’ approach. I tried it with keyboard maestro, flexi-deck and a better touch tool. whilst they all had pro’s and con’s keyboard meastro came out on top for me although it does need to be slightly customized per plugin which can generally be divided into two baskets:
1 - plugins that allow you to control the next and previous preset arrows etc and;
2 - plugins that don’t allow this.
The advantage of this way is it can be saved in the format of your DAW of choice which is then immediately reflected in the DAW’s media browser whatever that may be.
The huge advantage of m.c.'s is it brings across almost if not all of the meta data belonging to the preset (genre, intrument type, character etc.) where as my method only brings the top most level because its based open the words preceding it (i.e.if you had to chose ‘bass’ at the beginning this will give it the attribute ‘bass’ and so on.
Im still struggling to find a nice way to house all of them in a central location that can be seen by all DAW’s and have come to the consolation the concluition this may not be possible with the skills I currently obtain.
Hey, it seems like this thread has really slowed down… I thought people wanted to share their presets..
Recently I noticed that Reason supports .vstpreset’s as well, and with the new browser has piqued my interested again in the format.
Looking for factory presets (Vst3) from:
Air Music Tech (Xpand!2, Hybrid, Structure)
other Korgs I don’t have yet
Native Instruments synths FM8, Massive, Massive X, Kontakt Factory
Ik Multimedia Philharmik CE, Modo Bass2, Sample Tank
Izotope Iris
Eventide Anthology
and others..
So, basically I have now a good chunk of this done but I am waiting to check out the M.C.'s utility as I have most of the rest as nksf format now that I gathered from the NI user forums.
I was pretty impressed with how the community’s pages are organized, we should do something like that here. They even have a guys that sells them..
I have sent PM’s out already so if anyone else can help it would be greatly appreciated. I guess people are too busy atm or something.
For Reason13 users you can simply drag your ‘VST3 presets’ (user/Documents on Windows ) like this: (although it won’t read any metadata but folders are seen)
to me the whole point of the task is to get the meta data in there, or at least, the important parts of it. I can get close with a keyboard maestro macro which just loads the preset and then saves it with the same name and fills out the first couple metadata tags that get exposed to you (category, and sub category and character I believe)
I found that the task of accurately tagging the presets wasn’t going to be my primary goal as the given categories is quite limited in my opinion.
But to the rest we aren’t going to let the negatives hold us down, that is not the point of this thread.
Soon, I hope the first post will be updated, and the thread moved into C14 category or pinned somewhere.
Anyone will be able to improve any bank if they want to as not all may be tagged 100% to their liking.
Here is my collection so far… https://1drv.ms/f/s!AlWU8e7V8SIuipVb6oUJTh-zzRB71g?e=uQUEtX
Well done my man for getting this train moving! we should just decide/cover off one important thing, are vstpreset files cross compatible? I hear people say it doesn’t matter and they represent the same thing but im not sure about that…
No, sorry I should have been clear, compatible between Mac and Pc. A lot of people say it’s fine and it makes no difference but I have tried as I use both (not so much these days) and I can say that it is not always compatible at all.
Really? As in they simply don’t work? I have no experience with that, you will have to let me know if something works or doesn’t. Which ones in your experience don’t work?
