From the original SynthMaker forum (2004–2014), with its members’ names and dates.
ccpurno ·
Hi,
I am implementing a switchable background image in my new project.
I am using a trigger button to switch a selector, to prevent the background from needing
to be changed in every preset by the user.
But now the issue: when closing the project and reloading a project with the synth
in my DAW Host software, of course it will have the default background image again. 🙂
It seems there is no way out of this:
- If you want the background setting to be remembered by your host, you need use a VST parameters function
--> If you use a VTST parameter function, the skin will need to be changed in every preset.
Any ideas (without using an external setting file) ?
Thnx!
CC
exonerate ·
On the VST parameter primitive, theres an option for "Store in Presets" , I think if you set this to false it should work how you want.
Cheers 😉
Exo
Acrobat ·
exonerate wrote: On the VST parameter primitive, theres an option for "Store in Presets" , I think if you set this to false it should work how you want.
Cheers 😉
Exo
Ehm, no, if you don't store, it remains stuck to the value chosen before rendering to VSTi -
so it can be changed only during the session, everytime you reopen the .DLL it's always the same original value.
I think you are anyway forced to use save and load .txt primitives instead.
ccpurno ·
Thnx for your answers.
But isn't there a clever way to do this without an external text file?
Maybe disabling/enabling the preset loading module with a trigger button or something?
If there would be a function that gives a trigger just before the VST is closed, I might be able to solve it.
CC
Neptune ·
would a random counter help?
triggered by afterload when loading the vsti and triggered during preset switching
exonerate ·
One possible solution would be to connect the "p" output on the vst parameter directly to the preset manager primitive but not the preset text file primitive.
I've not tested that but it should work, you need your parameters connected to the preset manager so that the host can see them, the actual saving a preset to text file doesn't need the preset manager, if the parameter in question is not connected to the preset text file primitive it won't be saved with the presets, so that should be problem solved. 😀
Cheers 😉
Exo
ccpurno ·
Thnx!, I wil try that as soon as I have time.
CC
exonerate ·
Actually I've just thought, that method would work when saving to text file, but not when using the "name" on the preset manager to save/rename the preset.
It would definitely work with my Preset Manager, because that doesn't use the preset manager primitive at all for presets, it's only there to show the parameters to the host so they can be saved with the project.
Cheers 😉
Exo
matti ·
I wouldn't try to work any cumbersom and dangerous hacks to get it working. A settings text file is the best, safest and most "clever" way to do it 🙂
That would also make it "global". Every instance would have the same settings(upon loading the setting file ofcourse).
bootsy ·
Had similar problems here too - there seems to be no proper way to have some parameter not under preset control but to get the host to recall it correctly after song reload.
In your case I would recommend a separate configuration file as matti already suggested.
exonerate ·
Yeah actually just use a text file, that is the proper way to do it, I actually thought of a really simple way of doing it with the standard preset manager without a text file, but preset data doesn't work through a selector, which is weird.
Cheers 😉
Exo
ccpurno ·
Thnx Guys.
Will try both options and report back.
Hope to have some time tomorrow. (its a little bit hectic on my job now. just came home 🙂 )
CC
ccpurno ·
Thnx Guys,
I tried both and indeed: text file was the way to go.
Actually 2 text files. 😉 1 For the Panel image setting and 1 for the LCD 😉
It remembers the skin settings correctly, even when inserting a new
instance of my VSTi.
I believe I could write the settings to 1 text file using the (parser) rule primitives,
but I wonder if there is any more simple way to write/read 2
different module states to 1 text file.
Grtz,
CC
matti ·
Hmm.. what? Use it as a StringArray.
ccpurno ·
Thnx, I will try that!
CC
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker