[FFmpeg-user] -pix_fmt yuv420p and deinterlacing
knfrances at gmail.com
Sun Feb 26 00:16:07 EET 2017
Oh! Thanks for letting me know. I just assumed the conflation of the two
But then, how are my output videos becoming deinterlaced?
Inputs are uncompressed v210 in MOV. They're definitely interlaced, as
they're digitized from an analogue source (using an AJA ADC) with all
And outputs are definitely progressive, at least according to MediaInfo.
I'm just using a basic script, for example:
ffmpeg -i uncompressed_master.mov -c:v libx264 -pix_fmt yuv420p -c:a
> libfdk_aac -b:a 128k access_copy.mp4
So how are my MP4s becoming deinterlaced? Is it a result of declaring MP4
as the output container? I thought that MP4s could contain interlaced
content - am I wrong about that?
Thanks for help!
On Sun, Feb 26, 2017 at 11:06 AM, Marton Balint <cus at passwd.hu> wrote:
> On Sun, 26 Feb 2017, Katherine Frances wrote:
> Hi all,
>> When transcoding to H.264 from an interlaced 4:2:2 original, I always add
>> the flag *-pix_fmt yuv420p*, which obviously achieves two goals:
>> i. Chroma subsampling scheme: 4:2:2 -> 4:2:0
>> ii. Scan: interlaced -> progressive.
>> I'm interested in the *p* part of the flag. Can anyone tell me how the
>> deinterlacing is achieved, i.e., what filter is used here by default?
>> I searched around quite a lot, but couldn't find specifics on this in the
>> ffmpeg wiki, on the documentation, or elsewhere on the web.
> p means planar here, not progressive. You are not doing deinterlacing.
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> To unsubscribe, visit link above, or email
> ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".
More information about the ffmpeg-user