public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Henryk Plötz" <henryk@ploetzli.ch>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] audio problems with a2play
Date: Tue, 23 Nov 2004 03:34:29 +0100	[thread overview]
Message-ID: <20041123033429.132bf84b.henryk@ploetzli.ch> (raw)
In-Reply-To: <41A234FA.7020303@xmission.com>

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

Moin,

Hmm, If I'm not mistaken a2play has even other problems. I tried to play
sbc_test_01.sbc (for a start) through it while doing hcidump -x (the
old hcidump, that is). When doing the set configuration hcidump said

< ACL data: handle 0x002b flags 0x02 dlen 18
    L2CAP(d): cid 0x40 len 14 [psm 25]
      AVDTP(s): Set config cmd: transaction 0
      04 04 01 00 07 06 00 00 81 86 02 FA 

which decodes as
ACP SEID = 1 (OK)
INT SEID = 1 (OK)
Media transport capability (OK)
Media Codec capability
	Audio (OK)
	SBC   (OK)
	Sampling frequency = 16kHz (should be 48)
	Channel mode = Joint stereo (should be mono)
	Block length = 4 (should be 16)
	Subbands = 8 (should be 4)
	Allocation method = SNR (OK)
	Bitspool = 2 to 250 (OK)

As you can see the only correct parameter (apart from the hardwired
ones) is the allocation method. All others seem to be kind of bit
reversed. As a side note: The new hcidump AVDTP parser has the same
problem.

-- 
Henryk Plötz
Grüße aus Berlin
~~~~~~~ Un-CDs, nein danke! http://www.heise.de/ct/cd-register/ ~~~~~~~
~ Help Microsoft fight software piracy: Give Linux to a friend today! ~

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-11-23  2:34 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-22 18:12 [Bluez-devel] audio problems with a2play Brad Midgley
2004-11-22 18:39 ` Marcel Holtmann
2004-11-22 18:50 ` Brad Midgley
2004-11-23  2:34   ` Henryk Plötz [this message]
2004-11-23  3:49     ` Brad Midgley
2004-11-23  5:34       ` Marcel Holtmann
2004-11-23  6:06       ` Henryk Plötz
2004-11-23  9:34         ` Marcel Holtmann
2004-11-23 19:41           ` Henryk Plötz
2004-11-23 14:20         ` Brad Midgley
2004-11-23 19:38           ` Henryk Plötz
2004-11-23 21:14             ` Marcel Holtmann
2004-11-24  2:47               ` Henryk Plötz
2004-11-24  5:24                 ` Marcel Holtmann
2004-11-23 21:34             ` Brad Midgley
2004-11-23 21:52               ` Marcel Holtmann
2004-11-24  3:16                 ` Brad Midgley
2004-11-24  5:09                   ` Marcel Holtmann
2004-11-25  5:08                     ` Henryk Plötz
2004-11-24  2:58               ` Henryk Plötz
2004-11-24  4:22                 ` Brad Midgley
2004-11-24  4:54                 ` Brad Midgley
2004-11-24  5:06                 ` Marcel Holtmann
2004-11-26 15:46               ` [Bluez-devel] BT-Sco Thomas Lußnig
2004-11-26 14:59                 ` Marcel Holtmann
2004-11-26 16:33                   ` Thomas Lußnig
2004-11-26 17:19                     ` Marcel Holtmann
2004-11-28  3:07                 ` Brad Midgley

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=20041123033429.132bf84b.henryk@ploetzli.ch \
    --to=henryk@ploetzli.ch \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox