9/27/2023 0 Comments Ffmpeg vcodec h264![]() ![]() I alsoįound that when the INPUT file is already in h264, FFMPEG thinks it needs a bunch more stuff, like "-pix_fmt".which appears to be broken.Īlso, VLC is totally transparent to what the initial/final resolutions are, whereas FFMPEG requires you to phrase your request explicitly stating the target resolution.Īccording to the original post, the input needs to be 720x480 in MPEG2 and H.264. I.e I learned that FFMPEG's PAD filter REQUIRES them to put the output into h264 (which is what is slowing their padding time down). ![]() So I learned from this: Staying in MPEG2 or MPEG4 (until the final pass, where h264 is required for us), is the way to go. VLC can pad without scaling first, so FFMPEG should be able to, too. ![]() [ Problem initially found on Windows-10, using :įfmpeg version N-77681-gb6c61b7 Copyright (c) 2000-2016 the FFmpeg developers So if this next step fails because it can't find filters, get full version (static pkg, which has filters inside) here: So, I grabbed 180 secs (3 mins) of one of mine (it was ripped from a DVD using MakeMKV.720x480, vcodec=MPEG2) :įfmpeg -i Raising_Arizona(1987).mkv -acodec copy -vcodec copy -t 600 -ss 60 Raising_Arizona-3mins.mkvįor this next part, you need be sure you have a FULL distrib of FFMPEG for Windows (that includes filters), MyTemplate to grab 't-seconds' of a video file, starting 'ss-seconds' into itįfmpeg -i MOVIE.mkv -acodec copy -vcodec copy -t 60 -ss 240 MOVIE-1min.mp4 Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. How to reproduce: Try it, with one of each Summary of the bug: PAD filter works correctly only when vcodec is NOT H264 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |