Security is a high priority and code review is always done with security in mind. Wherever the question of 'best' cannot be answered we support both options so the end user can choose. We slightly favor our own code to keep the dependencies on other libs low and to maximize code sharing between parts of FFmpeg.

To achieve this we combine the best free software options available. The FFmpeg project tries to provide the best technically possible solution for developers of applications and end users alike. As well as ffmpeg, ffserver, ffplay and ffprobe which can be used by end users for transcoding, streaming and playing It contains libavcodec, libavutil, libavformat, libavfilter, libavdevice, libswscale and libswresample which can be used by applications. No matter if they were designed by some standards committee, the community or a corporation. It supports the most obscure ancient formats up to the cutting edge. The option does not mean same quality.Decode, encode, transcode, mux, demux, stream, filter and play anything Sameq tells FFmpeg to use the same quantization parameters when converting video with the same codec that was used for the input.

Basically, FFmpeg just reads and writes the container and doesn't change the codecs. Here's an example that changes the container from AVI to MP4, if the video bitstream is valid for MP4 as well: ffmpeg -i input.avi -c:v copy output.mp4Īgain: FFmpeg will copy anything that it finds. This, in essence, gives you the same quality, as nothing will be changed in the video bitstream. For example, your AVI video has an XviD video bitstream, and you can copy it to an MP4 container, without re-encoding the video. c:v copy tells FFmpeg to copy the bitstream of the video to the output. The accepted answer is incorrect-or at least doesn't really explain what the options actually do.

Ffmpeg codec