AMD, Intel and Nvidia driver issues and last recommended version

[oldpainlesskodi]

@DMU - thanks for your effort and trying, it's appreciated.

[chros]

Originally Posted by DMU

It’s better to add an executable file to the HDR madVR profile that will activate the BT.2020 color space on TV and set the most common metadata for movies. For example, MDL = 1000, etc. I can do this if you want.

Originally Posted by DMU

Link.

Be aware that (at least) LG responds differently to different hdr metadata values.
At least 2018 models works best with MDL and maxCLL 700 and setting this value in madvr with hdr output and pixelshader tonemapping. In 2019 models the peak can be set via a util but defaulting to 700 as well, other brands need to be tested.

[mclingo]

madshi has resurfaced on the tone mapping thread, have a look at this response to a query, do you think this could help with the 5700 BT2020 issue?


question :

We wanted to test the 112b beta on a JVC Z1 laser beamer with AMD Fluid Motion frame interpolation.

Unfortunately the Blusky Frame Converter or the ne AMD driver does not support BT.2020 anymore. So madvr shows REC.709. Is there a way to force madvr to recognize BT.2020 ?

answer:


You can use file name tagging like "movie [hdr=on, matrix=2020, primaries=2020].mkv", if that helps?

[el Filou]

I think that's a workaround for when madVR can't detect the correct input metadata (in this case because an intermediate filter strips/changes it).
In the case of the AMD issue, madVR is well aware of the correct input metadata but it's the output to the display that is incorrectly flagged.

[mclingo]

thanks for the explanation....lol, is my desperation to get this fixed showing

[el Filou]

I've seen you've posted on AMD forums about this, but have you or DMU tried using this form: https://www.amd.com/en/support/contact-email-form to file an official bug report?
NVIDIA has an official form to report bugs, but this is the closest thing I've found on AMD's site.

[huhn]

i called them "doesn't sound important" was pretty much the answer.

if you do such a thing do it technically don't make screenshots.

beware they are getting flooded right now.
https://www.youtube.com/watch?v=pboDbxogSw4
wrong meta data is nothing compared to a crashing driver.

BTW: https://www.amd.com/en/support/kb/re...rad-win-20-1-1

Some Radeon RX 5700 series graphics users may intermittently experience a black screen while gaming or on desktop. A potential temporary workaround is disabling hardware acceleration in applications running in the background such as web browsers or Discord.

[DMU]

Originally Posted by el Filou

I've seen you've posted on AMD forums about this, but have you or DMU tried using this form: https://www.amd.com/en/support/contact-email-form to file an official bug report?
NVIDIA has an official form to report bugs, but this is the closest thing I've found on AMD's site.

I am not sure this is a issue. Perhaps they (AMD) believe that they are doing everything right. I asked them a question here, but they are silent.
I am confused by the fact that the Polaris GPU's (RX series) send the correct flag on TV.
huhn is right, they now have a lot of reports from gamers.

[mclingo]

ive logged two faults with AMD, a second time only because i didnt hear anything, still silence. I've logged it a couple of times on their forum as well.

[claw]

I found that the current Nvidia 441.87 DCH driver for Windows 10 seems to have possible performance issues compared to earlier versions when running MadVR Tone mapping with high settings.

I was using the 436.48 Windows 7/8 driver with good render times in MadVR of 28-30 ms with a RTX 2080 Super. This was with my old Windows 8.1 build.

I upgraded my PC with new Z390 motherboard, CPU, SSD, and DDR4 memory and installed Windows 10 Pro. I let GeForce Experience install the current 441.87 driver. My MadVR render times shot up to 40 ms and higher resulting in stutter due to dropped and repeated frames.

Reinstalled Windows 10 and this time manually downloaded and installed the 436.48 DCH driver. MadVR render times are now 30-32 ms instead of 40+. GPU utilization also dropped from 95% to 88%.

[WuNgUn]

Interesting.... Thanks for the feedback.

[ryrynz]

Probably due to power profile and not the actual driver performance.

[VBB]

@claw - In both cases, did you make sure to switch the Nvidia Performance option from "Optimal" to "Adaptive"?

LOL @ryrynz just beat me to it by a few seconds

[claw]

Originally Posted by VBB

@claw - In both cases, did you make sure to switch the Nvidia Performance option from "Optimal" to "Adaptive"?

LOL @ryrynz just beat me to it by a few seconds

No, I did not. I did not know this was recommended. I will check on this tomorrow.

[mclingo]

I've tried a different workaround for HDR, I'm finding I much prefer the tone mapped with HDR rather than to SDR, so i've calibrated one of my presets to correct the colour issues, essentially I found that wacking up the saturation and adding a little red got my movies looking normal again, obviously this is a super dirty workaround but I much prefer it to using crappy windows HDR without tone mapping or tone mapping to SDR.

pretty happy with the results.

[el Filou]

So you mean if you enable HDR via Windows, madVR can't tone map and output HDR? What happens if you check the output HDR box while you already enabled HDR in Windows, madVR tries to change the display mode again via the private API?

[mclingo]

Hi, no I dont think it works llike that, thats the first thing i tried, you just get a washed out image like MADVR is sending SDR instead of HDR. I'll try it again with 113 in case anything has changed,

[mclingo]

it could be user error but this works now as long as I still use output as HDR, thats great as I dont need a workround now as I can turn on HDR from a shortcut from my remote.

[oldpainlesskodi]

Can I ask how you do that?

[mclingo]

which bit mate, tooggling HDR/OFF on or MADVR setup?