mpv-player / mpv-player/mpv

Add a property to read container average bitrate

Open
#8,995 9 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

meta:feature-request
Dominant language
C
Stars
37k
Forks
3.5k
Avg merge
1d 10h
Merged PRs (30d)
22

Description

Basically what I wish to accomplish is to calculate bits(pixel*frame) value of a video file and pick a profile according to the theoretical quality of the video based on its average bitrate, resolution and frame rate reported by the container. However I was unable to find a way to read the container's video average bitrate via properties. The closest thing I could find was video-bitrate which is not an average value and unfit for profile selection (because most videos start with a fade-in or something similar which requires less bitrate at the beginning). There was also video-params/average-bpp but I think it is for color depth since it displayed 24 for all the videos that I have tested. I would appreciate it if you could offer me a workaround or consider adding it as a feature.

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

No file or test is identified in the issue. Start by locating the existing video-bitrate property and tracing how media-container metadata becomes exposed properties. Done means a property reports the container's video average bitrate and can be used alongside resolution and frame rate for profile selection.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.