Most (maybe all) HDR playback fails using gpu or gpu-next, works robustly using libmpv
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
- Domain
- computer-graphics
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
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
- Fresh mpv CLI install from homebrew
- start HDR video playback (dv, bt.2020, pq) with --no-config, which seems to default to gpu or gpu-next
- Classic washed out failed HDR playback
- 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
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mpv-player/mpv
-
meta:feature-request
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
mpv-player/mpv#18855 · 2 comments ·
Maintainers usually reply within 1 day
-
meta:feature-request
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
mpv-player/mpv#18683 · 4 comments ·
Maintainers usually reply within 1 day
-
Subtitle delay value displays "-0ms"May be free again A pull request for this issue was closed without being merged. Openos:linux
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
mpv-player/mpv#18649 · 1 comment ·
Maintainers usually reply within 1 day
-
meta:feature-request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mpv-player/mpv#18464 ·
Maintainers usually reply within 1 day
-
Keyboard shortcut next and previous secondary subtitle filePossibly taken @ravarnax claimed this 225 days ago. Openmeta:feature-request
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
mpv-player/mpv#17693 · 5 comments · 1 reaction ·
Maintainers usually reply within 1 day
Similar issues
-
`sha256()` returns a wrong hash when libsql-ffi is built with gcc 11 or laterPossibly taken @colinhacks claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tursodatabase/libsql#2333 ·
Maintainers usually reply within 11 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OpenPrinting/cups#1826 ·
Maintainers usually reply within 1 day
-
Backport to 3.0 advertises a suffix that does not existPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
389ds/389-ds-base#8152 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
RetroAchievements/rcheevos#580 · 1 comment ·
Maintainers usually reply within 5 days