vo_gpu-next: vapoursynth filter seems could not receive dolbyvision's metadata
Open
Nobody has claimed this yet.
os:win
vo:gpu-next
- Dominant language
- C
- Stars
- 37k
- Forks
- 3.5k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 22
Description
Important Information
Provide following Information:
- mpv version
https://github.com/shinchiro/mpv-winbuild-cmake/releases/tag/20220723 - Windows Version
win11 release - Source of the mpv binary
https://github.com/shinchiro/mpv-winbuild-cmake/releases/tag/20220723 - If known which version of mpv introduced the problem
N/A - Possible screenshot or video of visual glitches
Reproduction steps
# mpv.conf
vo=gpu-next
-
run mpv.exe and play a dv file, and then activate any vapoursynth filter.
-
vf toggle vapoursynth="~~/test0.vpy"
# test0.vpy
video_in.set_output()
Expected behavior
correct color
Actual behavior
Log file
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start with the reproduction in mpv.conf and test0.vpy, then inspect the linked mpv-test.log and the gpu-next VapourSynth filter path. Confirm how Dolby Vision metadata is handled before and after enabling the filter; done means playback retains the expected colors with the filter active.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100