mirror of https://git.ffmpeg.org/ffmpeg.git
b0352b1997
The reasoning behind this addition is that various third party applications are interested in getting some motion information out of a video "for free" when it is available. It was considered to export other information as well (such as the intra information about the block, or the quantization) but the structure might have ended up into a half full-generic, half full of codec specific cruft. If more information is necessary, it should either be added in the "flags" field of the AVMotionVector structure, or in another side-data. This commit also includes an example exporting them in a CSV stream. |
||
|---|---|---|
| .. | ||
| Makefile | ||
| README | ||
| avio_reading.c | ||
| decoding_encoding.c | ||
| demuxing_decoding.c | ||
| extract_mvs.c | ||
| filter_audio.c | ||
| filtering_audio.c | ||
| filtering_video.c | ||
| metadata.c | ||
| muxing.c | ||
| remuxing.c | ||
| resampling_audio.c | ||
| scaling_video.c | ||
| transcode_aac.c | ||
| transcoding.c | ||
README
FFmpeg examples README ---------------------- Both following use cases rely on pkg-config and make, thus make sure that you have them installed and working on your system. Method 1: build the installed examples in a generic read/write user directory Copy to a read/write user directory and just use "make", it will link to the libraries on your system, assuming the PKG_CONFIG_PATH is correctly configured. Method 2: build the examples in-tree Assuming you are in the source FFmpeg checkout directory, you need to build FFmpeg (no need to make install in any prefix). Then just run "make examples". This will build the examples using the FFmpeg build system. You can clean those examples using "make examplesclean" If you want to try the dedicated Makefile examples (to emulate the first method), go into doc/examples and run a command such as PKG_CONFIG_PATH=pc-uninstalled make.