AMD, Intel and Nvidia driver issues and last recommended version [Archive] - Page 16

zapatista

20th November 2019, 16:41

because i am playing around with down converting some 4k HDR video files to 1080 with madvr , and my current 1080 tv can go up to 350 nits.

iirc early 1080 tv's usually only went up to about 150 - 180 nits , and most standard bluray mastering was (is ?) aimed at this . so with some of the 4k video down scaling to 1080 i am doing now, my next aim is to see if with some HDR files i can get a higher peak white in my 10 bit luma range to my tv.

disclaimer: i have no video expertise, just trying to squeeze a little further video improvement when playing some 4k HDR files

SamuriHL

20th November 2019, 16:47

But the point being your TV knows NOTHING about HDR, so passing correct metadata or not is irrelevant. What you're REALLY looking for is madvr's dynamic tone mapping solution so you can specify a real display nit that matches your tv and allow madvr to tonemap to that.

Klaus1189

20th November 2019, 17:42

why would you care about HDR passthrough if you don't have a HDR device.

if you want the last version with 3D support use that old driver and if not the newest is fine for SDR playback as far as everyone knows.

BTW. 3D is still "possible" with the newest driver but i said that before.

What is exactly possible in 3D with newest drivers and what is not? Is it helpful for users so I should add it in first post?

huhn

20th November 2019, 17:52

every computer game that worked in the past works now too and even new games like outerworlds work in 3D.

i get madVR to trigger 3D on my screen but it doesn't want to output 3D.
my guess only 3d vision works now not the OS 3D implementation. someone claimed 3D movies worked too but i haven't tested in in a long time i don't even have an nvidia card connected to a 3D device anymore.
or in short everything is still present in the GPU driver for 3D the last part is maybe up to madshi again.

the first time a talked about that it got totally ignored so it can't be that important and i personally couldn't care less about 3D every time i tested 3D i did it without glasses because i don't own any.

zapatista

21st November 2019, 03:20

SamuriHL,

thx for the correction, i shall check on that feature

Klaus1189

22nd November 2019, 17:30

Nvidia released 441.20 Game Ready Driver ... again?

huhn

22nd November 2019, 18:08

adding support for a new GPU nothing wrong with that.

Klaus1189

22nd November 2019, 21:20

But why not use Studio driver as basis and add support for the new card. Now there is a newer driver with an older version number. Looks odd nevertheless.

huhn

23rd November 2019, 00:01

you don't want to give a gamer a studio driver.

el Filou

23rd November 2019, 12:12

I'd say it depends on the release timing. The studio driver has the same game support as the last game ready driver released before it (release notes even list the recently added support for games), in addition to support for content creation apps.

huhn

23rd November 2019, 17:55

it's a marketing driver and you don't want to give your gamer only access to a studio driver.

it's doesn't matter what the content of the driver is the is name what matter and how that driver is delivered.
it doesn't matter if it is the same the AVG doesn't doesn't have a clue.

el Filou

26th November 2019, 20:52

Open Issues in Version 441.41 WHQL
Windows 10 Issues
[V-Sync]: V-Sync does not work. [2719115]Wow... :scared:

Klaus1189

26th November 2019, 21:25

I am still waiting for team blue for dedicated graphic cards, next year is gonna to be awesome :D

huhn

26th November 2019, 23:53

where can i take not working v-sync in one game for a working driver. i'm so sold.

nevcairiel

27th November 2019, 00:00

I am still waiting for team blue for dedicated graphic cards, next year is gonna to be awesome :D

Its a shame Intel graphics drivers have also been quite horrible since the beginning of time. :D

hntc255

27th November 2019, 10:05

Klaus1189

27th November 2019, 11:04

ryokoseigo

28th November 2019, 05:11

Hi guys , I am new here and I have a HDR proplem .

1. Play a HDR10 video and go fullscreen.
2. TV will not switch to HDR mode automatically, still SDR.
3. Refresh HDMI (unplug/plug HDMI cable or reboot TV ) , TV can switch to HDR mode.

***********

4. But if I turn the Windows 10 HDR button on , TV will switch to HDR mode automatically , so OS HDR API works well.

So I don't know what is wrong in my case. AMD driver? AMD HDR API? TV? MadVR? or something else.

Does someone has the same proplem?
Any suggestions would be helpful. Thanks!!

I tried many settings but nothing useful.

OS : windows 10 1909
Player : MPC-BE + LAV + MadVR(HDR passthrough)
GPU : AMD RX580
Driver : 19.10.x / 19.11.x RGB 444 8bit
TV : HDMI 2.0 , HDR supported

Exact same issue now after a reinstall of windows. Even using the same madvr files as previous install.

Nvidia- lastest drivers 441.41 and windows 1909, with the same mpc-be and lav setup too.

So confused why this is happening. It's happened to me before, and I don't really know what I did to fix it back then either.

hntc255

29th November 2019, 04:13

What happens when checking "Launch files in fullscreen" in MPC-BE?
I checked and can state that latest 19.11.3 is fine in windowed mode and fullscreen exclusive mode on Win10 1909.

What TV brand and exact model do you use? madVR version?

Thank you first.:p

I tried "Launch files in fullscreen" and exclusive mode , but it is the same.

TV : Toshiba 75u6900c (actually a TCL)
madVR : v0.92.17

all of the software are lastest version.

hntc255

29th November 2019, 04:16

Exact same issue now after a reinstall of windows. Even using the same madvr files as previous install.

Nvidia- lastest drivers 441.41 and windows 1909, with the same mpc-be and lav setup too.

So confused why this is happening. It's happened to me before, and I don't really know what I did to fix it back then either.

So it means that AMD / NV is innocent? :rolleyes:

Klaus1189

29th November 2019, 12:32

Probably a Win10 1909 issue, but only when creating a new fresh insallation?! It is fine here, but I was already on 1903 (did a fresh install back then) and did the update to 1909 via Windows update which was pretty small, so ...

tyguy

1st December 2019, 04:24

On the latest game ready drivers I’ve had issues with elevated blacks in hdr with madvr using ycbcr 422 with TV set to hdmi low black level with lgc9. The blacks are fine for me using rgb full and TV set to hdmi black level high.

huhn

1st December 2019, 05:44

did you change anything else then this output format setting?

Warner306

1st December 2019, 18:12

Hi guys , I am new here and I have a HDR proplem .

1. Play a HDR10 video and go fullscreen.
2. TV will not switch to HDR mode automatically, still SDR.
3. Refresh HDMI (unplug/plug HDMI cable or reboot TV ) , TV can switch to HDR mode.

***********

4. But if I turn the Windows 10 HDR button on , TV will switch to HDR mode automatically , so OS HDR API works well.

So I don't know what is wrong in my case. AMD driver? AMD HDR API? TV? MadVR? or something else.

Does someone has the same proplem?
Any suggestions would be helpful. Thanks!!

I tried many settings but nothing useful.

OS : windows 10 1909
Player : MPC-BE + LAV + MadVR(HDR passthrough)
GPU : AMD RX580
Driver : 19.10.x / 19.11.x RGB 444 8bit
TV : HDMI 2.0 , HDR supported

AMD HDR requires 10-bit output from madVR (D3D11). Did you do that?

tyguy

1st December 2019, 23:34

did you change anything else then this output format setting?

I set madvr to tv levels and also lavfilter video decoder to tv levels.

huhn

1st December 2019, 23:43

first of don't touch the lavfilter setting.

second that's always wrong the PC desktop works in full range.
when a GPU is ask to output YCbCr "whatever" it assumes a full range RGB image as an input and it will turn this into to a limited range YCbCr image that why YCbCr is not recommended as an output.

Asmodian

2nd December 2019, 00:43

I set madvr to tv levels and also lavfilter video decoder to tv levels.

I already (https://forum.doom9.org/showthread.php?p=1891137#post1891137) tried to tell you why that is the wrong setting.

If it sounds like your GPU starts sending limited range when in HDR so you get double compression (elevated blacks and depressed whites) when setting madVR to limited range.

hntc255

2nd December 2019, 01:36

hntc255

2nd December 2019, 01:50

AMD HDR requires 10-bit output from madVR (D3D11). Did you do that?

I tried the color format ycbcr 422 10 bit / 12bit , 420 10bit / 12bit in AMD driver.

And set "the native display bitdepth is '10bit or higher' "

As I say , it works fine after refresh the HDMI , really strange.

:thanks:

Klaus1189

2nd December 2019, 06:15

Other devices do work fine? I can also think of a reset of the TV, because I had strange things occuring on different manufactures after software update of the TV.

Klaus1189

3rd December 2019, 18:56

AMD released new Radeon Driver 19.12.1

Grimsdyke

4th December 2019, 12:35

Does anyone maybe know why the exe-installer of the intel-vga-driver does not work anymore on my system ?? It seem to open but then nothing happens.
So I have to use the zip-version, un-pack, and start the installer within. This works without any problems.
Is Win10-64bit security blocking the normal exe ? But why ? Any ideas ? Thx

Klaus1189

4th December 2019, 13:41

Perhaps corrupted file, check the size of exactly your downloaded file and download another copy again, compare the size of these two. It can happen from time to time, when something went wrong in the data transmission.

ced007

4th December 2019, 18:43

Hi,
I'm not sure to understand correctly the Nvidia table in the first post, I have a 1060 GTX with latest drivers. Is the 398.11 driver the latest version with correct HDR passthrough? Do I need to switch back to it?
Thanks in advance

Klaus1189

4th December 2019, 19:46

Hi ced007, it depends:
If you want to use HDR passthrough for Nvidia and want correct metadata :) you need either 398.11 from 2018-06-05 if you need/want to be able to use 3D or, if you don't need 3D, you can use 430.39 from 2019-04-23 or any newer version than that, preferred the newest for now, since there are no issues, at least I am I am aware of. RTX owners have no choice if they want both 3D and correct metadata, since there is no driver for RTX cards which can do both :(

