> > Why exactly is a mutex needed in the first place, let alone in an engine
> > module?
>
> Because multiple engine modules share state, especially because multiple
> engine module access the same fluid_synth_t instance, and could (possibly)
> call API functions on the same fluid synth instance at the same time.
>
In that case, there should be *one* engine module around the fluid_synth_t
instance, and the other modules should connect to this one module as input.
> > As stated above, ultimately the code needs to be reworked to avoid the lock
> > and use jobs or similar means to update engine module state.
Can we get rid of the shared state once the fixed fluidsynth 2.0.5 is out, or
is this unrelated?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/pull/85#issuecomment-484286150
_______________________________________________
beast mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/beast
