Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 720x480, 789 kb/s, 29.97 fps, 29.97 tbr, 30k tbn, 59.94 tbc (default)ĭecoding mpeg2 video codec is not very CPU intensive, so in case the mpeg2_qsv in not working, you may use CPU decoding and hardware accelerated encoding: ffmpeg -i input.ts -c:v h264_qsv output.I just found out about FFmpeg when recording gameplay on Bandicam using H.264 (Intel Quick Sync) codec. A decode call did not consume any data: expect more data at input (-10) Warning during encoding: incompatible video parameters (5) I am getting the following warning messages (but the output file is "playable"): Transcoding: ffmpeg -y -c:v mpeg2_qsv -i in.ts -c:v h264_qsv out.mp4 Using FFprobe for getting information: ffprobe in.ts The correct command for transcoding the video is: ffmpeg -c:v mpeg2_qsv -i input.ts -c:v h264_qsv output.mp4Īs far as I know, we don't have to use -hwaccel qsv, because there is nothing be accelerated in this simple transcoding (except decoding and encoding that handled by mpeg2_qsv and h264_qsv).īuild synthetic input file (for testing): ffmpeg -y -f lavfi -i testsrc=size=720x480:rate=59.94:duration=3 -vf "interlace=scan=tff:lowpass=complex,format=yuv420p" -c:v mpeg2video -profile:v main -pix_fmt yuv420p -flags +ilme+ildct in.ts The video applies interlace scan (not progressive scan). ![]() ![]() The codec of the input video is mpg2 (MPEG video Version 2).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |