From: Mikael Bengtsson <micke_b.b@hotmail.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] SCO Question
Date: Fri, 24 Aug 2007 13:35:31 +0200 [thread overview]
Message-ID: <BAY114-W2714BF579C6DC788F8247CD7D70@phx.gbl> (raw)
In-Reply-To: <076BF2A0-A0AF-44B5-9A4D-2BC3EBBE2940@cadvium.net>
[-- Attachment #1.1: Type: text/plain, Size: 2264 bytes --]
Hello Robert!
I want to do the same thing as you. The methods for redirecting audio according to the different HOWTO:s seems to involve A2D2P which, I think, is used for point-to-point communication with a headset. A2D2P is not SCO, but rather ACL (am I right)?
I would like to receive SCO and redirect it to the sound card via Alsa. The idea is that I will recieve SCO in a buffer and then write the buffer to the sound card with Alsa functions. The sound card must be initalized with the correct parameters regarding sample rate, PCM format and so on before beginning to write to the buffer.
I will also record voice via the sound card and then write to a buffer to the socket for SCO.
We have a test version where the voice from a Bluetooth client is echoed back from the master to the client. The result is that the person talking in the headset will here himself. This is simply done by reading the SCO socket and writing back the same data to the socket.
-Mikael> To: bluez-devel@lists.sourceforge.net> From: rbscott@cadvium.net> Date: Wed, 22 Aug 2007 11:23:16 -0700> Subject: [Bluez-devel] SCO Question> > Hello Bluez,> > How would I go about redirecting incoming SCO data to an alsa device, > and transmit incoming audio data out as SCO?> > I have read the following pages,> http://wiki.bluez.org/wiki/Audio> http://wiki.bluez.org/wiki/HOWTO/AudioDevices> > but everything described seems to do too much. I would prefer to > handle the RFCOMM channel, and SDP registration elsewhere. > Presently, I just want to determine how to redirect the SCO traffic.> > Thanks,> --robert> > -------------------------------------------------------------------------> This SF.net email is sponsored by: Splunk Inc.> Still grepping through log files to find problems? Stop.> Now Search log events and configuration files using AJAX and a browser.> Download your FREE copy of Splunk now >> http://get.splunk.com/> _______________________________________________> Bluez-devel mailing list> Bluez-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/bluez-devel
_________________________________________________________________
Dela filer, prata och spela spel med dina vänner på Messenger!
http://get.live.com/?revipcountry=se
[-- Attachment #1.2: Type: text/html, Size: 2786 bytes --]
[-- Attachment #2: Type: text/plain, Size: 315 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-08-24 11:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 18:23 [Bluez-devel] SCO Question robert
2007-08-24 11:35 ` Mikael Bengtsson [this message]
2007-08-24 12:06 ` Marcel Holtmann
2007-09-06 11:03 ` Mikael Bengtsson
[not found] <A1F0D47583A2D711919F00600819B3A45BDC65@goofy.vitronics.com >
2004-07-09 7:48 ` [Bluez-devel] SCO question Arnaud Mouiche
-- strict thread matches above, loose matches on Subject: below --
2004-07-08 20:11 Williams, Richard
[not found] <A1F0D47583A2D711919F00600819B3A4028BAE@goofy.vitronics.com >
2004-07-08 14:08 ` Arnaud Mouiche
2004-07-08 13:12 Williams, Richard
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=BAY114-W2714BF579C6DC788F8247CD7D70@phx.gbl \
--to=micke_b.b@hotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox