On Sun, 2016-04-17 at 11:32 +0100, Richard Shann wrote: > On Sun, 2016-04-17 at 09:48 +0100, Richard Shann wrote: > > On Sat, 2016-04-16 at 22:27 +0100, Richard Shann wrote: > > > But, all this depends on getting Denemo working on your > machine ... > > > there is no earthly reason fludisynth should be complaining about > a > > > full > > > queue, as nothing has been output until you try to play back... > > > > Well, as reported another email, I have discovered the circumstance > in > > which this happens - it is when another instance of Denemo is > already > > running (or so it seems). > > Well, it seemed so, but on re-trying a few times I see this flood of > fluidsynth queue full messages without any other instance of Denemo > running. So it would seem to be triggered off by something else. It > also > stops once the program is running,
I've run it under gdb and it actually stops when a new thread starts [New Thread 0xf1dbdb40 (LWP 20791) so this indicates that indeed some threads are not forced to start in a specific order. The other thought I had is that it could be due to running a 32-bit executable on a 64-bit machine, as I never see it on the version I build on this 64-bit machine. I can test this hypothesis next time the 64-bit binary gets built. Richard _______________________________________________ Denemo-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/denemo-devel
