Tiny Orbit

I am working on pulling all parameter values from a plugin preset and writing it to file. The idea is , you load up a plugin and with the click of the button you would run through the entire plugin preset library and extract all parameter values.

I know that by using "params" and "pgmnames" messages you can pull out all parameter names and preset names in one list. But i was wondering if you could call single parameter names and single preset names? Similar to how you can call a single parameter values with the "get" message.

I am working on pulling all parameter values from a plugin preset and writing it to file.  The idea is , you load up a plugin and with the click of the button you would run through the entire plugin preset library and extract all parameter values.

I know that by using "params" and "pgmnames" messages  you can pull out all parameter names and preset names in one list.  But i was wondering if you could call single parameter names and single preset names?  Similar to how you can  call a single parameter values with the "get" message.

Hello,
I am working on pulling all parameter values from a plugin preset and writing it to file.  The idea is , you load up a plugin and wit

vst-˜-pulling-all-preset-values-from-a-plugin

uzi 64 -> program name outlet
"params" -> preset name outlet

The issue i have is that i cant call just one specified preset/parameter value at a time, it seems you that you can only call out all known values in a list.

I guess i could call all values and save to memory, then call from there one by one but i was just wondering if the vst object could do it natively?

The issue i have is that i cant call  just one specified preset/parameter value at a time, it seems you  that you can only call out all known values in a list. 

I guess i could  call all values and save to memory,  then call from there one by one but i was just wondering if the vst object could do it natively?  

i donit think so, there is only the "params" command.

but you can easily distribute the outcoming dump of messages using objects like [cycle] or a gate with a counter, is that what you want? 

i donit think so, there is only the "params" command.

but you can easily distribute the outcoming dump of messages using objects like [cycle] or a gate with a counter, is that what you want? 



ok i see, you want to attach the names to the parameter numbers and values.

to store the parameter names in a list & then fetch them from there later when you call the values.

otoh, you might doublecheck if you really want to include the parameter names with a multi-preset-collection data file. you can always get the parameter names from the plug-in next time, so why store it with each of the presets?

what seems more important for a custom preset file format is to include the plug-in name (and if it is only a reminder for the user - you dont have to do it like they did it in .fxp/.fxb, which is using the actual VST ID)

in this case i would do something like
thresh 2
zl nth
to store the parameter names in a list & then fetch them from there later when you call the values.

otoh, you might doublecheck if you really want to include the parameter names with a multi-preset-collection data file. you can always get the parameter names from the plug-in next time, so why store it with each of the presets?

what seems more important for a custom preset file format is to include the plug-in name (and if it is only a reminder for the user - you dont have to do it like they did it in .fxp/.fxb, which is using the actual VST ID)


i am writing to text file, for further data wrangling outside of max. But i take your point, no need to spit it out every pull. 

i am writing to text file, for further data wrangling outside of max.  But i take your point, no need to spit it out every pull.  

cheers :) 

Vst ˜ : Pulling all preset values from a plugin