Skip to main content
A
Anonymous
November 29, 2016
Question

Distributing AE plugin sources under GPL license?

  • November 29, 2016
  • 2 replies
  • 1597 views

Hi guys,

today I have a special question for you:

What if a plugin uses some third-party libraries that come with GPL license?

Can I then just distribute the final plugin non-commercially also under GPL with full sources?

I think not, as Adobe apparently explicitly forbids open source components in their AE SDK (http://www.adobe.com/devnet/aftereffects/sdk/cc2017/eula.html) :

"6. Open Source Software.

Developer is not licensed to (and Developer agrees not to) integrate or use the SDK, other than third-party software described in Section 14.6, with any Open Source Software in a manner that requires disclosure, distribution or licensing of all or any part of the SDK in source code form, for the purpose of making derivative works, or at no charge. For the purposes of this Section 6, “Open Source Software” shall mean software licensed under the GNU General Public License, GNU Affero General Public License (AGPL), the GNU Lesser General Public License or any other license terms that could require, or condition Developer’s use, modification or distribution of such software on, the disclosure, distribution or licensing of any other software in source code form, for the purpose of making derivative works, or at no charge. Any violation of the foregoing provision shall immediately terminate all of Developer’s licenses and other rights to the SDK granted under this Agreement."

But then again, there are quite a lot of free AE plugins out there that come with sources and are licensed under GPL or similar, e.g.:

http://www.andrewdavidson.com/aeflame/

http://www.3dcg.net/

Also, an AE plugin for the popular OpenColorIO (proprietary license by Sony) exists that also does not seem to conflict with the Adobe SDK: http://opencolorio.org/License.html

And there are also commercial plugins that interface libraries like FFMPEG under GPL/GPL, like this: http://aescripts.com/aempeg/​

Can anyone from Adobe shed any light on this or does any other developer have any experience already in that regard?

This topic has been closed for replies.

2 replies

A
Anonymous
November 29, 2016

Mmh, and this seems to be Adobe's stand:

Using Adobe SDK’s with Open Source

A
Arie Stavchansky
Legend
March 1, 2018

Hi Toby,

Is your question related to if a developer "compiles" GNU GPL code with Adobe's SDK source?  My understanding is that if a plugin's source code does not "link to" or "compile with" source licensed under GPL it should be okay.

For example, if you have GPL source linked in your IDE to make a new, derivitate, program (i.e. your plugin), I think that would violate Adobe's policy on the matter.  However, if your plugin's source is not built with any GPL source, but makes use of some GPL application (a binary) during runtime, my interpretation is that it should be fine.

In the case of http://aescripts.com/aempeg/​ it seems like the plugin only interacts with the ffmpeg.exe binary and is not a derivative of the ffmpeg codec.  Another tool, rendergarden from Mekajiki also interfaces with ffmpeg, but they require the end user to install ffmpeg themselves.  Even if an AE plugin author bundles ffmpeg with their installer, it is not considered a derivative, but rather an "aggregate".  See the final paragraph of Section (5) of the GNU GPL:

A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an “aggregate” if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.

My take is that if your plugin installs unmodified GNU software (perhaps binaries) after it installs your own plugin, then it should be okay.  However, if you are using GPL'd source code to in the compiler and / or linker during your development process, that is when Adobe might take issue — because GNU requires you to release the modified work.

Ultimately, there are professional attorneys who specialize in these matters, and it is in the best interest to consult with them.  I know your post is almost two years old, but did you find any further clarification on the matter?

Thanks,

Arie

A
Anonymous
November 29, 2016

Sort of answering my own question: it seems it is also not possible from the GPL side:

GPL license questions

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices