Vulkan HWDEC rendering corruption
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 37k
- Forks
- 3.5k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 22
Description
mpv Information
mpv v0.41.0-333-gb51131dff Copyright © 2000-2026 mpv/MPlayer/mplayer2 projects
built on Mar 15 2026 18:03:15
libplacebo version: v7.362.0 (v7.360.0-11-g33b5dfa-dirty)
FFmpeg version: N-123511-g3e8bec787
FFmpeg library versions:
libavcodec 62.29.100
libavdevice 62.4.100
libavfilter 11.15.101
libavformat 62.13.101
libavutil 60.29.100
libswresample 6.4.100
libswscale 9.7.100
Other Information
- Windows version: 10.0.26200 Build 26200
- GPU model, driver and version:
NVIDIA GeForce RTX 5070 Laptop GPU Game Ready Driver - 581.80 - Tue Nov 4, 2025
AMD Radeon(TM) 880M Graphics 32.0.13046.16
Razer Blade 14 RZ09-05306EM3
- Source of mpv: shinchiro
- Latest known working version: -
- Issue started after the following happened: Playing a particular video file
Reproduction Steps
hwdec=auto-safe (though I believe any form of hwdec is the same) causes weird frame corruption as pictured. Tested exclusively on vulkan. I am not sure what GPU it is using on this laptop.
The file being played is a BlueRay of the anime movie "A Wind Named Amnesia".
Expected Behavior
Actual Behavior
Log File
Sample Files
My config folder is attached, but most of it is irrelevant. Only thing that matters as far as I can tell is that hwdec is on. Rest is attached a precaution. I don't use shaders but I have them downloaded.
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.
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 by reproducing the corruption with the attached mpv.zip sample, configuration, and logfile.txt using Vulkan hardware decoding, then determine which GPU and hardware-decoding path is active. Done means the supplied video renders without corruption with hardware decoding enabled, with a regression test or documented reproduction result if the affected path permits one.
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
- Needs clarification
- Newbie friendliness
- 35/100