Saving parameters from vst~

alex_trees's icon

Hello!

I'd like to save the parameters of an vst-plugin automatically in an easy way - so that parameters are remained when i reload the patch.

perhaps the easiest way is to use the write / read messages.
but then i have to do that manually each time.

i tried to use "write c:/test.fxb"
and then "read c:/test.fxb"

the file is actually created, but the parameters aren't stored correctly. if i read this file later, there are no parameter changes.

if i store it manually with "write" and then use "read c:/test.fxb" - it works.
so the problem is the "write c:/test.fxb" part.

is this a bug, or does someone know how to solve this?
or am i doing something wrong?

thank you in advance

alex

ps. or is there another even better way to do this?

Kasper's icon

hi

i send a
[write BlindSpeed:/Users/......../NameOfMyPreset] message to vst~ at closebang

and a
[read BlindSpeed:/Users/......../NameOfMyPreset] message to vst~ at
loadbang (delayed by some 500 milisec so the actual VST have the time
to load)

and it always worked

so it does not seem to be a bug - at least on Mac it works

best

kasper
>
>
>I'd like to save the parameters of an vst-plugin automatically in an
>easy way - so that parameters are remained when i reload the patch.
>
>perhaps the easiest way is to use the write / read messages.
>but then i have to do that manually each time.
>
>i tried to use "write c:/test.fxb"
>and then "read c:/test.fxb"
>
>the file is actually created, but the parameters aren't stored
>correctly. if i read this file later, there are no parameter changes.
>
>if i store it manually with "write" and then use "read c:/test.fxb"
>- it works.
>so the problem is the "write c:/test.fxb" part.
>
>is this a bug, or does someone know how to solve this?
>or am i doing something wrong?

--
Kasper T. Toeplitz
noise, composition, bass, computer
http://www.sleazeArt.com

Roman Thilenius's icon

it should work the way kasper describes it - but you could
also create your own effect preset type using [coll]

sending message "plug, something else" to [vst~] normally
makes the plug-in first perform loading until complete, then
[vst~] examines "something else."
but watch out with VST plug-ins which do slow or abnormal
initialisation stuff after loading (a dshort elay could be
helpful before loading presets automatically).

alex_trees's icon

thanks kasper,
that's what i inteded to do.
i found out that the automatically stored fxb-file (write c:/automatic.fxb) is different from the manually saved one.

i attached the two files as a zip

does anybody have an idea why this happens?

i'm using a pc, max 4.5.7

thank you
alex

alex_trees's icon

by the way
it states
"vst error: automatic.fxb: not a file for mda_plugin

so the writing seems to be messed up.

this might be a pc bug ?

thanks
alex

FP's icon

i don't know if it helps.
i did this:

Max Patch
Copy patch and select New From Clipboard in Max.

Kasper's icon

>thanks kasper,
>that's what i inteded to do.
>i found out that the automatically stored fxb-file (write
>c:/automatic.fxb) is different from the manually saved one.
>
>i attached the two files as a zip
>

it is for a mda plug-in?? which one??

kasper
--
Kasper T. Toeplitz
noise, composition, bass, computer
http://www.sleazeArt.com

alex_trees's icon

hi kasper
it's for the mda_BeatBox.dll
but it's the same with other vsts too....

any idea ?

thanks, alex

alex_trees's icon

Hi FP

you're the man
it works like this
this is really helpful

thanks alot

alex!

Frans-Jan Wind's icon

Thanks FP,

You made my life a whole lot easier!

Best,
Frans-Jan