Get factory presets for vst plugins
AAV
9月 03 2024 | 9:23 午後
Hello everyone.
A few months ago I started to get into max msp in order to build a simple vst host, without too much plugin overload... the truth is that so far it has been working well, so I would like to add more features...
The reason for my inquiry is if you know of alternative techniques to obtain the factory presets of the vst plugins. I clarify that I have already done it with the vst~ object but it does not work with all plugins. For example, it works with the discodsp plugins but not with the spectrasonics plugins...
I am developing all this in a Microsoft Windows environment...
Thank you very much for any help you can give me...
sorry for my English language.
AAV
9月 08 2024 | 7:26 午後
someone who can lend me a little help?
Roman Thilenius
9月 08 2024 | 10:08 午後
you did not say what format exactly you want to get the data, maybe you want to show us the patch where it is working sometimes already.
"get 1, get 2,..." should normally work with VST2, VST3, AU, but maybe for some plug-ins you must be a bit more patient and not request that subsequently after "plug"? or put a defer after the uzi?
AAV
9月 08 2024 | 11:47 午後
Hi Roman
Thanks for your reply. I really appreciate it!
The patch I have is very basic, it's just sending the corresponding messages to the vst object~
I didn't use uzi or defer because I still don't fully understand how they work... I'm a newbie to max
But at least now I know, from what you said, that I have to take into account that they don't load immediately.
My goal is to have the names of the presets that come from the factory in the vst be displayed in the patch, choose one, and have the parameters adjusted based on what I chose... In conclusion, what I want to avoid is opening the gui editor of each plugin and choosing manually... I don't usually create my own presets, because the ones that come by default are enough for me...
Let me know if more information is needed
Thanks again
Roman Thilenius
9月 09 2024 | 2:25 午前
oh you want the names, not the parameter data.
i dont think you did anything wrong, this more looks like a problem of spectrasonics and/or the vst~ object.
some complex instruments such as samplers sometimes do things their own way which only works in "major" host programs or even only in their GUI.
AAV
9月 09 2024 | 8:51 午後
Hi Roman!
Thanks again for your contribution.
I think that the vst~ object, from what I've been learning, is quite complete. I tried these same plugins in gig performer and it returns exactly the same results that this patch shows, so I can say that the issue depends more on the plugin than on the vst~ object.
I've been reading more in depth on the forum and I saw that other users mention objects like pattr and pattrsotrage in questions very similar to the ones I'm asking here... What's up with this? Could a solution be found? I ask because I still don't quite understand how pattr and pattrsotrage work...
Thanks in advance!
Roman Thilenius
9月 10 2024 | 3:11 午前
i dont think you reach those preset names, which are obviously not "real" preset names, in an alternative way from a host program.
maybe they are hidden vst parameters? ...you could try to export a bank in vstpreset format from the plugin to disk... and then hack into it with [filein] or java, maybe you´ll find the preset names inside.
AAV
9月 10 2024 | 9:25 午後
I'm going to do what you suggest with the vstpreset files to see what results I get... thanks a lot Roman!