mpv-player / mpv-player/mpv

mpv play 4k 60fps vp9 video with hwdec slower than Firefox, even than software decoding

Open
#14,548 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

down-upstream:ffmpeg os:win
Dominant language
C
Stars
37k
Forks
3.5k
Avg merge
1d 10h
Merged PRs (30d)
22

Description

mpv Information
mpv v0.38.0-580-g00f43e09 Copyright © 2000-2024 mpv/MPlayer/mplayer2 projects
 built on Jul  7 2024 00:04:00
libplacebo version: v7.349.0 (v7.349.0-dirty)
FFmpeg version: N-116159-gecd3a9783
FFmpeg library versions:
   libavcodec      61.9.100
   libavdevice     61.2.100
   libavfilter     10.2.102
   libavformat     61.4.100
   libavutil       59.28.100
   libswresample   5.2.100
   libswscale      8.2.100
Other Information

CPU: Intel i5-8400
GPU: Nvidia GTX 1050
Although I have BlackDesert in minimized(which do not consume too much resources), it's abnormal that firefox does better than mpv.
GTX 1050 has vp9 decoding support. link

screenshots:
mpv --no-config --profile=fast:
image

mpv --no-config --hwdec=d3d11va --profile=fast:
image

play file in firefox:
image

Reproduction Steps

MPV Software testing 1: mpv <file> --no-config
MPV Software testing 2: mpv <file> --no-config --profile=fast

MPV Hardware testing 1: mpv <file> --no-config --hwdec=d3d11va
MPV Hardware testing 2: mpv <file> --no-config --hwdec=d3d11va --profile=fast

Firefox Hardware testing: drag and drop into new tab

Expected Behavior

MPV Software testing 1: maybe slow
MPV Software testing 2: maybe slow

MPV Hardware testing 1: fast
MPV Hardware testing 2: fast

Firefox Hardware testing: fast

** slow means visable shuttering

Actual Behavior

MPV Software testing 1: slow
MPV Software testing 2: fast

MPV Hardware testing 1: slow
MPV Hardware testing 2: slow

Firefox Hardware testing: fast

** slow means visable shuttering

Log File

mpv <file> --no-config --hwdec=d3d11va --gpu-debug --log-file=output.txt
output.txt

Sample Files

No response

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

Start by reproducing the reported commands with the supplied mpv version and compare the software and d3d11va runs. Inspect output.txt alongside the playback behavior and the issue's hardware and codec details. Done means identifying and correcting the cause of visible shuttering during hardware-decoded VP9 playback, with the listed reproduction cases behaving as expected.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.