public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] audio problems with a2play
Date: Mon, 22 Nov 2004 19:39:27 +0100	[thread overview]
Message-ID: <1101148767.26578.9.camel@pegasus> (raw)
In-Reply-To: <41A22C0B.4050008@xmission.com>

Hi Brad,

> The iPhono stopped producing recognizable sound using a2play a few days 
> ago... but even the most successful transfers with a2play have been 
> mixed with static.

last time I tested it, it worked quite well.

> I'm convinced we need a media payload header. Page 23 of the A2DP spec 
> shows how the media payload header should look.
> 
> I tried changing a2play to send media_payload_header instead of 
> sbc_frame_header and I got "quiet" noise when I did that. I tried 
> various frame counts with no luck.
> 
> I need to get a better idea of what is going on...
> 
> * which frame exactly is a2play's calc_frame_length measuring? Is it the 
> same "sbc frame" that they're talking about in a2dp p.24?

It is the SBC frame length without the 4 byte SBC header.

> * how did you decide to put 2 0xff bytes in the CSRC section of the 
> media packet header? Why isn't this CSRC a multiple of 4 bytes like the 
> spec suggests on avdtp p. 46?
> 
> * what is the CSRC? (spec says "The CSRC list identifies the 
> contributing sources for the payload contained in this packet")

Actually I already tried to follow the AVDTP and A2DP specification, but
with no luck. My Aiptek headphone doesn't want to play nicely and I have
no clue how they got this thing qualified by the Bluetooth SIG.

>>From my testing I saw that my headphone only cares about the CC value of
the AVDTP media header. All other values are not used.

The 0xff 0xff in front of the SBC header are not part of the AVDTP media
header. It is already the media channel payload. This follows non of any
specification I know of. And I only know that values, because I sniffed
a connection between the sender device and the headphone with a protocol
analyzer.

Regards

Marcel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-11-22 18:39 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 [this message]
2004-11-22 18:50 ` Brad Midgley
2004-11-23  2:34   ` Henryk Plötz
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=1101148767.26578.9.camel@pegasus \
    --to=marcel@holtmann.org \
    --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