From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] audio problems with a2play
Date: Tue, 23 Nov 2004 21:22:55 -0700 [thread overview]
Message-ID: <41A40C9F.80609@xmission.com> (raw)
In-Reply-To: <20041124035850.4c086e3a.henryk@ploetzli.ch>
Henryk,
I am working right now on assembling a packet with more frames using
what is in cvs.
Brad
Henryk Plötz wrote:
> Moin,
>
> Am Tue, 23 Nov 2004 14:34:26 -0700 schrieb Brad Midgley:
>
>
>>we just send one sbc frame then? I was assuming that but not sure.
>
>
> Yes, for the beginning.
>
>
>>Are you saying we should put 0x9c in the stream or it should be in the
>>stream already? The SBC-specific stuff is definitely where my
>>understanding ends.
>
>
> It's already there. The format of an SBC frame is defined in the A2DP
> spec p. 53. They all start with a fixed length header of four bytes
> (that's what struct sbc_frame_header is) and then some more data (the
> length of which is calculated by calc_frame_len). We must send the whole
> frame (that is header plus data).
>
>
>>I think what we have in CVS looks better but it doesn't sound better
>>:(
>
>
> Hmm, I made it behaving to the specs (I think) (and yes, this time I
> actually made sure I committed it) and don't hear anything now.
>
>
>>Are you using the bluetake too?
>
>
> Yes.
>
-------------------------------------------------------
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-24 4:22 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
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 [this message]
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=41A40C9F.80609@xmission.com \
--to=bmidgley@xmission.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.