On 17.01.2025 21:53, ichthyo wrote:
However, I'd be cautious to work from a mental model that distinguishes
between an "LV2" Yoshimi, or an "Standalone Yoshimi" or even a "CLI
Yoshimi".
Because, up to now there is only one core Yoshimi engine and runtime,
which is only slightly and (really superficially) configured differently,
according of the launch mode (standalone vs. LV2).
Please also see the code examples from my other mail.
There is almost no impact of LV2 regarding config, and we should keep it
this way. In all the variants available right now, Yoshimi does the *full*
config handling, including all state loading and also all persistence,
for all of the base, instance, GUI / Window state and whatever.
But how do you see state loading and saving fitting into all of this?
State loading and saving happens constantly with LV2, which means it's
changing config all the time. Simply loading a project in your DAW with
LV2 instances can completely change the settings when firing up an
unrelated standalone instance later.
I know the it eases implementation, but I think this is very unintuitive
from a user perspective.
--
Kristian
_______________________________________________
Yoshimi-devel mailing list
Yoshimi-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/yoshimi-devel
