linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: RE: headset target seems to be playing but no sound
Date: Fri, 29 Jan 2010 17:03:20 -0500	[thread overview]
Message-ID: <1264802600.26570.717.camel@pc.interlinx.bc.ca> (raw)
In-Reply-To: <FE57175CCE23E5419899C1B0CFA26FAD12CDF72D40@EXMBXSD.dm.solekai.com>

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

On Fri, 2010-01-29 at 13:42 -0800, Gunn, Brian wrote: 
> 
> Don't know if this will help you guys or not, but I get garbled audio unless I specify a 48 byte buffer.

Sadly, no, this does not help.  :-(

> Here's the command I use to send audio to headsets:
> 
> aplay -D bluetooth -f S16_LE --buffer-size=48 test.wav
> 
> For me though, without the "--buffer-size=48", I get audio; it's just really garbled.

I've never got garbled.  Just always get the beep before and after the
audio is supposed to be playing.

b.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2010-01-29 22:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8396c2281001242007n5ae20eccj53d496f1297e5d22@mail.gmail.com>
2010-01-25  4:13 ` headset target seems to be playing but no sound Chao Deng
2010-01-25  4:21   ` Brian J. Murrell
2010-01-26  1:23     ` pigiron
2010-01-27  3:28       ` Chao Deng
2010-01-29  3:50         ` pigiron
2010-01-29 20:23           ` Brian J. Murrell
2010-01-29 21:42             ` Gunn, Brian
2010-01-29 22:03               ` Brian J. Murrell [this message]
2009-12-31  5:14 Brian J. Murrell

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=1264802600.26570.717.camel@pc.interlinx.bc.ca \
    --to=brian@interlinx.bc.ca \
    --cc=linux-bluetooth@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).