To get jack2's sync mode through qjackctl, go to the Setup window, and
add "-S" (capital S) to the end of the "Server Path" text. It is
important to not have extra spaces in that text, the server won't start
if you do.
Your report is most interesting. I am very glad to hear of ChickenSys
Translator; if I ever need it, I'm buying it (I'll run it in a VM of
course *grin*). I do have to wonder about the crashing. If the
original SF2 was bad enough, it could crash fluidsynth quite easily, and
at least in theory, the ChickenSys Translator could have translated the
badness of the original SF2 over. "Badness" could be many things; I
have been lately studying a bit of what really can go into an SF2 (or a
gig), and there's all sorts of transforms, effects, etc. If the
original SF2 was made with the wrong overabundance of that stuff, the
process trying to play it (or the gig converted from it) would simply
tie itself into a CPU-load knot and die, perhaps by trying to create too
much simultaneity in reverb (for an oversimplified example). And if
anything Jackish fails in really the wrong way (CPU overload is often
one way), it often takes Jack with it. I would love to see an
"auto-restart" in qjackctl :-)
But jack2 certainly is far more able to handle horsepower problems. I
am so happy it's in Debian Experimental!!! I wonder if LinuxSampler is
prepared to handle multi-CPU the way jack2 is?
> Thanks Jonathan for the heads up on Jack2!
Linux-audio-user mailing list