From: "João Paulo Rechi Vita" <jprvita@gmail.com>
To: Siarhei Siamashka <siarhei.siamashka@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: gstreamer and sbcdec problem
Date: Thu, 17 Dec 2009 10:49:48 -0200 [thread overview]
Message-ID: <aa32413d0912170449m162ca572p9e42275cf7c18201@mail.gmail.com> (raw)
In-Reply-To: <200912170841.14550.siarhei.siamashka@gmail.com>
2009/12/17 Siarhei Siamashka <siarhei.siamashka@gmail.com>:
> On Wednesday 16 December 2009, João Paulo Rechi Vita wrote:
>> On Tue, Dec 15, 2009 at 10:03 PM, Siarhei Siamashka
>>
>> <siarhei.siamashka@gmail.com> wrote:
>> > Also I don't have much trust in the current bluez SBC decoder
>> > implementation. Its quality may be not the very best. I was considering
>> > to eventually review its code, do some refactoring and merge some of its
>> > parts with the encoder (SBC encode and decode are quite symmetric), but
>> > did not find some spare time for this yet. Considering that bluez got SBC
>> > sink support now, improving the decoder may make sense.
>>
>> IMO it would make sense to export SBC codec in a library, since
>> encoding and decoding is done outside bluetoothd (ALSA, gstreamer or
>> PulseAudio). Also, the codec could be used for applications different
>> from A2DP streaming, and the more people using it, more tested (and
>> eventually improved) the code gets.
>
> I don't have first hand information regarding this matter myself, but
> according to SBC wikipedia page [1]:
> "The patent owners wrote that they allow the free usage of SBC in Bluetooth
> application, with the view to boost the use of this technology. All
> applications outside Bluetooth are however not free."
>
And if you continue reading the same paragraph: "The patent will
expire June 2, 2010.".
But anyway, gstreamer and pulseaudio uses SBC for bluetooth
application, so it's under the free usage terms (and also, there is a
copy of sbc.c in pulseaudio tree).
--
João Paulo Rechi Vita
MSc Computer Science Student
Computer Engineer
IC / Unicamp
http://jprvita.wordpress.com/
next prev parent reply other threads:[~2009-12-17 12:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 21:58 gstreamer and sbcdec problem Marian Harbach
2009-12-16 0:03 ` Siarhei Siamashka
2009-12-16 8:28 ` AW: " Marian Harbach
2009-12-16 10:15 ` Siarhei Siamashka
2009-12-16 11:41 ` João Paulo Rechi Vita
2009-12-17 6:41 ` Siarhei Siamashka
2009-12-17 12:49 ` João Paulo Rechi Vita [this message]
2009-12-17 14:53 ` Siarhei Siamashka
2009-12-17 16:35 ` João Paulo Rechi Vita
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=aa32413d0912170449m162ca572p9e42275cf7c18201@mail.gmail.com \
--to=jprvita@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=siarhei.siamashka@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).