ced007

4th December 2019, 20:30

Thank you Klaus1189, it helps a lot. I don't need 3D so I stay with the latest version 441.41.

Warner306

5th December 2019, 11:08

You might consider adding this link to the first post. This is a software fix that adds back 3D Vision support to newer Nvidia drivers. I have not tested it myself, but someone at AVS Forums says it works:

http://helixmod.blogspot.com/2017/05/3d-fix-manager.html

Someone here would have to test it.

Klaus1189

5th December 2019, 11:28

I added it, but I had to shorten some things because I used to many characters :eek:
See here (https://drive.google.com/file/d/1Ci43APVR38gUEMAqhDF_cO_SowJEi-DG/view?usp=sharing)

brazen1

5th December 2019, 17:13

I think that software is for gaming 3D only. 416.81 is still a good choice for 3D and HDR imo.

huhn

5th December 2019, 17:33

i already tested the helixmod a couple of months after nvidia removed 3D.
it doesn't work with madVR it only trigger 3d on my screen but doesn't send it and the OS doesn't know about 3D.

it could be used to add 3d back into madVR because all games work but that's it for now.

SamuriHL

11th December 2019, 00:38

New nVidia driver. Doesn't appear to impact HTPC....let's hope it doesn't break anything. LOL

https://www.neowin.net/news/nvidia-44166-whql-driver-delivers-mechwarrior-5-and-detroit-become-human-optimizations

huhn

11th December 2019, 01:04

the new amd driver has a great start: https://abload.de/img/amdriverivkfy.png
that's with disabled overlay.

SamuriHL

11th December 2019, 01:24

I don't think that word means what they think it means. LMAO

mclingo

11th December 2019, 13:30

Klaus1189, is the issue with raised blacks in EVR and incorrect colour space on 5700s worth a mention on your driver page?

Klaus1189

11th December 2019, 17:37

I thought of that already, but since this thread is meant for use with madVR and if you use either madVR or also MPC Video Renderer with D3D11 you don't have this issue. But I can add it if you wish. Just let me know.

mclingo

11th December 2019, 18:17

the EVR is definately affecting all 5700 cards so I'd deinately put that one down. The MADVR issue, even though we are not 100% sure it affects all cards, only one person has come back and said it isnt affecting them and they havent yet given us all their hardware details,I think right now we should assume its all 5700 cards.

- All 5700 series cards have elevated blacks withe EVR renderer: Workaround - use MPC or MADVR renderer.
- All NAVI based cards are outputting an incorrect colour space via the AMD HDR API, colours are greatly unsaturated - workaround; use a filter to correct or use Windows HDR

its your thread though mate, its up to you :) :) :) :)

Klaus1189

11th December 2019, 19:52

Can you give me some info for the affected driver versions? Can you also give me a link for the demo footage video where the sidebyside comparison was made? I want to take a look at the video.

mclingo

11th December 2019, 20:29

Hi, this is a new card, as far as I know both issues affect all driver versions. Not sure which footage you are referring to, I took pictures and mocked one up to try and show what the saturatiuon issue looks like. DMU and ALEXTRAL seem to have more detailed info on the HDR issue.

Klaus1189

11th December 2019, 20:31

Sorry, I missread the username, I want that one:
Perhaps he has an old AMD driver installed - 19.4.3 and earlier.
Picture. (https://drive.google.com/open?id=1KCPGNNIUYrrnvlQ68_l81BSOgaVCxg65)