try starting jackd (via qjackctl?) with a greater client timeout interval, say 3sec (jackd -t3000...)
usually, fluidsynth takes its time to load a soundfont and that time is proportional to it's file size and number of instruments--the bigger the longer--during that time, jack thinks that fluidsynth is not responsive and might kick it out from the chain, no matter if it's only on a fluidsynth stanza startup--qjackctl/jackd default client timeout is or used to be 533ms, a way too short for instance fluidsynth loading a full gm 8mb+ soundfont nowadays.
nb. i write fluidsynth and not just qsynth, as the latter is a hardwired front-end to the former. got that?
try starting jackd (via qjackctl?) with a greater client timeout interval, say 3sec (
jackd -t3000...)usually, fluidsynth takes its time to load a soundfont and that time is proportional to it's file size and number of instruments--the bigger the longer--during that time, jack thinks that fluidsynth is not responsive and might kick it out from the chain, no matter if it's only on a fluidsynth stanza startup--qjackctl/jackd default client timeout is or used to be 533ms, a way too short for instance fluidsynth loading a full gm 8mb+ soundfont nowadays.
nb. i write fluidsynth and not just qsynth, as the latter is a hardwired front-end to the former. got that?
hth.
cheers