avcodec: export motion vectors in frame side data on demand
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.
This commit is contained in:
2
configure
vendored
2
configure
vendored
@@ -1305,6 +1305,7 @@ EXAMPLE_LIST="
|
||||
avio_reading_example
|
||||
decoding_encoding_example
|
||||
demuxing_decoding_example
|
||||
extract_mvs_example
|
||||
filter_audio_example
|
||||
filtering_audio_example
|
||||
filtering_video_example
|
||||
@@ -2586,6 +2587,7 @@ zoompan_filter_deps="swscale"
|
||||
avio_reading="avformat avcodec avutil"
|
||||
avcodec_example_deps="avcodec avutil"
|
||||
demuxing_decoding_example_deps="avcodec avformat avutil"
|
||||
extract_mvs_example_deps="avcodec avformat avutil"
|
||||
filter_audio_example_deps="avfilter avutil"
|
||||
filtering_audio_example_deps="avfilter avcodec avformat avutil"
|
||||
filtering_video_example_deps="avfilter avcodec avformat avutil"
|
||||
|
||||
Reference in New Issue
Block a user