Most (maybe all) HDR playback fails using gpu or gpu-next, works robustly using libmpv

Open
#18,445 7 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reproducing the HDR sample with the attached output.txt conditions: macOS 15.7.3, mpv v0.41.0, --no-config, and gpu or gpu-next. Compare the behavior and logs with vo=libmpv and the listed HDR options; done means HDR playback works with basic gpu or gpu-next defaults rather than appearing washed out.

Written by the indexing model from the issue text.

Description

os:mac vo:gpu:macvk
mpv Information
mpv v0.41.0 Copyright © 2000-2025 mpv/MPlayer/mplayer2 projects
libplacebo version: v7.360.1
FFmpeg version: 9.0.1
FFmpeg library versions:
   libavcodec      63.1.101
   libavdevice     63.1.101
   libavfilter     12.1.101
   libavformat     63.1.101
   libavutil       61.1.101
   libswresample   7.1.101
   libswscale      10.1.101
Other Information
- macOS version: 15.7.3
- Source of mpv: homebrew
- Latest known working version: 0.40 perhaps
- Issue started after the following happened: I am not sure
Reproduction Steps
  1. Fresh mpv CLI install from homebrew
  2. start HDR video playback (dv, bt.2020, pq) with --no-config, which seems to default to gpu or gpu-next
  3. Classic washed out failed HDR playback
  4. with vo=libmpv and no other config, HDR plays normally. With a range of other config (currently --cocoa-cb-output-csp=display-p3-pq, --target-trc=pq, --target-prim=display-p3), still works normally. Nothing works at all with gpu or gpu-next, and many flags seems to have no effect.
Expected Behavior

HDR stream should at least activate with basic default parameters using gpu or gpu-next

Actual Behavior

HDR stream fails using gpu or gpu-next

Log File

output.txt

Sample Files

https://drive.google.com/file/d/1Xw7Aug5nx3r_hHEFVypTyQ-cD0Anu7cU/view?usp=sharing

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.