seekerla.blogg.se

Ffmpeg mp4 to h264
Ffmpeg mp4 to h264







ffmpeg mp4 to h264

stib$ ffmbc -i test.mov -vcodec libx264 -preset slow -profile baseline -acodec libfaac -ab 96k -crf 19 test.mp4

ffmpeg mp4 to h264

there's fast, slow, veryslow and placebo (might be more, can't remember). I use the libx264 presets - for example "slow" gives me the options listed below. You should contact the NVIDIA SDK development team and send them the input file so they can fix thier parser.Īs for the FFPLAY displaying green screen - I Know previous version of the SDK (i’m currently using version 11.1.5) caused green screen in certain scenarios but in the version i’m using it was fixed - maybe FFMPEG 4.4.-profile baseline seems to work for me, using libx264.

ffmpeg mp4 to h264

When using the CPU decoding ( * ffplay -vcodec h264 1000_raw_data.h264") I noticed video is OK but there are a lot of “Invalid NAL Units” Errors - it is possible that the h264 Parser that is used by the NVIDIA SDK is not handling the Invalid NAL unit properly and try to decode them which lead to a lot of errors. I tried to use the input you provided to the h264 decode sample of the SDK and got a lot of “CONCEALED ERRORS” the resulted video was not “green” as when using " * ffplay -vcodec h264_cuvid 1000_raw_data.h264" - I did get a few normal frames every few seconds but the video as a whole was not playble (lots of artifacts in the video) The SDK pass the input data through it own h264 parser to identify the h264 nal units and other h264 parameters. The FFMPEG H264 GPU decoding is implemented based on the NVIDIA Video SDK. I will provide my sample data here One Drive

  • ffmpeg -vcodec h264_cuvid -i 1000_raw_data.h264 output.mp4.
  • FFMPEG/libavcodec: 4.4.2 (installed from source, following Official Guide and Pytorch Guide.
  • ffmpeg mp4 to h264

    FFMPEG/libavcodec: 4.2.7 (installed using apt).So I think that maybe GPU H264 Codec is bugged, or there is some kind of H264 data format that GPU implementation cannot decode? I also ran a GPU H265 Decoder, and it can work well all day. I tried to use both libavcodec and ffmpeg application on two different servers and GPUs, and they seemed to perform similarly, failed to decode the same data, worked normally for the other. It didn’t always fail through, maybe approx 50% of input data. I found that codec h264_cuvid failed to decode on some data, while CPU implementation h264 / libx264 worked normally. My implementation is based on FFmpeg/decode_video.c at master









    Ffmpeg mp4 to h264