madVR - high quality video renderer (GPU assisted)

[Uoppi]

25 fps variable frame rate (according to Mediainfo) gets shown as 60 Hz, when using the "deint=Off" tag (smooth motion is off). Up until now, I don't think madVR has ever struggled with setting the correct refresh rate with variable frame rate.

On a more general level, a few times now I've seen the refresh rate being doubled, even though deinterlacing is off. I don't think that ever happened before, i.e. my TV's refresh rate previously remained at 24/25/30 Hz with 23.976 to 30 fps non-interlaced material. Have some changes been made recently to what values get shown in "Display" and "Composition rate"? At least previously they were showing the actual fps of the video file, not doubling it unless using deinterlacing or smooth motion.

[huhn]

do you have a sample? and media info is not 100% correct.

[Stereodude]

Off-topic, but wow.... ripping with HEVC produces BETTER image quality at HALF the size than ripping with medium-high quality h.264, but at the same time it seems kind of a tiny bit smoother-smeared looking, different from h.264, with less noise for sure.
That's not an entirely accurate summary. For UHD/4k content, yes, it's supposed to deliver equal results at half the bitrate. Does it? That's the design target of the codec. That doesn't mean it is delivering on the target today.

Is HEVC expected to become the future for both 4K and 1080p content? That leaves everyone without GTX 950/960 at a pretty big disadvantage unless they plan on upgrading GPU when Pascal and AMD's new cards come out...
The standard for what? 1080p Blu-ray is obviously going to stay H.264. Will the "scene" pirate rippers move to HEVC? No idea, and I don't care. HEVC doesn't have the same sort of bitrate savings at 1080p against H.264 that it does for UHD/4k and the amount of devices, phones, tablets, etc. in people's hands that support H.264 and not HEVC means H.264 should be around for a long time.

And why are we having this discussion in the madVR thread?

[XTrojan]

Does 3D subtitles work on all subtitles or does it need to contain 3D depth info (which only mkvmerge can get?)

[James Freeman]

Fellows, AACS 2.0 is not going to be decrypted anytime soon so it is pointless to prepare to watch UHD discs on our HTPCs.
I bought Spider-Man 2 4k UHD to experiment with madVR and compare versions only to realize it will be dusting on the shelf for a very long time...
Bummer :(

[flashmozzg]

Fellows, AACS 2.0 is not going to be decrypted anytime soon
Why you say that?

[sneaker_ger]

See and discuss here:
http://forum.doom9.org/showthread.php?t=173234

[hu1kamania]

Actually if you could do that with your previous screenshot (Smaug on his treasure) that'd be great.

Same settings as earlier, here is a before and after doubling, with no refinements, aside from SR2:

http://screenshotcomparison.com/comparison/163469

A better example of SuperSampling without refinements :)

[Nevilne]

Likely just shows that you're doubling in gamma and downscaling in linear light.
In addition, if you make screenshots with sharpening filters, they will probably have different strengths on different resolutions.

[hu1kamania]

Likely just shows that you're doubling in gamma and downscaling in linear light.
In addition, if you make screenshots with sharpening filters, they will probably have different strengths on different resolutions.

This was purely to show that positive results can be had with super sampling. Doubling 1080p and bringing it back to 1080p.

This wasn't available in previous versions of MadVR.

The only refinement was SR2, no other sharpening filters.

[ryrynz]

Likely just shows that you're doubling in gamma and downscaling in linear light.


Interesting point. If we're supersampling with NNEDI3 should we be downscaling in linear light?

Do you think there is there much point in allowing supersampling with the other scalers madshi? I suspect NEDI, NNEDI3 and super-xbr probably have us covered.

[madshi]

When I said your edge enhancement was the best I've seen I was only referring to actual edge enhancements like Adaptive Sharpen and the sharperning setting on my TV.

Reality Creation is not a real edge enhancement, it's a sort of intelligent high frequency booster. I wasn't a big fan of this filter on my Sony KDL-40W905A because it was associated with a denoiser filter (useful for DVD but I don't want that for Blu-Ray) and I've never found a setting that didn't boost also the flaws in the picture.

But Sony has made great progress and now the results are pretty impressive, I actually found a low setting that never harmed the picture (well, nothing I've seen so far). And like your idea, it works differently based on the resoltion of the picture (if you let the TV make the upscale of course). I don't know if it's thanks to the improve database but I like this filter now.
Too bad you can't do proper screenshots of what the Sony does. Would like to see it.

I'm not sure about that one since the clips is 24/1.001Hz and so was my refresh rate. I tested again last night and confirmed several times that I can play the clip with 0 dropped frames if "don't rerender frames when fade in/out is detected" is checked. With it unchecked I always get dropped frames (in the same spots) and they appear to coincide with fades in the video. :confused: Are the internal rendering paths different when that option is checked?
It is quite possible that the feature still makes problems. But the log you created didn't seem to contain frame drops caused by the feature. My best guess right now is that you got frame drops for other reasons in that log and maybe stopped playback too early to get the frame drops caused by fade detection. So maybe you can try again creating another log, or two, and maybe let it run a bit longer and let a few more frame drops happen, for which you're sure they're caused by fade detection.

Interesting addition, wondering which algorithm combination will work for 4k YouTube.
Or do it even give benefit vs just doing image enhancements. YouTube really need some sharpening~.
Sharper downscaling should already help a lot. If you want cheap performance with sharp downscaling, try Bicubic150.

.11 Not only had black OSD for me, it also played the video with an all black screen, until i resized or full screened the video.

.12 didnt fix the black screen issue

edit: It also depends on the video.. Some open to a black screen while others do not.

edit2: One difference I see with the problem files is that they are 1280x718
I have the same problem on an amd 290. I find that changing the image doubling from NNEDI3 to anything else fixes it.
Can you guys upload a small sample, together with your "settings.bin" file and a screenshot of the black screen with the Ctrl+J OSD turned on? Maybe also a debug log would help. Thanks!

Using the rate of frames that madVR gets as input would be more consistent with the values reported by other renderers, and imo be more useful information wise. For example if I play at 2x speed, the reported value doubles with the other renderers.
Other renderers also seem to use less values for calculating the average, so they converge faster to the current rate. Vanilla EVR even resets the calculation when changing the playback speed.
Ok, but do you actually make use of this information for anything important? Or is it just a cosmetical issue? I've so many things on my plate right now that I'd like to pass on cosmetical stuff atm.

I have created a little introductory page on my project's main page, on how to properly install and set madVR for best experience, especially a few tips for when using laptops.

I found myself in a pinch because of Nvidia Optimus, but now I seem to have figured out that there were a few simple tricks to be done.
Your images don't work for some reason. Can you do a very short summary of which tricks you had to use exactly to make Optimus work better?

By the way, while looking at this pattern (once I had solved the scaling issue), some of the new chroma upscaling algos fail this test. For example, reconstruction soft fails and Super-XBR above 75 significantly raises the brightness in a way which can't be good or accurate, even if it does look sharper.
Which test pattern is that? It's always "dangerous" to base test results on just one test pattern. I've seen different chroma upscaling algorithms do very bad on one test pattern and then suddenly very good on another. So judging final chroma upscaling quality is pretty hard to do.

Yes, I know about these settings in the player, as I say they have NOTHING to do with MadVR's decision to rescale a frame if it has black borders when the auto A/R is enabled. My player is set to normal size, no zoom, original A/R etc, and if I switch to EVR-CP (or if I switch MadVR's auto A/R off), as mentioned earlier, there is no scaling/zooming problem (but then of course, there is no auto A/R from MadVR).
Sure, here are two screenshots and the auto AR options:

Auto AR off: https://www.dropbox.com/s/hzek8rabi5ftemw/MadVR%20Auto%20AR%20off.png?dl=0Auto
AR on: https://www.dropbox.com/s/aiwl6wnldjdxi89/MadVR%20Auto%20AR%20On.png?dl=0
A/R options: https://www.dropbox.com/s/jom6ms9kr7wynhg/MadVR%20Auro%20AR%20Options.png?dl=0

My player is always set to 100% / no zoom. The issue goes away if I deselect the black bar detection in MadVR or if I switch to EVR-CP in MPC-BE.
Thanks, I fixed the link.

Video frame is set to touch window from the inside and keep aspect ratio. That's the way it should be.
Your posts are somewhat contradicting. Sometimes you say you have set the player to "100% / no zoom", and sometimes to "touch window from inside", which are 2 very different settings (only if the cropped video resolution doesn't match the screen resolution, though).

Generally, madVR tries to understand what the media player wants, which should be what *you* want, because the media player is supposed to have control over zooming behaviour. Things are rather complicated, though, because the whole "zoom control" settings somewhat conflict with that approach.

Anyway, if the media player is set to "100% / no zoom", and if madVR understands that, then madVR will not zoom, even if you activate any of the madVR zoom control settings. So if you really do not want madVR to do any zooming, then please set your media player to "100% / no zoom". However, and here comes a small catch: Only MPC-HC so far really tells madVR which zoom setting is active in the media player. All other players (including MPC-BE) do not do that, although I asked the devs to, so for all other players madVR has to guess the media player zoom mode. And that doesn't always work reliably. E.g. if you play a 1080p movie on a 1080p display, "100%" and "touch window from inside" have the same effect. In this situation madVR isn't able to guess properly which zoom mode the media player is set to. In this situation MPC-HC produces the best results because it reliably tells madVR which zoom mode the user has selected.

You can work around the issue by activating "crop black bars" *and* "notify media player [...]". This combination of settings results in the media player being forced to send a proper zoom rectangle to madVR which allows it to do a better guess which zoom settings your media player is set to. So if you're using MPC-BE, set it to 100% and activate those 2 madVR settings and you should be set.

Of course setting your media player to 100% means SD stuff is not upscaled, anymore... :(

madVR since 0.90.11 has crashed w/ Skylake iGPU (HD 520) on videos with dimension 702x480. Default settings, 64-bit.
Crash report?

Madshi, can make it multithreaded, since especially 4k can profit of the cropping feature?
It's on my to do list.

Could someone clarify what "crop black bars" is supposed to do? Should it zoom/scale the bars away or keep them visible (providing player is not set to zoom and madVR is set to lose no image content)?
"crop black bars" physically removes the black bars, so madVR has less pixels to work with. Should improve performance a bit, and of course logos (and hard coded subtitles!) are cut off, too.

If you disable "crop black bars", the image should still be shown with the same (or nearly the same) zoom factor and position, but the black bars are not physically cut off, so if you manually zoom out, logos and subtitles in the black bars are visible again.

depends.

but in most cases you have to scale the image more which could be slower.
I think there should always be a (small) performance benefit. Scaling factor should not be affected. The media player might change the window size, though (if "notify media player" is activated), which *may* affect scaling factor, once again. <sigh> Complicated...

What do i need to watch hdr with madVR if my TV is 10 bit and WCG?

- Last LAV nightly build
- Setting madVR ex. fullscreen+d3d11+10 bits and (?) DCI P3 in set is already calibrated
- Maximizin luminance and contrast TV setting(?)
- Setting TV WCG
- Ajusting madVR nits

With this settings i think madVR will send 10 bits DCI P3 (REC 2020) with dinamic range compressed to luminance settings. Am i correct?

What about PQ EOTF (ST 2084)? What does madVR with it?
Sounds about right. 10bit output is not really necessary, thanks to high quality dithering 8bit should suffice, but of course 10bit doesn't harm, either. Currently madVR always converts the PQ EOTF to a gamma curve. Whether your screen really supports full 10bit is something you might want to test. Simply use some test pattern to check whether you get less banding letting madVR output 10bit or 8bit.

I'm seeing an insignificant performance boost so I've decided to just disable "crop black bars".

Half of the time I don't even understand why madVR is scaling, so I guess I'm better off not using that feature, LOL. For example, because of the scaling, some videos even end up playing under a different/unexpected madVR profile (i.e. not the profile that would be used if "crop black bars" was disabled).
There are variations of the profile vars available if you want profiles to be selected according to the original resolution (before cropping). E.g. you can use "uncroppedSrcWidth" instead of "srcWidth".

25 fps variable frame rate (according to Mediainfo) gets shown as 60 Hz, when using the "deint=Off" tag (smooth motion is off). Up until now, I don't think madVR has ever struggled with setting the correct refresh rate with variable frame rate.
"shown as" (meaning listed in the OSD) or "shown at" (meaning actual GPU output is) 60 Hz? Maybe a screenshot of the OSD could help clarify that, together with a list of your madVR display mode switching settings.

On a more general level, a few times now I've seen the refresh rate being doubled, even though deinterlacing is off. I don't think that ever happened before, i.e. my TV's refresh rate previously remained at 24/25/30 Hz with 23.976 to 30 fps non-interlaced material. Have some changes been made recently to what values get shown in "Display" and "Composition rate"? At least previously they were showing the actual fps of the video file, not doubling it unless using deinterlacing or smooth motion.
Again I'm not sure what you mean. E.g. are you just talking about some numbers in the OSD, or are you talking about the actual refresh rate the GPU is outputting?

Does 3D subtitles work on all subtitles or does it need to contain 3D depth info (which only mkvmerge can get?)
Should work on all subtitles, even external SRT files, as long as you use the latest nightly LAV build. However, without the proper Blu-Ray playlist madVR receives a bunch of depth information without knowing which of that is meant for which subtitle track or which is meant for OSD etc. In that situation madVR will "guess" which depth (out of all the depths it receives) is likely to be a reasonable choice. Only when the playlist is available, LAV/madVR know exactly which depth information was meant for exactly the one subtitle track you've selected.

Do you think there is there much point in allowing supersampling with the other scalers madshi?
I considered it, but found no good way to offer it in the settings dialog. Maybe some time in the future.

[madshi]

When releasing v0.90.11 about a week ago I asked you guys for feedback about the following things:

1) Agressive downscaling anti-ringing filter: Is it working well for you, or do you see any problems?
2) New sharpening anti-ringing filter: Is it working well for you, or do you see any problems?
3) crispen edges: Do you prefer the linear light option to be enabled or disabled?

So far from what I remember I've received zero feedback about any of that. Of course you don't *have* to provide feedback, but if you don't, then I get the impression that I develop too fast for you guys to keep up. Which means I'd have to slow down development accordingly to allow you to catch up. Your choice... ;)

[clsid]

Ok, but do you actually make use of this information for anything important? Or is it just a cosmetical issue? I've so many things on my plate right now that I'd like to pass on cosmetical stuff atm.It's not important. Put it somewhere low on the todo list.

[hu1kamania]

When releasing v0.90.11 about a week ago I asked you guys for feedback about the following things:

1) Agressive downscaling anti-ringing filter: Is it working well for you, or do you see any problems?
2) New sharpening anti-ringing filter: Is it working well for you, or do you see any problems?
3) crispen edges: Do you prefer the linear light option to be enabled or disabled?

So far from what I remember I've received zero feedback about any of that. Of course you don't *have* to provide feedback, but if you don't, then I get the impression that I develop too fast for you guys to keep up. Which means I'd have to slow down development accordingly to allow you to catch up. Your choice... ;)

The most testing I did was with SuperSampling, and these were my preferred settings:

Image Downscaling: SSIM 1D 100% AR LL
Image Upscaling: Jinc AR
Image Doubling: NNEDI3, 32
Upscaling Refinement: Crispen edges: 1.0 w/ Linear Light and AR
Upscaling Refinement: Enhance detail: 1.0
Upscaling Refinement: SuperRes: 2 w/ linear light
Chroma Upscaling: NNEDI3 32

The short answer would be that I prefer the new settings.

I've been using them when applicable, I don't always refine with crispen edges. Hopefully the experts weigh in with a more detailed analysis!

[Sparktank]

I use:
chroma > ReconSoft (SR3)
luma < SSim 1D200 AR LL
Upscaling Refinement: AR ~2x
Crispen edges: 1.0 LL
SR3 LL
Image Enhancements: AR
CE LL

and it hasn't blown up the computer (yet). On bluray remuxes.
That's including using SVP to interpolate to double framerates. (at ~48)

[neno]

Hi, madshi:
There is a problem when I use madvr.(I tried the lastest version madvr and several players like MPC-BE and potplayer. Nothing changes. This problem disappears when I use other renderers, or change my videocard from R260X to GTX950.)
The problem is: the topmost line and the leftmost line of the video picture seems strange. For example, when the whole picture changes from white to black, the topmost line and the leftmost line keep white a few seconds and then gradually change to black with flash, just like they can not keep pace with the whole picture.
I tried to change some settings like scaling in madvr, and still can not solve it.
Can you please give me some suggestions? Thanks!

[6233638]

1) Agressive downscaling anti-ringing filter: Is it working well for you, or do you see any problems?I've just spent a good few hours doing testing with downsampling - mainly looking at Blu-rays instead of test patterns - and what I've seen so far is that the anti-ringing filter is massively improved.
Something may show up in artificial tests, but nearly every filter is now a viable option with linear light downscaling with the new anti-ringing filter, and I haven't noticed any drawbacks.

And speaking of downscaling, SSIM seems like a pretty good option.
Personally I think it's a bit sharp - especially on fine details - as aliasing can appear, but at the same time that kind-of seems to be the point of it. Get the image as sharp as can be, without adding any ringing.
I don't know if something like a 10% or 15% option might be possible, but if I'm not looking at it with a critical eye, 1D 25% looks pretty good most of the time, with the exception of very detailed/busy shots, or bad sources which already contain some degree of ringing.

[madshi]

It's not important. Put it somewhere low on the todo list.
Ok, will do.

The most testing I did was with SuperSampling, and these were my preferred settings:

Image Downscaling: SSIM 1D 100% AR LL
Image Upscaling: Jinc AR
Image Doubling: NNEDI3, 32
Upscaling Refinement: Crispen edges: 1.0 w/ Linear Light and AR
Upscaling Refinement: Enhance detail: 1.0
Upscaling Refinement: SuperRes: 2 w/ linear light
Chroma Upscaling: NNEDI3 32

The short answer would be that I prefer the new settings.

I've been using them when applicable, I don't always refine with crispen edges. Hopefully the experts weigh in with a more detailed analysis!
I use:
chroma > ReconSoft (SR3)
luma < SSim 1D200 AR LL
Upscaling Refinement: AR ~2x
Crispen edges: 1.0 LL
SR3 LL
Image Enhancements: AR
CE LL

and it hasn't blown up the computer (yet). On bluray remuxes.
That's including using SVP to interpolate to double framerates. (at ~48)
Thanks guys. Did you have a chance to compare Crispen edges with Linear Light and/or AR turned on vs off? Did you like LL on better? Or was turning on LL more of a "random" choice?

There is a problem when I use madvr.(I tried the lastest version madvr and several players like MPC-BE and potplayer. Nothing changes. This problem disappears when I use other renderers, or change my videocard from R260X to GTX950.)
The problem is: the topmost line and the leftmost line of the video picture seems strange. For example, when the whole picture changes from white to black, the topmost line and the leftmost line keep white a few seconds and then gradually change to black with flash, just like they can not keep pace with the whole picture.
I tried to change some settings like scaling in madvr, and still can not solve it.
Can you please give me some suggestions? Thanks!
That sounds quite weird, haven't ever heard of something like this before. Are you using any sort of hardware decoding? E.g. CUVID, native DXVA or copyback DXVA? If so, try software decoding to make sure it's not caused by hardware decoding.

I've just spent a good few hours doing testing with downsampling - mainly looking at Blu-rays instead of test patterns - and what I've seen so far is that the anti-ringing filter is massively improved.
Something may show up in artificial tests, but nearly every filter is now a viable option with linear light downscaling with the new anti-ringing filter, and I haven't noticed any drawbacks.
Wonderful, very helpful feedback! And of course I very much like your findings! :) So you did not find any aliasing caused by the new AR? What is your opinion about LL scaling now? I'm considering moving both LL and AR options for downscaling into the "trade quality for performance" section. Which would mean I'd consider highest quality to be achieved with both LL and AR turned on. Would you agree with that assessment?

Do you like sharpening algos? If not, I don't want to bother you with tests. But if you do, I'd like your feedback about Crispen edges linear light on vs off, and whether the sharpening AR filter works well for you or not.

And speaking of downscaling, SSIM seems like a pretty good option.
Personally I think it's a bit sharp - especially on fine details - as aliasing can appear, but at the same time that kind-of seems to be the point of it. Get the image as sharp as can be, without adding any ringing.
I don't know if something like a 10% or 15% option might be possible, but if I'm not looking at it with a critical eye, 1D 25% looks pretty good most of the time, with the exception of very detailed/busy shots, or bad sources which already contain some degree of ringing.
Ouch, I find 1D 25% already so low that it barely makes a difference for me. Do you really want/need less than that? It would not be a big problem to add, but I somewhat question if you'll see much of a detail improvement at all with such low values...

[Sunset1982]

"crop black bars" physically removes the black bars, so madVR has less pixels to work with. Should improve performance a bit

Ok, this has nothing to do with feedback to you actual features, but I find this one interesting so I'll post it.

Just did some testing with the crop black bars feature. Tested a 720p File which is upscaled to 2160p by my GTX960. Activating the crop black bars option brings me a better performance by 12ms rendering time.

man, thats a HUGE improvement!!! :eek: :thanks:

[huhn]

I think there should always be a (small) performance benefit. Scaling factor should not be affected. The media player might change the window size, though (if "notify media player" is activated), which *may* affect scaling factor, once again. <sigh> Complicated...

a 1080p 4/3 file with some letterbox 16/9 on a 1080p 16/9 screen is for sure not faster with black boarder detection.

and in the end the file should run without black boarder detection.
for a simple reason what if the file stops using black boarders?

that's why i would never recommend someone to use that potential extra processing power that is available when black border detection is cropping the image.

[leeperry]

I don't know if something like a 10% or 15% option might be possible, but if I'm not looking at it with a critical eye, 1D 25% looks pretty good most of the time, with the exception of very detailed/busy shots, or bad sources which already contain some degree of ringing.
Fully agreed, a lower strength than 25% would be most welcome and eventually ±1 increments would be the shiznit.

I find 1D 25% already so low that it barely makes a difference for me. Do you really want/need less than that? It would not be a big problem to add, but I somewhat question if you'll see much of a detail improvement at all with such low values...
Usual story that SR@1 is already very sharp so the goal would be to benefit from SSIM without the utter sharpness that comes with 25% in order to make the picture look more detailed than CR AR LL and yet not that sharp. I would myself either need softer SR strengths and/or softer SSIM.

[omarank]

When releasing v0.90.11 about a week ago I asked you guys for feedback about the following things:

1) Agressive downscaling anti-ringing filter: Is it working well for you, or do you see any problems?
2) New sharpening anti-ringing filter: Is it working well for you, or do you see any problems?
3) crispen edges: Do you prefer the linear light option to be enabled or disabled?

1) & 2) I have only tested with movie content and didn’t see any problem with the modified anti-ringing filters.

3) I prefer LL enabled with crispen edges. Previously too, I preferred finesharp with LL enabled before the LL option was dropped.

I've just spent a good few hours doing testing with downsampling
Have you tested Jinc downscaling? I would be interested to know your observations about Catmull Rom vs Jinc vs SSIM downscaling.

[Sparktank]

Thanks guys. Did you have a chance to compare Crispen edges with Linear Light and/or AR turned on vs off? Did you like LL on better? Or was turning on LL more of a "random" choice?

For me it was more of a random choice.
I'll have to check with diffrent types of movies to see if I can notice a difference with LL on or off.

So far, I don't see a difference if it's on or off.

Regardless of LL, madVR enchancements are making the horrid bluray transfer of Face/Off (1997) look better than a VHS upscale.

Once I get coffee going, I'll run some quick tests between the two to see if I see any real world differences.

[ang3l]

hi madshi

I'm experiencing an annoying bug with the latest version of madVR (MPC-HC.1.7.10.101.x86.VS2015 + MADV 0.90.12)

to reproduce the problem starting with the defaults settings (DX9 fullscreen exclusive)

you have to set image double and SSIM1D + antiringing as downscaler

then closing mpc with ctrl+c the program remains frozen and then I can just reboot my system

I tried on two pc with nvidia and amd and I have the same result so I think that system configuration isn't so important

it not happens with dx11 fullscreen exclusive, using SSIM1D without AR, or using any others downscaler with or without AR

[6233638]

Wonderful, very helpful feedback! And of course I very much like your findings! :) So you did not find any aliasing caused by the new AR?Well all of my testing was done with Blu-rays, and with that, things seemed to be ever so slightly sharper than they were before, but not necessarily more aliased.
When looking at very detailed/busy images, I'd almost say that you're best to use SoftCubic if your priority is to eliminate aliasing because it basically acts as a low-pass filter for the video. I've had a quick look over the sharpening tools and it seems that you can then sharpen this result to bring back some of the detail without introducing aliasing.
However, with a focus on sharpening tools for upscaling and SSIM for downscaling to make the image look very "detailed", I'm guessing that this is not the look most people want. I know that I was very unhappy with how strongly low-pass filtered and then oversharpened so many DVD releases were for example - though you can avoid the over-sharpening with madVR.
If you want that pixel-level detail which looks good in a static image, you're going to see aliasing when it moves in a video. You can't really get around that fact.

Here's an example from Oblivion which I think shows this off reasonably well. (http://www.filedropper.com/oblivion-aliasingsample) (note: my testing was at 50% scale)
Looking at the top-down shot at the chapter marker, if you compare SSIM at 25% to something like SoftCubic80+Sharpen Edges 0.5+Enhance Detail 1.5, there is dramatically lower aliasing in motion with the latter.
Of course the image is also lacking that really sharp and detailed look because the high frequency detail has been filtered out.
To be clear, those settings are not a recommendation for anyone, just a quick example of what I mean about the balance between aliasing/detail and the need for low-pass filtering (or similar) if you want to eliminate aliasing.
I'm not saying that there's anything wrong with SSIM or preferring that image though - it looks good for what it's trying to do, and for the type of content that I actually watch downscaled, it's very possible that I'll switch from Catmull-Rom over to SSIM.

I've had a look at the anti-ringing filter using proper test patterns now (such as a high-res star chart (http://abload.de/img/star-chart-bars-full-cxozp.png)) and I'd say that anti-ringing looks great for the cubic scalers.
It maybe adds a tiny bit of roughness at the very high frequency details, and Bicubic >60 could look a bit better, but I'd also not be recommending that people use the higher levels of Bicubic anyway.
For Lanczos/Spline/Jinc, it could stand to be a little bit more aggressive with linear light enabled. There are still some remnants of the dark ringing that you get with LL downscaling at some angles - though I never found it to be a problem with video.
With SSIM, anti-ringing is actually adding aliasing at all levels so that probably needs looked at. I thought I had seen this to some degree with some video clips, but assumed it was just because SSIM was so sharp - which was why I wondered if something like 10% SSIM might be an option.

What is your opinion about LL scaling now? I'm considering moving both LL and AR options for downscaling into the "trade quality for performance" section. Which would mean I'd consider highest quality to be achieved with both LL and AR turned on. Would you agree with that assessment?Absolutely. If you can make the tweaks that I mentioned above, other than the performance hit for enabling them, I see no reason why you wouldn't want to use them now that AR+LL works well with every scaling algorithm.

Do you like sharpening algos? If not, I don't want to bother you with tests. But if you do, I'd like your feedback about Crispen edges linear light on vs off, and whether the sharpening AR filter works well for you or not.Sorry, I've not really been using sharpening at all.
I did some tests when it was first introduced but my issue with sharpening has always been that it's not something I would ever want to apply globally.
It can help a bad source if you're tweaking it to be specific for that source, but always hurts a good source in my opinion.
And generally I find that a disc is either well mastered, or if it's not then it probably has a ton of sharpening already encoded in the video. There aren't many films in my library which just have a soft image.

If it was like debanding where I could hit a key to either toggle it on/off or perhaps switch between say three separate sharpening profiles I might be more inclined to use it.
That's not a feature request though, as I just don't think that sharpening is something I'd use much even if that were an option.

Ouch, I find 1D 25% already so low that it barely makes a difference for me. Do you really want/need less than that? It would not be a big problem to add, but I somewhat question if you'll see much of a detail improvement at all with such low values...If the aliasing with AR can be addressed, that may actually solve the problem instead of it needing to be less sharp - though if it's a small change, I'd still like to see how that looks.
At the same time, it's possible that SSIM just isn't what I'm looking for, so I may just be better off using another scaling algorithm instead of a reduced-strength SSIM.

Have you tested Jinc downscaling? I would be interested to know your observations about Catmull Rom vs Jinc vs SSIM downscaling.I didn't see much benefit to it compared against the other scalers to be honest. The difference may have been larger before the new anti-ringing filter was implemented?
I'd like to see examples if anyone has found cases where Jinc has made a difference though.

[Cudo]

When releasing v0.90.11 about a week ago I asked you guys for feedback about the following things:

1) Agressive downscaling anti-ringing filter: Is it working well for you, or do you see any problems?
2) New sharpening anti-ringing filter: Is it working well for you, or do you see any problems?
3) crispen edges: Do you prefer the linear light option to be enabled or disabled?

So far from what I remember I've received zero feedback about any of that. Of course you don't *have* to provide feedback, but if you don't, then I get the impression that I develop too fast for you guys to keep up. Which means I'd have to slow down development accordingly to allow you to catch up. Your choice... ;)
Seeing as my computer didn't blow up, probably everything is fine. :D

[Uoppi]

There are variations of the profile vars available if you want profiles to be selected according to the original resolution (before cropping). E.g. you can use "uncroppedSrcWidth" instead of "srcWidth".

:thanks: Cool! Sounds like "uncroppedSrcWidth" would do exactly what I need so I'll start using that instead.

Again I'm not sure what you mean. E.g. are you just talking about some numbers in the OSD, or are you talking about the actual refresh rate the GPU is outputting?

The numbers in the OSD as well as actual refresh rate the TV switched to. I've just never encountered a situation before where the refresh rate is doubled to 60 Hz (or 50 Hz for that matter) when it "shouldn't". But I guess that's a non-issue if frames simply get duplicated (30 Hz -> 60 Hz). Maybe it had something to do with a badly done variable frame rate encode with fluctuating fps (?). The VFR videos shot with my Galaxy Note 4 never produce this issue though, even if the fps is sometimes all over the place.

[madshi]

Just did some testing with the crop black bars feature. Tested a 720p File which is upscaled to 2160p by my GTX960. Activating the crop black bars option brings me a better performance by 12ms rendering time.
:)

a 1080p 4/3 file with some letterbox 16/9 on a 1080p 16/9 screen is for sure not faster with black boarder detection.
Black bar detection itself does not improve performance. But black bar detection with the additional option "crop black bars" activated should improve performance a bit - if there are black bars of noticeable size. Of course if you use cheap algos everywhere you might not notice. But if you do heavy lifting like NNEDI3 image doubling, you should notice a difference.

and in the end the file should run without black boarder detection.
for a simple reason what if the file stops using black boarders?

that's why i would never recommend someone to use that potential extra processing power that is available when black border detection is cropping the image.
99% of all Cinemascope Blu-Rays stay Cinemascope throughout the whole movie.

Anyway, whether it makes sense to setup a special profile to make use of the saved power is a question I don't want to answer. If all else fails, at least the GPU will consume less power, which is better for the environment, for your power bill and for fan noise.

1) & 2) I have only tested with movie content and didn’t see any problem with the modified anti-ringing filters.

