AMD, Intel and Nvidia driver issues and last recommended version

[el Filou]

I know, but I like variety of content more than perfect quality ;) and some TV channels are often showing old or rare movies that are nowhere to be found on streaming services or Blu-ray.
I use black bar detection only to crop TV logos/age warnings on 2.39:1 content, not for rendering performance. I wish it would work with D3D11 native.

[chros]

Oh, I see, makes sense now.

[mzso]

At long time ago a SmartDVB user reported a bug with madVR where it didn't enable deinterlacing even though it was enabled in settings, even forced it didn't work (I tested and confirmed). Maybe it was you? Anyway maybe that bug still hasn't been fixed.
Yes, it was me, probably. Anyway, I forgot how, but it was fixed on either SmartDVB or madVR's end.
But now I got a newer GPU and and upgraded to Win10, because it's not supported on win 8.1...

Anyway, one big difference is that back then it worked without a problem in media players like Potplayer, MPC, now it doesn't work anywhere.

[claw]

I’ve got a frustrating issue that I’m hoping someone can help me with. I’m running a GTX 1660ti and I’m trying to get working 3D and 4k. I’m really close with the 425.31 driver. The only issue I’ve got is that every time I reboot, my bit depth settings reset back to the default of 8 bit, which on my projector makes everything go magenta. If I set the bit depth to 12 bit at 24hz, it’ll switch back and forth correctly between 24/60hz and 8/12bit, but on reboot I have to reset those bit depths again. Is there a solution to this? Was this a common issue with earlier drivers? The bit depth is persistent on the newer drivers, but then 3d doesn’t work.

I use driver 436.48 as I have had no reason to update it.

I have a JVC projector and initially set the 2080Ti to output RGB 12-bit due to the Magenta bug.

I only had issues with retaining 12-bit on restart if I set the desktop to 4K59. I changed it to 4K23 and no longer had any issue with 12-bit reverting to 8-bit.

I also use a CRU custom resolution but I doubt that had anything to do with it.

I recently switched to RGB 8-bit and disabled Report BT2020 to display in MadVR. Reporting BT2020 also includes HDR metadata and that is what triggers the Magenta bug.

So I manually change picture mode in my JVC to one that is set up for SDR BT2020 for MadVR output.

I don't do 3D.

[angmav]

Hi Does anyone know how to delay the refresh rate change time for nvidia as I don’t have enough time for me to pick yes from the time it takes for my projector to handshake screen very annoying I run a team view screen and accept change that way there must be a setting I can change to delay timeout change many assistance would be greatly appreciated


Sent from my iPhone using Tapatalk

[huhn]

you can use a different program to change the refreshrate with madVR it's just doen't with no questions asked.

out of memory you could just use arrow key left enter.

[RXP]

Set up a dedicated HTPC which uses last recommended driver regarding madVR. Don‘t need to be highend hardware. Just take a look at 3300X. Not expensive and should be enough.

Use a dedicated gaming PC for gaming and always use latest GRD.

I dual boot my projection setup.

I need to keep the last 3D drivers and everything stable for the projector. So it has. Then my other boot is the latest drivers.

[angmav]

you can use a different program to change the refreshrate with madVR it's just doen't with no questions asked.

out of memory you could just use arrow key left enter.


Thanks what program do you recommend ?


Sent from my iPhone using Tapatalk

[huhn]

well madVR.

just set the device to 60 HZ and when madVR plays a file it will change the refreshrate and when it stops it's back to 60 hz.

if you need thsi for something not related to movie playback there are other tools but i never used one of these.

[Manni]

Thanks what program do you recommend ?


Sent from my iPhone using Tapatalk

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.

[angmav]

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]

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]

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*]

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]

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]

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". :D 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]

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.

[SamuriHL]

Which you can do manually. I've tried it and while it did trigger hdr output without the metadata the display is likely aggressively tone mapping it. And in fact if you do the trick where you start the video, stop it, and play again to get it to trigger hdr, you'll see that the windows hdr setting in display properties is enabled.

Sent from my SM-G975U using Tapatalk

[brazen1]

@brazen1: I think I read somewhere that there is a new Audio driver version in recent Nvidia drivers, does that fix this issue?
https://forum.doom9.org/showpost.php?p=1913991&postcount=1319

451.67 another complete waste of time. 12bit still doesn't retain after a reboot. Windows + nVidia audio coordination still broken.

Despite reports of fewer frame drops, nothing has changed for me. Same ol', same ol' drop every 4.5 mins.

NV HDR does activate (as usual) at first attempt despite reports claiming to have to restart the video.

I don't know who these driver 'improvements' are aimed at but it must be a very narrow specific group because all they do for me is make things worse and waste my time.

Back to 445.87 using 388.59 audio driver.

[Klaus1189]

Despite reports of fewer frame drops, nothing has changed for me. Same ol', same ol' drop every 4.5 mins.

yes madshi got a bug report through with this and they fixed it.

the refreshrate is supposed to be closer now with 1080p23 (for a while now) and now with 2160 23 now too with this driver or up coming ones.

looks like they have to fix this with every signle refreshrate and connector type...

just took them like a decade and it doesn't fix the core issue anyway.

edit: i just test my 1060 i have no frame repeat/drop expected ever with analog audio output so very lucky.
can a couple you guys test digital hdmi/DP over the same card that the only space where nvidia has any way to affect the audio clock?
i tested 451.77 studio.

edit2: can you plz check 119? if you have the time for 1440p and 2160p DP/HDMI if available.
i will try to check 1080p119 my TV doesn't support 1440 for some reason.
edit3: 1080p119 is working too.


Can you two please test it again, just to be sure that no CRU settings can create false results. HDR stuff beside. How is the 23 Hz refresh rate out of the box?
I am really interested in that. Thanks in advance ;)

[huhn]

with overlay rendering it'S 23.7617.

just as before not that important the important part comes now. i currently get a repeated frame every 10- unlimted hours room is at 34 degrees currently i'm using analog audio output using a realtek onboard audio card. if i get one of my "good" sounds card back in the system and i have the "newest" soundblaster and a asus essence STX here(and to many more rubbish cards i'm not willing to list here...) i would be shocked if i'm back to something like 20 mins or so.

i never really used CRU i had a panasonic TV there was no point in using it... my TV is still new so every custom refreshrate would be deleted anyway.

i will later try HDMI output with my sony it may have a properly working analog output unlike my panasonic which again is by design not working "properly" and everything can beat a PC DAC too so possible win win.

edit: HDMI digital is 1 h for me absolutely useless

[brazen1]

I wasn't and never have used CRU. I also always use digital HDMI provided by nVidia drivers and not analog DIN output with add-on audio cards. I tested a few HDR titles using passthrough matching refresh rates @23Hz. I didn't even bother to test SDR and I'm not going to. I didn't take note of the exact refresh rate before I reinstalled working drivers.

Using the combo I posted, for SDR and HDR at 23Hz through 60Hz... I have zero problems except a frame drop every 4.5 mins. All audio types work like they're supposed to and audio is produced automatically from display speakers and/or AVR speakers per ON/OFF state of AVR. 12bit retains after reboot. I get no banding introduced using my Q90R and I (think) colors pop more. NV HDR is used when it should be and O/S HDR is used when it should be (automatically). The only reason I even attempt new drivers is to simplify the audio workaround and this time was only because folks are jumping for joy about no more frame drops... which might be great for analog DAC users but 99% of us carry audio over HDMI digitally.

[huhn]

theses fixes are mostly for digital user.
the clock generator for audio and video could and even should be the same if only 1 HDMI out is used.

[brazen1]

theses fixes are mostly for digital user.


Not this one.

3D was fixed alright.
Auto switching between display vs AVR audio was fixed wonderfully too.
Offering 10bit RGB output is another ignore and sweep under the carpet adventure.
A frame drop every 4.5 mins remains. This is the latest fix.
Retaining 12bit so we could dither to 10bit after a reboot was a beauty of a fix also.
I can't even remember all the other fixes.

Hey we did get an API for software devs to utilize though! And after months of trial and error it finally switched HDR on and off. That was a nice bone tossed to us. Other than that, I can't think of a single fix that did me any good tbh. Gamers might be jumping for joy though... except I don't play games and never will.

[huhn]

you are missing the point. because it works for me it doesn't mean it will do anything for anyone else. i wanted to make that as clear as possible by stating i'm using analog and that's i'm lucky and the digital HDMI user should check this better out in detail.

nvidia has no clue and no affect on the clock of any sound card that is not there own digital output. so the only generally thing user could test on the fast is if this change did anything is the shown refresh rate using studio driver 451.77.

if you really care about motion this is the biggest upgrade you could get (you should use CRU if you really care about motion but what ever).

if it doesn't work for you you should say so because madshi is still in contact about this topic.

[brazen1]

I am a digital user and I have checked it out and I am passing on my observations. I have no motion problems that needs CRU to cure because I'm not using an OLED that has motion problems to begin with. Just one single dropped frame every 4.5 mins which I don't consider a motion problem beyond the 5ms it lasts. I don't think I'm missing any point? Fwiw, I'm not referring to your posts about your observations specifically. I'm actually referring to another person on another forum stating the latest driver 'fixed' the frame drop problem. It didn't for me. I don't know what that person could be doing different. You stated you are using analog with good results. That's a difference. Unfortunately, I could care less about analog improvements and as you and I both stated, HDMI might be a completely different outcome and my quick testing resulted in exactly that.

[huhn]

well you have a major motion issue every 4.5 mins. if you don't notice well fine but that doesn't mean it's not there.

1080p is been fixed for a long long time now this should count for 3D too.

i have no clue why you would take OLED or what ever tech into this dicussion why have nothing todo with this all technologies suffer the same under this because they get a flawed signal that can not be fixed.


why would a gamer or a game ever care they work totally different this change is only for video playback 23p is only for video playback.

ok i will report to madshi that nvidia fix doesn't work. neither the reported frame rate nor the dropped repeated frames changed what so ever correct?

edit: because you edit it is 42 ms just saying and no frame interpolation doesn't change that 42 MS of information are missing by a drop and 42 ms of information are repeated for a repeat.

[brazen1]

Oh, I notice it but it doesn't bother me enough to strive for a cure. If nVidia provides one great otherwise I'm not messing with CRU, custom timings, or anything else. It was fun at one point but I've lost interest. I didn't test 1080p only 2160p. I don't use 3D anymore so I will not be testing anything to do with it. I brought up gaming fixes because that is the only thing ever listed in detail about driver updates. Mostly the actual names of specific games and the actual improvements for them. I don't see too much of anything listed as addressing HTPC users though. However, I am glad madshi has been and continues to be a voice for the HTPC community and gets results. That said, before you report my findings to him... take account of others too. I only tested enough to know I was never going to keep and use it. I never even thought about repeated frames being interpolated or not. Interesting.

[Klaus1189]

Very informative. I am interested in audio over HDMI to AVR, so 23 Hz will get about 10 hours+ with no framedrop/repeat out of the box.
@huhn: please let madshi know that it doesn't work now with HDMI. Nvidia has to do some more tweaking.

[nevcairiel]

@huhn: please let madshi know that it doesn't work now with HDMI. Nvidia has to do some more tweaking.

Did you actually confirm this yourself, or just repeating what others said? Because only one of those is useful. :)

[Klaus1189]

I can not test this, because I don't have a Nvidia card here at the moment and both huhn and brazen1 are very reliable, they are not average users.

Perhaps you can test this and contribute to this issue?

[huhn]

so we have 1 test with numbers under terrible conditions (which is on par with my AMD results i'm used to) and one report of doesn't work with no numbers.

i don't know what to say anymore.

[Asmodian]

Would a test with HDMI and an on-motherboard digital or analog audio out be useful?

[huhn]

audio output with the same card is interesting the rest is all gambling because there is just a different clock generator.

[Klaus1189]

Then I must apologize. I think I missunderstood the hole thing. Please use easy words for a dummy like me :o
I want to buy an ampere card soon and when I read through the threads here I came across the news of better 23 Hz timings out of the box for new drivers and madshi is still in contact with a guy of Nvidia.

I have at the moment no Nvidia card to test, so I have to rely on user feedback here.
Please answer the following question, so a silly guy like me can understand that, too:
1.) What driver version (exact version) is supposed to have better out of the boxed 23 Hz timings?
2.) Are there more than one now?
3.) To what audio outputs does that apply?
4.) I am only interested in HDMI audio. Does that have better dropped/repeated frames?

I kindly ask you guys who have a Nvidia card: Please post a screenshot of madVR stats with the new driver, so I can clearly see the better timings out of the box without CRU and possible other stuff.

[Klaus1189]

HDMI digital is 1 h for me absolutely useless

if it doesn't work for you you should say so because madshi is still in contact about this topic.

These are some of the parts that led me to ask this. So 1 hour is definitely to short in my opinion, but hey what do yI know. Perhaps I misread it also. But as always I want to learn and improve my knowledge.

[huhn]

because i have 1 H doesn't mean you will have 1 H.