VSTi banks and patches question

[magickz]

Hi. Belated happy new year to everybody.

I used Usine to create around one hundred patches (fxp) for the OBXd plugin, and now I wonder how I can transport these into one single bank (fxb). Also, it seems that all presets have the same preset name, regardless of their filename. Is there a way to manage these in Usine? And if not, do you know some tool that you can recommend me, to import these presets into a bank, rename and move them from one bank into another one?

[nay-seven]

Sadly all plugins don't use the same process to create and store their presets, so can't help for this one.
but you can save the presets directly in Usine ? ( new presets manager in HH3 will help you soon)

[magickz]

Hi Nay-Seven, thank you. I understand.

Of course, Usine can store all patches, and it does it well. The only advantage of FXP/FXB would be the possibility to share the files with friends who are working in other DAWs. And it would be more elegant if the patches all have unique names in the preset browser instead of all the same.

Some plugins have a very good preset management implemented - for example the Minifilter V does it almost perfectly in my opinion -, many others don't.

HH3 is on the way, that is a very good news! Looking forward to it.

Have a great sunday!
#

[sm_jamieson]

Some VSTs rely on the host for preset management. As I said on the other thread, RENAME is mising from Usine.
I've put some FXP format information on the other thread.
The other thread being
http://www.sensomusic.org/forums/viewto ... 675#p36675

[magickz]

Simon, thanks for the information. I have no programming practice since more than ten years. I think I have to relearn everything - and it seems I forgot almost everything... but my focus should be on learning music related things for the first

I guess via macro in Notepad++ I could copy the filename of the opened file into the clipboard and use it in a search and replace process to replace the unwanted program names by the descriptive filenames, maybe I'll do that.

And in the last step create a bank with all corrected FXP files in the Minihost.

Best regards.

[sm_jamieson]

Yes it would be quite easy for a script to edit the fxp file to search for the program name in the header and change it.
You could also search for it in ascii format in the chunk data in case the VST uses that, but some VSTs compress their chunk data.
Note that there are 2 formats, a list of parameters format, and a binary chunk format, and the header tells you which one.
Anyway, I would expect a particular VST to be consistent, so if you do a test edit and it loads OK you could edit the whole lot (make a backup first of course !).

Unfortunately an fxb file does simply not contain an array of fxp format data, so the edits should be done on fxp files, using the VST to do the conversion (i.e. load bank, save as individual presets).