From: "Brad Midgley" <bmidgley@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] CVS audio-api.txt : 1st question
Date: Fri, 6 Jul 2007 17:44:17 -0600 [thread overview]
Message-ID: <d89ddf300707061644p5483ff3t8c6cb972e867e1d9@mail.gmail.com> (raw)
In-Reply-To: <468E76DD.6070303@free.fr>
Hi
> In my opinion the native elements wouldn't do any encoding/decoding
> work: this is clearly GStreamer Job as a media converting framework.
> I think we would have to:
> - extend the already included RTP GStreamer element to accept sbc and
> mp3 encoded streams.
> - wrap libsbc into a GStreamer element to do convert to do PCM to sbc.
> - create an a2dp Gstreamer element
Although this is really cool to deliver mp3 to the headset (less cpu
load, less transcoding noise), it might go too far down the road of an
early optimization for the case of a single audio client.
Mikko L at Nokia basically said they wouldn't consider anything along
these lines since it gets so complicated when a system sound needs to
interrupt mp3 playback. Do you:
- mix two mp3 streams together (technically possible)
- reconfigure the set for sbc and encode the streams to sbc (best
case is a delay, worst case a crash in the set during reconfiguration)
- stop the mp3 player and play the system sound mp3 instead (tricky)
It doesn't help that there's not much notion of a sound "card" that
can natively decode mp3. The audio servers don't account for this
possibility at all.
Brad
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-07-06 23:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 15:21 [Bluez-devel] CVS audio-api.txt : 1st question Fabien Chevalier
2007-06-29 18:10 ` Luiz Augusto von Dentz
2007-06-29 20:38 ` Brad Midgley
2007-07-02 17:03 ` Fabien Chevalier
2007-07-03 3:31 ` Brad Midgley
2007-07-03 8:04 ` Fabien Chevalier
2007-07-03 19:54 ` Luiz Augusto von Dentz
2007-07-03 21:08 ` Brad Midgley
2007-07-03 22:25 ` Luiz Augusto von Dentz
2007-07-04 1:57 ` Marcel Holtmann
2007-07-05 12:21 ` Fabien Chevalier
2007-07-05 13:53 ` Luiz Augusto von Dentz
2007-07-05 15:48 ` Fabien Chevalier
2007-07-05 14:12 ` Frederic Dalleau
2007-07-05 15:55 ` Fabien Chevalier
2007-07-05 16:40 ` Brad Midgley
2007-07-06 7:43 ` Fabien Chevalier
2007-07-06 13:12 ` Luiz Augusto von Dentz
2007-07-06 13:32 ` Fabien Chevalier
2007-07-06 13:43 ` Frederic Dalleau
2007-07-06 15:01 ` Luiz Augusto von Dentz
2007-07-06 17:07 ` Fabien Chevalier
2007-07-06 23:44 ` Brad Midgley [this message]
2007-07-07 6:29 ` Luiz Augusto von Dentz
2007-07-11 17:33 ` Fabien Chevalier
2007-07-11 21:56 ` Brad Midgley
2007-07-06 15:24 ` Fabien Chevalier
2007-07-06 15:38 ` Frederic Dalleau
2007-07-06 16:56 ` Fabien Chevalier
2007-07-05 12:53 ` Fabien Chevalier
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=d89ddf300707061644p5483ff3t8c6cb972e867e1d9@mail.gmail.com \
--to=bmidgley@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