mpv-player / mpv-player/mpv

How to view performance metrics (upload/render/present times)

Open
#14,824 2 comments 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.38.0-717-g92f052c14e Copyright © 2000-2024 mpv/MPlayer/mplayer2 projects
 built on Aug 23 2024 19:03:40
libplacebo version: v7.349.0 (v7.349.0-5-g82bf46ae)
FFmpeg version: N-116756-gcfe0a36352
FFmpeg library versions:
   libavcodec      61.11.100
   libavdevice     61.2.100
   libavfilter     10.2.102
   libavformat     61.5.101
   libavutil       59.34.100
   libswresample   5.2.100
   libswscale      8.2.100
Other Information
- Linux version:UnionTech OS Desktop 20 Pro
- Kernel Version:4.19.0-amd64-desktop
- Mesa/GPU Driver Version: OpenGL version string: 4.1 build 20240905 release db38ca5a4 db38ca5a4@20240905
Reproduction Steps

mpv --hwdec=vaapi --vo=gpu 1920-1080-60.flv --loop
Statistics on decoding time could not be found
What does key_page_0's vo-video-draw and vo-video-time mean

Expected Behavior

performance metrics can be viewed via stats (upload/render/present times)

Actual Behavior

last avg peak always equal to 0

Log File

mpv.log

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 with mpv's stats output and the key_page_0 values for vo-video-draw and vo-video-time, using the reproduction command and attached log. Determine why the last, average, and peak values remain zero; done means stats expose meaningful upload, render, and present times.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
cli, performance
Issue type
Feature
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.