AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Ffmpeg vcodec h26411/18/2023 ![]() ![]() Scan type, store method : Interleaved fields If input is encoded as PAFF, then -r 50 as output works fine!įollowing file has problem with -r 50 as output, it drops frames. It seems the problem happens when input is encoded as MBAFF. Your reply made me try to find out which inputs have problem with -r 50 as output on newer ffmpeg versions when using cuvid’s -deint adaptive, and which do not. ![]() Without these flags I found that cuvid_deint presumably did not recognise it as interlaced, and so I think either the deint did nothing, or just dropped half the frames. This doesn’t drop any frames, however it took a while to figure out the correct flags to use to create the h264 file: “-flags +ildct+ilme -top 1”. This is with FFmpeg built using jb’s suite from the 4.1 branch. Then the yadif version of the deinterlace is as follows:įfmpeg -i capture_h264.asf -vcodec hevc_nvenc -preset lossless -vf yadif=1 -acodec aac -ab 192k -r 50 -f mp4 encode_yadif_deint.mp4 -yįfmpeg -vcodec h264_cuvid -deint adaptive -i capture_h264.asf -vcodec hevc_nvenc -preset lossless -acodec aac -ab 192k -r 50 -f mp4 encode_cuvid_deint.mp4 -y I then created a lossless h264 file from it (I could have done this directly as part of the initial capture, but didn’t):įfmpeg -i capture_ffvhuff.asf -vcodec libx264 -pix_fmt nv12 -preset ultrafast -crf 0 -g 1 -flags +ildct+ilme -top 1 -acodec copy -f asf capture_h264.asf -y I started with a directshow capture file, capturing a 1080i50 signal, in yuyv422 format using the ffvhuff container. I was looking at this earlier as I was also trying to get cuvid deint working, and I don’t get the same problem. ![]()
0 Comments
Read More
Leave a Reply. |