It does not get degraded when preceded by fieldmatch. So a progressive content "PAL" DVD - just encoded and flagged interlaced like many are - when using yadif=deint=1 does get degraded. I double checked this - I was wrong about "does not use the file's encoding parameters, metadata or flagging" - If you feed use yadif=deint=1 only, without a preceding filter that has interlace/comb detection, and input file is flagged interlaced- all frames get deinterlaced. Yes, the ffmpeg documentation sucks and incomplete - I was just trying to clarify how deint=1 is supposed to be used in the ffmpeg contextĭeint=1 seems to only work as expected when you have a preceding fieldmatch filter that passes on the data. Not the avisynth or vdub version, because it does not communicate with the upstream filter (yet avisynth is starting to get frame properties like vapoursynth, and some avs filters have started to be modernized for this )įor ffmpeg, it's used for combed frame fallback from a preceding filter Unless you can provide some better documentation that it does check, I'd respectfully disagree. Nor does the link ProWo supplied state, or even imply, that the Deint=1 setting does a check before deciding to deinterlace it. It does not use the file's encoding parameters, metadata or flagging to decide whether to mark a frame as "interlaced" Yadif as used in AviSynth (and Handbrake and VDub?) doesn't check if a frame is interlaced before deinterlacing it. In that ffmpeg yadif context, "marked as interlaced" is supposed to refer to an internal ffmpeg decision, such as after -vf fieldmatch, where there might be some residual combing or leftover "interlaced" frames.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |