Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Ronald S. Bultje" <rsbultje@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Chema Gonzalez <chemag@gmail.com>
Subject: Re: [FFmpeg-devel] [PATCH 1/1] avcodec/mpegutils: add motion_vec debug mode
Date: Thu, 1 Sep 2022 09:30:11 -0400
Message-ID: <CAEEMt2ksqwJ8OemthsxBtUJgL4DgVQDqFWzi33PqHBx=zrLSHA@mail.gmail.com> (raw)
In-Reply-To: <20220831230918.1736362-2-chemag@gmail.com>

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

  reply	other threads:[~2022-09-01 13:30 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 [this message]
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
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='CAEEMt2ksqwJ8OemthsxBtUJgL4DgVQDqFWzi33PqHBx=zrLSHA@mail.gmail.com' \
    --to=rsbultje@gmail.com \
    --cc=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