View Issue Details

IDProjectCategoryView StatusLast Update
0000674madVRbugpublic2021-10-18 01:02
Reporterhuhn Assigned To 
Status newResolutionopen 
Platformx64OSwindows 11OS Version22000
Summary0000674: madVR hdr does not work on windows 11 newest build
Descriptionthe new win 11 build stop madVR from sending an HDR image. the image is just tone mapped to SDR i guess by windows or the GPU driver HDR is not send but madVR thinks it is the OSD still shows AMD HDR.
Steps To Reproduceget the newest win 11 build and a GPU driver that supports the new WDDM.
play a HDR file with madVR in passthrough.
Additional InformationmpcVR HDR still works by switching the OS HDR on or OFF even with OS HDR on the image does not seem to be 100 % correct.
TagsNo tags attached.
madVR Version92.17 it has TM curves but i dont know the version
Media Player (with version info)mpc-hc
Splitter (with version info)lav 0.74.1
Decoder (with version info)lav 0.74.1
Deinterlacingnone (progressive)
DXVA2 Scaling Activeno
Aero / Desktop CompositionOn
Problem occurs with modefullscreen exclusive mode
GPU ManufacturerAMD
GPU Model5700 XT
GPU Driver Version21.8.1



2021-08-20 11:43

reporter   ~0002820

this is more to let you know. i will keep you updated on this with the upcoming new windows versions. could be fixed in the next version could be the new default behaviour time will tell just a couple more months.


2021-08-20 12:01

administrator   ~0002821

Yeah, Microsoft continues to screw things up more and more with each OS update. That's not really surprising. Hopefully they can get it solved somehow. That said, madVR's DTM is probably the best there is, anyway, so the importance of having HDR output is not as high as it used to be. The latest LG OLEDs support getting full brightness in SDR mode, so there's no need to send them HDR, anymore.


2021-08-20 12:37

reporter   ~0002822

taking my shitty OLED and AMD into account i'm not so sure and the majority doesn't have OLEDs.
because there is no report BT 2020 and such.
not that i care about HDR.

what so ever there is a chance microsoft will do something about this because they broke older HDR games that doesn't use windows OS HDR but AMD and NVIDIA API. there are now games out there that will not be able to send HDR at all. usually they take backwards compatibility kinda serious. HDR games are just a couple of years old. on the other hand just look at 11...


2021-08-20 12:53

administrator   ~0002823

I think it might be more of an AMD driver problem, actually, and less of an OS problem. Because if SDR playback works fine, the OS shouldn't even know (or care) if the AMD/Nvidia private HDR APIs are used or not. So there's a chance that a new AMD driver might fix this.


2021-08-20 16:46

reporter   ~0002824

just for context.
i'm using win 11 dev builds since the release and everything was working fine with the last dev build.
this does not mean i don't update GPU driver too.


2021-10-06 02:35

reporter   ~0002825

win 11 is out now and it still "broken" it outputs an image now but the levels are wrong it not off by 16 levels it'S less but. i don't know
even through there is a new driver the problem was the same it changed with windows version.

currently the AMD API is working at 8 bit and even in windowed (tone mapping and it seems to do a good job...)so .... that'S not supposed to be happening.

there are reports HDR and refreshrate switching broke completely on nvidia.


2021-10-06 11:51

administrator   ~0002826

Might make sense to wait for newer drivers from both AMD and Nvidia. There's not much I can do about this, I fear.


2021-10-06 17:29

reporter   ~0002827

it worked on AMD to wait for new windows versions. it was literally not engaging HDR with older windows versions.

there are some other things that break with madVR that should be related to your code.
the identifications are now stacking up i'm already at 120. it's reported that if more than one device is listed in devices 10 bit doesn't work on nvidia (which is kinda random).

but my first response was also wait for a new driver first and than have a look.
identificationbug.png (104,010 bytes)   
identificationbug.png (104,010 bytes)   


2021-10-06 17:34

administrator   ~0002828

Can you reproduce the IDs stacking up problem? If so, can you zip and upload the settings.bin file with such a flood of IDs inside?


2021-10-06 17:55

reporter   ~0002829

sure and a log. the settings are relative random from testing.
not sure what trigger it i had to switch between tone map and passthrough to relibile add a couple of new idetification to madVR. could be an LG OLED issue too...


2021-10-06 18:01

reporter   ~0002830

there is no error when uploading so i zipped a 7z together with the bin which feels very wrong.
log and (1,650,751 bytes)


2021-10-06 18:08

administrator   ~0002831

That's interesting, some of the IDs are unique, but there are a *LOT* of duplicates in there. That's not really supposed to happen.

Issue History

Date Modified Username Field Change
2021-08-20 11:41 huhn New Issue
2021-08-20 11:43 huhn Note Added: 0002820
2021-08-20 12:01 madshi Note Added: 0002821
2021-08-20 12:37 huhn Note Added: 0002822
2021-08-20 12:53 madshi Note Added: 0002823
2021-08-20 16:46 huhn Note Added: 0002824
2021-10-06 02:35 huhn Note Added: 0002825
2021-10-06 11:51 madshi Note Added: 0002826
2021-10-06 17:29 huhn Note Added: 0002827
2021-10-06 17:29 huhn File Added: identificationbug.png
2021-10-06 17:34 madshi Note Added: 0002828
2021-10-06 17:55 huhn Note Added: 0002829
2021-10-06 18:01 huhn Note Added: 0002830
2021-10-06 18:01 huhn File Added: log and
2021-10-06 18:08 madshi Note Added: 0002831