Saving VST parameters with Conductor preset

[woodslanding]

I'm starting a new thread, as I'm sort of on a new topic now.

I've tried saving parameters in the conductor, and it seems like it's actually pretty non-trivial.

Data is saved in arrays okay, but the hard part is figuring out how to keep the parameters from the vsts preset data from overwriting the array data every time the conductor is changed. So I need to block the event flow to the array when the conductor preset is changed, then send the data from the array to the VST, and then re-enable the connection from the VST to the array, so subsequent changes get passed to the array. I haven't found the right timig to make this work yet.

Regards my previous wkp, I realize I could just store the data from the dynamic faders in local faders per track, but it occurred to me that it would be nice if edits to a VST preset from within its own GUI could also be saved with the conductor.

Thanks for any tips,
-e

[nay-seven]

As vst parameters are saved by presets managers, have you try to use the last 256 presets addon by 23fx
and link by bus the outlet num of the conductor to the inlet preset in of this addon
could work..?

[23fx23]

yes the 256pm can work for this.

or i would use an array out of vst, with a pass in between instead of stop, then out of the array a pass if chg back to vst.
So when will recall conductor, the array will retransmit changes to vst, however, you pass data to array only when you want, ie via a button once your editing is ok for ex, or when pressing a save button: data first pass to array, then a wait one store to conductor.
that way there should be no unwanted feedback without timing pbs.

[woodslanding]

I don't want to use a pm, though because it requires a seperate store procedure--I have to find a free slot in the PM, store data to that, and only then save to conductor. Multiply by 16 channels, and saving a preset takes 5 minutes! I want to press one button, because it's live performance.

I'd like to tweak knobs on the vst, and have the changes saved with the conductor, without having to also save the vst data into its own PM.

It should be possible, I just haven't got the timing right, I think. Here's the WKP:

http://www.sensomusic.com/forums/upload ... mCtl_4.wkp

My fear is that the conductor_changed impulse is not getting to the array before the cable from the vst does. And if this is the case, my idea is impossible.

[woodslanding]

Okay, if I delay the input from the program change, then I can make sure the output from the vst is disconnected from the array at the moment the program is changed. Then after it is changed, I can connect the output from the array to the vst input, to update the vst's parameters. Then I need to disconnect the array out from the vst in, and finally reconnect the vst output to the array input.

I think it is possible. I'm wondering if it would work better to use a script, though.

[woodslanding]

Okay, I've tried using a script, and I don't know how to trigger a series of events.... I assume I need to use a process loop, and some sort of counter? But I tried editing the counter script, and it seems like to count anything I have to use the process loop, and yet I also need to use the process loop to do a series of things in between counting.

I think it is too much for now, I'll try to do it with a bunch of wait modules....

[woodslanding]

I discovered the 'stop interval' subpatch, and have gotten the above sequence to work. But now it seems like array values are not being stored in conductor presets--is this right?? I thought I tested that before I ever started this. But maybe my test was faulty??

[woodslanding]

Alright, mystery solved, I think.

I forgot that most VSTs don't require you to save presets--if you edit a preset, it comes back that way the next time you select it.

So I need to save vst preset datas in the PM.... then I can actually make edits to them and save the edits in the conductor without losing the original presets. It's annoying that VSts (most of them anyway) behave this way. There's a reason no commercial synth is set up like this!!

Yikes, this is turning into a royal PITA

-e

[nay-seven]

glad you find a solution !

[woodslanding]

Oh, I wouldn't go that far

I have at least figured out the problem. A solution is still a ways off!

-e