mpv-player / mpv-player/mpv

Glitch with GPU-NEXT + HDR +VAAPI for AV1 format.

Open
#16,662 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

os:linux
Dominant language
C
Stars
37k
Forks
3.5k
Avg merge
1d 10h
Merged PRs (30d)
22

Description

mpv Information
mpv v0.40.0-dirty Copyright © 2000-2025 mpv/MPlayer/mplayer2 projects
 built on Jul 29 2025 22:35:55
libplacebo version: v7.351.0
FFmpeg version: n7.1.1
FFmpeg library versions:
   libavcodec      61.19.101
   libavdevice     61.3.100
   libavfilter     10.4.100
   libavformat     61.7.100
   libavutil       59.39.100
   libswresample   5.3.100
   libswscale      8.3.100
Other Information
- Linux version: Arch Linux
- Kernel Version: Linux laichiaheng 6.16.0-2-cachyos #1 SMP PREEMPT_DYNAMIC Thu, 31 Jul 2025 13:05:15 +0000 x86_64 GNU/Linux
- GPU Model: Navi 48 [Radeon RX 9070/9070 XT/9070 GRE] [1002:7550]
- Mesa/GPU Driver Version:
- Window Manager and Version: Mesa 25.3.0-devel (git-72cf81df54) (LLVM 20.1.8)
- Source of mpv: Arch Linux
- Latest known working version: none
- Issue started after the following happened: play HDR videos with AV1 format while VAAPI is enabled.
Reproduction Steps

Here is the source video from YouTube: https://www.youtube.com/watch?v=p0PE3t77weY

mpv --log-file=AV1_glitch.txt --no-config --vo=gpu-next --ytdl-raw-options=cookies-from-browser=firefox --target-colorspace-hint=auto --hwdec=vaapi --fs https://youtu.be/p0PE3t77weY

I recorded the glitch from my smart phone: https://youtube.com/shorts/uCCGXWKJlhs
It is between 00:12 to 00:15 at the top left corner.

Expected Behavior

No glitch, play smoothly.

Actual Behavior

I can see the glitch.

Image

Log File

output.txt

Sample Files

Lots of HDR videos on YouTube.

https://www.youtube.com/watch?v=p0PE3t77weY
https://www.youtube.com/watch?v=Ji-nP3Gk8Pw

I carefully read all instruction and confirm that I did the following:
  • I tested with the latest mpv version to validate that the issue is not already fixed.
  • 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

  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.

Research direction

Reproduce the issue with the supplied YouTube sample and the exact mpv command using --vo=gpu-next, --target-colorspace-hint=auto, and --hwdec=vaapi; inspect output.txt alongside the GPU, Mesa, kernel, and FFmpeg details. Trace the GPU rendering and VAAPI path involved in HDR AV1 playback. Done means the reported top-left glitch no longer appears under the supplied conditions.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
computer-graphics, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.