Hi, not sure I understand this. Could you please explain it a bit?
Hi, I’ve been checking all over the net for vstPresets, I didn’t seem to find any for the plugins I work with, and this made me believe there’s no great interest. Happy to know there is.
It’s a direct conversion from Arturia’s to vstPreset files, with the advantage of having the tags there as well.
Interested to know the disadvantages of vtPreset files, let me know.
Curious to know why you would prefer mediaBay instead of the analogLab wrapper of Arturia. Mind explaining this a bit?
One that comes to mind is when a 3rd party developer updates his VST. Same VST just a newer version. Then the .vstpreset won’t work in the newer version while the developer has taken the time to convert his original format presets to the new version.
Another one would be if you work in another DAW.
Ah, sure. This is why my utility checks timestamps in order to reconvert the new/replaced ones if needed. But yeah, it’s not an automatic update, user has to run the app.
Furthermore, when we do know how a vst handles its presets, the conversion gets trivial thus fast enough to perform it upon every plugin update, at least when the release info suggests changes in presets.
I think that vstPresets are handled as expected by Ableton Live as well, though not 100% since I’ve never used it in reality. Oh and I’ve just checked an old version of StudioOne (4) I have, it correctly recognizes vstPreset files.
I didn’t’ even know other DAWs would use .vstpreset. I guess I assumed it was proprietary for Cubase only. Good to know as the only other DAW I have used is PT.
Now…do you think this is possible?
Prior to UADx, there was no way to convert a UAD preset or UAD bank to .vstpreset. Now that UAD is selling out it’s not that big of an issue assuming more tools will be converted to UADx.
By timestamp, do you mean it looks at the identical title of the preset, then checks to see which is newer?
Haven’t tried it, though I have to guess it would need some effort but certainly possible.
Did you try creating a vstPreset using Cubase and then comparing the two files? Sometimes things are pretty simple to catch, other times, less easy, but you never know…
I have a small db which holds filenames and creation timeStamps. I do then compare with the given directory’s files and check for changed ones, exactly.
The program you’ve shown, it must be specific to those 3 plugins because obviously they are different, consist of varying parameters and controls? Ie once you’ve got it working for the Arturia plugins you couldn’t just run the same program on say Neural DSP plugins?
Being able to convert into other daw preset files is a bonus, I use reason, ableton and logic regularly but I say (if I can) we just focus on VST preset files for cubase as it’s most likely our everyday go to otherwise we wouldn’t be here.
The vstPreset file format is well known to all DAWs actually. In fact it’s something that makes me wonder why it’s not widely followed by manufacturers.
Currently I have two active apps. One is exclusively for Arturia’s VSTs. The other one is for VSTs which have an NKSf integration. So,
if they do have NKSf integration, i.e. you can see them inside Komplete Kontrol, then, most probably my app will work for them as well.
The best approach when we don’t know or can’t identify the structure of the presets, is actually what you’ve already proposed: Click->Save. The thing is that if we want this to be done in large volumes, we have to a) automate these clicks, because we still need the name of the presets, and b) tag afterwards.
Here’s an older video which does clicking:
BUT, this one again uses Arturia’s db to correctly identify the presets. As you can see I’m pasting the presets names in order to go to the stage of saving. Tagging comes afterwards, again based on Arturia’s own tagging system.
I guess I might prefer Arturias own program for Arturia plugins, but I would like the presets to be available in media bay as well, so I can search for sounds across different platforms, if that makes sense.
Sure it does , this is actually the main reason that I’ve done the conversion.
No. I avoid programming. 25 years ago NI Reaktor sucked my musicianship life out of me. Never again.
Maybe the FXP/FXB format is too old today to consider spending time working out a converter to .vstpresets? I don’t keep up on this stuff. I know UAD uses it. Robs Albino uses it or used it.
When I looked around a few months ago I was surprised no one as @fese even found out has created such a converter.
After my Quick Look at it, and I’m not a super coder or anything, but I got the feeling ‘converting’ the preset in a coding sense from one thing to another would be more time consuming than it’s worth because every plugin (manufacturer anyway) is different. If it didn’t kill my hands or I had a 16 year old desperate to earn some money to buy a car, I’d pay him/her to simply ‘load preset 1, copy name, save cubase vstpreset, load next preset 2, etc etc.
I got this working pretty good just with an apple script which was just pulled from a ‘watch me do’ action. You might have to do a watch me do for each type of GUI plugin, but the good news is that takes 5 seconds, so it’s still worth it. I got stuck on automatically saving the vstpreset with the exact same name. I’ve got an idea on how to solve it but I’d need someone’s help who knows Apple/script or something similar better than I do. A third but more unlikely was if we could get a bot or something that has image recognition, see knobs, look for text underneath, find equivalent and save but again, by the time you got this working I think you’d be chasing diminishing returns
Oh and for the names, all plugins will have a preset folder in audio/xxxx/presets etc, usually they are in alphabetical order as is the list on the plugin. So if you select all and copy then paste into excel or apple script or whatever you’re planning to use that’s your list and as long as you start at 1 they should name all correctly. The area you get into problems is when the plugin has subfolders and stuff like that. Which isn’t a problem necessarily, just a bit more work. I opted for a simple number system when no did it, save as 1,2,3,4,5,6 etc. and once they were all done, i did a rename from list in the finder cause that’s much quicker for me anyway.
Sure. This is why I turned to NKSf to vstPreset conversion. Took me half an hour to program, and 15 minutes to convert 65,000 presets, basically almost all my plugins. The problem with this approach however is I don’t really know whether it would be legal to share. I have a thread on this one: Sharing vstPreset files creation utilities, and this is actually the reason I haven’t already shared my utilities.
Hi, nope. Unfortunately many plugins hold names and properties inside database files, and many times they’re encrypted. AND this in conjunction with your previous points takes us to this: It would be ideal that the manufacturers prepare such vstPreset directories, it is just too simple for them. I can imagine some reasons for not doing this, and time needed is not one of them.
Hi, I’m not surprised at all. Many users are not even convinced that this type of browsing is helpful. So if there’s no big demand, a pro won’t easily get to prepare such utilities. At the same time, users who find this thing useful, some times turn to the Komplete Kontrol solution. You can see that for the NKS standard, there are some paid libraries over the net. They were done simply because there was interest in it, many users have Komplete Kontrol and want to have it working with as many plugins as possible in this dedicated controller.
I doubt there are any legal issues, not seriously and in the real world. We’ve paid for these plugins fair and square, we’re just opening them up in a certain state that’s pre configured to our DAW of choice. They are useless to anyone who doesn’t own them in the first place
You are right. I’m not talking about the end-user here. I’m talking about the developer who supplies a utility to get info from inside a file and convert it to something else. We, as end-users, can always do whatever we want with the purchased files, no doubt about that. Anyway, what I can do about this, is to get in contact with some manufacturers. I thought to do it in the past, but was just too busy with my actual projects outside of my hobby (music). IF their response is positive I will certainly get into sharing. Otherwise, we have to find this 16 year old mate
I’m not really following you there, I mean, as far as I’m concerned we’ve just performed lots of clicks with a recorder, something I think they should have done already given how much rebranding of the same thing goes on. But I’m sure you’re more ontop of it than I am. Let me know how it goes.