-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Oversaturated when paused if OSD pops up #15130
Comments
So why did you make a new issue? |
Does |
Does
The original issue didn't follow the template, was on mpv.net which is not mpv, and was on a much older version. |
No difference.
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. |
|
Unfortunately, issue still persists. 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 #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
.The text was updated successfully, but these errors were encountered: