From: "Mayank Batra" <mayankbatra@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Motorola HT820 audio fidelity
Date: Tue, 2 May 2006 10:31:48 +0530 [thread overview]
Message-ID: <6297d67c0605012201o52a1bb75u4622552cae9841f4@mail.gmail.com> (raw)
In-Reply-To: <4456E4DF.5000601@xmission.com>
[-- Attachment #1: Type: text/plain, Size: 2252 bytes --]
Brad,
The simplest approach would be to analyse all SEPs from the sink and if we
find an MP3 SEP, we can very well send the mp3 we receive from mpg123,
otherwise use the SBC codec.
Actually somewhere in the command line arguments we can take an input from
the user which codec does he prefer.
So if he writes something like:
a2play -c mp3
(Where -c is for the codec)
This should first try searching mp3 on the sink.
If not found, it should try SBC (which is of course mandatory and should be
found)
Whereas if he writes something like:
a2play -c sbc
This will straight away connect on SBC SEP.
Mayank
On 5/2/06, Brad Midgley <bmidgley@xmission.com> wrote:
>
> Mayank
>
> >
> http://www.assisttechnology.co.uk/documents/Sonorix_Bluetooth_Headset-Pamphlet.pdf
>
> Nice find.
>
> It brings up an interesting challenge. When using this headset, the
> driver should have access to the encoded audio so it can choose whether
> it's appropriate to decode the stream and then encode it in sbc or if it
> can pass the stream as-is to the set. I'll bet a gst bin could be
> constructed that would configure its elements accordingly for the input
> type and the headset caps.
>
> iirc, a2play assumes the first codec reported from the set is sbc. we
> should test it with the sonorix if somebody here has it to make sure we
> handle multiple codec capabilities properly.
>
> A bit of good news. It takes a couple of tries to get gxine to talk to
> my a2dp headset via the newly working plugin, but once it works the
> audio is very close to being in sync with the video and it is pretty
> solid for the duration of playing some video.
>
> Brad
>
>
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
[-- Attachment #2: Type: text/html, Size: 3116 bytes --]
next prev parent reply other threads:[~2006-05-02 5:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 0:24 [Bluez-devel] Motorola HT820 audio fidelity Fredrik Tolf
2006-04-28 3:19 ` Brad Midgley
2006-05-01 14:02 ` Fredrik Tolf
2006-05-01 14:48 ` Brad Midgley
2006-05-02 3:39 ` Mayank Batra
2006-05-02 4:49 ` Brad Midgley
2006-05-02 5:01 ` Mayank Batra [this message]
2006-05-04 17:28 ` Shawn Rutledge
2006-05-04 17:58 ` Brad Midgley
2006-05-02 11:02 ` Fredrik Tolf
2006-05-02 16:33 ` Brad Midgley
2006-05-04 2:20 ` Fredrik Tolf
2006-05-04 5:31 ` Brad Midgley
2006-05-04 9:26 ` Sergey Krivov
2006-05-09 3:20 ` Fredrik Tolf
2006-05-09 15:25 ` 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=6297d67c0605012201o52a1bb75u4622552cae9841f4@mail.gmail.com \
--to=mayankbatra@gmail.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