[FFmpeg-devel] GP License question

Ronald S. Bultje rsbultje at gmail.com
Tue Mar 22 15:35:12 CET 2016


Hi,

On Tue, Mar 22, 2016 at 10:34 AM, Aaron Boxer <boxerab at gmail.com> wrote:

> Hi Carl,
>
>
> On Tue, Mar 22, 2016 at 10:16 AM, Carl Eugen Hoyos <cehoyos at ag.or.at>
> wrote:
>
> > Aaron Boxer <boxerab <at> gmail.com> writes:
> >
> > > On Tue, Mar 22, 2016 at 8:32 AM, Carl Eugen Hoyos wrote:
> > > > Aaron Boxer <boxerab <at> gmail.com> writes:
> > > >
> > > > > I am developing a jpeg 2000 codec licensed under Affero GPL.
> > > >
> > > > Why don't you work on fixing the remaining issues with
> > > > FFmpeg's implementation instead?
> > >
> > > That would be OpenJPEG.
> >
> > (With the intention to distract from the fruitless
> > license discussion: We will not accept AGPL contributions
> > and we won't encourage you to start an AGPL fork.)
> >
>
> Thanks. Don't worry, I am not interested in contributing my AGPL component
> to FFMpeg.
> Nor am I interested in forking FFMpeg.
>
> But, I would like to find a way of distributing FFMPeg with my codec,
> so users can take advantage of it if they are interested.
> This codec will be significantly faster than any other open source codec.
>
>
> >
> > No, FFmpeg contains a native Jpeg 2000 codec. I don't
> > remember it being slow but it has missing features and
> > it would be great if you worked on it. See trac (or the
> > conformance samples) for examples for decoder problems,
> > the encoder does not compress good enough.
> >
>
> Thanks. I'm afraid I have my hands full with my own library :)
>
> Personally, I would recommend switching over to OpenJPEG:
> BSD 2 license, ISO reference implementation for standard,
> and large test suite. Rather than spending time on your native codec.
> Just my 2 cents.  Codec development requires an enormous amount of time
> and expertise to get right.


(Ignoring the encoder for a second,) what makes you think we don't have
that expertise?

Ronald


More information about the ffmpeg-devel mailing list