On 03.05.2025 13:39, Will Godfrey wrote:
On Tue, 29 Apr 2025 18:13:22 +0200
Kristian Amlie <krist...@amlie.name> wrote:
Yoshimi breaks both of these rules, and not in a way which is easy to
fix. We get away with allocating memory *most of time*, but the symptom
you are seeing is likely one of the few cases where it comes back to
bite us. To look on the bright side: Doing allocation-free programming
is really difficult, and Yoshimi works pretty well without it. We have
to appreciate that the developers working on it have one less pain point
to deal with.
The thing that's still puzzling is that on a first time start up in the
morning, and with one of the more complex voice patches, I'll get about a dozen
xruns on the first note, but no Xruns on any further playing of the same patch,
nor any *other* patch. If I then completely shut everything down and switch the
computer off, then about 10 minutes later switch on and try the same actions...
no Xruns at all.
Even across fresh reboots, things are going to be somewhat randomized,
for example due to parallelism, seek times on storage, etc. And I think
modern memory allocators do some randomization here and there to make
hacking more difficult.
But if it's completely deterministic, then I don't really have an answer
to that. 🤔
--
Kristian
_______________________________________________
Yoshimi-devel mailing list
Yoshimi-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/yoshimi-devel
