From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] audio problems with a2play
Date: Tue, 23 Nov 2004 22:14:56 +0100 [thread overview]
Message-ID: <1101244496.27351.29.camel@pegasus> (raw)
In-Reply-To: <20041123203836.046fb4f4.henryk@ploetzli.ch>
Hi Henryk,
> I also saw that you were modifying the way a2play packs its frame though
> that still doesn't look right to me. Maybe we should talk about our
> interpretation of the specs in this case.
>
> The way I see this we should have a media packet header from AVDTP p. 45
> and a media payload from A2DP p. 23. The media packet header should be
> 12 octets in length (as we don't use any CSRC). I think a2play does
> these right, except for the timestamp (I'll come to that in a second).
>
> Next thing should be media payload header from A2DP which is 1 octet in
> length and correct, too.
>
> Then there should be an SBC frame as per A2DP p. 53 just like my code
> produces them. That should start with 0x9C which I can't see anywhere in
> the a2play output.
so should it be and I got a trace from a friend with a prototype A2DP
device with a Zeevo ZV4002 and a Bluetooth stack from Impulsesoft. They
actually do it this way, but GCT puts in 0xff 0xff. I haven't find any
combination to make my Aiptek headphone understand the one byte media
payload header. The very ugly thing is that this headphone is actually
A2DP qualified.
> Now I saw Marcel tried adding a timestamp (which I did, too, without
> any effects, sadly). The way I read section 4.3.3.1 of A2DP would be
> that there should be an imaginary clock counting at the sampling
> frequency of the SBC frames and whose value should then be put into the
> timestamp field. Or, simply put: Count the samples sent so far.
This was only a quick and dirty hack to see how my headphone behaves if
I fill in that field. Actually it don't cares at all. I will check the
other A2DP trace again, because I saw that they filled in the timestamp
value and maybe the only count the SBC frames.
> I've modified the CVS to my beliefs. Please correct me if you think I'm
> wrong.
Didn't showed up so far.
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
next prev parent reply other threads:[~2004-11-23 21:14 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
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 [this message]
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=1101244496.27351.29.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