Skip to content

Add SSIM and HDR metrics auto-exposure - #756

Merged
solidpixel merged 3 commits into
mainfrom
opt-cli-ssim
Nov 11, 2026
Merged

solidpixel merged 3 commits into
mainfrom
opt-cli-ssim

Conversation

@solidpixel

@solidpixel solidpixel commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

I want to look at fixing the block artifacts reported in #364, but mPSNR is a terrible metric for tracking progress improving that kind of issue. This adds a port of my existing offline SSIM tool to the command line tool as a standard feature.

For HDR images we report "mSSIM" which follows the same design as the existing "mPSNR", averaging scores over all active fstop levels. It reports exceptionally high scores with the old default fstops ([-10, 10]), as the extreme levels tend to saturate out one way or another, so it only really works if you can narrow the exposure levels.

Based on this paper:

https://icg.gwu.edu/sites/g/files/zaxdzs6126/files/downloads/Photographic%20Tone%20Reproduction%20for%20Digital%20Images.pdf

... I've implemented an auto-exposure scheme that sets the default fstops to +-2 steps around a luminance geomean. Users can still override it using the -mpsnr option to set their own fstep levels.

The mPSNR metrics will pick up the same change, which I think is beneficial, so any existing mPSNR score in the reference results is expected to drop because we're no longer measuring the same thing.

@solidpixel solidpixel changed the title Add SSIM and HDR auto-exposure Add SSIM and HDR metrics auto-exposure Nov 11, 2026
@solidpixel
solidpixel merged commit cc02c25 into main Nov 11, 2026
21 checks passed
@solidpixel
solidpixel deleted the opt-cli-ssim branch November 11, 2026 22:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant