AMD, Intel and Nvidia driver issues and last recommended version

[angmav]

Originally Posted by Manni

If you have AnyDVD, you can also use setdisplayfrequency.exe from a batch file to change the refresh rate if you want to do it for non-video playback related reasons, or want to force a refresh rate manually.

For example, to change the refresh rate to 23p, here is the line to add in a batch file:

"c:\program files (x86)\Redfox\AnyDVD\setdisplayfrequency.exe" 23

There is a registry setting to extend the delay for the prompt to confirm the display mode change in Windows, but I can't remember what it is. I've extended it because my JVC takes a long time to sync, and I don't have this issue anymore, but can't recall how I did it.

Thank you for all your assistance


Sent from my iPhone using Tapatalk

[biship]

Originally Posted by nevcairiel

To be honest madVR is likely just a bit out of date when it comes to HDR handling. Multiple years of driver and OS HDR development - an area that was never fully fleshed out before, and no madVR updates to speak of.

Yes, it's very sad that he has another project that consumes all his time. I got to think a few days of Visual Studio and he'll fix a couple of the breaking bugs.

[biship]

HDR passthrough with MadVR is still broken in 451.77

[VBB]

And it will keep being broken with every new Nvidia driver, because Nvidia chose to change their API. It works just fine with drivers before 45x.xx

[SamuriHL]

I wouldn't hold out hope for a fix in madvr any time soon. madshi is focused on other things. At MOST we can expect to see some improvements to HDR tone mapping at some point this year. If we're very lucky. He didn't seem interested in this issue at all when it was brought on int he HDR thread. Even though it does impact HDR testing.

[*MidnightWatcher*]

For those you doing HDR to SDR tone mapping @ 8bit with madVR -- v. 451.67 is providing a pretty good 23.976 performance. At 4K, I'm now only seeing at most one dropped frame per movie. This is much better than the dropped/repeated frame every 4 or 12 minutes from the the previous driver I was using.

[Manni]

Originally Posted by *MidnightWatcher*

For those you doing HDR to SDR tone mapping @ 8bit with madVR -- v. 451.67 is providing a pretty good 23.976 performance. At 4K, I'm now only seeing at most one dropped frame per movie. This is much better than the dropped/repeated frame every 4 or 12 minutes from the the previous driver I was using.

Yes but HDR passthrough is still broken.

You can get no dropped frames with CRU and HDR passthrough with an older driver. I use 442.92 to get 12bits support as well (I need it occasionally for testing).

[*MidnightWatcher*]

Originally Posted by Manni

Yes but HDR passthrough is still broken.

You can get no dropped frames with CRU and HDR passthrough with an older driver. I use 442.92 to get 12bits support as well (I need it occasionally for testing).

I was using that one as well and decided to stop using 12bit.

[Manni]

Originally Posted by *MidnightWatcher*

I was using that one as well and decided to stop using 12bit.

Sure, if you don't need HDR passthrough either the latest are fine.

[SamuriHL]

Manni, I don't know if you saw my post about it but these latest drivers aren't passing metadata through even with HDR turned on in Windows. This seems completely broken to me. I currently have the driver installed but will be going back to the latest working studio driver. It's completely frustrating as we're so close to having an almost perfect driver.

[Manni]

Originally Posted by SamuriHL

Manni, I don't know if you saw my post about it but these latest drivers aren't passing metadata through even with HDR turned on in Windows. This seems completely broken to me. I currently have the driver installed but will be going back to the latest working studio driver. It's completely frustrating as we're so close to having an almost perfect driver.

I have but I wasn't saying anything different in my previous post(s).

The latest drivers are broken for HDR passthrough and 12bits, but if you don't need either of these features, I guess nothing stops the OP from using the latest.

I personally prefer to use the older studio drivers that handle both 12bits and HDR passthrough, as I get perfect refresh rate with CRU with these.

Maybe you misread my post, or it wasn't clear?

[SamuriHL]

It wasn't fully clear what "broken" meant. Mainly because you can force the driver to display in HDR, but, without it passing the metadata (which people without an HD Fury may not know about), yes, it's still "broken". I'll be going back to the previous studio driver, as well. I keep hoping they get one of these newer drivers to work with ALL the fun features working. Yes, I could mess with CRU to get better timing, but, who's got time for that?! LMAO

(P.S. I realize it's not clear why I keep trying when I have a working driver. I'm concerned that when I get a 3080TI I'll be forced into a newer driver that supports it...that's my real concern here.)

[Asmodian]

Originally Posted by SamuriHL

I keep hoping they get one of these newer drivers to work with ALL the fun features working.

Are you thinking Nvidia should change back to the HDR technique madVR currently uses? I think we are waiting for a madVR update to fix HDR, not Nvidia.

[SamuriHL]

You're missing the larger point. It doesn't (currently) matter what madvr does or doesn't do. The latest nVidia driver branch is not sending the HDR metadata at all. So even if you enable it using the Windows HDR setting, it doesn't help because the metadata is missing. IOW, this issue is bigger than hoping madshi changes madvr to enable HDR properly.

[SamuriHL]

Just to do some proof of what I'm saying, I enabled Windows HDR and loaded up an HDR mkv in PowerDVD 20 Ultra. As mentioned, no HDR metadata. Dropped back to 442.92 studio driver, all metadata restored, both in madvr hdr output and in PowerDVD + Windows HDR. nVidia broke it. They need to fix it.

[Asmodian]

When was the last update for PowerDVD?

Edit: Hmm, April 2020 was really recent, I wonder if they don't have the clout to get Nvidia to fix things either.

[VBB]

Nvidia didn't break it from their perspective. They simply changed the API, and now software manufacturers have to play catch-up. Kinda messed up to do this without announcing such a change way ahead of time.

[Asmodian]

So we are waiting for the software to update and PowerDVD is simply not up to date either?

That does seem very possible. Hoping for Nvidia to fix it seems like a false hope.

[SamuriHL]

I have my doubts on that theory. Not sending the HDR metadata is a bug we've dealt with before, and it wasn't every program under the sun that had to change. It was nVidia fixing the damn thing. And it took them a LONG time to do it, too. IOW, we've been through this nonsense before with them. So no, I don't buy an "API change that everyone else has to deal with". Enabling HDR in Windows isn't using the nVidia API. And I'm telling you, enabling HDR using the Windows display option does NOT send HDR metadata. What is it that these programs are supposed to do? PowerDVD doesn't use nVidia or AMD's HDR api...they force you to enable it in Windows if you want to use it.

[VBB]

Don't get me wrong. I agree with you that something needs fixing, even if the API change was intentional. But I fear that's something for Mathias to communicate to his Nvidia contacts, once he can figure out what madVR needs to do to comply. I have a feeling Nvidia wants us to use the OS HDR trigger. Probably a push from Microsoft, too.