On 28.12.2017 15:17, Nicolas George wrote:
Vasile Toncu (2017-12-28):
Are there any features that tinterlace has and this new filter has not?
If not, then I think it would be better to just replace tinterlace
entirely.
You did not answer the question. I asked if there are features in
tinterlace that are not in reinterlace. You answered the opposite
question.
There are some features that tinterlace has and reinterlace does not.
Tinterlace has some more flags, reinterlace has only simple low pass filter.
Also, in a newer version, tinterlace does support input formats on 16 bit.
Expecting these two, there are no other special features.
I can answer myself: tinterlace has asm optimizations. This is not for
me only to decide, but I am rather against having duplicated features
just for licensing reasons.
In this particular instance, I think you could use the GPL asm
optimizations while having the filter itself LGPL.
Your arguments are valid, but what happens if I want to use a GPL tinterlace
in an closed source application that will be distributed.
You cannot.
But making tinterlace LGPL would solve that for you just the same as
adding yet another filter that does the same thing.
Can one simply change the tinterlace from GPL to LGPL?
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
