Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Chema Gonzalez <chemag@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Cc: Chema Gonzalez <chemag@gmail.com>
Subject: [FFmpeg-devel] [PATCH 0/1] add motion_vec (motion vector) debug mode
Date: Wed, 31 Aug 2022 16:09:17 -0700
Message-ID: <20220831230918.1736362-1-chemag@gmail.com> (raw)

This is useful if you want to see the motion vectors (MV)
generated by an encoder. I used ffmpeg debug mode, which is
also used by similar functionality, like the QP value dumper.


Chema Gonzalez (1):
  avcodec/mpegutils: add motion_vec debug mode

 libavcodec/avcodec.h       |  1 +
 libavcodec/mpegutils.c     | 45 +++++++++++++++++++++++++++++++++++++-
 libavcodec/options_table.h |  1 +
 3 files changed, 46 insertions(+), 1 deletion(-)

-- 
2.37.2

_______________________________________________
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".

             reply	other threads:[~2022-08-31 23:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31 23:09 Chema Gonzalez [this message]
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
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

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=20220831230918.1736362-1-chemag@gmail.com \
    --to=chemag@gmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    /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