Seems like an issue from latest 1.1.1, due to recent threading changes it's probably locking the whole internal synth process while reading engine settings. But not sure... better ask on the fluid-devel list?
I'm not seeing these xruns on my side, at least when pressing the "Setup". However, I am sure that (re)starting any engine with new settings, will indeed cause a burst of xruns no matter what. This is in fact a side-effect behavior and it only got worst with libfluidsynth >= 1.1.x. I'm afraid there's not much to do on the Qsynth camp. Fact is, depending on your system and what not, it is very probable for that to occur on all fluidsynth versions, just more aggressive now.
Which libfluidsynth version?
Seems like an issue from latest 1.1.1, due to recent threading changes it's probably locking the whole internal synth process while reading engine settings. But not sure... better ask on the fluid-devel list?
I'm not seeing these xruns on my side, at least when pressing the "Setup". However, I am sure that (re)starting any engine with new settings, will indeed cause a burst of xruns no matter what. This is in fact a side-effect behavior and it only got worst with libfluidsynth >= 1.1.x. I'm afraid there's not much to do on the Qsynth camp. Fact is, depending on your system and what not, it is very probable for that to occur on all fluidsynth versions, just more aggressive now.
Byee