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

Paul B Mahol onemda at gmail.com
Sat Sep 3 12:15:29 EEST 2022


On Sat, Sep 3, 2022 at 2:46 AM Chema Gonzalez <chema at berkeley.edu> wrote:

> Hi again,
>
> On Fri, Sep 2, 2022 at 2:05 PM Paul B Mahol <onemda at 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.
>

And why is this related at all with this clumsy printfs patch?

There is already functionality in FFmpeg libs to give you MVs.

Nobody blocks you to write sane GUI tool that will import MVs from ffmpeg
API
and sell it for millions to customers.



> * is there any reason why we have the other ffmpeg debug sub-modes
> (mb_type, qp, skip)?
>

They should be ultimately removed and in better way exported.

>
> Thanks,
> -Chema
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".
>


More information about the ffmpeg-devel mailing list