From: Ben Pezzei <ben@webstuhl.net>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] partly OT: pipe sound from Headset to soundcard
Date: Thu, 27 Jan 2005 00:54:17 +0100 [thread overview]
Message-ID: <41F82DA9.8090806@webstuhl.net> (raw)
In-Reply-To: <41F7D274.4030208@xmission.com>
Hi Brad,
Brad Midgley schrieb:
> I had the same thought.
>
> We have a way to send line in to a stereo headset but there is a delay.
> (see bluetooth-alsa.sf.net)
Yeah, but this covers A2DP only, right?
Right now, I was trying to accomplish this via asound.conf:
something like:
pcm.foo {
type multi
<map soundcard>
<map headset>
}
pcm.bar {
type route
slave.pcm "bar"
<map channels card out -> hs in>
<map channels card in -> hs out>
}
hope the idea is understandable
http://www.alsa-project.org/alsa-doc/alsa-lib/pcm_plugins.html#pcm_plugins_route
but I guess this won't work
> You could write something similar that runs in userspace and copies
> audio streams around using sco.
C hacking? ;) well, if there is really no other way, i could
try it. Are there some docs around to dig in or just the btsco
sources?
greetings
ben
-------------------------------------------------------
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
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-01-26 23:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 17:10 [Bluez-devel] partly OT: pipe sound from Headset to soundcard Ben Pezzei
2005-01-26 17:25 ` Brad Midgley
2005-01-26 23:54 ` Ben Pezzei [this message]
2005-01-27 12:51 ` Lars Grunewaldt
2005-01-27 16:17 ` Brad Midgley
2005-01-27 21:32 ` Ben Pezzei
2005-01-28 2:47 ` Collin R. Mulliner
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=41F82DA9.8090806@webstuhl.net \
--to=ben@webstuhl.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox