All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koster Ken <ken.koster@elektrobit.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] headset audio playback real slooowwww
Date: Fri, 9 Nov 2007 18:34:29 -0700	[thread overview]
Message-ID: <200711091734.29670.ken.koster@elektrobit.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1938 bytes --]

I'm fighting a problem that I hope someone here can help with.

For reasons I won't go into here I'm stuck with an environment based off of
Kernel 2.6.10 running on an arm processor. I have been able to upgrade 
bluez-lib and bluez-util to 3.19 and I'm attempting to make use of the 
audio service to send audio to a bluetooth headset.

Everything is working with the exception that the playback is at half the
normal speed, so everything recorded is lower in pitch and takes twice
as long.  (a seven second sound sample takes fourteen to play back)

We're playing a sound sample I recorded on my laptop with arecord, it's a
u8 sample and plays back perfectly on the laptop.

Using hcidump and comparing the data being sent on the laptop with that on
the arm system shows the identical SCO data stream.  The only difference 
we can really see is that the laptop sends an 'HCI Command: Read Remote
Supported Features" to the headset while the arm system doesn't.  This
appears to be due to changes in the kernel code.  I managed to patch the
kernel code to add this (and only this) but it makes no difference.  A hack
I know, but we're getting desperate :-)

Using aplay -v -Dplug:bluetooth sample.u8  shows the identical pcm structure
and setup as the laptop.   Plug PCM: linear conversion PCM (S16_LE) followed
by Slave: Bluetooth Audio Device.

Any suggestions as to where I should concentrate? 

-- 
Ken Koster
Senior Software Engineer

EB - Discover the Experience 
22745 29th Dr. SE, Suite 200
Bothell, WA 98021, USA 
Tel: +1 425-444-2691 
Fax: +1 425-686-3102 
ken.koster@elektrobit.com 
www.elektrobit.com


----------------------------------------------------------------
Please note: This e-mail may contain confidential information
intended solely for the addressee. If you have received this
e-mail in error, please do not disclose it to anyone, notify
the sender promptly, and delete the message from your system.
Thank you.


[-- Attachment #2: Type: text/plain, Size: 314 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

             reply	other threads:[~2007-11-10  1:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-10  1:34 Koster Ken [this message]
2007-11-11  2:19 ` [Bluez-devel] headset audio playback real slooowwww Jim Carter
2007-11-12 17:41   ` Ken Koster

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=200711091734.29670.ken.koster@elektrobit.com \
    --to=ken.koster@elektrobit.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.