linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jelle de Jong <jelledejong@powercraft.nl>
To: Brad Midgley <bmidgley@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: possible sbc codec bug with audio glitches
Date: Sun, 16 Nov 2008 22:37:30 +0100	[thread overview]
Message-ID: <4920929A.30703@powercraft.nl> (raw)
In-Reply-To: <d89ddf300811160629v29a0602cgdfcf25ade32c4cfc@mail.gmail.com>

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

Brad Midgley wrote:
> Jelle
> 
>> The strange thing is that I can only hear the glitches on the right side
>> of the headset.
> 
> That is very strange it is only on one side. Do you know if you were
> you using the joint stereo setting in the codec?
> 

Thank you Brad for taking the time to read and answer to my question,
this is really appreciated. I dont exactly know what you mean with joint
stereo settings in the code?

I use the bluez git build on 2008-11-06. The only info I got is from the
bluetoothd running in debug mode, please see the attachment for more
information.

I hope the below section is the most relevant?

config a2dp - device = 00:0C:55:D1:C9:78 access_mode = 2
codec sbc - frequency = 1 channel_mode = 1 allocation = 1 subbands = 1
blocks = 1 bitpool = 44
a2dp_source_config: selected SEP 0xb81b1020
avdtp_ref(0xb81acbf0): ref=3
setup_ref(0xb81b62a8): ref=1
avdtp_set_configuration(0xb81acbf0): int_seid=1, acp_seid=1

Thanks in advance,

Jelle

[-- Attachment #2: bluez-glitches-debug.txt.tar.gz --]
[-- Type: application/x-gzip, Size: 3007 bytes --]

  reply	other threads:[~2008-11-16 21:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-16 11:52 possible sbc codec bug with audio glitches Jelle de Jong
2008-11-16 14:29 ` Brad Midgley
2008-11-16 21:37   ` Jelle de Jong [this message]
2008-11-17  1:15     ` Brad Midgley
2008-11-20 10:19       ` Jelle de Jong

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=4920929A.30703@powercraft.nl \
    --to=jelledejong@powercraft.nl \
    --cc=bmidgley@gmail.com \
    --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).