linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Marian Harbach" <harbach@Mathematik.Uni-Marburg.de>
To: <linux-bluetooth@vger.kernel.org>
Subject: AW: [PATCH 1/1] Bluetooth: fix unset of RemoteBusy flag
Date: Tue, 15 Dec 2009 21:58:16 +0100	[thread overview]
Message-ID: <000401ca7dc9$550a3030$ff1e9090$@uni-marburg.de> (raw)
In-Reply-To: <1260899794-5107-1-git-send-email-gustavo@las.ic.unicamp.br>

Hi,

I have the same problem as described in this post:

http://www.spinics.net/lists/linux-bluetooth/msg03627.html

I found that depending on filesize, the original input is delayed by some
bytes (180-260 for 16kHz PCM input) and additionally the first few samples
are overwritten when doing sbcenc followed by sbcdec.

Is there a fix for this issue? 

Cheers
Marian


  reply	other threads:[~2009-12-15 20:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-15 17:56 [PATCH 1/1] Bluetooth: fix unset of RemoteBusy flag Gustavo F. Padovan
2009-12-15 20:58 ` Marian Harbach [this message]
2009-12-15 21:52   ` Gustavo F. Padovan
2009-12-17 20:06 ` Marcel Holtmann

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='000401ca7dc9$550a3030$ff1e9090$@uni-marburg.de' \
    --to=harbach@mathematik.uni-marburg.de \
    --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).