BrainModular

Hi all

I think this is little strange behaviour :

I use VST, choose ist preset (for ex. 'brass1') and modify it and then save workspace... after reloading workspace I expect to have everything like in the moment of saving .. but VST is in it's initial state, without my changes...

but ... my changes ARE stored but in preset 'brass1' wich I have to load manually....

this is very strange I think - first : factory preset is lost - my changes are saved in it , second: saving workspace should be saving workspace - my actual state of all tweeks.

I know - I can use preset manager and recall it on activation of patch but factory preset is still lost.


what do you think about this?

try to add a combox box to the inlet " program " of you vst , choose your program with this combobox , make your changes , then save your project...

So does this mean that changes to a vstPreset are automatically saved when the patch is saved? I'm not sure I would want that--many times, I am controlling a bunch of parameters, and when call up a new preset, I don't want the results of this messing around to be saved.

So, I'd like to ask: How exactly does Usine manage presets in hostedVSTs?? What data is stored and where?? I have never quite figured out how Plogue does this, and periodically I get unexpected results! So I always save all individual VST data independently of the host save. But that's a lot to remember, and keep track of!

Thanks!
-eric

hi

Olivier, what about this? please give us some details about storing vst state...

I have the same problem: sometimes, when I save a workspace, my VST settings are saved correctly...other times, on a different workspace, the settings are not saved, and sometimes this happens to the same Vst!!

Normally the VST state is totally saved in the patch.
They are saved as Chunks if possible or as separate parameters.
It works for 99% of VST's. So tell me which VST's don't work (by mail please). I'll take a look.