3) I prefer LL enabled with crispen edges. Previously too, I preferred finesharp with LL enabled before the LL option was dropped.
K, thanks.

For me it was more of a random choice.
I'll have to check with diffrent types of movies to see if I can notice a difference with LL on or off.

So far, I don't see a difference if it's on or off.
If you can see a difference I'd like to hear which you prefer. Thanks.

I'm experiencing an annoying bug with the latest version of madVR (MPC-HC.1.7.10.101.x86.VS2015 + MADV 0.90.12)

to reproduce the problem starting with the defaults settings (DX9 fullscreen exclusive)

you have to set image double and SSIM1D + antiringing as downscaler

then closing mpc with ctrl+c the program remains frozen and then I can just reboot my system
FWIW, simply pressing Alt+F4 would have closed MPC-HC in this situation (at least it did for me). But thanks for letting me know, it was a resource leak and should be fixed in the next build.

Well all of my testing was done with Blu-rays, and with that, things seemed to be ever so slightly sharper than they were before, but not necessarily more aliased.
Ok, I like to hear that!

When looking at very detailed/busy images, I'd almost say that you're best to use SoftCubic if your priority is to eliminate aliasing because it basically acts as a low-pass filter for the video. I've had a quick look over the sharpening tools and it seems that you can then sharpen this result to bring back some of the detail without introducing aliasing.
Fair enough. But my main worry was that the AR algo would add introducing by itself, which would be quite bad. If that's not the case then at least I know that the AR algo itself works fine. Which algo combination the user might prefer for best sharpness vs lowest aliasing is something I'm worried about at this point. Just want to make sure that the more aggressive AR algo isn't harmful in any way.

I've had a look at the anti-ringing filter using proper test patterns now (such as a high-res star chart (http://abload.de/img/star-chart-bars-full-cxozp.png)) and I'd say that anti-ringing looks great for the cubic scalers.
It maybe adds a tiny bit of roughness at the very high frequency details, and Bicubic >60 could look a bit better, but I'd also not be recommending that people use the higher levels of Bicubic anyway.
For Lanczos/Spline/Jinc, it could stand to be a little bit more aggressive with linear light enabled. There are still some remnants of the dark ringing that you get with LL downscaling at some angles - though I never found it to be a problem with video.
The algo is currently very "logical" in its aggressiveness. I don't want to make it any more aggressive (for Lanczos/Spline/Jinc) because that would most probably introduce new problems. It's as aggressive as I feel reasonable safe to do.

With SSIM, anti-ringing is actually adding aliasing at all levels so that probably needs looked at.
Oh, that's exactly the kind of feedback I need!

I've been able to reproduce that somewhat with your star test pattern. Have added that to my to do list for maybe next weekend.

Seeing as my computer didn't blow up, probably everything is fine. :D
My question was not about performance but about image quality.

The numbers in the OSD as well as actual refresh rate the TV switched to. I've just never encountered a situation before where the refresh rate is doubled to 60 Hz (or 50 Hz for that matter) when it "shouldn't".
This all heavily depends on which frame rate the decoder/splitter reports to madVR. Usually this is out of my control. madVR makes its refresh rate decisions based on that information.

[madshi]

madVR v0.90.13 released

http://madshi.net/madVR.zip

* added support for finding the right 3D depth for the active subtitle track
* added "use alternative glitch handling mode" option for D3D11 presentation
* added a workaround for glitch problems with shaky 3D GPU drivers
* fixed: downscaling sometimes crashed, when not using SSIM
* fixed: Intel GPU always used DXVA scaling when DXVA deint/decode was active
* fixed: SSIM AR eventually left some resources open
3D users please make sure you use the very latest LAV nightly build, once more.

[Georgel]

This should be left on the first page as all Optimus laptops will have problems with mpc-hc + madVR.

The solution is quite simple.

First, you have to go to where mpc-hc is installed for example C:\Program Files (x86)\MPC-HC and rename your mpc-hc.exe to mpc-hc1.exe.

After this you have to go to Nvidia control panel -> Manage 3D settings -> Add, then browse to C:\Program Files (x86)\MPC-HC\mpc-hc1.exe and set to to use High performance Nvidia Processor.

I will add photos in here.

https://www.dropbox.com/s/khfwwz86cwf3k6v/12.png?dl=0

https://www.dropbox.com/s/7rrf8thbdjnwx9k/10.png?dl=0

https://www.dropbox.com/s/oog8l8150u47uti/11.png?dl=0

This should do the trick.

If power is anywhere under maximum performance, I experience -drops in performance. I am running an Acer VN7-791G with GTX860M and the latest Nvidia driver, 361.91.

[hu1kamania]

Thanks guys. Did you have a chance to compare Crispen edges with Linear Light and/or AR turned on vs off? Did you like LL on better? Or was turning on LL more of a "random" choice?

In my limited testing, I couldn't see much of a difference in Cripen Edges with Linear Light on and off. So I guess keeping it checked was more of a random choice.

With the AR filter from Refinements + Crispen Edges, I was able to detect a difference, and it was an improvement. Very subtle in my test though.

Edit: I'll have to take back what I said about Crispen edges and linear light. Depending on SR strength, I do see a difference and prefer it to be on with SuperSampling up until I hit SR4.

[mindz]

This has probably been asked before, but i couldnt find the answer.

When choosing super-xbr for chroma, why dont the sliders move when applying AR or choosing different sharpness? Do the changes have effect or dont they?

[mogli]

Before v0.90.13 madVR used DXVA image scaling while deinterlacing, now it uses the user chosen image scaler. Is this intentional or caused be the next to last fix (NVIDIA here, not Intel)?

[GCRaistlin]

99% of all Cinemascope Blu-Rays stay Cinemascope throughout the whole movie.

In my experience, there was at least one movie ("Gone Girl", 2014) that is 2,35:1 but switching for a couple of secs to 16:9. If set to crop black borders, madVR would simply cut such "non-standard" frames to 2,35:1 (unfortunately I don't have this movie anymore so I can't check myself)?

[6233638]

The algo is currently very "logical" in its aggressiveness. I don't want to make it any more aggressive (for Lanczos/Spline/Jinc) because that would most probably introduce new problems. It's as aggressive as I feel reasonable safe to do.That's fair. Though most of my testing was focused on cubic/SSIM downscaling, I did not see it as being a problem with the Blu-rays that I tested, so it's probably more of a theoretical issue.
As I said before, they're massively improved now - to the point that people should be able to use linear light downscaling with any of them based on their preference.

[Warner306]

I've only used crispen edges. The new anti-ringing may be a small improvement with a slight decrease in performance. But I wasn't overly bothered by crispen edges before. I haven't checked sharpen edges.

I don't see any improvement using linear light.

[Warner306]

I was browing this: Dolby Vision Whitepaper (http://www.dolby.com/us/en/technologies/dolby-vision/dolby-vision-white-paper.pdf).

I am wondering what the CPU/GPU cost is of decoding the enhancement/HDR layer (HDR10)? My system can't handle high-bitrate HEVC, so it is difficult to tell what is going on.

[Cudo]

This should be left on the first page as all Optimus laptops will have problems with mpc-hc + madVR.

The solution is quite simple.

First, you have to go to where mpc-hc is installed for example C:\Program Files (x86)\MPC-HC and rename your mpc-hc.exe to mpc-hc1.exe.

After this you have to go to Nvidia control panel -> Manage 3D settings -> Add, then browse to C:\Program Files (x86)\MPC-HC\mpc-hc1.exe and set to to use High performance Nvidia Processor.

I will add photos in here.

https://www.dropbox.com/s/khfwwz86cwf3k6v/12.png?dl=0

https://www.dropbox.com/s/7rrf8thbdjnwx9k/10.png?dl=0

https://www.dropbox.com/s/oog8l8150u47uti/11.png?dl=0

This should do the trick.

If power is anywhere under maximum performance, I experience -drops in performance. I am running an Acer VN7-791G with GTX860M and the latest Nvidia driver, 361.91.
Here's a better way to get to what you have done.

Download Nvidia Inspector:
http://www.techspot.com/downloads/5077-nvidia-inspector.html
Click the Profile Settings button:
http://i.imgur.com/gLvT5wB.png
In the Profiles box, select Media Player Classic
Scroll down to "Common" (Blue text with a horizontal line)
Under Common you will see "Power management mode"
To the right of that you will see "Adaptive"
Click in that box and select "Prefer maximum performance"
Scroll down to "Other" (Blue text with a horizontal line)
Under Other you will see "Enable application for Optimus"
To the right of that you will see a bunch of capital letters
Click in that box and select SHIM_RENDERING_MODE_ENABLE
Click Apply Changes

[madshi]

First, you have to go to where mpc-hc is installed for example C:\Program Files (x86)\MPC-HC and rename your mpc-hc.exe to mpc-hc1.exe.

After this you have to go to Nvidia control panel -> Manage 3D settings -> Add, then browse to C:\Program Files (x86)\MPC-HC\mpc-hc1.exe and set to to use High performance Nvidia Processor.

If power is anywhere under maximum performance, I experience -drops in performance. I am running an Acer VN7-791G with GTX860M and the latest Nvidia driver, 361.91.
Here's a better way to get to what you have done.

Download Nvidia Inspector:
http://www.techspot.com/downloads/5077-nvidia-inspector.html
Click the Profile Settings button: [...]

In the Profiles box, select Media Player Classic
Scroll down to "Common" (Blue text with a horizontal line)
Under Common you will see "Power management mode"
To the right of that you will see "Adaptive"
Click in that box and select "Prefer maximum performance"
Scroll down to "Other" (Blue text with a horizontal line)
Under Other you will see "Enable application for Optimus"
To the right of that you will see a bunch of capital letters
Click in that box and select SHIM_RENDERING_MODE_ENABLE
Click Apply Changes
Ok, thanks!

In my limited testing, I couldn't see much of a difference in Cripen Edges with Linear Light on and off. So I guess keeping it checked was more of a random choice.

With the AR filter from Refinements + Crispen Edges, I was able to detect a difference, and it was an improvement. Very subtle in my test though.

Edit: I'll have to take back what I said about Crispen edges and linear light. Depending on SR strength, I do see a difference and prefer it to be on with SuperSampling up until I hit SR4.
I've only used crispen edges. The new anti-ringing may be a small improvement with a slight decrease in performance. But I wasn't overly bothered by crispen edges before. I haven't checked sharpen edges.

I don't see any improvement using linear light.
Ok, thanks for your feedback!

That's fair. Though most of my testing was focused on cubic/SSIM downscaling, I did not see it as being a problem with the Blu-rays that I tested, so it's probably more of a theoretical issue.
As I said before, they're massively improved now - to the point that people should be able to use linear light downscaling with any of them based on their preference.
Good to know, thanks!

This has probably been asked before, but i couldnt find the answer.

When choosing super-xbr for chroma, why dont the sliders move when applying AR or choosing different sharpness? Do the changes have effect or dont they?
They do, but all the settings are changing all the time, and results are different in different test patterns, so I don't always get around updating the sliders, and they're a VERY rough estimate, anyway. Don't put too much weight into them.

Before v0.90.13 madVR used DXVA image scaling while deinterlacing, now it uses the user chosen image scaler. Is this intentional or caused be the next to last fix (NVIDIA here, not Intel)?
The changelog only mentions Intel, but it also applies to NVidia, and yes, it's an intentional change. Actually it was a bug that the chosen image scaler was *not* used. If you like it to be used, you can always manually select it. I'll change the changelog.

In my experience, there was at least one movie ("Gone Girl", 2014) that is 2,35:1 but switching for a couple of secs to 16:9.
There are a couple of IMAX movies, which switch between Cinemascope and 16:9, but those are not too common.

If set to crop black borders, madVR would simply cut such "non-standard" frames to 2,35:1 (unfortunately I don't have this movie anymore so I can't check myself)?
The exact behaviour depends on the "zoom control" settings. You can define exactly what you want madVR to do in such a situation. There are dedicated options for exactly this sort of thing.

I was browing this: Dolby Vision Whitepaper (http://www.dolby.com/us/en/technologies/dolby-vision/dolby-vision-white-paper.pdf).

I am wondering what the CPU/GPU cost is of decoding the enhancement/HDR layer (HDR10)?
How should anybody know? There's no real technical information available. Whitepapers are mostly useless.

[Warner306]

Ok, thanks!

How should anybody know? There's no real technical information available. Whitepapers are mostly useless.

I was referring to the current implementation of HDR content mapping. Does this require a lot of CPU/GPU resources to decode?

I was curious if the Dolby Vision approach adds a bunch of overhead with little improvement in picture quality.

I think HDR content looks pretty good on my 1080p display, but the availability of content and the need for a new graphics card make it unappealing right now for HTPC use.

[madshi]

Decoding the base layer does not cost anything extra over SDR. HDR content mapping is done by the GPU (when using madVR), so it costs some GPU performance, but no CPU performance. How much GPU? I don't know, you can test that using the Exodus/Life of Pi HDR demo clips, if you want to know.

[ryrynz]

madVR since 0.90.11 has crashed w/ Skylake iGPU (HD 520) on videos with dimension 702x480. Default settings, 64-bit.

Yup, that'll be the same problem already reported a few times, I suspect it'll be fixed in the next version.

Madshi, this is till happening on my 960 using latest drivers with similar resolution content with .13. Tried earlier drivers, still crashes.

Occurs when I play this (https://mega.nz/#!rI5BRRqD) and have NNEDI3 enabled (doubling or quadrupling) and downscale into a window. .10 doesn't crash.

[FDisk80]

* added "use alternative glitch handling mode" option for D3D11 presentation

What does this do?

[ryrynz]

Another issue, when typing in a profile, group name & rules under devices each key press takes me to color and gamma, so I have to click back on the profile/group name etc after each key press to finish typing.

[jmelan]

It works on mine GF980 + ASUS VG278.

Switching to Fullscreen Exclusive and back takes ages(maybe 10 seconds).
Switching from Windowed to Fullscreen Windowed takes 1-3 seconds and sometimes during this time temporary switches left/right image. 20-80 dropped frames.
Regular resizing is instantaneous, 2-4 dropped frames.

MPC HC x32 1.7.10
LAV 0.67.0.126-git
madVR 0.90.12

P.S. Switching any non-3D video from windowed to fullscreen windowed crashes the player.
It's happening only in the case of non-3D video on stereoscopic 3D-mode screen.
3D on 3D ok
3D on non-3D ok, image SBS.
non-3D on non-3D ok.

Thanks!

testing out 3d playback:

win 10
gtx 970
nvidia 3d vision
asus rog pg278q monitor (nvidia 3d vision, 2560x1440 native)

mvc in mkv test file (created with makemkv) works fine on stereoscopic player

however with:
MPC-HC x64 1.7.10
LAV nightly 0.67.0.136
madvr 0.90.13

3d appears to trigger (nvidia ir emitter lights up) but must be out of sync with nvidia 3d vision as all images are still double

I do not see a way to select 120 hz frame sequential or Nvidia 3d vision in the monitor "3D format" properties. Is nvidia 3d vision supported?

thanks!

...i am also getting crashing of MPC-HC when 2d content is switched from windowed to fullscreen when stereoscopic 3d is enabled in the nvidia control panel
- it also only occurs on my 3d enabled monitor but not my 2D monitor
- does not crash when I change from madVR to EVR in MPC-HC

[Warner306]

Decoding the base layer does not cost anything extra over SDR. HDR content mapping is done by the GPU (when using madVR), so it costs some GPU performance, but no CPU performance. How much GPU? I don't know, you can test that using the Exodus/Life of Pi HDR demo clips, if you want to know.

Thanks for the clarification.

Can/will madVR decode Dolby Vision?

[Warner306]

What does this do?

Yes, "glitch handling mode" implies poor workmanship.

[ryrynz]

What does this do?

Probably this.


* added a workaround for glitch problems with shaky 3D GPU drivers

[madshi]

Madshi, this is till happening on my 960 using latest drivers with similar resolution content with .13. Tried earlier drivers, still crashes.

Occurs when I play this (https://mega.nz/#!rI5BRRqD) and have NNEDI3 enabled (doubling or quadrupling) and downscale into a window. .10 doesn't crash.
mega doesn't let me download that file without some sort of crypt key.

* added "use alternative glitch handling mode" option for D3D11 presentation
What does this do?
With that option unchecked, when using D3D11 presentation, madVR detects presentation glitches the way Microsoft recommends. Unfortunately that has proven to be sometimes problematic, because it relies on GPU drivers reporting proper and reliable presentation statistics, and GPU drivers don't seem to always report that properly, especially for 3D playback. So this new option activates a different method to detect presentation glitches, which is basically the same solution I've been using for D3D9 for years. For now the new option is just for testing, but I might force it on in a future version if it proves to work well.

So if you don't mind, try turning it on and see if you can find any difference (positive or negative). In most cases you should probably not notice any difference.

Oh yes, there were some users who had problems with presentation queues not properly filling, e.g. when using 10bit output. I think this new option *may* work around that. But if it does, I wonder if it affects audio/video sync?

Another issue, when typing in a profile, group name & rules under devices each key press takes me to color and gamma, so I have to click back on the profile/group name etc after each key press to finish typing.
Yeah, it's on my to do list.

testing out 3d playback:

win 10
gtx 970
nvidia 3d vision
asus rog pg278q monitor (nvidia 3d vision, 2560x1440 native)

mvc in mkv test file (created with makemkv) works fine on stereoscopic player

however with:
MPC-HC x64 1.7.10
LAV nightly 0.67.0.136
madvr 0.90.13

3d appears to trigger (nvidia ir emitter lights up) but must be out of sync with nvidia 3d vision as all images are still double

I do not see a way to select 120 hz frame sequential or Nvidia 3d vision in the monitor "3D format" properties. Is nvidia 3d vision supported?
I don't do anything specific to support NVidia 3D Vision specific hardware. All I'm doing is using the OS 3D APIs to do 3D playback. Whether that works or doesn't work with NVidia 3D Vision hardware I can't say. If it doesn't work then there's not much I can do about it. I'm probably not going to add extra code for a proprietary NVidia solution. You could ask NVidia about it. I think they should be able to make it work for NVidia 3D Vision hardware. After all I'm using the official OS 3D APIs.

...i am also getting crashing of MPC-HC when 2d content is switched from windowed to fullscreen when stereoscopic 3d is enabled in the nvidia control panel
- it also only occurs on my 3d enabled monitor but not my 2D monitor
- does not crash when I change from madVR to EVR in MPC-HC
This is a known bug in the NVidia drivers. You can work around it by either using D3D9 presentation, or by telling madVR to enable/disable OS 3D support, depending on whether you play 2D or 3D content. Unfortunately NVidia 3D drivers are pretty shaky atm, especially in Windows 10.

Can/will madVR decode Dolby Vision?
Currently no. And as I said, there's zero technical information available for it, so unless Dolby releases information, it's going to stay "no".