Retrieving parameters and values from vst to use as preset
Hi there,
I would like to retrieve the parameters and values from a few vst objects, so I can use that to loadbang my vst presets when opening the patch. As the patch will be used on other computers, I would like to have a solid solution to make sure the vsts work.
In the patch below I use one vst which has 142 parameters, so I count them down with get $1. Then I unpack all my values and would like to store them in a list. Here I use coll, but somehow the values are always 0, so something must be wrong. Also I don't really know, if I have my list, how can I use that to bang the settings into my vst?
Someone any idea?
Thank you!
maybe even this would work
Hey,
The coll object does definately work now, the only thing, I don't really think this answers my last question. Because this set up works now to find the parameters and to store them as a list, but this list is what I need to trigger the vst when opening it on another laptop, because it doesnt save its preset automatically right, so I would like to just loadbang all the nedded parameters.
Do you understand what I mean?
THANK you very much.
sure I do,
the question is, do you want one set of default parameters ?
if so set @embed 1 argument to coll.
that way your default list will be stored with the patch
and can be recalled.
but take care to dump coll only after vst loaded completely.
Is that another problem to be solved ?
Thank you so much for your help.
I just made an adjustment, so I have now the way on how to retrieve it. Also, according to your answer how to load that retrieved data, but here I am still struggling to use the data from coll correctly.
Can you have a look maybe? That would be fantastic. Thx.
you either use uzi or metro, not both.
this will work if plugin is in search path.
the trick is to tell plug to load and retreive some info using comma separated message.
plug MReverb.vst, get -7
plug can output infos only if it loaded completely
Okay nice, now I understand it :). Just one last question, I do have to keep both coll objects? Or could I store presets, delete that part and then only do the recall part, save it and then it's set for when I am opneing it again?
Thank you very much.
you don't need 2 colls but take care
to store only state that you want.
that because parameters get output
all the time, which would overwrite the coll.
also keep in mind that named colls get synced if one edits any copy.
for each vst you need diffeent coll name.
I would do some gating for storing params
In case some vst plugs can't cope with fast parameter retrieving using uzi,
you could use counter that requests next param after each output.
if you write all parameter values into a list, you can store multiple presets in a single coll.
Thank you guys!