From: Paul B Mahol <onemda@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: "Ronald S. Bultje" <rsbultje@gmail.com>
Subject: Re: [FFmpeg-devel] [PATCH 1/1] avcodec/mpegutils: add motion_vec debug mode
Date: Fri, 2 Sep 2022 23:08:41 +0200
Message-ID: <CAPYw7P6RmWvkwMydd4-qXMMY1CvwJburt9WnELX5OSQPtxQapQ@mail.gmail.com> (raw)
In-Reply-To: <CAEb0Mfd2E8+G49jrJokZzLuLApAGppumvk_UFXTS5C956s5q7w@mail.gmail.com>
On Fri, Sep 2, 2022 at 8:04 PM Chema Gonzalez <chema@berkeley.edu> wrote:
> Hi again,
>
> On Fri, Sep 2, 2022 at 9:10 AM Paul B Mahol <onemda@gmail.com> wrote:
> >
> > On Fri, Sep 2, 2022 at 5:12 PM Chema Gonzalez <chema@berkeley.edu>
> 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.
>
> 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".
>
_______________________________________________
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".
next prev parent reply other threads:[~2022-09-02 21:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 23:09 [FFmpeg-devel] [PATCH 0/1] add motion_vec (motion vector) " Chema Gonzalez
2022-08-31 23:09 ` [FFmpeg-devel] [PATCH 1/1] avcodec/mpegutils: add motion_vec " Chema Gonzalez
2022-09-01 13:30 ` Ronald S. Bultje
2022-09-01 15:05 ` Chema Gonzalez
2022-09-01 17:55 ` Paul B Mahol
2022-09-01 18:43 ` Chema Gonzalez
2022-09-02 7:59 ` Paul B Mahol
2022-09-02 15:12 ` Chema Gonzalez
2022-09-02 16:13 ` Paul B Mahol
2022-09-02 18:03 ` Chema Gonzalez
2022-09-02 21:08 ` Paul B Mahol [this message]
2022-09-03 0:46 ` Chema Gonzalez
2022-09-03 9:15 ` Paul B Mahol
2022-09-03 12:07 ` Ronald S. Bultje
2022-09-12 23:49 ` Chema Gonzalez
2022-09-01 0:21 Chema Gonzalez
2022-09-01 0:22 Chema Gonzalez
2022-09-01 0:26 Chema Gonzalez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPYw7P6RmWvkwMydd4-qXMMY1CvwJburt9WnELX5OSQPtxQapQ@mail.gmail.com \
--to=onemda@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=rsbultje@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git