madshi bug tracker - madVR
View Issue Details
0000585madVRbugpublic2018-11-21 20:072019-11-25 08:13
92.17 (probably any version that supports HDR)
Zoomplayer 14
DXVA2 Copyback
none (progressive)
all modes
GTX 1060, 1070
0000585: Cannot activate HDR via DisplayPort
I have a problem with activating HDR via DisplayPort. This is with a LG 34BK95U - 5120x2160 which requires DP 1.4 to get the full width. HDMI (which limits it to 3840 width) works fine.

Basically, it seems that madVR does not recognize that HDR is supported via DP, and thus always does tonemap HDR instead. (And I HAVE checked that HDR can be activated otherwise via DP.)
It only occurs with the above monitor (or probably with the 34WK95U which is identical) and only on the Displayport (1.4). Other than that, just play a HDR file with "passthrough HDR to display" set and "send HDR metadata to the display" checked and note that the HDR indicator does not appear and that the resulting image is from "tonemap HDR ..." instead.

I've included a log.

It may or may not be related, but the "identification" for this monitor is wrong, e.g. it shows NVIDIA for the manufacturer (among other things). (Again, this is only on the DisplayPort 1.4 input to this monitor - the HDMI input is fine and DisplayPort (1.2) inputs on other LG monitors are fine.) And Moninfo shows correct data for this DP 1.4 input.

Even stranger, additional identical identification entries keep getting added, always 2 at a time (but I don't know what triggers it). The data is identical for all, with all but the last grayed out. (I'm currently at 23 entries.)
No tags attached.
zip madVR - (389,651) 2018-11-21 20:07
png Untitled.png (115,761) 2019-08-22 04:29
Issue History
2018-11-21 20:07jmonierNew Issue
2018-11-21 20:07jmonierFile Added: madVR -
2018-11-21 20:15jmonierNote Added: 0002441
2018-12-04 19:37madshiNote Added: 0002443
2018-12-04 19:37madshiAssigned To => madshi
2018-12-04 19:37madshiStatusnew => assigned
2019-01-15 13:20jmonierNote Added: 0002471
2019-01-16 04:49DreamfallNote Added: 0002472
2019-01-16 14:49jmonierNote Added: 0002474
2019-01-16 15:08jmonierNote Edited: 0002474bug_revision_view_page.php?bugnote_id=2474#r553
2019-01-16 15:10jmonierNote Edited: 0002474bug_revision_view_page.php?bugnote_id=2474#r554
2019-08-22 04:29zaockleNote Added: 0002542
2019-08-22 04:29zaockleFile Added: Untitled.png
2019-08-22 04:32zaockleNote Edited: 0002542bug_revision_view_page.php?bugnote_id=2542#r588
2019-11-25 08:13zaockleNote Added: 0002582

2018-11-21 20:15   
For some reason, OS data did not appear. The problem occurs on both Win 8.1 and 10.
2018-12-04 19:37   
That's really weird. I'll have to create a special build to collect more information, when I find some time...
2019-01-15 13:20   
Note that another user has reported (on Doom) what seems like exactly the same problem.
2019-01-16 04:49   
I have exactly the same problem. It seems that there's something wrong with NVIDIA driver 416.94 or above, 416.81 is the last working driver version. MadVR said my display does not support HDR after I upgrade to 417.22, after rolling back to 416.81 everything works fine.

Here's a thread I found in NVIDIA forum, maybe it's helpful: [^]
2019-01-16 14:49   
(edited on: 2019-01-16 15:10)
The problem reported directly above is NOT "exactly" the same problem as originally reported. On Win 8.1, the problem originally reported still exists with the Win 8.1 416.81 driver. I have not tested Win 10 with the 416.81 driver since I mostly use Win 8.1, although I previously tested it on Win 10 with more recent drivers.

Also, my problem is unique to to the Displayport connection on the 34WK/BK95 monitor. The HDMI port on this monitor is fine. I don't have any other monitor with both HDR and a Displayport so I don't know about any other monitor.

Information on the monitor used and whether it is on a Displayport would be very helpful.

2019-08-22 04:29   
(edited on: 2019-08-22 04:32)
I am also having this exact same issue with an LG monitor (34GK950F). I haven't tried an HDMI connection, but it might behave like the others have reported. What's interesting that I'll add is that if I turn on the OS HDR, madVR WILL properly force output back to SDR when fullscreen with no context menu's open. But it won't work in reverse. Currently running studio driver 431.70 on a 2070S, LAV using CUVID, MPC-HC 1.8.7. Adding a screenshot.

2019-11-25 08:13   
Just following up, I was actually able to resolve this. I had to run DDU in safe mode a couple times in a row to completely remove all old drivers and monitor registry entries. Afterwards I installed the latest driver (441.28 studio) and it seems like madvr can read the EDID correctly now showing LG instead of NVIDIA as the manufacturer. it can aslo activate HDR from Win10 SDR mode when opening an HDR video.