Linux bluetooth development
 help / color / mirror / Atom feed
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 22:32:44 +0100	[thread overview]
Message-ID: <41F95DFC.6060805@webstuhl.net> (raw)
In-Reply-To: <41F91420.8080300@xmission.com>

Hi Brad,

Brad Midgley schrieb:

> Your program would be an alsa client, copying from one alsa device to 
> another. No btsco changes at all.

yup, I have written some "prove of concept" proggy which copies
the mic - stream from the soundcard to the headset-earphone.
Bad, bad style, but it works (ALSA-API only).

But: To finally manage the other way round (Headset mic to
soundcard playback) the code should work in some sort of
Duplex mode.

Since I still think, this whole thing can be accomplished via
asound.conf and/or jackd (or even some sort of pipe-system),
I'll ask around if someone has already done this kind of
setup.

greetings
ben

PS Is there a problem with mail delivery on this list?




-------------------------------------------------------
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

  reply	other threads:[~2005-01-27 21:32 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
2005-01-27 12:51     ` Lars Grunewaldt
2005-01-27 16:17     ` Brad Midgley
2005-01-27 21:32       ` Ben Pezzei [this message]
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=41F95DFC.6060805@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