Commit ce076de by default causes MESA: warning: Not using HDR metadata to avoid protocol errors

mpv Information

mpv v0.40.0-185-gbd2118026 Copyright © 2000-2025 mpv/MPlayer/mplayer2 projects
libplacebo version: v7.351.0
FFmpeg version: 7.1.1
FFmpeg library versions:
   libavcodec      61.19.101
   libavdevice     61.3.100
   libavfilter     10.4.100
   libavformat     61.7.100
   libavutil       59.39.100
   libswresample   5.3.100
   libswscale      8.3.100

Other Information

- Linux version:
  NAME=Gentoo
  PRETTY_NAME="Gentoo Linux"
- Kernel Version:
  Linux redacted 6.16.0-rc6 #755 SMP PREEMPT Mon Jul 14 redacted 2025 x86_64 12th Gen Intel(R) Core(TM) i5-12400 GenuineIntel GNU/Linux
- GPU Model:
  00:02.0 VGA compatible controller [0300]: Intel Corporation Alder Lake-S GT1 [UHD Graphics 730] [8086:4682] (rev 0c)
  01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7)
- Mesa/GPU Driver Version:
  OpenGL version string: 4.6 (Compatibility Profile) Mesa 25.2.0-devel (git-36172c41dc) [I'm actually using Vulkan 1.4.313.0 but don't have vulkaninfo installed]
- Window Manager and Version:
  kwin_wayland 6.4.2 with HDR enabled
- Source of mpv:
  Gentoo stock live ebuild (media-video/mpv-9999::gentoo)
- Latest known working version:
  Commit 5b1df3c5d900298e433539c99e8e5ea60acfa068 [triple checked for good measure]
- Issue started after the following happened:
  After latest rebuild of the mpv from git a new Mesa warning popped up. It had been days since I last used mpv and at first suspected a Mesa change but thankfully it wasn't too hard to find the suspect range of mpv commits and manually bisect them.

Reproduction Steps

With current git master and my SW/HW combo even mpv --config=no <Literally any video including SDR> prints MESA: warning: Not using HDR metadata to avoid protocol errors between the VO and AV lines.

Upon further testing, it seems that that warning is only printed with the new default --target-colorspace-hint-mode=target but not when it's set to source or source-dynamic.

For what it's worth, the verbose output places that line here:

[vo/gpu-next/libplacebo] Picked surface configuration 71: VK_FORMAT_R16G16B16A16_UNORM + VK_COLOR_SPACE_HDR10_ST2084_EXT
[vo/gpu-next/libplacebo] Spent 145.414 ms translating SPIR-V (slow!)
[vo/gpu-next/libplacebo] Spent 14.415 ms translating SPIR-V
MESA: warning: Not using HDR metadata to avoid protocol errors
[cplayer] first video frame after restart shown

but I have no idea, how much one can trust the ordering here.

Expected Behavior

Not having that warning. ;)

Actual Behavior

Ugh... I'm a bit confused what exactly is going on but it would seem that git master by default has broken HDR on Linux now, since while it looks HDR-ish, the colors are just slightly washed out. The fix or work-around is to set --target-colorspace-hint-mode=source|source-dynamic that has correct looking colors. Except those two don't feel like HDR but rather like well mapped HDR to SDR... (but of course the display is still in HDR mode and mpv does for all 3 of possible values report use of BT.2020 and PQ).

In short, I have no idea what the actual behavior is, sorry.

Log File

output.txt

Sample Files

No response

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.

Start by reviewing commit ce076de and comparing it with the last known working commit 5b1df3c5d900298e433539c99e8e5ea60acfa068. Reproduce with mpv --config=no using the reported HDR setup, compare target-colorspace-hint-mode values, and inspect output.txt; done means the warning is absent and HDR colors are correct without regressing source or source-dynamic behavior.