Hi Paul, Can you please describe how you can get the MV values?
Thanks, -Chema On Thu, Sep 1, 2022 at 10:52 AM Paul B Mahol <[email protected]> wrote: > > On Thu, Sep 1, 2022 at 5:06 PM Chema Gonzalez <[email protected]> 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 <[email protected]> > > wrote: > > > > > > Hi, > > > > > > On Wed, Aug 31, 2022 at 7:10 PM Chema Gonzalez <[email protected]> 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 > > [email protected] > > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > > > To unsubscribe, visit link above, or email > > [email protected] with subject "unsubscribe". > > > _______________________________________________ > ffmpeg-devel mailing list > [email protected] > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > [email protected] with subject "unsubscribe". _______________________________________________ ffmpeg-devel mailing list [email protected] https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
