From: Holger M. <ho...@ma...> - 2013-01-30 07:34:01
|
On Tue, 29 Jan 2013, Aere Greenway wrote: > Rosegarden and Fluidsynth Developers: > > In working with Fluidsynth problems, the Fluidsynth developers have > wondered why I insist on using JACK with Qsynth, rather than just > configuring it to use PulseAudio. Yesterday I finally found out why I > do this, but what the cause of the problem is, possibly both sets of > developers (together) might be able to postulate. > > Here are the steps of a test you can do to illustrate the problem: > > 1. Configure Qsynth to use "pulseaudio" instead of "jack". Even doing > this can cause hangs if you have more than one engine configured. Best > approach is to not restart the engine when it prompts you, instead, > terminating Qsynth, and bring it back up after completing the > configuration changes. Using Pulse and JACK works here by disabling Pulseaudio clients to start it (autospawn = no in /etc/pulse/client.conf) and starting Pulseaudio in QjackCtl. See http://www.marzen.de/Holger/pulseaudio_and_jack/ Fluidsynth is available as a DSSI module to be used in Rosegarden. No problems at all AND lower latencies. |