Feature Request Pattr FXP for VST~?

newtfish's icon

Hi,

A real useful feature for the VST~ object would be to be able to consistently save FXP information when changes are made to a VST.

Often there are parameters inside the FXP that are not available to max, so its not possible to restore the full state of a VST just using the available parameters in max.

It would be nice if VST~ saved the FXP information inside the patch, whenever a change is made to the vst. Just like live does.

Denis's icon
Max Patch
Copy patch and select New From Clipboard in Max.

Hello,
I was searching around this topic and I wanted to share my method.
If you want to save VST presets within the pattrstorage & json system, this is how I do.
- connect the following objects connected to your vst~object's 4th outlet : [route -4] [uzi] ---3rd outlet------(get $1) -----back to [vst~] 1st inlet.
- create a [multislider] object with as many sliders as the number of your plugin's parameters. Don't forget to give it a scripting name to include it in your pattrstorage system. you could even arrange to automatically adapt the mutlislider's slider number with proper messages.
- from the 4th outlet of the [vst~] object, connect the message [set $1 $2] to the [multislider].
- send the message [get -4] to the vst~ object ; this will update the multislider.
- from the [multislider], connect a [listfunnel 1] object. this will send all the parameter movements when you recall [pattrstorage] presets.
I attach the snippet.
This way you can even morph between vst presets and I find it very cool (using the recall method of pattrstorage).
Hope it helps some of you!

Denis's icon
Max Patch
Copy patch and select New From Clipboard in Max.

update with automatic multislider resize:

Roman Thilenius's icon

the main difference between DAWs and vst~ as a VST host is that vst~ as a max object (and not an application) and therefore does not have the rights to tell maxmsp what it should do.
adding chunks of whatever to .maxpat files sounds like a good idea but such an option would bring a lot of new problems into max world.

what is wrong with savin the plug-in content as .fxb to disk? then you will have its whole content ready next time, and not only a single preset.

Denis's icon

there is nothing wrong to me. Having this other possibility just helps me a lot to be able to include vst plugins states into my general patch presets, also this way I can morph (interpolate) between them, I don't need to give multiple names to multiple preset files, etc. I feel totally fine if this doesn't help you.