From: Keith Duthie <psycho@albatross.co.nz>
To: linux-sound@vger.kernel.org
Subject: Re: good (and free) mp3 encoders?
Date: Mon, 24 May 1999 16:02:36 +0000 [thread overview]
Message-ID: <marc-linux-sound-92777142103760@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-92733463802226@msgid-missing>
On Sat, 22 May 1999, Michael Stutz wrote:
> IIRC there can't be an mp3 encoder that is free software because of patent
> problems; I seem to have heard of recent changes in the patent ownership but
> I don't think that the situation has changed. So if we want a free mp3
> encoder, we will have to either convince the patent holders that this is
> okay, or design a replacement format that we can use with free software
> (this is actually an item on the GNU Task List, but I don't think that
> anyone is working on it yet).
Not entirely true. Bladeenc is going to be released with source[1] if and
when some patent issues are dealt with. These patent issues are very
strange. Apparently software can't be patented is Sweden, but the mp3 guys
have a software patent in Sweden. Look at the bladeenc site
http://www.bladeenc.cjb.net for more details.
[1] apparently it will not be LGPLed as the author originally intended due
to the patent
--
Understanding is a three edged sword. Do you *want* to get the point?
http://www.albatross.co.nz/~psycho/ O-
next prev parent reply other threads:[~1999-05-24 16:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-21 0:52 good (and free) mp3 encoders? qozmo x xx
1999-05-22 0:18 ` 17.cV.478H
1999-05-22 6:08 ` Michael Stutz
1999-05-22 20:47 ` Erik de Castro Lopo
1999-05-23 8:31 ` donthomp
1999-05-24 15:58 ` Michael Hoefling
1999-05-24 16:02 ` Keith Duthie [this message]
1999-05-24 16:13 ` Michael Stutz
1999-05-24 18:04 ` Dan Hollis
1999-05-24 18:19 ` Michael Stutz
1999-05-25 3:33 ` Keith Duthie
1999-05-26 22:12 ` flatmax
1999-05-27 3:15 ` Deirdre Saoirse
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=marc-linux-sound-92777142103760@msgid-missing \
--to=psycho@albatross.co.nz \
--cc=linux-sound@vger.kernel.org \
/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.