madVR - high quality video renderer (GPU assisted)

[mrmojo666]

AMD no issue? This is really bull-shit. AMD is a piece of junk.

don't this so

[iSeries]

madshi, 0.92.17 completely resolved the red tint / black crush issues I mentioned before with the old "process HDR via pixel shader math" option. The new menu correctly triggers the HDR mode on my LG C7 and tonemaps with your algorothm instead of the TV's dumb mode. Watching Pacific Rim at 700 nits with "are you nuts!?" highlight recovery and the dream has finally been realized.

:thanks:

I hadn't tested this on my new C7, however I assumed that this TV always tone-mapped when in HDR mode. Is this with or without 'output video in hdr format' ticked? How do you know the TV isn't still tone-mapping? I assume 'active hdr' (dynamic contrast on 'low') is off on the TV?

[jandari]

Can confirm HDR passthrouh doesnt work with nVidia 4xx.xx drivers on my 1070ti.
Maybe this has something to do with it

This driver release supports the Vulkan VK_EXT_swapchain_colorspace and VK_EXT_hdr_metadata extensions allowing applications to output HDR content to HDR displays via the Vulkan APIs.

[sat4all]

@madshi
Toggling hdr tab in madtpg doesn't switch my display to hdr mode, I'm not sure if this was introduced by .16 or .17

Can confirm HDR passthrouh doesnt work with nVidia 4xx.xx drivers on my 1070ti.
Maybe this has something to do with it

This driver release supports the Vulkan VK_EXT_swapchain_colorspace and VK_EXT_hdr_metadata extensions allowing applications to output HDR content to HDR displays via the Vulkan APIs.

HDR passthrough work fine here with my gtx1060 using 4xx.xx drivers

[jandari]

Tested again, doest't work.

Tried HDR switch in Windows, it works.

Switching back to 3.99 for now.

[Warner306]

@madshi

Same here, so red tint / black crush issues are resolved.

The only thing that is confusing for me is that now using lower nits gets the picture to become darker and setting more nits means I will get the brighter picture. Now correct me If I'm wrong but wasn't this the other way around in the previous builds? Anyway, 700 seems way to bright so I think I will settle for 600 but I'm glad I can finally set more than 100.

Thank you madshi!

If you are outputting in HDR, higher PQ values will make the image brighter and lower numbers will make the image darker. They are absolute luminance values and not relative like HDR -> SDR. The target peak nits specifies the brightest pixel to be shown by the display.

[mclingo]

all looking good here, just upgraded to AMD 18.9.3, LAV 70.2.15 and MADVR v0.92.17 - so far everything seems to be working well, HDR switch, 3D switch, 23hz playback, colour sat problem also still fixed. havent tested to see if there has been any progress with refresh rate switching bug with MADVR and AMD cards coming out of 3D MVC back to a 4k desktop yet but its good to see all the basics working very well.

EDIT, thats a shame, the black screen bug is still there closing a 3D movie and coming back to a 4k desktop with MADVR refresh rate switching, this is my last bug, i have an otherwise fully stable no workaround system now the cololur SAT issue is fixed.

any chance at all you could revisit this MADSHI, I know you say its a driver bug but it really does only affect MADVR refresh rate switching, doesnt do it on MPC-BE, KODI DS, MPC-HC, tested all those recently and have tested ZOOM and KM in the past as well.

[madshi]

Is it possible to bring up the madVR Settings GUI from a command line?
Yes, you can use "madHcCtrl.exe editLocalSettingsDontWait".

Unfortunatedly,Running the highlights recovery algorithm will consume pc resources tremendously so that the playback of HDR movies gets stammering and stuttering very much.I'm expecting the algorithm will improve dramatically soon later.
Nope, there's no improvement planned. I've already optimized it as much as I could, using DirectCompute. If your GPU is too slow to run the highlight recovery algo, you either need to reduce other quality settings (e.g. chroma upscaling quality), or you need a faster GPU.

madshi, 0.92.17 completely resolved the red tint / black crush issues I mentioned before with the old "process HDR via pixel shader math" option. The new menu correctly triggers the HDR mode on my LG C7 and tonemaps with your algorothm instead of the TV's dumb mode. Watching Pacific Rim at 700 nits with "are you nuts!?" highlight recovery and the dream has finally been realized.
Glad to hear that! Have you had a chance to compare quality with my madVR's tone mapping vs passthrough?

Madshi, what was the problem here?
The new build uses substantially less CPU for me. I also noticed previously that the problem got worse if any CPU-intensive background processes were active. So I suspect that Windows 10 r1803 created some sort of (single threaded) CPU bottleneck.
A simple OS API, which was very fast and lightweight before, suddenly consumed lots of CPU in the latest Windows 10 build and took ages to execute. I've called this API a lot, so this slowed down everything. So in v0.92.17 I'm now internally "caching" this API call to solve the issue.

So a madVR bug then? With all the upgrades that happen, settings files can cause all sorts of problems over time.
Yes, the previous "process HDR content" feature was broken since v0.92.15.

Same here, so red tint / black crush issues are resolved.

The only thing that is confusing for me is that now using lower nits gets the picture to become darker and setting more nits means I will get the brighter picture. Now correct me If I'm wrong but wasn't this the other way around in the previous builds? Anyway, 700 seems way to bright so I think I will settle for 600 but I'm glad I can finally set more than 100.
Well, it's a very complicated thing, because madVR can either send the video relative gamma encoded, or absolute PQ encoded. It all depends on how the TV interprets either data. It's hard to predict what will happen exactly. So you can only try what happens and what looks good, and what does not.

Toggling hdr tab in madtpg doesn't switch my display to hdr mode, I'm not sure if this was introduced by .16 or .17
Are you sure this was introduced by a new madVR build? Maybe it was a driver or OS update?

Can confirm HDR passthrouh doesnt work with nVidia 4xx.xx drivers on my 1070ti.
I can confirm that HDR passthrough with Nvidia's custom API doesn't work properly for me on the latest Windows 10 build with 411.70. I'll notify my Nvidia contact about this.

[sat4all]

Are you sure this was introduced by a new madVR build? Maybe it was a driver or OS update?


Hmm, i'm not sure but hdr passthrough playback is working fine so it's only about madtpg. Anyway i will revisit after finishing a long calibration session :D

[jerryleungwh]

May I ask what are some suggested settings on the HDR page? I have an LG OLED with HDR support. I believe that it is considered that tone map HDR with pixel shaders and output in HDR format should provide the best quality, but I am not too clear about the options provided even after reading some related posts here. So I have read an OLED should be able to produce up to 10000 nits, should I put that in target peak nits? I have seen some users putting 600 or 700 here and I tried that myself, and it seems to me that when the peak nits of the frame is higher than the value I put here, some of the brighter areas will be dimmed down, doesn't that mean I am not viewing the content as bright as it is supposed to be? But then it does seem if I just do passthrough the brightest area get crushed to almost and loses some detail, should I just use the * value in "HDR * nits, BT.2020 ->DCI-P3" given in the OSD as target peak nits so it reaches the brightest as it needs to while also get "correct tone mapping"? Thanks!

[SamuriHL]

I can confirm that HDR passthrough with Nvidia's custom API doesn't work properly for me on the latest Windows 10 build with 411.70. I'll notify my Nvidia contact about this.

Thank you! Most of us are sticking with 399 for that reason.

[blu3wh0]

Nvidia 4xx.xx triggers HDR properly only in fullscreen exclusive mode for me.

[madshi]

jerry, the newest OLEDs top out at about 800nits, or something like that. Definitely very far away from 10000nits. I can't really tell you which settings are the best. I can only advise to try different "target peak nits" values, in combination with "output video in HDR format" either on or off. And then use the settings combination that looks best to your eyes.

The other options are less important. The "measure each frame's peak luminance" and "highlight recovery strength" options can help sometimes, so they might be worth trying. You can leave the other options (tone mapping curve & color tweaks) at default.

[SamuriHL]

May I ask what are some suggested settings on the HDR page? I have an LG OLED with HDR support. I believe that it is considered that tone map HDR with pixel shaders and output in HDR format should provide the best quality, but I am not too clear about the options provided even after reading some related posts here. So I have read an OLED should be able to produce up to 10000 nits, should I put that in target peak nits? I have seen some users putting 600 or 700 here and I tried that myself, and it seems to me that when the peak nits of the frame is higher than the value I put here, some of the brighter areas will be dimmed down, doesn't that mean I am not viewing the content as bright as it is supposed to be? But then it does seem if I just do passthrough the brightest area get crushed to almost and loses some detail, should I just use the * value in "HDR * nits, BT.2020 ->DCI-P3" given in the OSD as target peak nits so it reaches the brightest as it needs to while also get "correct tone mapping"? Thanks!

I'm sure others will chime in here, as well. I'm still learning myself so hopefully I don't get any of this wrong.

First, no OLED is reaching 10000 nits. That's the theoretical unicorn screen. No consumer device comes even remotely close. OLED, particularly LG OLED can MAYBE hit 800-850 max depending on how it's set up. This is why most of us with an LG OLED tend to run around the 700-800 target nit range. The theory being that if you're setting a target higher than the display is capable of, it is going to trigger the TV's internal tone mapping (CAVEAT: It probably is regardless, but, we're trying to get as close with the target nit as possible to the TV max nit...whether tone mapping is always done or not in HDR mode is something we're still working on figuring out). So, there's no easy answer to your questions, unfortunately. Trial and error are what it's going to take to determine what looks best to you. If you're on an LG OLED, I'd probably stay below 850 as my target nit. I've been using 800 lately and think that's probably a bit too high.

[Ver Greeneyes]

A simple OS API, which was very fast and lightweight before, suddenly consumed lots of CPU in the latest Windows 10 build and took ages to execute. I've called this API a lot, so this slowed down everything. So in v0.92.17 I'm now internally "caching" this API call to solve the issue.

Aah, that makes sense. I thought something in the system might have started spewing lots of warnings or something. Fingers crossed Microsoft are done breaking things for a while ;)

[SamuriHL]

I'd not bet on it. The fall update is about to be unleashed upon us all. LOL

[jerryleungwh]

@madshi thanks for the prompt reply! I have seen some comparison pictures with "highlight recovery strength" in hdr to sdr conversion and I assume it works pretty much the same when outputting in hdr format, and I think it definitely looks better with this on so I will use this and maybe keep it at low or medium. Maybe I should try with 750 nit next time and see how does it differ from passthrough. Though, at first glance it seems to me that the resulting image in passthrough is brighter than when I set this to 1000, doesn't that mean the screen can actually go over 1000 nits? Though it might just have been the wrong tone mapping by the TV that made the whole area a bit more bright so I though it was " brighter", I can't say for sure yet

@SamuriHL may I ask what result did you get that makes you think 800 is "too high"? Maybe I can use the same criteria to better adjust my setting

Thanks!

[suanm]

@madshi
I reduce physical resolution of TV set so that i can play fluently HDR movies with highlight recovery algorithm by choosing high option.When i set bright peak nits to 100,the dynamic images effects look obviously brighter than it does in passthrough mode.As it is 200 nits,dynamic images effects get close to passthrough.While choosing more than 600 nits,the effects seem undifferentiated with passthrough.

[SamuriHL]

@SamuriHL may I ask what result did you get that makes you think 800 is "too high"? Maybe I can use the same criteria to better adjust my setting

Thanks!

I want to be clear, at 800 it looks fantastic. My reasoning for saying that it may be too high is that I don't know the max nit level for my specific TV. I have no way to measure it. My goal is to keep the target nit under the max nit that my TV is capable of in an effort to minimize my TV's internal tone mapping. It's very likely that it's tone mapping regardless, but, if madvr does its job at the theoretical max limit for my TV, I'm HOPING that whatever the TV does internally doesn't mess with it too much. As from my experience so far, that seems to be the case. At 800, I can see a NOTICEABLE improvement over pass-through. Hope this makes sense.

[jerryleungwh]

@SamuriHL Thanks! I'll test this again a few times to see what works better then.

@madshi may I also ask does "measure each frame's peak luminance" works kinda like sending dynamic data to the TV, if it's just about how the result looks? Like the tone mapping could be tuned according to what is needed for each frame?

[sat4all]

Are you sure this was introduced by a new madVR build? Maybe it was a driver or OS update?


Indeed, it's from nvidia 4xx.xx drivers. the weird thing is that madvr can switch my tv to hdr mode during playback but not madtpg!
About Defeating TV's internal tone mapping, i've measured my LG OLED HDR peak arround 394nits so i've set madvr target nit to 400nits for HDR Processing and while comparing it to HDR>SDR i couldn't see any loss of details while enjoying the luminance boost of HDR mode.
Hope madshi can implement his idea of outputing maxCLL based on selected target nits in the next official or test release.
Thanks for making my TV HDR mode usefull again ;)

[iSeries]

I want to be clear, at 800 it looks fantastic. My reasoning for saying that it may be too high is that I don't know the max nit level for my specific TV. I have no way to measure it. My goal is to keep the target nit under the max nit that my TV is capable of in an effort to minimize my TV's internal tone mapping. It's very likely that it's tone mapping regardless, but, if madvr does its job at the theoretical max limit for my TV, I'm HOPING that whatever the TV does internally doesn't mess with it too much. As from my experience so far, that seems to be the case. At 800, I can see a NOTICEABLE improvement over pass-through. Hope this makes sense.

Hi, to be clear, when using MadVR tone mapping are you turning off Active HDR on your TV?

[waldnebel]

I've tried to insert those custom resolution values madVR calculated (first picture) into the CRU tool which you can see in picture 2.

Why is the horizontal front porch not accepted by CRU? It's red and the OK button is greyed out. It looks like madVR and the GPU driver doesn't have any problem with that front porch value. There wasn't any error message obviously.

http://thumbs2.imagebam.com/f1/f9/b1/886d43989055034.jpg (http://www.imagebam.com/image/886d43989055034)
http://thumbs2.imagebam.com/81/b3/2f/72df22989055004.jpg (http://www.imagebam.com/image/72df22989055004)

[SamuriHL]

Hi, to be clear, when using MadVR tone mapping are you turning off Active HDR on your TV?

I've not done a WHOLE lot of testing yet, but, in the testing I did yesterday I've found that I get better results with the LG dynamic HDR turned ON. I suspect that's because it's looking at each frame and madvr's output is probably close to what it would change. I don't really know and this is just a guess. But to me, it definitely looks better with the dynamic HDR turned on.

[iSeries]

Yeah I've found Active HDR to be very effective so I wouldn't want to lose that in order to use MadVR's tone mapping. I'll be honest though, I've gone backwards and forwards between MadVR tone mapping at 700nits (with highlight recovery set to medium...I have no idea what this should be set to), and straight passthru, and I can't see any difference...ok MadVR tone mapping is ever so slightly darker (I guess I can increase target nits to make brighter) but aside from that almost imperceivable difference it looks the same. What are the benefits of MadVR tone mapping vs letting the TV do it (LG C7)

[SamuriHL]

If you're going to tone map while in HDR mode, medium highlight recovery is probably not strong enough. Try the Are you nuts?! setting and see if that makes a difference for you. The tone mapping option was originally designed (I believe) with projectors in mind that don't necessarily have native HDR capability. The idea would be to tone map HDR to SDR. On OLED, we have trouble getting high enough brightness in SDR mode so we have to try to see if it works for us in HDR mode if we want to keep the brightness. If the difference in the TV's tone mapping vs madvr isn't perceptible to you there may not be a benefit in using the option. Try 800 nits and see what you think with a stronger highlight recovery. Also know that this is a work in progress and that it's being worked on by madshi between each version. So this option will get better with time. I already prefer it with my setup to pass-through as I can definitely see a difference.

[foxyshadis]

It boggles my mind that there isn't a standard EDID format to report max nits, so that having to guess-and-check constantly wouldn't be necessary.

[huhn]

the max nits it pretty much a lie anyway. 2% 4 % 50 % max nit...

[madshi]

Maybe I should try with 750 nit next time and see how does it differ from passthrough. Though, at first glance it seems to me that the resulting image in passthrough is brighter than when I set this to 1000, doesn't that mean the screen can actually go over 1000 nits? Though it might just have been the wrong tone mapping by the TV that made the whole area a bit more bright so I though it was " brighter", I can't say for sure yet
I don't know, I can't analyze such things just by reading your descriptions. In any case, the higher you set the target peak nits, when using "output video in HDR format", the more processing is done by the TV and the less by madVR. However, if you set the target peak nits too low, madVR will compress too much. So it's a balance act to find the "best" value.

@madshi may I also ask does "measure each frame's peak luminance" works kinda like sending dynamic data to the TV, if it's just about how the result looks? Like the tone mapping could be tuned according to what is needed for each frame?
I don't really understand what you're saying. The measurement functionality doesn't report anything to the TV, if that's what you're asking. It just changes madVR's tone mapping curves.

Indeed, it's from nvidia 4xx.xx drivers. the weird thing is that madvr can switch my tv to hdr mode during playback but not madtpg!
Maybe you're using madVR in FSE mode, and madTPG in windowed mode?

I've tried to insert those custom resolution values madVR calculated (first picture) into the CRU tool which you can see in picture 2.

Why is the horizontal front porch not accepted by CRU? It's red and the OK button is greyed out. It looks like madVR and the GPU driver doesn't have any problem with that front porch value. There wasn't any error message obviously.
Why are you asking this question here? Shouldn't you ask the CRU developers about it? I don't kow the answer. Maybe CRU requires the front porch to be divisible by a certain factor (like 16 or 8 or something)?

I'll be honest though, I've gone backwards and forwards between MadVR tone mapping at 700nits (with highlight recovery set to medium...I have no idea what this should be set to), and straight passthru, and I can't see any difference...ok MadVR tone mapping is ever so slightly darker (I guess I can increase target nits to make brighter) but aside from that almost imperceivable difference it looks the same. What are the benefits of MadVR tone mapping vs letting the TV do it (LG C7)
The higher you set the target peak nits, the more processing is done by the TV. The difference may not be visible in all/many scenes. You may need to know what you're looking for. There could be differences in hue accuracy (color shift or not), in highlight detail, and other things. If you check out the AVSForum thread where we've been discussing all this for months, you'll find some movie scenes and HDR demos we like to use for comparing different tone mapping algorithms.

The tone mapping option was originally designed (I believe) with projectors in mind that don't necessarily have native HDR capability.
Not true.

On OLED, we have trouble getting high enough brightness in SDR mode
SDR is supposed to have peak white at around 100-200nits. Which is easy for OLED.

[alps006]

Well, AMD may be a piece junk for you but in my set up I have perfect 4K and 3D playback with RX-460 on Windows 10.I am using 18.5.1 driver and have not updated to new drivers as I am not having any issues. May I ask what issues you are having or had with AMD? If you are having issues, then I am 100% sure it's your own setup related, and AMD has got nothing to do with it. I am a proud user of AMD for years and it definitely isn't a piece of junk. AMD no issue? This is really bull-shit. AMD is a piece of junk.

[SamuriHL]

Not true.


Well....that's why I said (I believe). LOL


SDR is supposed to have peak white at around 100-200nits. Which is easy for OLED.

Ok, fair enough. That is definitely true for SDR.

[ryrynz]

Madshi, that OS API could be buggy or poorly optimized, have you inquired with MS about it? I wonder if 1809 has improved it.

Is there any proper test content one could use to roughly determine optimal peak nits for tone mapping?

[Klaus1189]

Well, AMD may be a piece junk for you but in my set up I have perfect 4K and 3D playback with RX-460 on Windows 10.I am using 18.5.1 driver and have not updated to new drivers as I am not having any issues. May I ask what issues you are having or had with AMD? If you are having issues, then I am 100% sure it's your own setup related, and AMD has got nothing to do with it. I am a proud user of AMD for years and it definitely isn't a piece of junk.

Same here :)

[ryrynz]

Please don't quote entire posts for two word replies. We know most AMD users are satisfied with their setups.

[mkohman]

Hi Guys,

Please forgive me if this has already been covered in a previous post but I need advice in some of MadVR features involving those who have a 2.39:1 scope screen with a projector.

I have recently changed my 16.9 setup to a 2.39:1 setup and built a new screen. Most of my movies (99%) that I watch on this setup are wide screen format and I use my JVC projector to zoom the top and bottom black bars away and fill the screen with the movie.

I notice that madVR has functions that may assistance with this setup under screen config and zoom control... Can someone with a similar setup who are using these features or someone who knows about these features and believe this may be helpful please assist me and give me some tips...

Also there is apparently a way to overcome the multi format movies (ie Nolan movies) what is the setting for that please?

Thanks I advance for all your help..

Sent from my moto g(6) using Tapatalk

[sat4all]

Maybe you're using madVR in FSE mode, and madTPG in windowed mode?


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:

[jerryleungwh]

I don't really understand what you're saying. The measurement functionality doesn't report anything to the TV, if that's what you're asking. It just changes madVR's tone mapping curves.

Oh sorry for not being very clear about it. I was just wondering, because the mapping curves are changed each frame accordingly, would it work like some HDR formats with dynamic metadata like Dolby Vision or HDR+?

Also, I just tested with passthrough and tone mapping with target peak nit at 800 in HDR mode and I noticed some of the bright lines could result in haloing while in passthrough, while tone mapping doesn't and seems to produce a more detailed image, but is also slightly dimmer than passthrough. I personally prefer tone mapping but I'll read more comments here to see what everyone else thinks before I settle down on the settings.

Correct me if I'm wrong but highlight recovery seems to be quite GPU intensive and more so on higher levels? I want to try the "are you nuts" setting because some other users here suggest it might work well in HDR tone mapping mode but with NGU sharp chroma upscaling and tone mapping together it's a bit too much for my gtx 1060 even when overclocked at +170 MHz core clock and +179 MHz memory clock

[ryrynz]

Sacrifice the chroma, it doesn't make that big a difference most times anyway, go to medium or low, doubt you'll notice the difference.. Personally I'd go NGU AA over sharp for chroma but your choice.

[mclingo]

If you are having issues, ...

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.

[Magik Mark]

Do we have any update on which Nvidia driver works best for custom resolution in Windows 10?

[mrmojo666]

Well, AMD may be a piece junk for you but in my set up I have perfect 4K and 3D playback with RX-460 on Windows 10.I am using 18.5.1 driver and have not updated to new drivers as I am not having any issues. May I ask what issues you are having or had with AMD? If you are having issues, then I am 100% sure it's your own setup related, and AMD has got nothing to do with it. I am a proud user of AMD for years and it definitely isn't a piece of junk.

totally agree and reading all the issues around with nvidia drivers....not sure which one is better. Sometimes i had to struggles with specific driver, but generally speaking all is more than good with amd
(win10 1803)

[Warner306]

Madshi, that OS API could be buggy or poorly optimized, have you inquired with MS about it? I wonder if 1809 has improved it.

Is there any proper test content one could use to roughly determine optimal peak nits for tone mapping?

I would set target nits to 480 nits and increase the backlight of your display until the image looks balanced. 480 nits is considered a neutral value for BT.2390 when it comes to compression. I've been using different backlight settings for SDR and HDR content, just adjusting this by remote before and after playback.

There is some more information on target nits in the link in my signature if you're interested.

[Warner306]

Do we have any update on which Nvidia driver works best for custom resolution in Windows 10?

All of the driver versions should work more or less the same. If one driver version doesn't work, try a different driver version. Also, some driver versions work for some but not others.

[khanmein]

Well, AMD may be a piece junk for you but in my set up I have perfect 4K and 3D playback with RX-460 on Windows 10.I am using 18.5.1 driver and have not updated to new drivers as I am not having any issues. May I ask what issues you are having or had with AMD? If you are having issues, then I am 100% sure it's your own setup related, and AMD has got nothing to do with it. I am a proud user of AMD for years and it definitely isn't a piece of junk.

Well, NVIDIA also don't have issues, so it might be your own personal issue. We all know that NVIDIA is always performed better when using madVR + MPC.

So far the issue that I always complained is related to FSE mode. I don't even want to use AMD #poorpeople. No offense, but I really don't want to argue with you.

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.

[mclingo]

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.

[aufkrawall]

Windows 10 surely doesn't help to stabilize drivers.
That said, I neither experienced any driver related madVR issue with my RX 560 nor with my 1070 Ti this year. "Good" ol' 8 bit DVI output...

[mclingo]

We can all agree on that I think, all this AMD vs NVIDIA is a bit pointless, especially the power vs poverty argument as that is the most irrelevant one as everyone has different needs, stability over power every time for me, I oculd have bought a more expensive NVIDIA card when I got me RX580 but I cant live without native 23,976 support and the stability AMD provide with 3D playback as I am a 3D superfan.

[SamuriHL]

I'm seriously looking into the possibility of rolling back to Win 8.1 on my HTPC. I didn't think I'd be able to originally but the more I look into it and the things I use, I think it's more possible than I thought. I already backed up my Win 10 with fall update installation so I just need a couple hours to pull the trigger and see how stable it is compared to what I have now. The fact that we have to continue to play these driver games is annoying. That's on MS not AMD or nVidia.

[mclingo]

If the AMD situation ever gets like that I think i'll drop back as well, have you not thought about switching to RED just to see what life on the other side of the tracks?

[SamuriHL]

Many years ago I was a huge AMD fan but nVidia surpassed them a long time ago. I've no real desire to go back. AMD has their own headaches. I know you've no issue with them and that's excellent. I'm not discounting that at all. I just have zero desire to switch away from nVidia at this point. I suspect that if I get back to 8.1 this week things will probably be a lot better HTPC wise with madvr.