madVR - high quality video renderer (GPU assisted)

[brazen1]

I have to say the driver situation is becoming very messy for NVIDIA users at the moment, constant requesrts on here for which version to use. Someone should setup a thread specifically to monitor drivers changes and how it affects MADVR / HTPC playback, we could then just refer people to that. You could then maybe work out which driver works for most people and have that listed as the fallback, goto most stable driver.

if this ever becomes necessary for AMD cards i'd do that.

To end the constant requests for which driver depends on what you expect or don't expect the driver to do for your particular interest. It has been stated MANY times, if you seek a driver that does everything HTPC related and is free of any problems, use 385.28.

Some folks don't care about HDR usage. Some aren't interested in 3D. Some don't care about audio properties if the AVR is off. Some don't care if 8bit or 10/12bit is used. Some need HTPC aspects only and others game too. And the list goes on. Again, if you seek a driver for HTPC use free of any problems use 385.28. I should say THE LEAST AMOUNT OF PROBLEMS as some remain to this day. Whether they are of importance to you in your particular usage is for you to determine. In this day and age, so many feel they are entitled to someone doing the dirty work and then hand them the outcome. So, you rely on those that actually get their hands dirty, figure it out yourself, or rely on misinformation because it sounds good to you.

As for a thread detailing driver version changes, I was doing this for months. No one cared. I quit.

Furthermore, I read your posts in lots of forums. You take stabs at nVidia every chance you get while promoting AMD as if it's problem free. Then you pop in demanding answers from folks like madshi to correct your problematic AMD usage. Then you use outdated O/S's and every other "workaround" claiming how perfect your stuff is but the next day you start demanding fixes again. Your nVidia vs. AMD thing needs to stop. We're here to help each other and avoid self promotion and brands.

[madjock]

You beat me...I agree.

@mclingo

Constant AMD this and that, and always having a dig, we really do not care, and you seem to forget all the stuff you have posted in the past when you had lots of issues with AMD...

Please stop, its turned into the mclingo thread on more than one occasion.

https://forum.doom9.org/showthread.php?t=175363

https://forum.doom9.org/showthread.php?p=1837392#post1837392

etc.

etc.

[LigH]

^ SamuriHL:

"You are what you need" ... I don't mind a CPU made by AMD if it has a reasonable price/performance ratio (intel's ratio got worse with Meltdown/Spectre, AMD was more "honest" in this regard and didn't have to apologize for so much loss). But regarding GPU features, nVidia has its advantages. Unfortunately. It needs more potent opposition to come down to reasonable pricing.

My summary: Being a "fanboy" is also a matter of wealth.

Sorry for off-topic.

[SamuriHL]

That's the thing...both AMD and nVidia have their strengths and weaknesses when it comes to madvr. Everyone has to choose what works best for them but there's always going to be a compromise. In the end, if your GPU has enough power to run the features of madvr you want with issues you can accept, you've found the sweet spot. All the rest is just noise. Of course we all want trouble-free madvr but these are PC's and far too many variables that have little to nothing to do with madvr. I'm quite satisfied with the latest build of madvr and my chosen GPU platform. It's not without issues, but, when doing what we're supposed to be doing with madvr, which is watching content, man that experience is AWESOME!

[Asmodian]

We need to keep discussion of video cards to a minimum in this thread. Please. It is hard to avoid but please try. :)

edit: SamuriHL, this post looked wrong after your's. I am not talking about any specific posts but we often take it too far. As I said it is hard to avoid because GPUs are so relevant to madVR. :o

[brazen1]

I agree ^. I think too many folks listen... and watch... their equipment... and their software... rather than their movie. I installed madVR v0.92.17 this weekend. Couldn't be happier. Fixed on ongoing issue started a few releases ago. (Madshi, yours, and your testers contributions for recent tone mapping additions will vastly improve capability for those previously suffering without it. Well done!) My routine is update/upgrade, test, report, workaround if possible, if not revert, and then set and forget. From there, I stop listening and watching my setup and instead enjoy the movie putting all the details out my mind and simply immerse myself into the entertainment. That is the goal isn't it?

Thank you madshi for continuing to enhance our pleasure, remain state of the art, and thrust into the future. And others as well like Nev for the filters, and all the other unnamed contributions pulling everything together creating one hell of an experience every time we desire it.

[HillieSan]

In this world nothing is perfect. I don't know which dictionary you're using. Furthermore, I don't use HDR or any AMD cards, but I dare to confirm that AMD had more issues than NVIDIA when come with into this topic.

I disagree. AMD and NVIDIA both have their issues. AMD RX-480 is doing quite well for me, but it lacks some perfomance with MadVr. It's not a big deal for me. I have an GTX-1080 but I use it for gaming. I don't like the custom resolution solution with NVIDIA to get a stable image.

[mclingo]

To end the constant requests....s.

You beat me...I agree.

......

if you dont like my contributions.

TUFF.

[mariner]

Novice needs help with watching BT2020 content

Greetings.

Using madVR for watching 4K HDR yt content on standard monitor, and playback turns into a slide show. The setting is "Let madshi decide"

System is i7 NUC with HD620 graphics using mpc/LAV.

Appreciate any kind assistance.
Many thanks and best regards,

Note:
This was first posted it the HDR thread, but moved here at member's suggestion for better exposure.
https://forum.doom9.org/showthread.php?p=1853552#post1853552

[mclingo]

hi, yeah I suggested you bring it here. can you post your MADVR osd so we can see your settings and how large your rendering times are. I dont have a NUC but I think this will be useful for us to see.

[mclingo]

https://forum.doom9.org/showthread.php?p=1853185#post1853185

ok guys, i've renamed my thread the general MADVR discussion thread so we can keep our hardware conversations off the main thread.

BRAZEN1 / MADJOCK - totally happy to have a proper discussion with you or anyone else off this thread about hardware, we should keep it off this thread in future and point people in this threads direction if this conversation starts up again.


lets keep this thread completely technical so MADSHI doesnt have hundreds of posts to plough through again.

[madshi]

Good a reply from my Nvidia contact. He's looking into the 4xx driver HDR problems. And he told me he got madVR onto the Nvidia driver HDR check list already a year ago. Which means basically all new driver releases are checked for HDR compatability with madVR... :) So he's kind of wondering how the new 4xx problem didn't get noticed. Maybe they only tested FSE mode, in which 4xx HDR switching still seems to work? Anyway, there's a good chance it might be fixed "soon".

I'm seriously looking into the possibility of rolling back to Win 8.1 on my HTPC.
It's definitely a valid option. That said, the biggest win10 problem (render and present queues not filling) seems to be fixed in v0.92.17.

Novice needs help with watching BT2020 content

Greetings.

Using madVR for watching 4K HDR yt content on standard monitor, and playback turns into a slide show. The setting is "Let madshi decide"

System is i7 NUC with HD620 graphics using mpc/LAV.
First thing to check is if the decoder queue (Ctrl+J) is properly filled or not. Decoding UHD HDR content is pretty difficult, so you need to pick a suitable decoder. If the decoder queue is nicely filled, then which queue (from top to bottom) is the first one which is in trouble?

[SamuriHL]

Good a reply from my Nvidia contact. He's looking into the 4xx driver HDR problems. And he told me he got madVR onto the Nvidia driver HDR check list already a year ago. Which means basically all new driver releases are checked for HDR compatability with madVR... :) So he's kind of wondering how the new 4xx problem didn't get noticed. Maybe they only tested FSE mode, in which 4xx HDR switching still seems to work? Anyway, there's a good chance it might be fixed "soon".


Oh SWEET! Very nice!!


It's definitely a valid option. That said, the biggest win10 problem (render and present queues not filling) seems to be fixed in v0.92.17.


I was considering it due to the issues with HDR in the latest nVidia driver but if that's potentially going to be fixed I may hold off. I'm not really having any other issues at present and need to stay fairly current with driver.

[wnholt01]

i'm using windowed mode with both. Another strange thing with nvidia 4xx.xx drivers, HDR passthrough work fine with mpc-be but not with kodi dsplayer and yet both in windowed mode.
Anyway back to 39x.xx and everything is working as it should.
:thanks:

I also noticed the HDR pass through stopped working in Kodi dsplayer after updating to 4.xx xx drivers, while MPC-HC still worked. I am using full screen mode but found that switching video renderer to DXVA2 native in internal Kodi LAV video filter fixed the pass through problem. Prefer to use D3D11 over DXVA2 but suppose it will have to do until driver issues get resolved.

[brazen1]

Hi madshi. Good to hear your nVidia contact is still available. I know he's helped in the past. I assume you can't flood the guy with what could use attention but here's a couple things left to your discretion if at all: Sorry this is so loooong. I wanted to be thorough.

(1) 10bit selection for RGB especially at 23/24Hz and survive a reboot.

(2) No auto switch from stereo to multiple speaker setup in Windows Audio considering if AVR state is On or Off.

(3) And the ever popular Audio Video sync for common refresh rates such as 23.976 f/ps leads to dropped frames without creating custom timings.

#2 is my personal pet peave. If all of this was addressed, and imo, this would be perfection.

Here are some relevant notes I posted in another thread:


I have discovered what I assume is another bug introduced by NVidia drivers. Yesterday I decided to work it out. The problem:

Right click your volume icon with your AVR OFF or in standby using passthrough. It should be setup for Stereo.
Now, turn your AVR ON. It should be setup for 5.1 or 7.1 etc. (What ever you use during video playback)
This should automate between stereo and 7.1 (for example) as you toggle your AVR off and on. If it doesn't, you will have to manually change it. If you forget, high bitrate audios will malfunction (audio filter errors) during video playback mode and/or youtube videos from desktop mode will not start.

Not knowing if this was associated with a Windows update or something else, I decided to install NVidia drivers working backwards to rule them out as the culprit or find a working driver to identify where the problem originated.
Eventually the audio setup started working as intended and I've concluded it is an NVidia driver issue. Here's what I installed and concluded using DDU between installs:
391.35-desktop-win10-64bit-international-whql.exe = Audio problem.
391.24-desktop-win10-64bit-international-whql.exe = Audio problem.
391.01-desktop-win10-64bit-international-whql.exe = Audio problem.
390.65-desktop-win10-64bit-international-whql.exe = Audio problem. This is the driver the audio problem was introduced.
All of these drivers also cannot retain a 12bit setting after a reboot but you should be using 8bit anyway since 12bit introduces banding unless your display handles 12bit native properly.

388.59-desktop-win10-64bit-international-whql.exe = Does not turn HDR off after HDR playback but Audio switching problem is not present. This was the last good driver for audio switching.
387.92-desktop-win10-64bit-international-rs3-whql.exe = Does not turn HDR on prior to HDR playback.
385.69-desktop-win10-64bit-international-whql.exe = Working properly for HDR and Audio switching but any mouse movement turns 3D into 2D briefly. This is the driver I have reverted to. This also means I will need to use FSE.
385.28-desktop-win10-64bit-international-whql.exe = Working properly for HDR and Audio switching.
These drivers survive a reboot when using 12bit but again, you should be using 8bit unless your display handles 12bit native properly.

Understanding Nvidia has worked out many bugs, it now has these:

No 10bit selection when using RGB.
No auto switch from stereo to multiple speaker setup in Windows Audio considering if AVR state is On or Off.
Audio Video sync for common refresh rates such as 23.976 f/ps leads to dropped frames without creating custom timings.

[madshi]

Sorry, brazen1, I'm getting many requests to ask my Nvidia contact about all kinds of bugs, but I can't do that if I don't want to lose him. I'm trying to bother him only with absolutely critical issues, which are also his responsibility.

[Asmodian]

Good a reply from my Nvidia contact. He's looking into the 4xx driver HDR problems. And he told me he got madVR onto the Nvidia driver HDR check list already a year ago. Which means basically all new driver releases are checked for HDR compatability with madVR... :) So he's kind of wondering how the new 4xx problem didn't get noticed. Maybe they only tested FSE mode, in which 4xx HDR switching still seems to work? Anyway, there's a good chance it might be fixed "soon".

Great info, thanks for the update. :)

Using madVR v0.92.17 with drivers 411.70 I can switch into HDR mode with both Windowed and FSE (in that my TV displays its HDR logo) but it instantly switches back to SDR mode when the video starts playing in Windowed mode.

D3D11:
If it ever goes into FSE it works fine, even if I then switch back to Windowed (either by bringing up a window over it or switch the player out of full screen).

D3D9 (new path):
When in FSE it flickers back and forth between HDR and SDR when playing the video (I get a blank screen due to the TV never getting time to stabilize in one mode). If I pause it I can see the frame in HDR. If I then force it into fullscreen Windowed (by bringing up the madVR settings window) it stays in HDR mode. If I disable FSE in the settings at this point the movie continues playing in HDR in full screen Windowed.

Maybe this is helpful? :confused:

(This is using: Windows 10 Pro, Titan X (Pascal), Zoom Player 14.3, LG OLED C7P)

And thanks for the new version! :thanks:
I am very impressed by the new "tone map HDR using pixel shaders" when using "output the video in HDR format". It works really well with my TV, I get a noticeably better map of highlights when targeting my measured brightness (680 nits) with no trade-offs, at least that I have noticed. It also works well in SDR mode, all the tricky scenes I had noticed had issues in the past have no issues now.

[alps006]

I am on 1803 and no issues to report but I haven't updated the driver to the latest, still using 18.5.1. I usually don't update drivers when I have a working one.Hi, out of interest, have you moved to 1803 yet, i've been putting this off for fear of problems, there has been much said about AMD card and 1803 on here with MADVR.

[mariner]

....
First thing to check is if the decoder queue (Ctrl+J) is properly filled or not. Decoding UHD HDR content is pretty difficult, so you need to pick a suitable decoder. If the decoder queue is nicely filled, then which queue (from top to bottom) is the first one which is in trouble?
.....

Thanks for the kind reply, madshi.

LAV can handle the clip with ease using DXVA in EVR-CP. It appears to be using DXVA as well in madVR.

Not sure how to read the queue numbers, but here they are:

decoder queue 2-3/16
uplodad queue 1-2/8
render queue 1-2/8
present queue 0-1/8
dropped frames 2674

Test clip (#337):
https://www.youtube.com/watch?v=mHUOCxVT5ro

[alps006]

LoL!!!well, nvidia also don't have issues,we all know that nvidia is always performed better when using madvr + mpc.

[Asmodian]

decoder queue 2-3/16

Notice how your decoder queue is not full, it should be 15-16/16 or close. This is a sign decoding is too slow. Make sure LAV is on DXVA2 (copy-back).

Another idea is to lower your buffer sizes, UHD buffers take up a lot of RAM. Try something like 8 CPU and 6 GPU buffers.

[chungexcy]

Hi Madshi,

Thanks for updating 0.92.17. I found a problem related to a HDR passthrough issue with my 3DLUT file. I'm using Windows 8.1 platform, with NVIDIA GPU GTX960 and GTX1070 on two machines, using HDMI 2.0 to my TV with HDR ability.

It was working well on 0.92.16 and earlier versions. But on 0.92.17, it's not working on both of my machines.

Basically the problem is, when I choose "tone map HDR using external 3DLUT", it seems madVR fails or "forgets" to send metadata to my TV (which doesn't trigger HDR on).

However, for "let madVR decide" and "passthrough HDR to display", these two options will still "trigger" my HDR on my TV. If I switch to "passthrough HDR to display", the HDR will be turned on, as expected.

Once the HDR is turned on during the playback, if I switch from "passthrough HDR to display" to "tone map HDR using external 3DLUT", the HDR is still on. That's why I guess madVR "forgets" to trigger HDR with 3DLUT like before.

[nevcairiel]

Notice how your decoder queue is not full, it should be 15-16/16 or close. This is a sign decoding is too slow. Make sure LAV is on DXVA2 (copy-back).


Actually, make sure its set to DXVA2 (Native), and that madVR reports DXVA in the OSD. Copy-Back is too slow on Intel GPUs for UHD.

[mclingo]

I am on 1803 and no issues to report....

thanks

[aufkrawall]

Actually, make sure its set to DXVA2 (Native), and that madVR reports DXVA in the OSD. Copy-Back is too slow on Intel GPUs for UHD.
Shouldn't this be impossible, according to huhn? :devil:

[sat4all]

Hi madshi,

The new HDR tone mapping settings page doesn't include Output video in HDR format check box when using tone map HDR using external 3DLUT.

Thanks

[huhn]

Shouldn't this be impossible, according to huhn? :devil:

yeah i never excluded iGPUs... oh wait i did.

[PurpleMan]

Guys, I'm getting confused with all the different posts on the subject.

I have a Sony X940E which has a 10-bit panel. Using my Nvidia card (1050), which Output format should I be using?

Right now I use 4k 23hz 8-bit RGB FULL.
Should I be using anything else? (like 12 bit RGB, 422/444/420)

Also, should I use the same for both SDR and HDR?

[brazen1]

Many of us match refresh rates because everything we play is not just one native rate. Also Windows and GUI's for programs such as front ends are designed for 60Hz. So, while a permanent setting of 23Hz might match any 23Hz titles you are playing, anything else will not match and certainly your Desktop and GUI's won't be optimal. If you are matching rates and end up with a UHD 23Hz title, great. RGB Full at 60Hz is what I use and match refresh rates at 12bit. RGB is preferred because that is what a PC uses unlike a dedicated set top player. So, RGB from the GPU output avoids any extra conversions when a PC is used. Unfortunately, nVidia does not offer a 10bit RGB setting. (this was one of 3 fixes I had hoped madshi would consider mentioning to his nVidia contact when/if appropriate) So, you have two choices: Use 12bit. It will dither down to what ever your source is. But, in the event your display does not handle 12bit properly, even dithered down, it may introduce 'banding'. Also the newer drivers can't even survive a reboot if this setting is used so if you do... you'll have to remember to reset it or use driver 385.28 before the problem was introduced. Or, select 8bit, and avoid the issues at the cost of nothing you will likely notice. SDR vs HDR: SDR usually always uses 8bit and HDR 10bit. You need not change any settings HDR vs SDR for refresh rates. Regarding your 23Hz. Understand, some displays are 60Hz max. Some 120Hz and beyond. Folks with 60Hz displays often desire playback at 60Hz used in conjunction with a smoothing algo like that included in madVR. This is to avoid 3:2 pulldown which introduces judder. In my experience, even with smoothing algo's, there is still some judder. Ultimately, my display is 240Hz interpolated. I can have perfect multiples of refresh rates and am not limited to 60Hz so I can match rates without any pulldown or mismatch of rates coupled with a smoother. You need to know your own and select your optimal settings to match your environment.

[mariner]

Notice how your decoder queue is not full, it should be 15-16/16 or close. This is a sign decoding is too slow. Make sure LAV is on DXVA2 (copy-back).

Another idea is to lower your buffer sizes, UHD buffers take up a lot of RAM. Try something like 8 CPU and 6 GPU buffers.

Actually, make sure its set to , and that madVR reports DXVA in the OSD. Copy-Back is too slow on Intel GPUs for UHD.

Thanks for the kind reply, Asmodian and Nevcairiel.

1. Both DXVA2 (copy-back) and DXVA2 (Native) don't work.

2. D3D11 works if Hardware Device is set to Automatic, but fails if HD Graphics 620 is selected.

3. Lowering the queue size in the rendering general setting has no effect.

4. GPU usage hits the 90s, while CPU usage stays in the 20s.

5. Render and Present queue stay low.

6. About 7000 dropped frames and few hundred repeated frames reported for the 4min clip. Is madVR rendering the clip at 29fps?

Many thanks for your kind assistance,

[madjock]

Fullscreen Exclusive (OSD wise anyway) seems to be working again with Windows 10 1809, they must have fixed what they broke. :)

Shows 60 Hz in the composition rate, although its 23.976, had that before if I remember.

[mclingo]

Fullscreen ......

out of interest madjock and apologies if this is offtopic but is 1809 the upate with the black explorer theme?

[madjock]

out of interest madjock and apologies if this is offtopic but is 1809 the upate with the black explorer theme?

Yes, looks like you just select Light/Dark for App mode and it applys it to everything. Not a fan myself tbh.

[Morku]

Hi, I have an issue with videofiles contains:
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L4@Main
Codec ID : V_MPEGH/ISO/HEVC

The videoplayer stays black, only audio is running.

In this state, I am also unable to see information with Ctrl+J.

What I have found out: other videofiles like
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High 10@L5
are running fine.

So currently I use MPC-HC 18.2.4, LAV Video Decoder 0.72.0.15 and madVR 0.92.17. No Hardware Decoder is used in LAV settings.
When I change MPC-HC to Enhanced Video Renderer, the HEVC files runs fine.
So what I have found out is: the current setting is "chroma upscaling: Bilinear" (done by GPU). When I change this setting to Cubic (custom pixel shader code), the HEVC runs fine with madVR again.

I can change it when the file is currently playing. The video is black -> I change to Cubic -> video is visible -> I change to Billinear -> Black. When I open Ctrl+J during Cubic and change back to Billinear, the image freeze (but audio still playing).

Currently I am able to verify the issue with 2 old laptops, Intel Core i7 620LM with "Intel HD Graphics" and another with Sandy Bridge generation.

I changed on my Desktop PC the setting also to chroma upscaling Billinear, but the files run fine there (980 Ti NVIDIA GPU).

So... the issue is maybe in combination with some (old) Intel GPU, or the madVR settings in whole combination. I would like to share you my madVR settings to veryify the issue, but I can't find the location of the setting file and can't find any export function. Can you tell me?
If there is also some more information missing, just ask.

[ryrynz]

Which D3D version you using? Try 9 if you're using 11 and the other way around, also try using default settings (use the batch file)

[mclingo]

Yes, l.....

cool, thanks

[dbcooper]

Microsoft have pushed out their semi-annual Windows 10 update (1809) today. Anyone noticed any bugs with MadVR?

[Morku]

Which D3D version you using? Try 9 if you're using 11 and the other way around, also try using default settings (use the batch file)

If you are talking about general settings -> "use D3D11 for presentation", it doesn't make any difference when I un-/check this option. It stays black.

[mytbyte]

@morku: try reverting to LAV 0.71, it solved my problem of missing hardware decoding for 4K, as I reported on the LAV thread

@dbcooper: I got upgraded to 1809, no trouble so far

[brazen1]

@Morku
Try unchecking Rendering/General Settings/delay playback start until render queue is full.

[Morku]

It is unchecked. It also doesn't make any difference to enable.
Like I said, if you tell me how, I would share you my settings.

Only changing chroma upscaling to one of the custom pixel shader code seems to fix the issue. Also "Nearest Neighbor" let the image stays black.

@mytbyte
Like I said, I am not doing hardware decoding, it's disabled in LAV.

[mkohman]

Guys apologies if this is a silly question but with the latest Windows 10 update I can't no longer stream from my server which is located in another room which also runs window 10 via SMB within kodi.. Does anyone know a way around this or is it not reccomended to share via SMB within Kodi? If not then what's the best way to share. Mkv files within kodi Thanks

Sent from my moto g(6) using Tapatalk

[mytbyte]

@mytbyte
Like I said, I am not doing hardware decoding, it's disabled in LAV.

I misread:)...

[Warner306]

Guys apologies if this is a silly question but with the latest Windows 10 update I can't no longer stream from my server which is located in another room which also runs window 10 via SMB within kodi.. Does anyone know a way around this or is it not reccomended to share via SMB within Kodi? If not then what's the best way to share. Mkv files within kodi Thanks

Sent from my moto g(6) using Tapatalk

Did you go through the troubleshooting posted at the DSPlayer forums? There are two important links there and one video that should be followed.

[mkohman]

Did you go through the troubleshooting posted at the DSPlayer forums? There are two important links there and one video that should be followed.No I didn't could you please direct me to the links or maybe post numbers.. Thank you so much..


Sent from my moto g(6) using Tapatalk

[Warner306]

The post is here: https://forum.kodi.tv/showthread.php?tid=223175&pid=2769562#pid2769562

[yok833]

Hi guys,

It seems that I have an issue since I updated W10 and the latest nvidia drivers.

By default my desktop is in SDR and madvr switch automatically to hdr when I watch a movie.

Now, when madvr starts an hdr content, I have "nv hdr" at the top of the osd and the problem is that I do not have the hdr settings enabled on my tv (even if the hdr logo appears at the beginning of the video).

If manually, I activate hdr on W10 before launching madvr with hdr content, then I have "os hdr" on the osd and the hdr settings of my tv are enabled automatically.

Before the updates, i never had these issues and madvr was switching automatically from sdr (desktop)/hdr(video) with the good hdr settings of my tv???

[mclingo]

just installed 1809, all "appears" to be working as before but unfortunately its brought back the AMD red colour sat issue in MADVR for me, i'll try reinstall AMD drivers.

[Klaus1189]

Hi guys,

It seems that I have an issue since I updated W10 and the latest nvidia drivers.

What Win10 update? -> 1809?
Latest Nvidia Driver 4xx.xx has HDR issues, Nvidia users switched back to 399.xx.
But I am not a Nvidia user anymore for two years now and I don't regret it.

But to know how newer cards are behaving now 10-2018, I only have an older one, I need to know the following:
Is it temporaily with 4xx.xx Nvidia driver still problematic, when you set your desired Color depth of for example 10 bit (is it now available for RGB and YCbCr? or still 8bit and 12 bit only) and restart system, I remember I had trouble of Driver setting itself back one year back when I tried a 1080Ti Lightning Z.
If they have fixed it the last 12 months, maybe a Nvidia will probably sometime in the future suited for my needs.

[brazen1]

What are the HDR issues with 4xx.xx and why did you switch back to 399.xx?
I altered the latest 411.70 driver to workaround the audio bug today and installed it. What should I look for?
We are aware of no RGB 10bit. I use 8bit so as not to introduce banding so I really don't care.
Yes, you can select only 12bit and let it dither to 10bit but then there is banding.
This setting, as you stated, does not survive a reboot and reverts to 8bit.
8bit seems ideal to me.
If you want the 12bit setting to survive a reboot, you'll need to use 385.28 before the bug was introduced.
So back to the latest driver... What are the HDR issues I should look for? Preliminary testing revealed nothing out of the 3 players I used.