Re: [tim-janik/beast] BSE: SF2: use shared engine module instead of global soundfont lock (#85)

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.

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.

I agree that ultimately the solution I submitted is not perfect.

To avoid long discussions, I'll try to put more work into this branch and resubmit a new version that can hopefully do this without lock.

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]