On 05.04.2016 12:12, Kieran Kunhya wrote:
Yes. Well, AGPL extends the definition of distribution to include use over
the network.
Would we need then to send a copy of the AGPL to every viewer of our
channels?
How do we even know who they are when it's a terrestrial (OTA) broadcast?
Should we
On Tue, Apr 05, 2016 at 09:54:45AM +, Carl Eugen Hoyos wrote:
> Aaron Boxer gmail.com> writes:
>
> > I still think the advantages (i.e. closing the application
> > server loophole)c outweigh this disadvantage.
>
> I believe the mistake you make here is the main reason for
> this whole frui
Hi,
On Tue, Apr 5, 2016 at 6:15 AM, wm4 wrote:
> On Tue, 05 Apr 2016 10:12:09 +
> Kieran Kunhya wrote:
>
> > >
> > > Yes. Well, AGPL extends the definition of distribution to include use
> over
> > > the network.
> >
> >
> > Would we need then to send a copy of the AGPL to every viewer of o
On Tue, 05 Apr 2016 10:12:09 +
Kieran Kunhya wrote:
> >
> > Yes. Well, AGPL extends the definition of distribution to include use over
> > the network.
>
>
> Would we need then to send a copy of the AGPL to every viewer of our
> channels?
> How do we even know who they are when it's a ter
>
> Yes. Well, AGPL extends the definition of distribution to include use over
> the network.
Would we need then to send a copy of the AGPL to every viewer of our
channels?
How do we even know who they are when it's a terrestrial (OTA) broadcast?
Should we just send one to every citizen on earth
Aaron Boxer gmail.com> writes:
> I still think the advantages (i.e. closing the application
> server loophole)c outweigh this disadvantage.
I believe the mistake you make here is the main reason for
this whole fruitless discussion including the misunderstandings.
Carl Eugen
_
Aaron Boxer gmail.com> writes:
> I also want to reiterate that because FFmpeg can be distributed
> under GPL v3, and Grok is licensed under the AGPL, there are no
> licensing issues regarding distributing FFmpeg together with Grok.
As was already discussed before, this is simply not true:
The
On Mon, Apr 04, 2016 at 06:06:28PM -0400, Aaron Boxer wrote:
> I could give you an OS image that has a version of FFmpeg that uses
> proprietary codecs.
Aside from Carl's comment, please define "proprietary codecs." Proprietary
codecs have different licenses, just like how both ISC and GNU AGPL a
On Mon, Apr 4, 2016 at 6:54 PM, Timothy Gu wrote:
> Hi,
>
> On Mon, Apr 04, 2016 at 03:54:11PM -0400, Aaron Boxer wrote:
> > >
> > > >
> > > > The following changes were made:
> > > >
> > > > 1. Removed bpp (redundant as this information is already stored in
> > > precision)
> > >
> > > Does comp
On Mon, Apr 4, 2016 at 6:19 PM, Carl Eugen Hoyos wrote:
> Aaron Boxer gmail.com> writes:
>
> > I could give you an OS image that has a version of
> > FFmpeg that uses proprietary codecs.
>
> You could, but you are not allowed to.
>
True.
Well, I guess you have come up with one disadvantage of
Hi,
On Mon, Apr 04, 2016 at 03:54:11PM -0400, Aaron Boxer wrote:
> >
> > >
> > > The following changes were made:
> > >
> > > 1. Removed bpp (redundant as this information is already stored in
> > precision)
> >
> > Does compilation still work without this change?
> >
>
> Yes.
Then the change is
Aaron Boxer gmail.com> writes:
> I could give you an OS image that has a version of
> FFmpeg that uses proprietary codecs.
You could, but you are not allowed to.
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org
On Apr 4, 2016 5:12 PM, "Reimar Döffinger" wrote:
>
> On Mon, Apr 04, 2016 at 03:48:38PM -0400, Aaron Boxer wrote:
> > On Mon, Apr 4, 2016 at 3:16 PM, Reimar Döffinger <
reimar.doeffin...@gmx.de>
> > wrote:
> >
> > > The really huge, gigantic, elephant sized issue with AGPL for me is
> > > that it
On Mon, Apr 04, 2016 at 03:48:38PM -0400, Aaron Boxer wrote:
> On Mon, Apr 4, 2016 at 3:16 PM, Reimar Döffinger
> wrote:
>
> > The really huge, gigantic, elephant sized issue with AGPL for me is
> > that it is _completely_ unclear to me what you actually have to
> > do to fulfill the license requ
On Mon, Apr 4, 2016 at 1:51 PM, Timothy Gu wrote:
> On Sun, Apr 03, 2016 at 05:34:15PM -0400, Aaron Boxer wrote:
>
> > From d12c685578f21b403f6c03505edd84db367306c5 Mon Sep 17 00:00:00 2001
> > From: Aaron Boxer
> > Date: Sun, 27 Mar 2016 00:15:20 -0400
>
> > Subject: [PATCH] Support the followi
On Mon, Apr 4, 2016 at 3:16 PM, Reimar Döffinger
wrote:
> On Mon, Apr 04, 2016 at 10:51:23AM -0700, Timothy Gu wrote:
> > On Sun, Apr 03, 2016 at 05:34:15PM -0400, Aaron Boxer wrote:
> > Also it should be made clear that if Grok is linked into FFmpeg, the
> resulting
> > binary is a mixture of AG
On Mon, Apr 04, 2016 at 10:51:23AM -0700, Timothy Gu wrote:
> On Sun, Apr 03, 2016 at 05:34:15PM -0400, Aaron Boxer wrote:
> Also it should be made clear that if Grok is linked into FFmpeg, the resulting
> binary is a mixture of AGPL and GPL works. If --enable-gpl or
> --enable-version3 is not enab
On Sun, Apr 03, 2016 at 05:34:15PM -0400, Aaron Boxer wrote:
> From d12c685578f21b403f6c03505edd84db367306c5 Mon Sep 17 00:00:00 2001
> From: Aaron Boxer
> Date: Sun, 27 Mar 2016 00:15:20 -0400
> Subject: [PATCH] Support the following jpeg 2000 codecs:
>
> a) latest release of openjpeg (2.1)
>
Hi
On Mon, Apr 04, 2016 at 10:32:24AM -0400, Aaron Boxer wrote:
[...]
> Someone has mentioned the extra effort required to make the source
> available over the network.
> I would be happy to work on this.
its maybe not the right thread to discuss this (as people look at
it from a agpl dislike bi
Le sextidi 16 germinal, an CCXXIV, Aaron Boxer a écrit :
> You are right, I don't understand. So far, nobody has provided a
> reasonable explanation for why AGPL is not acceptable, while GPL v3 is.
GPLv3 is already there, the question to accept it or not is not on the
table. Maybe if the question
Hi Josh,
On Mon, Apr 4, 2016 at 9:30 AM, Josh de Kock wrote:
> On 04/04/2016 14:21, Aaron Boxer wrote:
> > All of your arguments could be applied equally to GPL v3 components. And
> > yet,
> > FFmpeg is happy to allow distribution under GPL v3. So, I don't see what
> > the problem is here.
> Th
On 04/04/2016 14:21, Aaron Boxer wrote:
> All of your arguments could be applied equally to GPL v3 components. And
> yet,
> FFmpeg is happy to allow distribution under GPL v3. So, I don't see what
> the problem is here.
The problem is AGPL can make certain builds of FFmpeg _unusable_, it's a
pain t
Hi,
On Mon, Apr 4, 2016 at 9:21 AM, Aaron Boxer wrote:
> Hi Ronald,
>
>
> On Mon, Apr 4, 2016 at 8:56 AM, Ronald S. Bultje
> wrote:
>
> > Hi,
> >
> > On Mon, Apr 4, 2016 at 8:43 AM, Aaron Boxer wrote:
> >
> > > Hi Ronald,
> > >
> > >
> > > On Mon, Apr 4, 2016 at 8:34 AM, Ronald S. Bultje
> >
Hi Hendrik,
On Mon, Apr 4, 2016 at 9:06 AM, Hendrik Leppkes wrote:
> On Mon, Apr 4, 2016 at 2:49 PM, Aaron Boxer wrote:
> > On Mon, Apr 4, 2016 at 5:37 AM, Michael Niedermayer
>
> > wrote:
> >
> >> On Sun, Apr 03, 2016 at 05:31:25PM -0400, Aaron Boxer wrote:
> >> > Hi Folks,
> >> >
> >> > Here
Hi Ronald,
On Mon, Apr 4, 2016 at 8:56 AM, Ronald S. Bultje wrote:
> Hi,
>
> On Mon, Apr 4, 2016 at 8:43 AM, Aaron Boxer wrote:
>
> > Hi Ronald,
> >
> >
> > On Mon, Apr 4, 2016 at 8:34 AM, Ronald S. Bultje
> > wrote:
> >
> > > Hi,
> > >
> > > On Mon, Apr 4, 2016 at 7:59 AM, Aaron Boxer wrote
On Mon, Apr 4, 2016 at 2:49 PM, Aaron Boxer wrote:
> On Mon, Apr 4, 2016 at 5:37 AM, Michael Niedermayer
> wrote:
>
>> On Sun, Apr 03, 2016 at 05:31:25PM -0400, Aaron Boxer wrote:
>> > Hi Folks,
>> >
>> > Here is a small patch to get FFmpeg working with both OpenJPEG master and
>> > Grok master,
On Mon, 4 Apr 2016 08:43:10 -0400
Aaron Boxer wrote:
> Sorry, I was wrong in my original statements. I've learned a bit more about
> how these
> licenses work.
>
> This is not a fork. FSF allows GPL 3 and AGPL 3 code to be combined.
> If FFmpeg can be distributed according to GPL 3, then it can
Hi,
On Mon, Apr 4, 2016 at 8:43 AM, Aaron Boxer wrote:
> Hi Ronald,
>
>
> On Mon, Apr 4, 2016 at 8:34 AM, Ronald S. Bultje
> wrote:
>
> > Hi,
> >
> > On Mon, Apr 4, 2016 at 7:59 AM, Aaron Boxer wrote:
> >
> > > On Mon, Apr 4, 2016 at 7:13 AM, wm4 wrote:
> > >
> > > > On Sun, 3 Apr 2016 17:31:
On Mon, Apr 4, 2016 at 5:37 AM, Michael Niedermayer
wrote:
> On Sun, Apr 03, 2016 at 05:31:25PM -0400, Aaron Boxer wrote:
> > Hi Folks,
> >
> > Here is a small patch to get FFmpeg working with both OpenJPEG master and
> > Grok master, for J2K support. The comment on the commit has all of the
> >
Hi Ronald,
On Mon, Apr 4, 2016 at 8:34 AM, Ronald S. Bultje wrote:
> Hi,
>
> On Mon, Apr 4, 2016 at 7:59 AM, Aaron Boxer wrote:
>
> > On Mon, Apr 4, 2016 at 7:13 AM, wm4 wrote:
> >
> > > On Sun, 3 Apr 2016 17:31:25 -0400
> > > Aaron Boxer wrote:
> > >
> > > > Hi Folks,
> > > >
> > > > Here i
Hi,
On Mon, Apr 4, 2016 at 7:59 AM, Aaron Boxer wrote:
> On Mon, Apr 4, 2016 at 7:13 AM, wm4 wrote:
>
> > On Sun, 3 Apr 2016 17:31:25 -0400
> > Aaron Boxer wrote:
> >
> > > Hi Folks,
> > >
> > > Here is a small patch to get FFmpeg working with both OpenJPEG master
> and
> > > Grok master, for
On Mon, Apr 4, 2016 at 3:39 AM, Tobias Rapp wrote:
> On 04.04.2016 02:36, Aaron Boxer wrote:
>
>> [...]
>>
> >
>
>> Thanks, Michael. Here is an updated patch with the bpp change removed.
>>
>> Aaron
>>
>> From fb7551a8f9fe6a5317f01c9f33a76f8ae67ad979 Mon Sep 17 00:00:00 2001
>> From: Aaron Boxer
On Mon, Apr 4, 2016 at 5:37 AM, Michael Niedermayer
wrote:
> On Sun, Apr 03, 2016 at 05:31:25PM -0400, Aaron Boxer wrote:
> > Hi Folks,
> >
> > Here is a small patch to get FFmpeg working with both OpenJPEG master and
> > Grok master, for J2K support. The comment on the commit has all of the
> >
On Mon, Apr 4, 2016 at 7:13 AM, wm4 wrote:
> On Sun, 3 Apr 2016 17:31:25 -0400
> Aaron Boxer wrote:
>
> > Hi Folks,
> >
> > Here is a small patch to get FFmpeg working with both OpenJPEG master and
> > Grok master, for J2K support. The comment on the commit has all of the
> > details; the main
On Sun, 3 Apr 2016 17:31:25 -0400
Aaron Boxer wrote:
> Hi Folks,
>
> Here is a small patch to get FFmpeg working with both OpenJPEG master and
> Grok master, for J2K support. The comment on the commit has all of the
> details; the main change is to remove the OPJ_STATIC flag from configure,
> s
On Sun, Apr 03, 2016 at 05:31:25PM -0400, Aaron Boxer wrote:
> Hi Folks,
>
> Here is a small patch to get FFmpeg working with both OpenJPEG master and
> Grok master, for J2K support. The comment on the commit has all of the
> details; the main change is to remove the OPJ_STATIC flag from configur
On 04.04.2016 02:36, Aaron Boxer wrote:
[...]
>
Thanks, Michael. Here is an updated patch with the bpp change removed.
Aaron
From fb7551a8f9fe6a5317f01c9f33a76f8ae67ad979 Mon Sep 17 00:00:00 2001
From: Aaron Boxer
Date: Sun, 3 Apr 2016 20:30:04 -0400
Subject: [PATCH] Support the following jp
On Sun, Apr 3, 2016 at 7:02 PM, Michael Bradshaw wrote:
> Tested with OpenJPEG 1.5, 2.0, and 2.1 on OS X with clang. Correctly
> decoded and re-encoded the balloon.jp2 sample.
>
Thanks for testing.
>
> On Sun, Apr 3, 2016 at 2:34 PM, Aaron Boxer wrote:
> > From d12c685578f21b403f6c03505edd84
Tested with OpenJPEG 1.5, 2.0, and 2.1 on OS X with clang. Correctly
decoded and re-encoded the balloon.jp2 sample.
On Sun, Apr 3, 2016 at 2:34 PM, Aaron Boxer wrote:
> From d12c685578f21b403f6c03505edd84db367306c5 Mon Sep 17 00:00:00 2001
> From: Aaron Boxer
> Date: Sun, 27 Mar 2016 00:15:20 -0
Hi Folks,
Here is a small patch to get FFmpeg working with both OpenJPEG master and
Grok master, for J2K support. The comment on the commit has all of the
details; the main change is to remove the OPJ_STATIC flag from configure,
so that FFmpeg can be configured with a dynamic build of both codecs
woops, forgot to attach the patch.
On Sun, Apr 3, 2016 at 5:31 PM, Aaron Boxer wrote:
> Hi Folks,
>
> Here is a small patch to get FFmpeg working with both OpenJPEG master and
> Grok master, for J2K support. The comment on the commit has all of the
> details; the main change is to remove the OP
41 matches
Mail list logo
