Open Quenser opened 3 hours ago
Exact same issue as in https://github.com/mpv-player/mpv/issues/11152
So why did you make a new issue? edit: I see it was suggested but no idea why.
Does --gpu-shader-cache=no
fix it?
Does icc-profile-auto=no
fix it? --no-config
also disables loading of any external files, which include icc profiles provided by Windows.
edit: I see it was suggested but no idea why.
The original issue didn't follow the template, was on mpv.net which is not mpv, and was on a much older version.
Does
--gpu-shader-cache=no
fix it?
No difference.
Does
icc-profile-auto=no
fix it?--no-config
also disables loading of any external files, which include icc profiles provided by Windows.
No difference either.
Edit: Good call though, I do have icc profiles for both displays that I can reproduce it on. It only happens if HDR is enabled. Edit2: That was my old install, no user made profiles active here.
--icc-cache=no
should fix it then.
--icc-cache=no
should fix it then.
Unfortunately, issue still persists. Also funnily enough if I open it on an affected monitor and drag it over to another (in SDR mode) it persists over there too.
What I find really weird is how the OSD seems to trigger it. If I pause the video and don't pop the OSD up there are no issues.
mpv Information
Other Information
Reproduction Steps
Exact same issue as in https://github.com/mpv-player/mpv/issues/11152 Screenshots in #11152 illustrate it perfectly.
Using a very similar TV. Issue only occurs if watching content in HDR.
Content has to be started on the display with enabled HDR for the issue to occur. Does not occur if launched on SDR display and dragged over to HDR display. Reproduceable with any type of content. Independent of codec, HDR or SDR.
--no-config fixes it. Issue occurs if manually commenting all configs out. Tried with no mpv.conf at all, issue still occurs.
Log is running with my default conf and on a different screen with HDR enabled because it kept launching on the main screen and not the one I am usually watching on.
Expected Behavior
No Saturation when OSD shows up.
Actual Behavior
Picture oversaturates to an insane degree when paused if I accidentally make the OSD pop up. This is very troublesome for OLED displays as they react pretty badly to it even after only a few seconds.
Log File
output.txt
Sample Files
No response
I carefully read all instruction and confirm that I did the following:
--log-file=output.txt
.