On 22.01.25 22:00, Will Godfrey wrote:
The more I see this, the more I think LV2 should not touch the stand-alone
files: config, instance, state at all. As far as possible each LV2 instance
should be treated as a completely separate entity.
A new LV2 instance should only read the hard defaults, and from then on use
get and put all data, which the host will then manage where and when it
wants.
There is a lot you want to configure different than the "hard defaults".
Just look into the settings GUI. Oscil size, Keyboard layout, PadSynth
crossfade, XML compression....
Moreover, you definitively want to preserve your window layout.
The LV2 host has no GUI for this stuff.
Then on top comes my strong objection against introducing lots of
specific LV2 behaviour. The complexity within Yoshimi is already hard
to manage without it.
First of: what are the actual problems we see with the current state of affairs
regarding LV2? Before we got into this discussion, we were able to live with the
current situation since some years, and at least my own experience shows that
configuration is rather an occasional annoyance when working with several
LV2 or standalone instance. Not a real problem. Because you can manage somehow.
If we really think that config handling for LV2 is a serious problem,
shouldn't we rather consider to store config differently for LV2 and apart
from the standalone settings? Wouldn't it be sufficient just to use a different
instance-key (for the config files and the window layout files?) Like e.g.
a 6 digit hash-ID which is somehow derived from an identifier which
characterises the plugin instance reproducably?
-- Hermann
_______________________________________________
Yoshimi-devel mailing list
Yoshimi-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/yoshimi-devel
