I´m currently on vacation and haven’t had any time yet to play with the newest commits. That commit => vo_gpu_next: add `--target-colorspace-hint-mode` option · mpv-player/mpv@ce076de · GitHub is stopping me from “blindly” merging them all on my side. If I understand it correctly, the “default” value breaks known behavior. (different source of metadata => default uses display values as default, on my mind, the preferred choice would be source, needs to be manually set…)
I will test behavior probably next week with my hdfury. If everything is as expected, I will merge it and publish a new build. (I will probably swap the default value for metadata source so that no change on the user end is needed)
The new build, including all the changes, is currently compiling!!
I tested it on my end and with the setting “target-colorspace-hint-mode=source” added to the mpv.conf, the behavior is as previously known. (file metadata is passed to the display)
Overriding the default value “target” seems difficult (or at least it’s not as simple as I thought)… Well, I haven’t looked deeper into that. I don´t want to bring too much complexity into the mpv repo/making it even more out of tree… I will make a note about adding target-colorspace-hint-mode=source to the mpv.conf on the main HDR post and a side note at the first post here in the next days.
I’m getting some brightness flickers with HDR content when tone mapping to SDR. Very occasionally but distracting. Rolled back to 07-20 build and its all good again.
Reset all my settings and mpv.conf. With base settings there is no problem. But as soon as I add ‘vo=gpu-next’ to my mpv.conf the problem starts.
Doesn’t happen at exactly the same spots each time, but I’ve been watching the first few minutes of Ready Player One (a straight UHD rip I made) and that’s been triggering it for me.
Can you please test with libplacebo-opts=tone_map_metadata=hdr10 added to your mpv.conf? Is the behavior any different? Can you also test it with hdr-compute-peak=no in your mpv.conf?
As I just said. It only has that one line in it now, I don’t think sharing that as a file is really required.
I’m on windows 11 24H2 all up to date, AMD RX 9070 on 25.6.3 drivers initially and I’ve just tried with today’s new drivers 25.8.1 but still happening.
Also tried with various video playback quality settings, refresh switching on and off, hardware decoding on and off, but all cause the same problem.
Interestingly using the mpv executable from the same build does not exhibit the issue, so it’s something Plex htpc is doing differently than the mpv application.
I’m currently using the “Make my GPU hurt” setting, but I have tried normal and low as well and have the same issue.
I tried with the latest shinchiro build and have the same problem.
I’ve just tried on my desktop PC, with an nvidia rtx 4080 and this also has the same issue.
So I’m pretty sure others will be able to recreate this problem. But it is not very consistent when it occurs and requires carefully watching every frame or you’ll miss it.
I’ll DM a link to a clip of a video that’s affected.