Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Anton Khirnov <anton@khirnov.net>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Cc: "Carotti, Elias" <eliascrt@amazon.it>
Subject: Re: [FFmpeg-devel] libavc/libx264: add support to propagate SSE values through encoder stats
Date: Thu, 19 Oct 2023 13:48:33 +0200
Message-ID: <169771611358.29037.16521815224024070919@lain.khirnov.net> (raw)
In-Reply-To: <235b296cd67fed2c79862d4403dbe268d2f7e25b.camel@amazon.it>

Quoting Carotti, Elias via ffmpeg-devel (2023-09-23 12:04:28)
> Hi,
> please find attached a patch to propagate the SSE for a frame into the
> encoder stats.
> Since libx264 already provides PSNR values, this is done by basically
> inverting the formula to recover the SSE values.

Thanks, pushed.

> Would it be possible to also append other values to the errors vector?
> E.g., libx264 also computes SSIM but other values could be provided.

It is certainly conceivable, but it's a nontrivial question whether it
should be added to this side data or to a new one. Ideally the same type
of data should be produced both by this and the various
metrics-computing filters.

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

      parent reply	other threads:[~2023-10-19 11:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-23 10:04 Carotti, Elias via ffmpeg-devel
2023-10-02 17:35 ` Carotti, Elias via ffmpeg-devel
2023-10-10 10:54   ` Anton Khirnov
2023-10-11 10:54     ` Carotti, Elias via ffmpeg-devel
2023-10-13 14:16       ` Anton Khirnov
2023-10-13 16:35         ` Carotti, Elias via ffmpeg-devel
2023-10-19 11:50           ` Anton Khirnov
2023-10-19 11:48 ` Anton Khirnov [this message]

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=169771611358.29037.16521815224024070919@lain.khirnov.net \
    --to=anton@khirnov.net \
    --cc=eliascrt@amazon.it \
    --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