New subject: Jack fallback to alsa when firefire device off?

18 Feb 2011

Thu, 17 Feb 2011 10:30:47 -0500 письмо от Paul Davis &lt;paul(a)linuxaudiosystems.com&gt;om>:

...
  On Thu, Feb 17, 2011 at 10:23 AM, Dan Capp
&lt;reflectremain(a)gmail.com&gt;
 wrote:
  why install pulseaudio in the first place? I
don't know to be honest.  I'm
  still getting to grips with how Linux audio works
and what the various
 drivers and tools even do, let alone how they do it. So it's good to  hear
  someone with a different perspective on the
usefulness of PulseAudio etc.
 The KXStudio website states the following:
 "users will be glad to know that Jack2 is present and that *all*  audio
  output is sent to it. This includes Pulse-Audio,
which means that you  don't
  have to stop Jack if you need to, for example,
open a Web Browser to  watch
  some tutorial videos."
 I've read lots of people agree that this is a great idea - I'm  still
trying
  to fully understand why because it seems that I
DO need to stop Jack, or  at
  least re-route it, if I want to open a web
browser and watch some  tutorial
  videos.  
 Personally, I would say that KXStudio has made a mistake here. There
 is no reason to run PulseAudio for this purpose. Torben wrote a
 libflashsupport-jack which routes Flash straight to JACK, and
 http://jackaudio.org/faq describes ways to get a variety of other
 desktop software to talk to JACK. I spend all day listening to
 internet radio and my own music collection via Rhythmbox, browing the
 catalog at emusic.com, watching Flash *and* working on Ardour ... all
 via JACK and all without a large, complex layer like PulseAudio in the
 middle.

 Some of these are not quite as robust as they should be but it would
 be far better (I think) to focus resources on making them more robust
 than introducing PulseAudio as a desktop<->JACK middle layer.
 _______________________________________________
 Linux-audio-user mailing list
 Linux-audio-user(a)lists.linuxaudio.org
 http://lists.linuxaudio.org/listinfo/linux-audio-user There is not mistake. Each
way has advantages and disadvantages. As for me - when i work with pro audio software, i
don't like to lost jack-less applications, like web browser. For most software, which
may, there are default settings to use jack - i.e., audacious, vlc, and kde sound system
has jack backend at highest priority. As for switch between firewire / alsa - it could be
done easily, as simple as lash_button (but checkbox and written with python... probably,
even as some applet).

Btw, latest version of jack2-simple-config in KXStudio has own configurator, which can
change settings on the fly, but when i changed backend between dummy and alsa (firewire -
did not use yet), changes take effect only when i stop and start jack later (oh, studio).
Also it is nice, to have some effects host (ingen or some rack) for output. I.e., i have
ladish project with jack-rack (with Plate Reverb Stero) and musescore, because freeverb,
used in fluidsynth, as much as all other convolver-based reverbs, can't give good
results for short reverbs (in JR i muted long reverb, that sounds like reall hall). Since
freeverb has only one very long impulse, it just truncates it for short reverbs, producing
awful result (more like resonance of huge metallic list, that reverb).

Re: [LAU] Jack fallback to alsa when firefire device off?