Re: [FFmpeg-devel] [PATCH 1/1] avcodec/mpegutils: add motion_vec debug mode

[Chema Gonzalez <chema@berkeley.edu>]

Hi again,

On Fri, Sep 2, 2022 at 2:05 PM Paul B Mahol <onemda@gmail.com> wrote:
> > > > So is there a filter that already dumps this information?
> > > Not in text but in visual, note that you can write own code that uses
> > > library to dump MV as text, because MV are exported when certain flag is
> > > enabled.
> > Not sure if I follow this. Is the suggestion to use external code that
> > just uses the ffmpeg libraries (libavcodec in this case)?
> Yes, no point to add bunch of printfs if code already exports MV
> alternative way.

Hmm... IIUC, your suggestion is not to provide the MV vector list
using an ffmpeg debug sub-mode. Instead, have the user write her own
code using one of the ffmpeg libraries. What you mean by "visual" is
something similar to
[this](https://www.ffmpeg.org/doxygen/0.6/api-example_8c-source.html),
right?

Couple of questions:
* is there a (sane) way to have this code included in ffmpeg?
Something like a series of C files/scripts where this type of
functionality would live. FWIW some companies charge thousands of
dollars for h264 stream parsers, where some of the functionality
allows you to access these values using a GUI.
* is there any reason why we have the other ffmpeg debug sub-modes
(mb_type, qp, skip)?

Thanks,
-Chema
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".