Vasile Toncu (2017-12-27): > It is because of licencing issues. I wanted the new filter to be LGPL.
Thanks for the explanation. That is a valid reason. But as is, it would result would be duplicated code for people who do not worry about licensing. 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. 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. Regards, -- Nicolas George
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
