Re: [Yoshimi-devel] persistent Config and state

2025-01-26 Thread Kristian Amlie
Phew! There was a lot to go through in this thread. Apologies if I'm repeating some stuff here, there was so much I had to reply one by one, and send them as one batch. I think we are converging on something in the last email though, so feel free to skim the other replies. More below. On 2

Re: [Yoshimi-devel] persistent Config and state

2025-01-26 Thread Kristian Amlie
I think we are getting closer to an agreement here! 🙂 On 25.01.2025 00:51, ichthyo wrote: On 23.01.25 23:40, Will Godfrey wrote: Like that LV2 at startup would only see the hard defaults, and would not save anything to the main config or instance files, On 24.01.25 10:50, Will Godfrey wro

Re: [Yoshimi-devel] persistent Config and state

2025-01-26 Thread Kristian Amlie
Phew! There was a lot to go through in this thread. Apologies if I'm repeating some stuff here, there was so much I had to reply one by one, and send them as one batch. I think we are converging on something in the last email though, so feel free to skim the other replies. More below. On 2

Re: [Yoshimi-devel] persistent Config and state

2025-01-26 Thread Kristian Amlie
Phew! There was a lot to go through in this thread. Apologies if I'm repeating some stuff here, there was so much I had to reply one by one, and send them as one batch. I think we are converging on something in the last email though, so feel free to skim the other replies. More below. On 23.0

Re: [Yoshimi-devel] persistent Config and state

2025-01-24 Thread ichthyo
On 23.01.25 23:40, Will Godfrey wrote: Like that LV2 at startup would only see the hard defaults, and would not save anything to the main config or instance files, On 24.01.25 10:50, Will Godfrey wrote: ..., certainly for LV2 where the idea of a primary instance doesn't make sense. For sta

Re: [Yoshimi-devel] persistent Config and state

2025-01-24 Thread Will Godfrey
On Fri, 24 Jan 2025 01:17:43 +0100 ichthyo wrote: >On 23.01.25 23:40, Will Godfrey wrote: >> Like that LV2 at startup would only see the hard defaults, and would not save >> anything to the main config or instance files, but would be relying on: >> SynthEngine::getalldata( >> SynthEngine::putalld

Re: [Yoshimi-devel] persistent Config and state

2025-01-23 Thread ichthyo
On 23.01.25 23:40, Will Godfrey wrote: Like that LV2 at startup would only see the hard defaults, and would not save anything to the main config or instance files, but would be relying on: SynthEngine::getalldata( SynthEngine::putalldata( Hi Will, see at the end of my other mail. Where I've e

Re: [Yoshimi-devel] persistent Config and state

2025-01-23 Thread Will Godfrey
I've just done an experiment with a side branch. I added the lines: if (isLV2) return; to the very start of: Config::loadConfig( Config::updateConfig( Like that LV2 at startup would only see the hard defaults, and would not save anything to the main config or instance files, but would be

Re: [Yoshimi-devel] persistent Config and state

2025-01-23 Thread ichthyo
On 22.01.2025 23:14, ichthyo wrote: Thus, if you know an example where just loading a LV2 project will silently change a *configuration setting* (as opposed to some further runtime state), then we'd break the new invariant and we'd have to consider how to sort that out. Again, what I say here