mpv-player / mpv-player/mpv

Add --screenshot-metadata CLI option

Open
#2,726 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Hi, I would really love a CLI option where I can specify the metadata which is written to a screenshot PNG. This would be an addition to the --screenshot-template option, but would store the metadata in the file not in the files name. In that way, you could really use the %P (path) placeholder, which is normally not usable here, because test-[%P] would be translated to test-[/home/user/test.png].png which is not a valid filename.

Example:

mpv --screenshot-metadata "filename:%f" \
    --screenshot-metadata "path:%P" \
    --screenshot-metadata "position:%fc"

So that pngmeta would print the following output:

$ pngmeta ~/test.png
filename: test.mp4
path: file:////home/user/test.mp4
position: 5835467

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 tracing mpv's CLI handling for --screenshot-template and the screenshot-writing path. Check how PNG output is currently produced, then define how repeated --screenshot-metadata values map to PNG metadata while preserving the example placeholders. Done means the option accepts the shown inputs and pngmeta can read the resulting filename, path, and position values.

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
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.