From: David Elze <wegwerf@datenschrott.de>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] headset via bluetooth-headset not fully working
Date: Sun, 04 Nov 2007 18:46:37 +0100 [thread overview]
Message-ID: <1194198397.2823.29.camel@aero64.datenschrott.de> (raw)
In-Reply-To: <472DFD88.6060108@pagema.net>
Hey maHo,
Am Sonntag, den 04.11.2007, 18:12 +0100 schrieb maho+bluez:
> What aplay -v -Dplug:headset /usr/share/sounds/alsa/Front_Center.wav says?
> Doesn't it say that "Prorotocol not available (92)" ?
Nope, the output is just:
# aplay -v -Dplug:headset /usr/share/sounds/alsa/Front_Center.wav
Playing WAVE '/usr/share/sounds/alsa/Front_Center.wav' : Signed 16 bit
Little Endian, Rate 48000 Hz, Mono
Plug PCM: Rate conversion PCM (8000, sformat=S16_LE)
Its setup is:
stream : PLAYBACK
access : RW_INTERLEAVED
format : S16_LE
subformat : STD
channels : 1
rate : 48000
exact rate : 48000 (48000/1)
msbits : 16
buffer_size : 24048
period_size : 144
period_time : 3000
tick_time : 0
tstamp_mode : NONE
period_step : 1
sleep_min : 0
avail_min : 144
xfer_align : 144
start_threshold : 24048
stop_threshold : 24048
silence_threshold: 0
silence_size : 0
boundary : 1576009728
Slave: Bluetooth SCO Audio
Its setup is:
stream : PLAYBACK
access : MMAP_INTERLEAVED
format : S16_LE
subformat : STD
channels : 1
rate : 8000
exact rate : 8000 (8000/1)
msbits : 16
buffer_size : 4008
period_size : 24
period_time : 3000
tick_time : 0
tstamp_mode : NONE
period_step : 1
sleep_min : 0
avail_min : 24
xfer_align : 24
start_threshold : 4008
stop_threshold : 4008
silence_threshold: 0
silence_size : 0
boundary : 2101346304
Rate conversion is done (48kHz->8kHz) so this can't be the problem
anyways. Furthermore, if I play some longer file (or for example a
mp3 via xmms with the headset as alsa output device selected) the
same happens. Headset beeps initially, sound is playing according to the
user level in Linux quite normally but there is no sound at the headset,
just this very low noise (that goes away when the user level player,
aplay or xmms, is done).
Oh, and I also tried to record something off the headset via arecord:
the sound seems to be recorded (again, no errors at all) but the
resulting wav-file is just empty.
Greets, David
-------------------------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2007-11-04 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 16:14 [Bluez-users] headset via bluetooth-headset not fully working David Elze
2007-11-04 17:12 ` maho+bluez
2007-11-04 17:46 ` David Elze [this message]
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=1194198397.2823.29.camel@aero64.datenschrott.de \
--to=wegwerf@datenschrott.de \
--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