Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

screenshot-tag-colorspace = no, not working as expected #15987

Open
5 of 6 tasks
JySzE opened this issue Mar 1, 2025 · 2 comments
Open
5 of 6 tasks

screenshot-tag-colorspace = no, not working as expected #15987

JySzE opened this issue Mar 1, 2025 · 2 comments

Comments

@JySzE
Copy link

JySzE commented Mar 1, 2025

mpv Information

mpv v0.39.0-781-gf94b44c8e Copyright © 2000-2025 mpv/MPlayer/mplayer2 projects
 built on Feb 16 2025 00:06:00
libplacebo version: v7.350.0 (v7.349.0-30-g056b852-dirty)
FFmpeg version: N-118471-ga50d36b5f
FFmpeg library versions:
   libavcodec      61.33.102
   libavdevice     61.4.100
   libavfilter     10.9.100
   libavformat     61.9.107
   libavutil       59.56.100
   libswresample   5.4.100
   libswscale      8.13.100

Important Information

- Platform version: Windows 10
- GPU model, driver and version: Nvidia RTX 4080, DCH, 566.36
- Source of mpv: sourceforge
- Latest known working version: no idea
- Issue started after the following happened: no idea

Reproduction Steps

Set conf to yes or no and save a screenshot using sample files.

Expected Behavior

Expected behavior is the screenshot-tag-colorspace = no & screenshot-tag-colorspace = yes but with metadata stripped using optipng -strip all should look the same but they do not.

I just want to set screenshot-tag-colorspace = no so I don't have to strip metadata every time I take a screenshot to get proper viewing.

Actual Behavior

Colors are wrong, here is a comparison: https://slow.pics/c/eFYXWAY2

Images in order:

  1. Raw window capture using snipping tool (color is correct)
  2. screenshot-tag-colorspace = no (color is wrong)
  3. screenshot-tag-colorspace = yes (color is wrong)
  4. screenshot-tag-colorspace = yes but meta stripped using optipng (color is correct)

Slow.pics comparison not using optimize feature as it fixes the problem on the screenshot-tag-colorspace = yes image.

Changing any other settings:

screenshot-format = png
screenshot-sw = no
screenshot-high-bit-depth = no
screenshot-tag-colorspace = yes
screenshot-png-compression = 4

Results in still incorrect colors no matter what.

Log File

output.txt

Screenshot Metadata:

screenshot-tag-colorspace = yes : https://pastebin.com/raw/Ga8n3a2P

screenshot-tag-colorspace = no : https://pastebin.com/raw/B1Kqa3w5

screenshot-tag-colorspace = yes but metadata has been stripped using optipng -strip all : https://pastebin.com/raw/YDeUvzqW

Sample Files

Using this mpv conf: mpv.txt
Using this sample video: https://files.catbox.moe/gnytqy.mkv

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.
@Traneptora
Copy link
Member

What happens if you use --vo=gpu-next?

@JySzE
Copy link
Author

JySzE commented Mar 2, 2025

What happens if you use --vo=gpu-next?

If you check the mpv.conf sample file I provided I already am.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants