From: "Carotti, Elias via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org> To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org> Cc: "Carotti, Elias" <eliascrt@amazon.it> Subject: [FFmpeg-devel] libavc/libx264: add support to propagate SSE values through encoder stats Date: Sat, 23 Sep 2023 10:04:28 +0000 Message-ID: <235b296cd67fed2c79862d4403dbe268d2f7e25b.camel@amazon.it> (raw) [-- Attachment #1: Type: text/plain, Size: 597 bytes --] 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. 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. Best, Elias NICE SRL, viale Monte Grappa 3/5, 20124 Milano, Italia, Registro delle Imprese di Milano Monza Brianza Lodi REA n. 2096882, Capitale Sociale: 10.329,14 EUR i.v., Cod. Fisc. e P.IVA 01133050052, Societa con Socio Unico [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #2: 0001-Add-the-SSE-calculation-for-libx264.patch --] [-- Type: text/x-patch; name="0001-Add-the-SSE-calculation-for-libx264.patch", Size: 2601 bytes --] From dfd47efb7f7cb264fef62d0d8fb70ff8168bdfd7 Mon Sep 17 00:00:00 2001 From: Elias Carotti <eliascrt _at_ amazon _dot_ it> Date: Fri, 15 Sep 2023 20:05:43 +0200 Subject: [PATCH] Add the SSE calculation for libx264. Since libx264 only provides a per-frame per-channel PSNR, this is inverted to get back the SSE. --- libavcodec/libx264.c | 37 ++++++++++++++++++++++++++++++++++++- 1 file changed, 36 insertions(+), 1 deletion(-) diff --git a/libavcodec/libx264.c b/libavcodec/libx264.c index 77a9f173b4..0fae155ff2 100644 --- a/libavcodec/libx264.c +++ b/libavcodec/libx264.c @@ -129,6 +129,8 @@ typedef struct X264Context { int roi_warned; int mb_info; + + int64_t sse[3]; } X264Context; static void X264_log(void *p, int level, const char *fmt, va_list args) @@ -726,7 +728,40 @@ FF_ENABLE_DEPRECATION_WARNINGS pkt->flags |= AV_PKT_FLAG_KEY*pic_out.b_keyframe; if (ret) { - ff_side_data_set_encoder_stats(pkt, (pic_out.i_qpplus1 - 1) * FF_QP2LAMBDA, NULL, 0, pict_type); + const AVPixFmtDescriptor *pix_desc = av_pix_fmt_desc_get(csp_to_pixfmt(pic_out.img.i_csp)); + int error_count = 0; + int64_t *errors = NULL; + + if (ctx->flags & AV_CODEC_FLAG_PSNR) { + double scale[3] = { 1, + (1 << pix_desc->log2_chroma_h) * (double)(1 << pix_desc->log2_chroma_w), + (1 << pix_desc->log2_chroma_h) * (double)(1 << pix_desc->log2_chroma_w), + }; + double mse; + int i; + + error_count = pix_desc->nb_components; + + av_log(ctx, AV_LOG_DEBUG, "PSNR values from libx264: %.3f %.3f %.3f.\n", + pic_out.prop.f_psnr[0], pic_out.prop.f_psnr[1], pic_out.prop.f_psnr[2]); + + for (i = 0; i < pix_desc->nb_components; ++i) { + double max_value = (double)(1 << pix_desc->comp[i].depth) - 1.0; + double plane_size = ctx->width * ctx->height / scale[i]; + + /* psnr = -10 * log10(max_value * max_value / mse) */ + mse = (max_value * max_value) / pow(10, -pic_out.prop.f_psnr[i] / 10.0); + + /* SSE = MSE * width * height / scale -> because of possible chroma downsampling */ + x4->sse[i] = (int64_t)floor(mse * plane_size); + }; + + errors = x4->sse; + } + + ff_side_data_set_encoder_stats(pkt, (pic_out.i_qpplus1 - 1) * FF_QP2LAMBDA, + errors, error_count, pict_type); + if (wallclock) ff_side_data_set_prft(pkt, wallclock); } -- 2.34.1 [-- Attachment #3: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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 reply other threads:[~2023-09-23 10:04 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-23 10:04 Carotti, Elias via ffmpeg-devel [this message] 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
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=235b296cd67fed2c79862d4403dbe268d2f7e25b.camel@amazon.it \ --to=ffmpeg-devel@ffmpeg.org \ --cc=eliascrt@amazon.it \ /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