On Wed, 2009-06-17 at 01:29 +0200, Lennart Poettering wrote:
> On Wed, 17.06.09 07:04, Ng Oon-Ee (
ngoonee@...) wrote:
>
> > I've been lurking round the jack-devel list, following the dbus
> > 'thread' (I believe something of this magnitude is more a rope than a
> > thread, though). Someone mentioned PA grabbing everything, in the case
> > of more than one sound cards in the machine (as is the case with all
> > pro-audio setups, I believe).
> >
> > Besides the solution that Lennart mentioned, pavucontrol, this can be
> > automated by editing /etc/pulse/default.pa, removing the lines
> > concerning module-hal-detect, and manually loading
> > module-alsa-sink/source with the correct hw parameters. This would be
> > more convenient for scripts/packagers, whatever.
>
> Which I can only advise against. For many reasons: breaks hotplug,
> module-alsa-sink/-source are obsolete, unstable device names, and so
> on and so on.
>
> Just use pavucontrol or just upgrade to JACK2 and everything starts to
> work witout any further intervention due to the mentioned device
> reservation logic.
>
> Lennart
>
Hi Lennart,
Would there be a script-based alternative to the pavucontrol method,
then? Or is Jack2 'it' in that sense?
As I have previously mentioned on the pulse list, the reason I turn off
hotplug through HAL is so I can, through scripts, define whether I want
PA accessing my sound card or my jack server (via
module-jack-sink/source). I admit to a lack of understanding on the
specifics of the new JACK2 device reservation, as well as the dbus
hoo-ha surrounding it, but it seems to me that the general effect would
be to suspend PA totally when JACK2 starts and resume it when JACK2
finishes. Is this understanding correct?
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
