KXStudio also sets Jack up as the uber sound driver for the system, which I LOOOVE! I never have to think about whether or not Jack needs to be started, etc., because it's always running. KXStudio also integrates Pulseaudio as just another Jack client. This makes it really easy to capture the sound out of anything that happens to be running on my PC. And everything Just Works(tm).


On 10/31/2012 01:07 AM, Holger Marzen wrote:
On Wed, 31 Oct 2012, John O'Hagan wrote:

On 29/10/12 09:33, D. Michael McIntyre wrote:
On 10/28/2012 02:06 PM, Jim Cochrane wrote:
jackd is started up whenever I start
rosegarden, even though this box is unchecked.  Is there another spot in
the GUI to disable jack that I'm not seeing?
There is no box for that as such.  Rosegarden isn't starting jackd so
much as the JACK API is starting jackd.  I misremember the technical
details, but basically we made a minor change to use a different API
call, and now the audio server starts itself when Rosegarden does if
it's not already running.  This is basically a good thing, since it
starts Rosegarden with all of its features enabled by default.

I suppose we could consider making some config option that would prevent
Rosegarden from even attempting to start JACK, but I'd really rather not
bother unless there is a lot of demand.  It's just one more confusing
configuration option for people to misunderstand, one more thing for
everybody to have to translate, and one more thing for users to forget

I agree with the approach, but there is an unfortunate consequence in 
this case, at least on my Debian XFCE box, RG 12.04: after using 
Rosegarden, jackd remains running, and prevents all my normal (ALSA) 
applications' audio from working, except the handful which are 
automatically jack-aware. This means manually terminating jack, from a 
task manager or whatever, after each RG session; users still have to 
manage jack, with all the attendant potential for confusion.
On my Xubuntu 11.10 I never had a problem. Rosegarden started and endet
my jackd. My .jackdrc was "/usr/bin/jackd -dalsa -r44100 -p128 -n2 -Xseq
-D -Chw:5,1 -Phw:0,1"

But since JACK has so many advantages (e.g. recording flash-sound when
running firefox to record streaming-only content in the web) I decided
that all applications should be redirected to jack. This works with the
following ~./asoundrc or /etc/asound.conf:

pcm.!default {
    type plug
    slave.pcm "jack"

pcm.jack {
    type jack
    playback_ports {
        0 system:playback_1
        1 system:playback_2
    capture_ports {
        0 system:capture_1
        1 system:capture_2

My jackd is now started by qjackctl that's autonatically started by my
session manager.

I can now even record the sound that's produced by virtual machines
(VirtualBox), eg. browser sounds of a Windows-VM.

Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe