AMD, Intel and Nvidia driver issues and last recommended version

[mclingo]

A bit off topic, l]

indeed this is the TV we've all been waiting for, it looks like its going to be available in 4k 75 inches but it will be silly money until they can sort out the fab as each LED has to be laid down individually, I fear these will always be out of 99.99% of peoples price range.

My guess is the 75inch will be at least 10,000

[NoTechi]

Still no success after a fresh install to get 3D mvc working :scared:

I did a windows 10 reset (all drivers and apps deinstalled)

I freshly installed (and nothing else):
amd driver (19.12.3)
lav filter (0.74.1)
madvr (did a fresh install with latest released and updated to latest beta with default settings)
mpc-be (1.5.4)
in this order and just changed some settings for 3d playback with no success.

My settings (in German but should be self explaining):
AMD display settings (https://ibb.co/RNTsNV3)
AMD graphic settings (https://ibb.co/L9djWnn)
AMD advanced graphic settings (https://ibb.co/7b2PB9m)
LAV Video Settings (https://ibb.co/y6qQ0Fq)
LAV Video Formats (https://ibb.co/YPvbx6j)
madvr display properties (https://ibb.co/2Py6yBx)
madvr stereo 3d settings (https://ibb.co/YhQbPsc)
madvr general settings fullscreen (https://ibb.co/hWQvPDr)
madvr display modes - default no display modes listed as test (https://ibb.co/4tHJ6q2)
mpc settings - external filter (https://ibb.co/tB9mcpN)
mpc settings - external filter priority (https://ibb.co/kqhTfTF)
mpc settings - video renderer (https://ibb.co/56Lk52p)
mpc settings - fullscreen (https://ibb.co/nRmGd5b)
Windows 10 display resolution (https://ibb.co/4sWkHcM)
Windows 10 display refresh rate (https://ibb.co/WznVyWG)
madvr info playing kodi mvc iso sample (https://ibb.co/TTK3JDv)
madvr info playing mclingo sample mvc mkv (https://ibb.co/Y7wbzpz)

I hope I just overlooked some detail setting somewhere but to be honest I really run out of ideas. If someone has an idea what else I could try let me know.

Well as long as I get 3D mvc running before the new Samsung Video wall is available all is fine :p

NoTechi

Kodi 3D test clips (https://kodi.wiki/view/Samples#3D_Test_Clips)

[mclingo]

Hi, the 3D toggle should be off in windows, this can sometime cause it you need to let MADVR toggle it, also, coming to this conversation later have I missed that you are using two displays and also splitting processing over two graphics cards or something, can you post you full hardware chain details, it has to something simple.

[NoTechi]

Just unchecked the 3D (was just on to kinda force it anyhow I never had it on with my nvidia and madvr did always handle it). No difference with it unchecked so.

I don't have the second display connected since I installed the amd gpu. So my current hardware chain is pretty straight forward:
AMD RX 5700 XT --> AVR Marantz 7011 --> JVC X7900

Isn't it kinda strange that madvr is reporting:
h264, 8bit, 4.2.0 -> NV12,8bit,4.2.0 (DXVA2)

NoTechi

Edit: Oh and I deactivated the internal intel gpu within the bios so I don't have any intel drivers installed

[NoTechi]

OMG I found it!!!!! And I am not sure if I should tell you since this is soooooo stupid but at least I got a nice freshly installed windows now and got my 3D back!!!

So my mistake was that within mpc setup with external filters I did not set the external lav filters to "prefarable" ... in other words they never got used .... :p I have no clue why this changed in my windows setup before the fresh install but it deffinitly cost me some time and nervs :P

Sorry for poluting this thread a bit with my 3D/driver stuff ..... I am back to watching movies now ... finally :P

Many thanks mclingo and huhn for brainstorming with me :thanks:

NoTechi

[mclingo]

haha, done that myself plenty of times, glad its all working, thats the main thing :)

[chros]

My guess is the 75inch will be at least 10,000
Way more! More like 30k at least, let's have bet :)
Here's a guy who bought The Wall (https://www.avsforum.com/forum/86-ultra-hi-end-ht-gear-20-000/3093044-samsung-wall-owners-thread-2019-a.html#post58650524) ("last year" model) 3 months ago, 146" = $400k :D

[huhn]

the sony 1080p microled cost 250000.

so yeah good luck.

[nevcairiel]

the sony 1080p microled cost 250000.

so yeah good luck.

It won't be quite that expensive anymore, the technology improved drastically, but it'll still be expensive, 5 digits for sure, but probably not 6 unless you get to the real big sizes.

[huhn]

not even 6 months:
https://www.youtube.com/watch?v=YaChI1WNG2M

not saying it not going to be cheaper.
that's the price of the small one (technically you can make them smaller but that would be sub 1080p)

[mclingo]

i'd seriously think about getting a loan and paying 10k for 75 inch as long as it was 4k as it would essentially be the last TV I would ever need to buy assuming it never breaks down...I fear we are a long way off that still. :)

[chros]

i'd seriously think about getting a loan and paying 10k for 75 inch as long as it was 4k as it would essentially be the last TV I would ever need to buy assuming it never breaks down...I fear we are a long way off that still. :)
:D :D :D Yeah, with 1 year warranty in the UK :D

[el Filou]

as it would essentially be the last TV I would ever need to buyIt wouldn't. Displays always keep progressing (currently the next step will be covering more and more of the BT.2020 colour space), so even such a model would feel old at some point.

[mclingo]

this is true but I cant see a percentage bump in colour space feeling necessary at all as it would only effect a tiny amount of my current collection, i'd only replace if they then came out with a 3D MLED TV.

[Asmodian]

Give them 5 years though.. OLED has some time left but building a major new factory might be a bad idea. I like my OLEDs but micro LEDs looks really nice. Some amazing breakthroughs make me much more hopeful we will seem them affordable pretty soon instead of the far future.

The 48" 2020 OLED might be my last OLED. :D

[huhn]

the sony micro led is an oled.
https://pro.sony/s3/2019/01/17001755/4692870152.pdf

Defective pixels
The panel fitted to this unit is manufactured with high
precision technology, giving a functioning pixel ratio of at
least 99.99%. Thus a very small proportion of pixels may
be “stuck,” either always off (black), always on (red, green,
or blue), or flashing. In addition, such “stuck” pixels may
appear spontaneously over a long period of use due to the
physical characteristics of the organic light-emitting
diodes.
Such occurrences do not indicate a malfunction.

[oldpainlesskodi]

AMD 20.1.1 driver is out, mentions HDR washed out colours fix in the changelog, but the BT2020 issue is still present using the private API in MadVR on the RX 5700 XT. Win HDR Toggle working fine.

[NoTechi]

Did AMD remove support for Bluesky Fluid Motion on new cards?
I tried to activate it following this (https://bluesky23.yukishigure.com/en/bfrc/howto/FluidMotion.html) but in advanced I can just adjust brightness on my 5700 XT.
They are mentioning a "Bluesky FRC Utility" to activate it, but I cannot find it and if it is not supported directly within AMD drivers this sounds like a new potential risk to ruin my setup :P

NoTechi

[oldpainlesskodi]

Not sure. It wasn't there by default, but I used this utility to add it back in https://forums.guru3d.com/threads/radeonmod-tweak-utility.403389/ - available in the tweaks tab.

[NoTechi]

Not sure. It wasn't there by default, but I used this utility to add it back in https://forums.guru3d.com/threads/radeonmod-tweak-utility.403389/ - available in the tweaks tab.

Thanks ... are you using fluid motion with your 5700XT?

NoTechi

[huhn]

DXVA2 is still limited range.

[oldpainlesskodi]

@NoTechi - no, as I use refresh rate matching.

@Huhn - can you explain what you mean, just so I am clear? Many thanks.

[mclingo]

AMD 20.1.1 driver is out, mentions HDR washed out colours fix in the changelog, but the BT2020 issue is still present using the private API in MadVR on the RX 5700 XT. Win HDR Toggle working fine.

heartbreaking, when I read your first few words I got really excited, its clear we really need MADSHI to look at this, i've logged a bug but no reply as yet, still showing as "new"

[oldpainlesskodi]

Yeah, I guess there are 3 possibilities now at this stage.

1 - design flaw in the card
2 - AMD thought they fixed the issue
3 - the AMD API has changed.

My money is on 3, but who knows.

[el Filou]

Using Windows' own HDR switch correctly signals BT.2020, so it's not a design flaw in the card. And if using the same API function successfully results in signalling BT.2020 with older cards and the problem only happens with the 5700 series, then it means it's either a bug in madVR or a bug in the 5700-specific code in AMD's driver (my bet).
I've had a quick look in the AGS documentation on github, here's the struct to pass for the function to set the display mode:
https://gpuopen-librariesandsdks.github.io/ags/struct_a_g_s_display_settings.html
And here's the 'flags' parameter, which just has an option to disable local dimming: https://gpuopen-librariesandsdks.github.io/ags/amd__ags_8h.html#a6abe17185f4f06f30f1b6d26566d74a9
So it looks like you have to pass the colour space coordinates.
Either madVR doesn't pass the correct coordinates for BT.2020 only for the 5700 (I fail to see why it would do that, can be checked with a debugger maybe?), or it's an AMD bug where the 5700-specific code in the driver fails to send the BT.2020 signalling when this function is called with the corresponding coordinates.

[huhn]

is no secret the new API version uses a new syntax so yes they change something.
so updating is a lot of work.

i'm doing with every version a fast DXVA2 check before it test the hard to test issues if they didn't fix this very obvious major bug i just don't waste my time on it anymore.

DXVA2 outputs limited range madVR doesn't fall for that (it most likely ask for limited).

[el Filou]

Where's the new syntax? The official changelog doesn't mention anything https://github.com/GPUOpen-LibrariesAndSDKs/AGS_SDK/blob/master/CHANGELOG.md The documentation which I linked to says they just added new elements to the enum over time as support for new HDR modes was added, but doesn't say anything about different syntaxes or functions. Do you mean AMD is as bad at documentation as they are at coding drivers? :D ;)

Oh well I don't care much, it was just to point to a possible troubleshooting path.

[huhn]

Breaking API change for DX11 extensions
You now call agsDriverExtensionsDX11_CreateDevice() at creation time to access any DX11 AMD extensions

https://github.com/GPUOpen-LibrariesAndSDKs/AGS_SDK/releases/tag/v5.1.1

[DMU]

Guys, I described everything here (https://github.com/GPUOpen-LibrariesAndSDKs/AGS_SDK/issues/33).
Tested using HDFury.

[mclingo]

Guys, I described everything here (https://github.com/GPUOpen-LibrariesAndSDKs/AGS_SDK/issues/33).
Tested using HDFury.

DMU, i also passed that info onto MADSHI on the bug report I created, I'm sure MADSHI will know exactly what it is when he has time to look at it.

http://bugs.madshi.net/view.php?id=630


Feel free to add any comments everyone, pretty sure i've probably explained this really poorly when I logged it.

[DMU]

Madshi has everything to fix this issue if AMD does not solve it. There is a software solution. We just need to be patient.

[oldpainlesskodi]

Guess we just have to sit on our hands then until Madshi is ready to surface again.

Slightly impatiently waiting lol......

[huhn]

so where did you test NAVI because NAVI is the only GPU with this issue?

[el Filou]

https://github.com/GPUOpen-LibrariesAndSDKs/AGS_SDK/releases/tag/v5.1.1
- This change dates back to more than two years. It would have broken all cards, not just 5700 (which obviously didn't even exist)
- The function for switching display to HDR is under category 'General API functions', not DirectX Extensions : https://gpuopen-librariesandsdks.github.io/ags/modules.html

[huhn]

seriously... no if a game ships with AGS 5.0.6 and it is not updated it stays with that version and it will use code from this version.

do you really think they can force every developer to update AGS?
the version madVR uses is 5.0.6 and you still get an image so it still works.

i mean when nothing changed then it has to work so feel free to up date AGS in madVR but you will not get an image.

[el Filou]

Well that's perfect as I wasn't talking about updating anything! In fact I think it's just a bug in AMD's driver.

[huhn]

works with POLARIS doesn't work with NAVI.
yes can't agree more.

[mclingo]

ive been contacted by someone on the KODI forum who tells me the new driver fixed this issue for them, I cant see how it could have given what we know, however, I've asked them to post it here so we can find out what kit they have etc in case there is something we all have in common other than an AMD card that he doesnt have.

[oldpainlesskodi]

At this stage any info is welcome. Navi bug, Madvr issue - who knows.

[DMU]

I would say that this is a feature of AMD private API (AGS) and their drivers. Especially they did it or made a mistake, only AMD can answer.

[oldpainlesskodi]

Could be, but I don't know why the WIN HDR toggle displays everything correctly vs the MadVR API.

[mclingo]

MADSHI should really have a windows API HDR switch as a fall back for these kind of situations, it used to have one but doesnt work, I think we've already discussed that, I wonder why it didnt work?

[DMU]

@oldpainlesskodi
Perhaps because Windows communicates directly with the AMD driver kernel.

@mclingo
It works now.
The idea is to activate the BT.2020 flag with WinAPI, and send the correct metadata to the TV using AMD private API (AGS).

[oldpainlesskodi]

@ DMU - makes sense.

[mclingo]

has anyone tried applying alexkrals shader fix to DSplayer, it works perfectly with MPC-hc player and can be toggled off and on easily, this would be a decent workaround if we could also set a rule for its use only with HDR movies, i had a go but just got totally lost, there are instructions but i just couldnt get it to work, the process seemed simply enoough but it just didnt work for me.

[DMU]

@mclingo
Using a shader is not a good idea. Since it converts the DCI-P3 color space to the BT.709. 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.

[oldpainlesskodi]

"I can do this if you want"?

Do you have a reliable way of doing that?

[mclingo]

mine is a first gen HDR oled, to be honest the BT2020 coverage is pretty low anyway so converting to BT.709, I probably wont be able to see any difference. However, I think we'd probably all like to have a go at your proposed workaround if its simple for you to do, dont want you spending hours on something that might not work or few people will use.

[DMU]

Sorry guys. Unfortunately, this does not work with madVR profiles.

[mclingo]

can you post a link to the exe, we can trigger it from a key shortcut while KODI is open, for me this is preferable to using windows HDR API

cheers