From: David Henningsson <david.henningsson@canonical.com>
To: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
General PulseAudio Discussion
<pulseaudio-discuss@lists.freedesktop.org>
Subject: idea: a reserve alsa plugin
Date: Thu, 02 May 2013 12:55:05 +0200 [thread overview]
Message-ID: <51824609.30405@canonical.com> (raw)
Just had an idea which I'll write down here before I forget it
again...and I'm not saying I'll implement this anytime soon either, but
here goes:
There is a device reserve protocol between PulseAudio and JACK2 - when
JACK needs the sound card, it'll send a dbus message to PulseAudio and
grab a name in D-Bus.
However, there are plenty of applications who like to access ALSA
directly, without going through JACK2 or PulseAudio. By making a
"reserve" plugin, we could have this functionality for those apps too.
In practice, if the app usually opens "plughw:0" or "hw:0", it could
instead open "reserve:plughw:0" or "reserve:hw:0" to also reserve the
device from PulseAudio usage while the device is open. Meanwhile,
PulseAudio is free to use other audio devices (which is not the case
when using e g pasuspender).
How does that sound?
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
next reply other threads:[~2013-05-02 10:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 10:55 David Henningsson [this message]
2013-05-02 12:37 ` [pulseaudio-discuss] idea: a reserve alsa plugin Arun Raghavan
2013-05-02 13:23 ` David Henningsson
2013-05-02 14:13 ` "Negative" volume settings in a kcontrol Mike Looijmans
2013-05-06 13:22 ` Clemens Ladisch
2013-05-28 11:46 ` Mike Looijmans
2013-05-29 19:42 ` Mark Brown
2013-05-31 7:01 ` Mike Looijmans
2013-07-16 13:45 ` Need help diagnosing "hw_ptr skipping" message Mike Looijmans
2013-07-17 14:02 ` Clemens Ladisch
2013-05-02 14:28 ` idea: a reserve alsa plugin Tvrtko Ursulin
2013-05-02 14:37 ` [pulseaudio-discuss] " David Henningsson
2013-05-02 14:50 ` Tvrtko Ursulin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51824609.30405@canonical.com \
--to=david.henningsson@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=pulseaudio-discuss@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).