Brightness "jumps" / discontinuity when using bt.2446a tone mapping and an icc color profile

[Nox996]

mpv Information

mpv v0.38.0-784-gd02f03bc Copyright © 2000-2024 mpv/MPlayer/mplayer2 projects
 built on Sep 16 2024 00:06:46
libplacebo version: v7.349.0 (v7.349.0-10-g76bb971-dirty)
FFmpeg version: N-117044-g00f5a34c9
FFmpeg library versions:
   libavcodec      61.13.100
   libavdevice     61.2.101
   libavfilter     10.2.102
   libavformat     61.5.101
   libavutil       59.36.100
   libswresample   5.2.100
   libswscale      8.2.100

Other Information

- Windows version: Microsoft Windows [Version 10.0.22631.4169]
- GPU model, driver and version: AMD RX 7800 XT, AMD driver v24.8.1 
- Source of mpv: https://github.com/shinchiro/mpv-winbuild-cmake/releases
- Introduced in version: not known

Reproduction Steps

mpv configuration:

vo=gpu-next
profile=high-quality
scale=ewa_lanczossharp
cscale=ewa_lanczossharp
video-sync=display-resample
interpolation=yes
tscale=oversample

tone-mapping=bt.2446a

icc-profile-auto

I have tested the issue with two setups (and two different PCs):

1. Using Eizo color calibration software and a CS2740
2. Using a Panasonic TV + DisplayCAL

The important option to set is icc-profile-auto - the issue is only appearing when using an icc profile

Steps: 0) install a color profile (e.g. the one that is attached to this issue below as "sample" - not sure if this problem appears with any icc color profile)

1. start playing an HDR10 file (i.e. one where hdr-compute-peak does it's job - I haven't had the issue with DoVi files)
2. Wait for a scene where the max nits drops from "above" 203 nits to "203 nits or lower"

Expected Behavior

mpv should deliver smooth changes in frame brightness when using bt.2446a tone mapping and icc color profiles.

Actual Behavior

in scenes where the detected peak goes from "above 203 nits" to "203 nits or lower", the brightness of the scene jumps from one frame to the next, see attached screenshots.

In addition, it can be seen that the bt.2446a tone mapping status output disappears. This does not happen when leaving the icc-profile-auto option out - there, it simply stays at "203 --> 203" mapping.

Log File

output.txt

Sample Files

CS2740(24808080)07Nat_D65_g2.4_max.icc.zip

I carefully read all instruction and confirm that I did the following:

• [X] I tested with the latest mpv version to validate that the issue is not already fixed.
• [X] I provided all required information including system and mpv version.
• [X] I produced the log file with the exact same set of files, parameters, and conditions used in "Reproduction Steps", with the addition of --log-file=output.txt.
• [X] I produced the log file while the behaviors described in "Actual Behavior" were actively observed.
• [X] I attached the full, untruncated log file.
• [X] I attached the backtrace in the case of a crash.