From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] SBC packer done, kind of
Date: Wed, 24 Nov 2004 12:33:20 -0700 [thread overview]
Message-ID: <41A4E200.9000601@xmission.com> (raw)
In-Reply-To: <1101318257.27351.138.camel@pegasus>
Marcel,
Too bad 0xff is an invalid media payload header or we could work out a
way to send it regardless of which headset is listening.
You were saying there is a way to tell the aiptek is listening...
The current rcplay works fine with this headset. Something must have
changed since the last time I tried. (Even streams like 5 which don't
work with a2play work with rcplay.) I just wish we knew that sbc over
rfcomm was an official part of the a2dp profile.
Brad
Marcel Holtmann wrote:
> Hi Brad,
>
>
>>a2play in cvs w/NONSPECAUDIO should behave for you like it did when it
>>was last working for you. i disabled all the new stuff (it didn't help
>>or hurt the bluetake).
>
>
> for the Aiptek headphone I only get the NONSPECAUDIO version working and
> you must send 0xff 0xff for the first media payload. For all further
> media payloads it seems that it doesn't matter anymore.
>
> Setting the pt, timestamp and ssrc is working for me. Does it also work
> for you? If yes, there is no need to uncomment it.
>
>
>>that's really too bad the framing didn't fix things for yours like it
>>did the bluetake. they are totally out of spec. that doesn't bode well
>>for interoperating with the other headsets out there.
>
>
> This is very sad. So I can't help here with testing this until someone
> sends me a Bluetake headphone.
>
> 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
-------------------------------------------------------
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 19:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 0:47 [Bluez-devel] SBC packer done, kind of Henryk Plötz
2004-11-23 6:27 ` Marcel Holtmann
2004-11-23 6:48 ` Henryk Plötz
2004-11-23 9:24 ` Marcel Holtmann
2004-11-23 19:49 ` Henryk Plötz
2004-11-23 21:03 ` Marcel Holtmann
2004-11-24 3:21 ` Henryk Plötz
2004-11-24 5:01 ` Marcel Holtmann
2004-11-24 6:34 ` Marcel Holtmann
2004-11-25 4:22 ` Marcel Holtmann
2004-11-25 5:07 ` Henryk Plötz
2004-11-24 7:55 ` Brad Midgley
2004-11-24 14:39 ` Marcel Holtmann
2004-11-24 17:36 ` Brad Midgley
2004-11-24 17:44 ` Marcel Holtmann
2004-11-24 19:33 ` Brad Midgley [this message]
2004-11-25 6:07 ` Marcel Holtmann
2004-11-24 20:37 ` Henryk Plötz
2004-11-25 2:49 ` Marcel Holtmann
2004-11-25 5:02 ` Henryk Plötz
2004-11-25 5:30 ` Marcel Holtmann
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=41A4E200.9000601@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox