From: Chip McArtor <mcm262@psu.edu>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Headset audio capture failing when using Bluez's ALSA plugin
Date: Tue, 08 Jan 2008 23:08:36 -0500 [thread overview]
Message-ID: <478448C4.3020102@psu.edu> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2175 bytes --]
Hello, I recently installed a USB bluetooth dongle with the intent of
using my Jabra BT500 headset in VOIP applications. I've followed the
Bluez audio service wiki with some degree of success; audio playback on
my headset works flawlessly with a variety of players. Audio recording
through the headset's mic, on the other hand, consistently stops
capturing audio after what appears to be ~250ms into the recording session.
I've tested this using both arecord and Skype's test call feature.
Running arecord yields
$ arecord -D bluetooth -f S16_LE
>boo.wav Recording WAVE 'stdin' :
Signed 16 bit Little Endian, Rate 8000 Hz, Mono
Aborted by signal Interrupt...
(manually stopped after several seconds)
The output file boo.wav is exactly 250ms long, and appears to contain
the very beginning of my recording. Skype similarly fails on the call
test (audio playback is fine, but the capture test fails to grab any
audio). In both cases, the Jabra makes the "call end" tone when I
finish my recording test. Also while recording, I get the following
system message several times:
hci_scodata_packet: hci0 SCO packet for unknown connection handle 45
Any thoughts on what the problem could be? Thanks for your help.
Chip McArtor
Software versions:
bluez-libs 3.24
bluez-utils 3.24
alsa-lib 1.0.14a
linux 2.6.23 i686 SMP
BT adapter info:
hci0: Type: USB
BD Address: 00:15:83:BE:9C:58 ACL MTU: 384:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:1984896 acl:74 sco:38817 events:196 errors:0
TX bytes:1970090 acl:57 sco:38591 commands:67 errors:0
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'BlueZ (0)'
Class: 0x080100
Service Classes: Capturing
Device Class: Computer, Uncategorized
HCI Ver: 2.0 (0x3) HCI Rev: 0x7a6 LMP Ver: 2.0 (0x3) LMP Subver:
0x7a6
Manufacturer: Cambridge Silicon Radio (10)
~/.asoundrc:
pcm.bluetooth {
type bluetooth
device 00:16:8F:08:8F:80
profile "voice"
}
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3278 bytes --]
[-- Attachment #2: Type: text/plain, Size: 278 bytes --]
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2008-01-09 4:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 4:08 Chip McArtor [this message]
2008-01-09 4:15 ` [Bluez-users] Headset audio capture failing when using Bluez's ALSA plugin Brad Midgley
2008-01-09 14:01 ` Chip McArtor
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=478448C4.3020102@psu.edu \
--to=mcm262@psu.edu \
--cc=bluez-users@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