AviSynth License and avsFilmCutter

[Ebobtron]

Hi all,

I would like to thank the AviSynth team for your wonderful work.

I have began work on enhancing the script editor in FilmCutter (http://forum.doom9.org/showthread.php?t=97438) with the functions,
env->GetVar("$PluginFunctions$");
env->GetVar("$InternalFunctions$");as shown in sh0dan's example found here, http://forum.doom9.org/showthread.php?p=729114#post729114.

// As a special exception, the copyright holders of Avisynth give you
// permission to link Avisynth with independent modules that communicate with
// Avisynth solely through the interfaces defined in avisynth.h, regardless of the license
// terms of these independent modules, and to copy and distribute the
// resulting combined work under terms of your choice, provided that
// every copy of the combined work is accompanied by a complete copy of
// the source code of Avisynth (the version of Avisynth used to produce the
// combined work), being distributed under the terms of the GNU General
// Public License plus this exception. An independent module is a module
// which is not derived from or based on Avisynth, such as 3rd-party filters,
// import and export plugins, or graphical user interfaces.

Would I be correct to believe that the above section of the license is the part that will apply to avsFilmCutter if I implement linking to AviSynth by use of "avisynth.h"?

I do not wish to appear dumb, although on matters such as these I am, nor do I intend in anyway to challenge the license. I am not sure I understand.

As I read it, no matter how I do it, I must distribute a complete copy of the source code for AviSynth, even if I release FilmCutter with a GPU license when I link using avisynth.h.

I could use some guidance.

Thanks for the help,
Ebobtron
http://members.aol.com/avsfilmcutter

[IanB]

Basiclly if you ship Avisynth*.exe with your package then you must also ship the associated source, no matter what interface you use.

If your package only uses avisynth.h (like 95% of all pluggins) and you do not ship any Avisynth*.exe, i.e. you just tell people where to get it, then you can do your own thing.

If you use a deaper interface, i.e. internal.h then you are bound by the full agreement, i.e. your own source must also be released under a compatible aggreement.

A grey area is where your installer automagicly downloads and installs avisynth. The accepted tradeoff is simply having an option to also automagicly download the matching source.

[Fizick]

I am not jurist, but:
1. Link to sourceforge Avisynth download page is enough.
2. If you use avisynth.h ONLY (not linked avisynth.dll, lib), you may be NOT GPL.
3. But why you afraid to be GPL? :)

[Ebobtron]

Hello,
If your package only uses avisynth.h (like 95% of all pluggins) and you do not ship any Avisynth*.exe, i.e. you just tell people where to get it, then you can do your own thing.Thanks IanB, the above describes my circumstances I believe. FilmCutter is a tool for AviSynth users, not the other way around. FilmCutter's webpage does not have a link to AivSynth.org, I will fix that.
:thanks:
3. But why you afraid to be GPL? Hi Fizick,
I am not afraid of GPL at all. Until now, FilmCutter having a license was not important to me, kind of like the about box, other parts of FilmCutter have been more important. Now the rules change because I am not just supporting AviSynth I am using it. I will not license FilmCutter without knowing what I am doing, if I have to make that decision now so that FilmCutter's next version can be released without a copyright violation, I will. If I can continue as is or with a simple acknowledgement ok, if not that is ok too. I want you to be able to try out your new filter picking popup without me breaking the rules. :D

Thanks very much guys,
Ebobtron
http://members.aol.com/avsfilmcutter