Re: [FFmpeg-devel] tinterlace license

2018-02-08 Thread Vasile Toncu
Shall I start a new thread for the patch with the new filter, or can I use this one? ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] tinterlace license

2018-02-08 Thread Vasile Toncu
From the git history I figured out that they wrote a quite big part of tinterlace. Other parts are written mainly by the maintainers of ffmpeg project. Look at the first commit: lavfi: port tinterlace filter from MPlayer That means you need to look at the MPlayer history too to know

Re: [FFmpeg-devel] tinterlace license

2018-02-08 Thread Nicolas George
Vasile Toncu (2018-02-08): > From the git history I figured out that they wrote a quite big part of > tinterlace. Other parts are written mainly by the maintainers of ffmpeg > project. Look at the first commit: lavfi: port tinterlace filter from MPlayer That means you need to look at

Re: [FFmpeg-devel] tinterlace license

2018-02-08 Thread Vasile Toncu
Hello, Then the best solution - imo! - is that you send a patch that adds your new filter that uses the existing asm optimizations if FFmpeg was configured for GPL. First send one patch only adding a new filter (with a new name) to get some technical review I'll send a patch with my new

Re: [FFmpeg-devel] tinterlace license

2018-02-07 Thread Stefano Sabatini
No objections from my side for the parts I contributed (but IIRC was mostly a port of code authored by other people). Best regards. Il 06/feb/2018 19:19, "Thomas Mundt" ha scritto: > Hi, > > 2018-02-05 11:58 GMT+01:00 Vasile Toncu : > > > Hello, >

Re: [FFmpeg-devel] tinterlace license

2018-02-06 Thread Thomas Mundt
Hi, 2018-02-05 11:58 GMT+01:00 Vasile Toncu : > Hello, > > I'm looking forward to modify *tinterlace* filter from GPL to LGPL. The > ASM opts will remain under GPL. > > Previously I tried to make a whole new filter, *reinterlace*, that acts > just like tinterlace, but

Re: [FFmpeg-devel] tinterlace license

2018-02-05 Thread Carl Eugen Hoyos
2018-02-05 14:22 GMT+01:00 Vasile Toncu : > >>> Yes, I wrote one, reinterlace. It implements tinterlace functionality as >>> it >>> was on version n3.0.2, without ASM opts. >> >> Sorry if you have already answered this question: >> Can the existing asm optimizations be

Re: [FFmpeg-devel] tinterlace license

2018-02-05 Thread Vasile Toncu
Yes, I wrote one, reinterlace. It implements tinterlace functionality as it was on version n3.0.2, without ASM opts. Sorry if you have already answered this question: Can the existing asm optimizations be used with the filter you wrote? Yes, I can integrate them with my filter. -Vasile

Re: [FFmpeg-devel] tinterlace license

2018-02-05 Thread Carl Eugen Hoyos
2018-02-05 14:06 GMT+01:00 Vasile Toncu : > >>> I'm looking forward to modify *tinterlace* filter from GPL to LGPL. >> >> I was under the impression you had already written a new filter >> licensed under LGPL: What happened to it? > > Yes, I wrote one, reinterlace. It

Re: [FFmpeg-devel] tinterlace license

2018-02-05 Thread Vasile Toncu
I'm looking forward to modify *tinterlace* filter from GPL to LGPL. I was under the impression you had already written a new filter licensed under LGPL: What happened to it? Yes, I wrote one, reinterlace. It implements tinterlace functionality as it was on version n3.0.2, without ASM opts.

Re: [FFmpeg-devel] tinterlace license

2018-02-05 Thread Carl Eugen Hoyos
2018-02-05 11:58 GMT+01:00 Vasile Toncu : > I'm looking forward to modify *tinterlace* filter from GPL to LGPL. I was under the impression you had already written a new filter licensed under LGPL: What happened to it? Carl Eugen