Console flood when mapping PQ to BT.1886 [vo/gpu-next/libplacebo] New swap chain configuration was deemed not supported

[NSQY]

mpv Information

mpv v0.39.0-615-gca211b5b Copyright © 2000-2025 mpv/MPlayer/mplayer2 projects
 built on Jan 10 2025 14:04:25
libplacebo version: v7.350.0 (v7.349.0-30-g056b852-dirty)
FFmpeg version: N-118276-g292c1df7c
FFmpeg library versions:
   libavcodec      61.31.100
   libavdevice     61.4.100
   libavfilter     10.6.101
   libavformat     61.9.104
   libavutil       59.54.101
   libswresample   5.4.100
   libswscale      8.13.100

Other Information

- Windows version: Microsoft Windows NT 10.0.26100.0/26100.2605
- GPU model, driver and version: RTX 4070 ti 566.36
- Source of mpv: https://github.com/zhongfly/mpv-winbuild

Reproduction Steps

This seems to only occur in my env if I specify a target peak of 203 or lower. Higher values seem fine.

mpv --no-config --vo=gpu-next E:\SolLevante_HDR10_r2020_ST2084_UHD_24fps_1000nit.mov --target-trc=bt.1886 --target-peak=203
● Video  --vid=1  (prores 3840x2160 24 fps) [default]
● Audio  --aid=1  (pcm_s24le 6ch 48000 Hz) [default]
○ Audio  --aid=2  (pcm_s24le 2ch 48000 Hz) [default]
AO: [wasapi] 48000Hz stereo 2ch float
VO: [gpu-next] 3840x2160 yuv444p12
[vo/gpu-next/libplacebo] New swap chain configuration was deemed not supported: format: supported, color space: unsupported. Failling back to 8bit RGB.
[vo/gpu-next/libplacebo] New swap chain configuration was deemed not supported: format: supported, color space: unsupported. Failling back to 8bit RGB.
[vo/gpu-next/libplacebo] New swap chain configuration was deemed not supported: format: supported, color space: unsupported. Failling back to 8bit RGB.
[vo/gpu-next/libplacebo] New swap chain configuration was deemed not supported: format: supported, color space: unsupported. Failling back to 8bit RGB.
[vo/gpu-next/libplacebo] New swap chain configuration was deemed not supported: format: supported, color space: unsupported. Failling back to 8bit RGB.
[ ... ]

Expected Behavior

I expect mapping from transfer x or y with a full range of target peak

Actual Behavior

console spam until peak or trc changed

Log File

mpv_log.txt

Sample Files

example.mov

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

• I tested with the latest mpv version to validate that the issue is not already fixed.
• I provided all required information including system and mpv version.
• 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.
• I produced the log file while the behaviors described in "Actual Behavior" were actively observed.
• I attached the full, untruncated log file.
• I attached the backtrace in the case of a crash.

[kasper93]

--target-colorspace-hint=no