From: "Tim-Philipp Müller" <t.i.m@zen.co.uk>
To: Discussion of the development of and with GStreamer
<gstreamer-devel@lists.freedesktop.org>
Cc: linux-bluetooth@vger.kernel.org,
Thiago Sousa Santos <thiagossantos@gmail.com>
Subject: Re: Moving bluetooth plugin to gstreamer
Date: Thu, 16 Aug 2012 18:09:15 +0100 [thread overview]
Message-ID: <1345136955.28588.5.camel@zingle> (raw)
In-Reply-To: <CABBYNZJ16G7zOEm+AJwmb8SeEtRyGzfiKFf+QsK8NdQGUUGqDA@mail.gmail.com>
On Thu, 2012-08-16 at 16:25 +0300, Luiz Augusto von Dentz wrote:
Hi,
> Since we now have a proper library for SBC codec
> (http://git.kernel.org/?p=bluetooth/sbc.git;a=summary) and its patent
> has expired June 2, 2010. (source:
> http://en.wikipedia.org/wiki/SBC_(codec)), I wonder if it wouldn't be
> a good idea to move the plugin to gstreamer tree?
>
> The plugin has the following elements:
>
> bluetooth: sbcenc: Bluetooth SBC encoder
> bluetooth: sbcdec: Bluetooth SBC decoder
> bluetooth: sbcparse: Bluetooth SBC parser
> bluetooth: avdtpsink: Bluetooth AVDTP sink
> bluetooth: a2dpsink: Bluetooth A2DP sink
> bluetooth: rtpsbcpay: RTP packet payloader
Sounds like a good idea to me.
We'd probably add them to gst-plugins-bad first though, since that's
where new plugins are usually added before they get moved to -good or
elsewhere. And probably only to git master (ie. for the upcoming
0.11/1.0 API version).
Would the idea be that you'd turn libsbc from noinst into a proper
library, or would we just move that over into the plugin as well?
Cheers
- Tim
next prev parent reply other threads:[~2012-08-16 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 13:25 Moving bluetooth plugin to gstreamer Luiz Augusto von Dentz
2012-08-16 17:09 ` Tim-Philipp Müller [this message]
2012-08-16 19:50 ` Joao Paulo Rechi Vita
2012-08-17 3:13 ` Marcel Holtmann
[not found] ` <CAD2+Bb1+32YKBTNnG93dchn9SNU0ur4ZKCZtKV80ohc3bkwsYg@mail.gmail.com>
2012-11-08 15:20 ` Luiz Augusto von Dentz
2012-11-08 15:32 ` Tim-Philipp Müller
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=1345136955.28588.5.camel@zingle \
--to=t.i.m@zen.co.uk \
--cc=gstreamer-devel@lists.freedesktop.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=thiagossantos@gmail.com \
/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.