Problem: Ca'nt make the EXE save a preset after export

[kortezzzz]

HI everybody,
I'm new to this forum and to FS, and I'm still learning the basics of this program.
First, I must say that after reading few posts, i see that the forum is great, and you guys are fantastic.

Well, my problem is very basic, i guest. I just don't have the knowledge to solve it
I'v just made my first project and tried to test it and i see that the exported EXE project
doesn't save my "after export" edits. its just loading the "pre-export" presets, now matter
what i do...
i"ll be glad to get some help
thanks in advance, and sorry for my bad english...

[MyCo]

The preset manager is made for VST export. In VST, preset changes are written to the VST host. The VST Host then has to somehow store that preset changes. Flowstone doesn't care about how the host actually stores it.
To save your preset changes in exported EXEs, you have to provide a storage mechanism. Eg. you can save your presets as TXT file (the preset manager has this function). But you'll have to reload that text file after the next start of your EXE to get your last control states.

[kortezzzz]

Thanks for the the fast reply, MyCo. got the point.
so, lets say that the presets are already stored as txt files
on my hard-drive; what should i do to load the last edits?
should i store first the new edits as a new bank and reload them manually?

i would like to make an automatic mechanism that can load the "defalt bank"
with my last edits every time i open the exported exe project. i wonder if there is
a way to "force" my project to go to a specific folder and read my "defalt bank"
or the "re-made presets" (last used) from there, right after the project get loaded.

thanks again, man.

[trogluddite]

Hi there, kortezzz,

What you want to do can be achieved in a rather round-about kind of way....

When you save a preset, the file path is constructed inside the preset manager as a string.
The trick is to get hold of this file path string, and save it in a separate text file that will always be in the same place - the exe's own folder is a good choice, as there is a "plugin folder" primitive that can reliably find it.
At load time, you can use an "After Load" primitive to trigger loading of the text file, extract the preset path, and pass it to the manager for loading.
I've used a similar system in the past for VST plugins where I want the plugin to override the settings stored inside the host - I'll see if I can dig up anything useful from my old schematics, as the system I used should be easy to adapt for putting into an exe.

[kortezzzz]

thank you, trog
Using the "after load" primitive sounds as the right way
to do the trick, but i still can't find a way to trigger my
project to open my last edited presets from the project's folder
automatically (without any dialog pop-ups, this is important. "clean job"... ).

a good schematic example would be great, man.
i also want to know if there are any other special rules
when using a "preset folder", like putting both EXE file and
preset folder in the same "parent folder" and act.

i also would like to say that the EXE exporting option is JUST AMAZING!!
one of the reasons why i love FS very much. it lets you make lovely
live tools that can be used without any daw. LOVE IT

thank you again, and i hope you will find the lost schematic...

[RJHollins]

Thanks TROG for explaining a procedure to do this. I never thought we'd have to do a 'work-around', but after both your's and MyCo's explanation, the technique you describe is the 'path' I'll try
Thanks!

[kortezzzz]

Hi RJHollins,
Thanks for trying. hope you'll find a way to do that. I tried some methods but without a success so far
wondering why its so difficult to perform. Have been thinking about using a combination of preset manager+save\load
file+custom folder primitive, but its not working for me.

[billv]

The trick is to get hold of this file path string, and save it in a separate text file.

So it is possible ....???...So 'alt preset' systems not needed.....
Interesting.