From: Brad Midgley <bmidgley@xmission.com>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: alsa-lib plugin devel
Date: Mon, 24 Jan 2005 01:17:21 -0700 [thread overview]
Message-ID: <41F4AF11.2090109@xmission.com> (raw)
Hi
I've started working on an alsa-lib plugin to send audio to a bluetooth
device (see http://bluetooth-alsa.sf.net)
I stubbed it out so I can see that it gets invoked when I address it
directly with
aplay -B 1000000 -D pcm.a2dp sound.wav
And I can see it is invoking the plugin code (just filled in with a
bunch of printf's). What I'm struggling with is how to make this driver
appear to clients that use alsa-lib. In the simplest case,
aplay --list-devices
Does not show my device in its list! So clients that look up alsa
devices will never see it.
my .asoundrc looks like:
pcm.a2dpplug {
type plug
slave { pcm "a2dp" }
}
pcm.a2dp {
type a2dp
bdaddr "00:08:F4:30:05:BB"
}
and I tried it with and without the first section. How do I get my
bluetooth device to show up in a device scan?
Brad
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next reply other threads:[~2005-01-24 8:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-24 8:17 Brad Midgley [this message]
2005-01-24 8:36 ` alsa-lib plugin devel Clemens Ladisch
2005-01-24 16:31 ` Brad Midgley
2005-01-24 16:46 ` Takashi Iwai
2005-01-24 16:49 ` Brad Midgley
2005-01-24 17:12 ` Takashi Iwai
2005-01-24 17:25 ` Marcel Holtmann
2005-01-24 16:53 ` Marcel Holtmann
2005-01-24 17:09 ` Takashi Iwai
2005-01-24 17:23 ` Marcel Holtmann
2005-01-24 17:41 ` Takashi Iwai
2005-01-24 17:56 ` Marcel Holtmann
2005-01-24 20:08 ` Brad Midgley
2005-01-25 10:19 ` Takashi Iwai
2005-01-25 13:12 ` Florian Schmidt
2005-01-24 9:24 ` Jaroslav Kysela
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=41F4AF11.2090109@xmission.com \
--to=bmidgley@xmission.com \
--cc=alsa-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.