Tonemapping for SDR Monitors?

[notshoka]

Hello, I notice that the HDR feature omits any mpv tonemapping config implementation, thus making HDR videos look incorrect on a SDR monitor.

Is there any way to disable to HDR feature to allow for mpv's tonemapping parameters?

[notshoka]

i have figured out the problem:

in my mpv config, I have gpu-api=d3d11.
When I run HDR videos on my standalone mpv executable with gpu-api=d3d11, my tone-mapping configurations run as expected.

but, running gpu-api=d3d11 in this stremio version doesn't render out tone-mapping properly, unless I change gpu-api=vulkan, then the tone-mapping for HDR to SDR renders properly.

is there a reason for this, as i may have missed something?

(also, this stremio project is real amazing work, im loving it a lot, thank you so much for this.)

[Zaarrg]

That is indeed weird that "api=vulkan" fixes it. Because the app itself does not really have anything to disable the hdr feature as that is for windows to decide. Aka auto hdr and similar.

One thing the stremio player does is set "gpu-next" or "gpu".

To overwrite that u can go to via Windows+R :

%localappdata%\Programs\LNV\Stremio-5\portable_config

And then try setting the MPV VideoOutput to something like just gpu and then set in mpv.conf the api to d3d11.

[MPV]
VideoOutput=gpu
InitialVolume=50

But other then that im not quite sure what the issue might be as there is not really anything set that would force hdr or any other configuration options in paticular.

Potentialy as alternative to see what mpv is using when playing a vid u can press the key left of 1 this will open the console. Tho this is not fully functional as there is no way to close it. To close that console u will have to restart the app.

[notshoka]

I can confirm that changing from "gpu-next" to "gpu" does seems to also fix the issue, but I could be wrong in terms of compatibility and will still be using "gpu-next" with gpu-api=vulkan.

This is because I copied and pasted some of my standalone mpv configuration files to this github version, and some of the commands I use require gpu-next.

For reference, this is my conditional HDR to SDR profile I am using instead in this github version:

profile-desc=HDR -> SDR
profile-cond=get("video-params/gamma") == "pq" and get("video-params/primaries") == "bt.2020"
profile-restore=copy-equal
target-peak=85
tone-mapping=spline
tone-mapping-param=2.00
gamut-mapping-mode=auto
hdr-compute-peak=yes
target-colorspace-hint=yes
icc-profile-auto=yes
gamma-factor=1.1

But so far this isn't really an issue for me anymore as switching from d3d11 to vulkan fixed this "issue?", and also doesn't change anything noticeable for me and continues to run fine when ran this way on my own standalone mpv version.

Oh, and I also made sure to use the exact same mpv configuration files in this github version (aka not replacing the files with my own mpv configuration files), and only ever changed the conditional profiles in mpv.conf and the issue is the same.

So this could very well be my lack of reading of the mpv manual with what I've used.