From: Sebastian Eichner <mailsp@sebastian-eichner.de>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] A2DP working :-) , voice not :-(
Date: Wed, 1 Dec 2004 08:39:06 +0100 [thread overview]
Message-ID: <200412010839.06669.mailsp@sebastian-eichner.de> (raw)
Hi all!
First of all: thank you very much for your work and your help!
As suggested i installed a vanilla 2.6.9 kernel with mh4-patches, and
also updated bluez-libs and bluez-utils to the current version 2.11.
And, success: with yesterdays cvs version i have a2dp audio working
with my BT420! BTW: As sox plays only a very few of my mp3's i use
mpg123 for decoding:
mpg123 -s test.mp3 |sox -t raw -r 44100 -s -w -c 2 - -r 44100 -s -w
-t au - |sbc/sbcenc - | ./a2play 00:08:F4:30:03:71
But: i cannot get the normal voice headset to work.
The aplay command starts but then i do not hear anything, nor does
aplay finish:
aplay -D plughw:Headset test.wav
Playing WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 22050 Hz,
Mono
In the system log i get the following entries:
Dec 1 08:32:08 linux kernel: snd-bt-sco: playback_trigger 0
Dec 1 08:32:08 linux kernel: snd-bt-sco: setting playback to NULL
Dec 1 08:32:09 linux kernel: snd-bt-sco: playback_open
Dec 1 08:32:09 linux kernel: snd-bt-sco: prepare ok bps: 16000 size:
8000 count: 2000
Dec 1 08:32:09 linux kernel: snd-bt-sco: playback_trigger 1
Dec 1 08:32:09 linux kernel: snd-bt-sco: setting playback to bspcm
Looks alright, doesn't it?
Do you have an idea what could be wrong? I checked the mixer settings
via alsamixer, which are fine too (BTW: what is this
"loopback"-switch?).
Thanks for any suggestions!
Sebastian
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2004-12-01 7:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 7:39 Sebastian Eichner [this message]
2004-12-01 7:54 ` [Bluez-devel] A2DP working :-) , voice not :-( Marcel Holtmann
2004-12-01 8:07 ` Sebastian Eichner
2004-12-01 8:31 ` Marcel Holtmann
2004-12-01 8:43 ` Sebastian Eichner
2004-12-01 9:43 ` Marcel Holtmann
2004-12-01 11:24 ` Sebastian Eichner
2004-12-01 11:31 ` Marcel Holtmann
2004-12-01 16:33 ` Sebastian Eichner
2004-12-01 11:35 ` [Bluez-devel] BTsco suche.org
2004-12-01 11:41 ` Marcel Holtmann
2004-12-01 11:57 ` suche.org
2004-12-01 12:08 ` Marcel Holtmann
2004-12-01 14:20 ` [Bluez-devel] btsco2 Thomas Lußnig
2004-12-01 17:58 ` Brad Midgley
2004-12-01 20:22 ` Domain Admin
2004-12-01 21:32 ` Brad Midgley
2004-12-01 21:51 ` Bluetooth
2004-12-01 23:54 ` Lars Grunewaldt
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=200412010839.06669.mailsp@sebastian-eichner.de \
--to=mailsp@sebastian-eichner.de \
--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