Re: [Lame-dev] MAD in LAME

[Alexander L. <Alexander@Leidinger.net>]

On 23 Jan, Steve Lhomme wrote:

> 3. 
> modify mpglib to output
> floating point and have finaly quantization step a
> easy-to-change module so it can output other than 16bit.
> (replace mpglib with MAD?  MAD has agreed to write a call back
> which will return all data needed by the frame analyzer)

> I wonder what is the progress of this, and if there are any license issue with
> using MAD (libmad ?) in LAME (MAD is GPL and LAME is LGPL, that means AFAIK that
> some part of the MAD code can be used in LAME).

Again, but this time in public:
The version of mpglib we have in the LAME tree is GPL'ed (this doesn't
affect the ACM codec). There's soneone who wants to import the LGPL'ed
mpglib (with our own modifications/bugfixes applied/feeded back to the
original mpglib), he has already an OK from most of the
modification/bugfix authors to relicense the work under the LGPL, but I
haven't heard anything since last year.

Perhaps the author(s) of libmad is/are willing to relicense it to LGPL?

> My concern is that I want to integrate the decoding part in the LAME ACM codec.
> And since mpglib might be replaced by libmad someday it would be easier to make
> the move now.

Feel free to do the work, in a way we can do a smooth transition (e.g.
dependand on a define).

Bye,
Alexander.

-- 
                      Loose bits sink chips.

http://www.Leidinger.net                       Alexander @ Leidinger.net
  GPG fingerprint = C518 BC70 E67F 143F BE91  3365 79E2 9C60 B006 3FE7