On Wed, 17.06.09 07:35, Ng Oon-Ee (
ngoonee@...) wrote:
> Hi Lennart,
>
> Would there be a script-based alternative to the pavucontrol method,
> then? Or is Jack2 'it' in that sense?
pactl set-card-profile foo off
> 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?
The device reservation logic is (as the name suggests...) per
device. i.e. only the device jack asks for will be released. And when
JACK goes away PA will again take posession of it. While the device is
taken by jack it is marked 'suspended' in PA.
And what I was proposing at the beginning of that other thread is that
if Jack takes a service name on the bus PA could watch for it and load
the connectivity modules automatically, providing some ports in jack
that folks can connect if they wish.
Lennart
--
Lennart Poettering Red Hat, Inc.
lennart [at] poettering [dot] net
http://0pointer.net/lennart/ GnuPG 0x1A015CC4
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
