MPV does not behave well in HDR with KWin SDR brightness < MAX

Open
#18,626 5 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
c, linux

Research direction

Start with the attached debug log and identify which video output and color management path mpv uses with KWin when SDR brightness is below the display maximum. Compare the reported primaries and transfer values in the good and washed out states, then trace the relevant handling in the video output code. Done means SDR content remains correctly rendered at lower KWin SDR brightness; the issue does not name a file or test, so locating the responsible code will take investigation.

Written by the indexing model from the issue text.

Description

os:linux
mpv Information
mpv v0.41.0 Copyright © 2000-2025 mpv/MPlayer/mplayer2 projects
 built on Aug 28 2026 19:44:41
libplacebo version: v7.360.1
FFmpeg version: n9.0.1 (runtime n9.0.2)
FFmpeg library versions:
   libavcodec      63.1.101 (runtime 63.1.102)
   libavdevice     63.1.101 (runtime 63.1.102)
   libavfilter     12.1.101 (runtime 12.1.102)
   libavformat     63.1.101 (runtime 63.1.102)
   libavutil       61.1.101 (runtime 61.1.102)
   libswresample   7.1.101 (runtime 7.1.102)
   libswscale      10.1.101 (runtime 10.1.102)
Other Information
- Linux version: Arch Linux
- Kernel Version: 7.2.7-zen1-1-zen
- GPU Model: NVIDIA Corporation TU106 [GeForce RTX 2070]
- Mesa/GPU Driver Version: 4.6.0 NVIDIA 615.71.09
- Window Manager and Version: KWin 6.7.91 (6.8 Beta 2 ~= 6.8.0)
- Source of mpv: Arch Linux repositories
- Latest known working version: n/a
- Issue started after the following happened: n/a
Reproduction Steps

When using MPV in KWin with a HDR display, and HDR enabled, and SDR content, I experience the following:

  • When KWin's SDR brightness is set to the display's peak brightness (in my case, 418 nits), content looks correct, and is appropriately vibrant. MPV is using Primaries: bt.709 Transfer: bt.1886.
  • When KWin's SDR brightness is set below the display's peak brightness (<418 nits), content is washed out, dull, slightly desaturated, etc. MPV is using Primaries: [0.705 0.296, 0.192 0.755, 0.144 0.040, 0.313 0.329] in bt.2020 Transfer: pq.
  • In the above state, during KWin's night light transition, MPV switches for several random frames to displaying primaries and transfer as in the initial good state, and content appears briefly normal.

Screenshots in MPV look normal in any case.

The following screenshots show each state, with the caveat that the bad screenshot looks worse in-person:

Good Bad
Image Image

In Plasma 6.8, KWin's SDR brightness can be read with kscreenctl list-outputs (as SDR brightness: 418 nits) and modified with kscreenctl <output> set-sdr-brightness <brightness>.

Expected Behavior

Content looks correct regardless of KWin's SDR brightness.

Actual Behavior

SDR content viewed in HDR looks incorrect where KWin's SDR brightness is less than the maximum, with interesting switches with several frames looking correct during night-light transition.

Log File

mpv-debug-output.txt

Sample Files

This can be observed in normal YouTube content via yt-dlp.

I carefully read all instruction and confirm that I did the following:
  • I tested and confirmed that the issue exists with the latest release version or newer.
  • 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.
Dominant language
C
Stars
38.2k
Forks
3.7k
Avg merge
1d 13h
Merged PRs (30d)
76

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mpv-player/mpv

All issues in mpv-player/mpv

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.