On 2011-05-18 00:29, Shamus wrote:
Hello everyone,
There was a problem with fluidsynth kicking out JACK on startup, which
was addressed with a patch as shown in the archives:
http://lists.nongnu.org/archive/html/fluid-dev/2011-02/msg00012.html
While this patch does indeed solve the problem of kicking out on
startup, there are at least two more places where this occurs (and there
may be others; I haven't done any exhaustive testing in that regard).
The first occurs when you reset fluidsynth; apparently it takes a
different path than the files that the patch touched. The same goes for
libfluidsynth: qsynth built from a patched fluidsynth displays the same
behaviors as an unpatched fluidsynth.
How to fix this is beyond me, I deal with microprocessor emulation, not
realtime audio. :-) However, I would be willing and able to test any
patches you care to send my way. ;-)
Warmest regards,
Shamus
Hi Shamus,
Being kicked out by Jack is essentially an optimization problem; Jack
kicks Fluidsynth out if it does not respond in time. I think this
timeout is configurable. Could it be that you're on the edge and just
need to adjust the timeout up a little bit, or increase the latency? In
general, it doesn't make sense that libfluidsynth would behave different
than the fluidsynth executable since the executable is just a wrapper
around libfluidsynth.
Also, are you using Jack for MIDI as well as audio, or do you use Jack
audio + alsa MIDI?
// David
_______________________________________________
fluid-dev mailing list
fluid-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/fluid-dev