[FFmpeg-user] Resolving -filter_complex overlay / -vf yadif conflicts in subprocess call Python script

pittschick at me.com pittschick at me.com
Thu Sep 12 12:46:04 EEST 2019


Thank you Carl. Point taken. I will investigate making it optional, then we just have the operators knowledge to rely on… Many thanks too Reto.

Joanna


> On 11 Sep 2019, at 21:37, Carl Eugen Hoyos <ceffmpeg at gmail.com> wrote:
> 
> Am Mi., 11. Sept. 2019 um 14:08 Uhr schrieb Gyan <ffmpeg at gyani.pro>:
> 
>>     ffmpeg -i input_file -i watermark.png -filter_complex "[0]yadif=0:-1:1[v];[v][1]overlay"
>>            -c:v libx264 -pix_fmt yuv420p -c:a aac
>>            -metadata copyright=“blah” -metadata comment=“contact blah” -report output_file
>> 
>> 
>> The yadif filter will only deinterlace if the frame is marked as interlaced.
> 
> The metadata that marks frames as interlaced is typically wrong:
> It will mark progressive frames as interlaced and the de-interlacer
> will permanently damage the frames.
> 
> Carl Eugen
> _______________________________________________
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".



More information about the ffmpeg-user mailing list