From: Frederic Dalleau <frederic.dalleau@access-company.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] A few questions about bluetooth-alsa project
Date: Tue, 03 Jul 2007 18:40:27 +0200 [thread overview]
Message-ID: <468A7BFB.4080401@access-company.com> (raw)
In-Reply-To: <468A7156.1050708@gmail.com>
Hi Rogue,
> I see that there are some alsa-lib modules being built. So, do I still
> need to specify a custom asoundrc file? Wouldn't the device show up
> automatically in the applet's preferences?
>
As far as I know, the device won't show up whether there is an .asoundrc
or not.
However, when the softvol plugin is declared in .asoundrc, it appears in
the mixer. So I suspect there is a way to make the plugin appears in the
players. I have never looked after that for now.
At least the entry must be declared in .asoundrc or
/usr/share/alsa/alsa.conf. I just found a utility called asoundconf.
This may be funny to try.
Hope this helps.
Frederic
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-07-03 16:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 20:33 [Bluez-devel] A few questions about bluetooth-alsa project Rogue
2007-07-03 1:58 ` Brad Midgley
2007-07-03 3:31 ` Marcel Holtmann
2007-07-03 15:55 ` Rogue
2007-07-03 16:40 ` Frederic Dalleau [this message]
2007-07-03 16:56 ` Frederic Dalleau
2007-07-11 20:14 ` Rogue
2007-07-03 18:14 ` Brad Midgley
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=468A7BFB.4080401@access-company.com \
--to=frederic.dalleau@access-company.com \
--cc=bluez-devel@lists.sourceforge.net \
/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.