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

[Chema Gonzalez <chema@berkeley.edu>]

So is there a filter that already dumps this information?

Thanks,
-Chema

On Fri, Sep 2, 2022 at 12:56 AM Paul B Mahol <onemda@gmail.com> wrote:
>
> On Thu, Sep 1, 2022 at 8:43 PM Chema Gonzalez <chema@berkeley.edu> wrote:
>
> > Hi Paul,
> >
> > Can you please describe how you can get the MV values?
> >
>
> See how filters do it. They visualize MV but using similar logic one could
> dump them to ton of texts.
>
>
>
> >
> > Thanks,
> > -Chema
> >
> >
> > On Thu, Sep 1, 2022 at 10:52 AM Paul B Mahol <onemda@gmail.com> wrote:
> > >
> > > On Thu, Sep 1, 2022 at 5:06 PM Chema Gonzalez <chema@berkeley.edu>
> > wrote:
> > >
> > > > Hi,
> > > >
> > > > All the other debug modes (qp, skip, mb_type) use the same approach.
> > > >
> > > >
> > > This adds to much code for something that is already possible.
> > >
> > >
> > > > -Chema
> > > >
> > > >
> > > > On Thu, Sep 1, 2022 at 6:30 AM Ronald S. Bultje <rsbultje@gmail.com>
> > > > wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > On Wed, Aug 31, 2022 at 7:10 PM Chema Gonzalez <chemag@gmail.com>
> > wrote:
> > > > >>
> > > > >> Add a new debug mode ("motion_vec") that prints the values of the
> > > > >> motion vectors (MV).
> > > > >
> > > > >
> > > > > Isn't this super-hacky? In a well-designed system, a codec might
> > export
> > > > its MVs using designated structs (which we already have) and then use
> > these
> > > > structs to print it in a codec-agnostic way using a filter (which IIRC
> > we
> > > > already have?).
> > > > >
> > > > > Ronald
> > > > _______________________________________________
> > > > 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".
> > > >
> > > _______________________________________________
> > > 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".
> > _______________________________________________
> > 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".
> >
> _______________________________________________
> 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".
_______________________________________________
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".