From: Andre Renaud <andre@bluewatersys.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: Headset+Alsa problems (without Pulse Audio)
Date: Thu, 14 Jul 2011 11:19:47 +1200 [thread overview]
Message-ID: <4E1E2813.4040408@bluewatersys.com> (raw)
In-Reply-To: <20110713230417.GA15596@dell.ger.corp.intel.com>
Hi Johan,
> You can use whatever audio subsystem you like as long as it can hook up
> to the interface that BlueZ provides. The Media API itself hasn't been
> designed for any specific audio subsystem as such, but PulseAudio
> support for it was developed in parallel so it's what probably works
> best right now. And as I said, if you really need something else, such
> as ALSA user space plugins, feel free to take on the effort to port them
> to the Media API. The only reason they're about to get dropped is that
> no-one has shown the interest and resources to port them over and it
> doesn't make sense to keep maintaining two parallel API's (the old unix
> socket based and the new D-Bus based Media API). Btw, I also hope that
> you've done some proper study to conclude that PulseAudio doesn't suit
> your needs and are not just going on a "hunch" about it.
Thanks for that. Can you tell me if there are any other upper layer
systems that support the Media API?
Regarding the usage of pulse audio, our primary restriction at the
moment is disk space, so minimising the number of libraries used is of
great importance. We only have 8MB available on the final system, so as
you can imagine bringing in large libraries is not always possible. The
study you mention is what we're conducting at the moment. I'd welcome
any alternatives that you can suggest. Given what has been discussed so
far, we are currently doing further investigation into using PulseAudio.
Regards,
Andre
prev parent reply other threads:[~2011-07-13 23:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 4:38 Headset+Alsa problems (without Pulse Audio) Andre Renaud
2011-07-13 8:09 ` Johan Hedberg
2011-07-13 22:38 ` Andre Renaud
2011-07-13 23:04 ` Johan Hedberg
2011-07-13 23:19 ` Andre Renaud [this message]
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=4E1E2813.4040408@bluewatersys.com \
--to=andre@bluewatersys.com \
--cc=linux-bluetooth@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.