madVR - high quality video renderer (GPU assisted)

[oldpainlesskodi]

Once you set a custom resolution and enable it (either manually in nVidia Control Panel aka NCP or with madVR) are you still able to switch into 10/12 bit color depth?

I'm on the latest fastring of Win10, and using the latest version of the Nvidia driver, using a custom res, it keeps defaulting to 8bit for me - using driver 382.53 it works as it should and defaults to 12 bit with a custom res.

K

[Robominator]

Madshi, comparing HDR content to SDR it seems like reds a bit off, for example on the HDR version of Blade Runner 2049 the word Replicants is red on the blu-ray but pink on the 4K with HDR -> SDR conversion.
Changing settings doesn't help, this is with high quality hue and compress highlights, I found that 250 nits to be somewhat comparable between versions.



I agree , i found out the same thing.

[austinminton]

on the HDR version of Blade Runner 2049 the word Replicants is red on the blu-ray but pink on the 4K with HDR -> SDR conversion.


I use hdr passtrough in madvr on my hdr capable TV and I also get replicants in pink. I have checked this on the uhd with a uhd player and its also in pink.

I am guessing this is on the uhd itself. Not a madvr issue.

[ryrynz]

Good to know, interesting that they'd change the colors so much between different versions at the same time of release.

[austinminton]

What is more interesting is how did you manage to spot this difference? You have eyes of a hawk!

[Braum]

When I'm playing content with a very high bitrate like UHD HDR Bluray (overall bitrate > 65 Mb/s with peak at more than 100 Mb/s) the video stutter and I'm dropping a lot of frames.

I've tried playing the file on a SSD and the issue remains.

Some UHD Bluray read flawlessly but other stutter a lot.

Any insight as to why ?

Windows 10
Madvr v0.92.10
Potplayer 64bits v1.7.7145

Intel i5 3570K
AMD 7870XT 2 Go
8GB of ram
Crucial MX100 250Go Sata 6Gb/s
Seagate Barracuda Green 2To Sata 6Gb/s

[nevcairiel]

Most definitely running out of power to decode them. High-bitrate HEVC UHD streams require quite a lot of CPU power to decode, and your graphics card is also too old to assist in that process, so yeah. Not enough performance.

[mclingo]

When I'm playing c.....

this card, (a) I doubt this card supports 2160p output and if it does you will only get 23,976hz

(b) has no HEVC hardware decoding.

So your cpu is not only crunching through decoding HEVC but also downscaling as well.

IMHO - Best option is to pickup a cheap 4k card, the cheapest you will find used is the RX 460 or Nvidia 1030. Both should play these movies fine with madvr settings at default.

You cpu is ivy bridge so no HEVC hardware decode on there either i'm afraid.

[Braum]

Most definitely running out of power to decode them. High-bitrate HEVC UHD streams require quite a lot of CPU power to decode, and your graphics card is also too old to assist in that process, so yeah. Not enough performance.


this card, (a) I doubt this card supports 2160p output and if it does you will only get 23,976hz

(b) has not HEVC hardware decoding.

So your cpu is not only crunching through decoding HEVC but also downscaling as well.

IMHO - Best option is to pickup a cheap 4k card, the cheapest you will find used is the RX 460 or Nvidia 1030. Both should play these movies fine with madvr settings at default.

You cpu is ivy bridge so no HEVC hardware decode on there either i'm afraid.
Indeed, the four threads of my cpu are at 100% utilization @4.41Ghz, I should have thought about it
The GPU is doing nothing. Well it's time for an upgrade !

Thank you for your answer !

[Megalith]

* "remove compression artifacts" now always runs as part of NGU (if possible)

Am I the only one who doesn't like this change? Can't this feature inadvertently soften or smear the image? (My philosophy is that imperfections in the image should be left alone if it is part of the source.)

[ryrynz]

You still have to tick to enable 'remove compression artifacts' and be running NGU (sharp only still I believe) it's just there's no option to run it separately like there used to, which makes sense as it's basically free with NGU.


1) How does NGU Sharp + the new lowest RCA strength 1 look to you? Maybe NGU Sharp (only High and Very High) should always run with RCA strength 1 now, even if RCA is turned off? Or is it still better to allow NGU Sharp + RCA off?


Best to keep it as something you enable, based on what I've seen even at 1 it ever so slightly softens the picture although one could argue this would be almost imperceptible it doesn't seem to offer much if any benefit IMO.
If it only targeted what is humanly seen as "artifacts" then it wouldn't be a problem, personally I'd find deblocker + derainbow algos more useful. In what situations does RCA offer it's best results? Anyone got any screenshots or sample to share to see it in action?

[mytbyte]

Yes. You first select a standard setting which offers 12 bit color. Then, when madvr switches modes to your custom setting (say 4K@23), it will use 12 bit color. When using HDMI 2.0, 12 bit color is not supported in 4K50 or 4K60 modes. However, the NVIDIA interface will allow you to choose 12 bit color for these modes. If you select 12 bit color for either mode, it will still use 8 bit at 4K50/60 because that is all that the HDMI connection will allow, but when you switch modes to 4K30 or below, it will use 12 bit color.

Not sure that's true, if 4k = 3840x2160, I sure can use 12 bit @50-60 hz with chroma set to @4:2:0 with GTX 960 and GT 1030...are you saying that this is not possible if you make a custom resolution?

madshi,

Would you mind clarifying how to go about generating a 3D LUT for BT.2020 content mastered to the DCI-P3 colorspace (basically all UHD Blu-Rays thus far)? You mentioned before that DCI-P3 within a BT.2020 container is basically just DCI-P3. However, if I try to generate a 3DLUT for DCI-P3, wouldn't that result in wrong colors since my projector can only accept BT.2020?

My understanding is that you don't calibrate to DCI-P3 with Bt.2020 content, you always do BT.2020 LUT conversion to your screen capabilities, unless you truly have content that's DCI-P3 and that doesn'r really exist afaik...the conversion from DCI-P3 to BT.2020 or XYZ for cinema is done post-grading...there are no official DCI-P3 files

[nevcairiel]

Not sure that's true, if 4k = 3840x2160, I sure can use 12 bit @50-60 hz with chroma set to @4:2:0 with GTX 960 and GT 1030

You never want to set Chroma to 4:2:0 though, its like the worst choice for quality. Always prefer 4:4:4/RGB in 8-bit over some 4:2:0 mode in 12-bit.

[mclingo]

You never want to set Chroma to 4:2:0 though, its like the worst choice for quality. Always prefer 4:4:4/RGB in 8-bit over some 4:2:0 mode in 12-bit.

Where I agree in principle I honestly can't see any difference at all in real world viewing on my 4k setup and having everything in the chain set as 4:2:0 just makes everything more simple as you're not left wondering if everything is switching properly between 444 and 420 when you are playing 4k HDR vs 4k vs 4k SDR, everything just plays using the same settings.

I dont doubt i'm losing something somewhere but convenience wins out on this occasion, however, if someone could point to a real world clip where I could definitely see a difference i may change my mind.

[ashlar42]

madshi, I see you explain how zoom control doesn't work when using D3D11 decoding in LAV Filters, I've also discovered that hardware deinterlacing through madVR doesn't work as well (when using 3D11 decoding).

Is this something that's going to change in the future or are there insurmountable obstacles stopping that?

[Statick]

Advanced media players should be able to handle your zooming requirements. Zooming is usually controlled by the media player.

I'm specifically using the zoom function in MadVR because of the superior scaling algorithms compared to media players. it does the job well, except for zooming away top and bottom bars which I would prefer it did not do

[brazen1]

Where I agree in principle I honestly can't see any difference at all in real world viewing on my 4k setup and having everything in the chain set as 4:2:0 just makes everything more simple as you're not left wondering if everything is switching properly between 444 and 420 when you are playing 4k HDR vs 4k vs 4k SDR, everything just plays using the same settings.

I dont doubt i'm losing something somewhere but convenience wins out on this occasion, however, if someone could point to a real world clip where I could definitely see a difference i may change my mind.

On the contrary, it's a nightmare and a constant switching guessing game. 4k exclusively might be one thing but start adding diversity of other types of sources like 3D and players such as PDVD and dedicated ROMS. You'll quickly find yourself MANUALLY switching Full vs Limited in your display constantly and the 'auto' setting isn't going to cut the mustard. This is because displays are unique and have a preference. For your visual test, play your good looking 4k. Then play a 1080 2D or 3D. Then play a disc in your dedicated player. After that play anything with PDVD that is locked in RGB Full. If you can't notice the difference, simply manually switch your display Full vs Limited setting during playback of each test provided you've also calibrated each. RGB Full across the board has none of these clashes because it allows Full where 420 and 422 are Limited only. There are many other differences such as Desktop vs Video modes. Although 420 is convenient for you, I don't think it's a good general practice for others.

[mclingo]

On the contrary, .....

no knightmares for me, no switching anything, no need to change between full and limted on anything, not sure what you are referring to.

The point of using this is that I dont have to switch anything once you got your colour space chain right.

One problem I was getting was that I'd get audio dropouts when using 444 full RGB when playing 4k stuff, mainly high bit rate and HDR stuff and far more black screens and loss of HDMI, even though it was in 23p and should not have been a bandwidth issue. 1080p playback was flawless though so it does suggest bandwidth. This happened even after checking and replacing all my cabling and ensuring my full equipment path fully supported HDMI 2.0.

I am considering taking another look at this as I'm thinking of scrapping HDR, after comparing some of the latest HDR offerings to their SDR versions they are either only slightly better or worse. Star trek 2009 looks terrible on my TV.

My TV is a first gen HDR TV how with relatively low nits so this is expected.

[brazen1]

I think I made it obvious to exactly was being referred. Did you happen to test any of those scenarios or just making assumptions that you're unaffected by them? If you only see a slight difference SDR to HDR, consider what is being explained to you. Then again, perhaps your display isn't capable of the full benefits of modern sources, software, and hardware after all and no amount of massaging is going to relieve your experience.

[Asmodian]

The point of using this is that I dont have to switch anything once you got your colour space chain right.


I don't understand, you don't have to switch anything if you simply use 8-bit RGB, and that would be the better option.

Also your dropout issue is probably cables or devices, I have had many HDMI cables that claimed to be 2.0 but had issues. 4:2:0 uses half the bandwidth but as way to get around bad HDMI cables it seems like a horrible sacrifice in quality. We are talking about madVR here. :devil:

[mclingo]

I don't understand, you don't have to switch anything if you simply use 8-bit RGB, and that would be the better option.

Also your dropout issue is probably cables or devices, I have had many HDMI cables that claimed to be 2.0 but had issues. 4:2:0 uses half the bandwidth but as way to get around bad HDMI cables it seems like a horrible sacrifice in quality. We are talking about madVR here. :devil:

like I say, I may try it again at some point but I see no deterioration whatsoever in picture quality in real world viewing so I see no real need right now.

[mytbyte]

Madshi, as per the discussion above, just out of curiosity, is there a signal path with madVR that would allow avoiding upconverting 4:2:0 from the file to RGB buffers for processing i.e. to keep everything in component colorspace all the way to the display?

[nevcairiel]

Madshi, as per the discussion above, just out of curiosity, is there a signal path with madVR that would allow avoiding upconverting 4:2:0 from the file to RGB buffers for processing i.e. to keep everything in component colorspace all the way to the display?

Not on a PC, its internally always RGB.

[Damien147]

Do you guys get sudden restarts?
Latest Win 10/Madvr(happened also with 0.92.10)

[ryrynz]

No such stability issues for anyone else here, it's your system and you'll have to narrow it down. Start with your graphics card software and stress test the hardware of your system.

[Damien147]

Ok,thank you.

[Clammerz]

I'm specifically using the zoom function in MadVR because of the superior scaling algorithms compared to media players. it does the job well, except for zooming away top and bottom bars which I would prefer it did not do
The Media Player only instructs the renderer what to do. It doesn't actually zoom any pixels itself. MadVR still does that.

[mclingo]

another issue thats been discussed is 444 full rgb 8 bit vs 420 10 bit. Running my desktop in 444 full RGB I lose true 10bit, most, if not all of the HDR movies available are now in 10 bit and my signal path is fully 10 bit compatible so it seems silly not to use it.

The Problems arise with chroma subsampling conversions when playing movies on your PC and this is where i start to get lost down the rabbit whole. if the content is already 420 it gets converted to 444 before being output to your TV, I get that. If you then output the 444 image to your TV then another conversion isnt required but if your desktop is set to 420 it has to convert back to that to output range before feed your monitor or TV with that, that also makes sense.

So, there is an extra chroma conversion and this this is where the loss of quality is happening, correct?

Couple of questions then.

1. To what extent does this second conversion make any difference (I cant see any difference) if the image started off as 420 as all blurays do, are we assuming it makes a difference or does any one have proof visual proof. I would certainly agree if you fed the GPU an image in 444 colour space which was then converted to 420 before being output to your TV there would quality loss, thats obvious but if the original movie was in 420 to start with is anything really changing on that second conversion?

2. Playing a 10 bit HDR movie in 8 bit 444 is not going to look as good as a movie played in 10 bit 420, it cant be, that's obvious, 8 bit dithered gradients cant look be as good as full 10 bit colour gradients, they will be close though. However if we want to play movies in 10 bit we cant use 444 full RGB at the moment as HDMI 2.0 bandwidth doesnt support it. So the question would be, what is better, losing full 10 bit or having an extra chroma conversion to preserve 10 bit colour.

This is an issue thats only arisen recently as we are now only just starting to see 4k HDR content to play, prior to this there was no bandwidth restrictions, we could set our PC as 444 10 bit 1080p and there would be no need for a conversion back to 420.

I'd be interested to know if there are an objective answers to this.

[huhn]

10 bit is worthless on current TVs.

[brazen1]

I have an objective answer. You misunderstand one important piece of criteria. HDMI 2.0 doesn't support RGB Full 444 above 30Hz but it does support it under 30Hz. Titles are 23.976 aka 23/24 Hz. Therefor it is supported and how many of use it (as intended). This means we have no judder, we are applying 10bit in Video mode (actually 12bit dithered) from an HDMI 2.0 port. We also don't want to use our Windows Desktop at 30Hz or we get unusable LAG, so we force 12bit video and default 8bit desktop (automatically). Fwiw, 8bit can look and perform better than 10bit at times. There are those that feel mismatching frame rate of the original source and bumping it to 60Hz for some unknown reason and then using an algo to try and smooth out the mismatch as much as possible is a better idea. I really don't understand what the higher resolution offers them for what they give up but that's another discussion.

[huhn]

the unknown reason is to avoid very common processing issues on TVs.

and well i have bad news for you if it comes to 4:4:4 23 hz on Samsung tvs.

[brazen1]

Agree. Some Samsung TV's. And most if not all other TV manufactures as well. As you taught me in the past, ANY 60Hz TV is screwed and by all rights, should be. Those that are truly 120Hz are very, very workable with no problems, such as mine (Samsung). I should not have wrote "for some unknown reason". I simply forgot to be honest because it's a problem for others I take for granted. The more I think about it, 60Hz and a smooth motion algo is really a good option. Now I understand why madshi put it in madVR. I'm sure 60Hz display users really appreciate it too. Using the telecine option in nVidia would be a good idea in this case too I suppose.

[huhn]

if you add that i'm not aware of a single Samsung TV that can do 4:4:4 at 23p what so ever there are more reasons even through less important ones.
Using the telecine option in nVidia would be a good idea in this case too I suppose.
this is for deinterlancing and i have no clue what suppose to happen with it because toggling has no effect last time i check and i clearly know what telecine.

[qazokm123]

Do you guys get sudden restarts?
Latest Win 10/Madvr(happened also with 0.92.10)

Yes. happens. Every day. Win10/Madvr latest/mpc-be/potplayer.
Nvidia-GTX970.

It is random. PLaying well for 30/40/45... mins, PC restarts.
Also tried , reset all madvr settings to original. Still happens.
Scared.

- Now using back EVR(c), no restarts happening.

Try again next ver madvr.



[]
Will try again, and look at windows logs.

[]
NO more reBoot of windows10
with mpc-be , LAV 0.70.2.88 , madvr 0.92.10
Tests with hours of video.
Nice!

[ryrynz]

I'd bet money on your system or underlying software being unstable, not madVR. Look in your Windows error logs.

[Clammerz]

This is an issue thats only arisen recently as we are now only just starting to see 4k HDR content to play, prior to this there was no bandwidth restrictions, we could set our PC as 444 10 bit 1080p and there would be no need for a conversion back to 420.
But it isn't really a new issue since the core scenario of "420" content has almost always existed. It's just a rehashing of the fundamental issue of chroma subsampling.

You keep asking about these kinds of nuances over and over and keep stating you don't see any difference. I don't see why you are hung up on it. If you don't see any difference then be happy.

If you want to understand why it makes a difference, it's because you are upscaling chroma to full resolution (most likely) using MadVRs high quality scalers (to RGB [not just 444, there's a difference] high bitdepth). To then downscale that again to 420, not only just undoing the high quality chroma upscaling (and possible any refinements you have selected) but potentially also damaging the chroma image more due to the potential of poor or substandard chroma downscalers used by the GPU/drivers.

There's a debug/test image on the first page of this thread if you want to test to see what is ending up on your screen.

I guess the only "somewhat new" twist on the scenario is the addition of 10bit. You make the incorrect assertion "Playing a 10 bit HDR movie in 8 bit 444 is not going to look as good as a movie played in 10 bit 420". It all depends on the every piece in the pipeline and how it interacts and also the perception of the user. Some users are more distracted by noise level (8bit from 10bit), some users are more distracted from blurry chroma (420). It's also no point sending 10bit if something in your chain is downconverting it to 8bit.

[j82k]

2. Playing a 10 bit HDR movie in 8 bit 444 is not going to look as good as a movie played in 10 bit 420, it cant be, that's obvious, 8 bit dithered gradients cant look be as good as full 10 bit colour gradients, they will be close though.

I think that depends on your TV. I thought the same until I tested it using 10-bit gradient patterns. On my 2016 LG Oled I get smoother gradients using 8-bit full RGB for HDR movies.
I guess some TVs don't have real 10-bit panels even if stated in the specs. So my suggestion would be to just test it and decide for yourself.

[Nyago123]

I think that depends on your TV. I thought the same until I tested it using 10-bit gradient patterns. On my 2016 LG Oled I get smoother gradients using 8-bit full RGB for HDR movies.
I guess some TVs don't have real 10-bit panels even if stated in the specs. So my suggestion would be to just test it and decide for yourself.

I also have a 2016 OLED (and E6). "Test it" is probably the best advice.

I'm not sure everything is all worked out at the video driver+OS levels either. For example, I see pronounced banding / macroblocking (LG E6 HDR tone map induced clipping?) with nVidia video settings @ RGB 12-bit Full playing HDR video fullscreen windowed in certain scenes - easiest repro for me is in Blade Runner 2049 at ~36:28 in the white background, left of Gaff's head.

But I played around and what I found is (all 23Hz 2160p):

(NV HDR = where MadVR auto switches; OS HDR = I hit the toggle switch in Windows myself before starting the video)

1. Fullscreen windowed NV HDR RGB 12-bit Full = issue
2. Fullscreen exclusive NV HDR RGB 12-bit Full = no issue
3. Fullscreen windowed OS HDR RGB 12-bit Full = no issue
4. Fullscreen windowed NV HDR YCbCr 12-bit 4:4:4 (Limited) = no issue

A while back (maybe almost a year ago) I found that nVidia YCbCr 4:4:4 and 4:2:2 had extreme color shift in the secondaries with my HTPC setup. The RGB primaries were within 0.5 dE but cyan/magenta/yellow were way off. In RGB mode the colors were near perfect when calibrated.

I haven't checked it lately since plenty of driver, OS, firmware, etc updates but there are just so many variables I didn't want to spend the time; hence I run the HTPC in RGB.

[mclingo]

well this is the problem isnt it, everyone has different setups and pipelines so its very difficult to know which setup is best, and yet people on here seem very sure my 10bit setup will be worse than if I switch to 8bit, I think its clear that nobody knows this for sure.

I Moved back to 444 last night, not seeing any dropouts or black screens yet so I'll see how it goes.

[mclingo]

I also have a 2016 OLED (and E6). "Test it" is probably the best advice.

I'm not sure everything .....

useful, thanks.

[j82k]

I just tried pretty much all available 10/12 bit modes again and I still think full RGB 8-bit gives me the best gradients for hdr videos. LG 55C6V, Nvidia 1050ti with latest drivers.


Nvidia full RGB 8-bit, madVR 8-bit
https://i.imgur.com/KNo49lb.jpg

Nvidia YCbCr444 12-bit, madVR 10-bit
https://i.imgur.com/OqgXx3W.jpg

Playing the test pattern directly to the TV via USB gives me the same worse result as on PC using 10/12 bit so I don't think theres anything wrong with my setup. Gonna stick with full RGB 8-bit.

[mclingo]

right then, nice to have to objective evidence, i'll see how 444 8 bit goes then, cheers.

One thing I do prefer with 444 is BTB/WTW which isnt achievable with 420, test pattern looks much better on my OLED with BTW/WTW, the gradients are smoother at the bottom end.

[Asmodian]

I have an objective answer. You misunderstand one important piece of criteria. HDMI 2.0 doesn't support RGB Full 444 above 30Hz but it does support it under 30Hz.

8-bit 4K 60Hz RGB Full works great with HDMI 2.0. :confused:

There are those that feel mismatching frame rate of the original source and bumping it to 60Hz for some unknown reason and then using an algo to try and smooth out the mismatch as much as possible is a better idea. I really don't understand what the higher resolution offers them for what they give up but that's another discussion.

Only if your TV is not good at 24p or you don't like switching refresh rates is 60Hz with smooth motion better. A tuned 23.976 Hz refresh rate is ideal and no one argues this point, expect users of SVP or similar.

Personally I like smooth motion and a 60Hz desktop so I don't have to wait for refresh rate changes but I do believe a proper matched refresh rate is better.

I am not sure what resolution has to do with it? Are you saying the motion clarity is noticably worse with 60Hz with smooth motion compared to a perfectly matched refresh rate, because that is not true, and even if it was the resolution in non-moving scenes is still there. There is already so much motion blur in 24p content that smooth motion doesn't really add any.

[Siso]

I am not sure what resolution has to do with it? Are you saying the motion clarity is noticably worse with 60Hz with smooth motion compared to a perfectly matched refresh rate, because that is not true, and even if it was the resolution in non-moving scenes is still there. There is already so much motion blur in 24p content that smooth motion doesn't really add any.

Personally I prefer a 72hz over 60hz and smooth motion, smooth motion is nowhere near close a tuned refresh rate...The blur is way too much. The difference between them is big.

[brazen1]

@Asmodian. Sorry. Since the entire discussion was about 8bit vs 10bit or higher depending on resolution Hz, thought it went without saying, so rephrasing for better understanding:
HDMI 2.0 doesn't support RGB Full 444 above 30Hz with 10bit or higher color depth but it does support 10bit or higher under 30Hz.

Waiting for the display to match the refresh rate of the title takes all of about 1 second at the beginning of playback and once again at the end of playback. It doesn't bother me but I understand it does others. Once I tried forcing 60Hz for a 23.976 title and using 'smooth motion' algo to see what the improvement was (before understanding those with 60Hz don't really have any other choice). Blur and judder was terrible. I know you say there should be no difference and respect your opinion and how you arrive at your deductions but this is simply my experience. Matching refresh rate has always been very pleasant and smooth as butter for me. My present 4k display is true native 120Hz as was my previous 1080 (both Samsungs). Judder during panning scenes is a pet peeve of mine over any other irregularities. I simply will never own a display under 120Hz and fwiw, both displays advertise as 240Hz using interpolation which I find even more attractive since imo, (through interpolation) adds to the sharpness, clarity, and realism many deem fake and full of miscalculated frames although I've have NEVER experienced those claims.

[feelingblue]

A little question.

Why any mkv3d is displayed in 2D?
I tried any kind of settings in both player (MPCHC) and Madvr.
With my old Popcorn player the film are perfectly reproduced in 3d.

thanks

[brazen1]

That's a big question you ask without providing any info. We can't guess what you are not doing correctly. Perhaps if you list the things you have done and everything else pertinent like the hardware you are using, we can point out your mistake(s). That's if they are related to madVR otherwise you're in the wrong forum and another such as the one in my signature might be more appropriate.

[feelingblue]

That's a big question you ask without providing any info. We can't guess what you are not doing correctly. Perhaps if you list the things you have done and everything else pertinent like the hardware you are using, we can point out your mistake(s).

I have created mk3D file using makemkv.
The file is created correctly because it exctract Mpeg4-3D track
My stand alone player play it correctly with 3D activated.
MadVr not, play it as a normal 2D film.
Is Madvr compatibe with mk3d SBS files?

[brazen1]

Yes. We're more interested in what I suggested you provide such as:
Did you enable 3D in madVR?
Did you install LAV filters with the optional 3D part of the download?
Did you enable 3D system wide in your O/S?
What kind of GPU are you using and did you enable 3D driver settings or not?
What software player are you using and is its 3D settings enabled correctly?
Make certain stereoscopic in your GPU and your O/S are enabled prior to playback testing.

This is the madVR software forum. If there is a specific problem using madVR that contributes to your loss of 3D, we will be happy to assist you. If your problem is a combination of other difficulty areas, this is not the forum to seek assistance because when you go off topic it is troublesome for others. Provide the settings you are using in madVR. If they are wrong, we will tell you. If not, then they are correct and you should seek more answers elsewhere since the problem will be attributed to something different. I provided a small list of things to check. I can tell you, 3D is working correctly when using madVR and 3D problems usually begin in another software and/or its settings.

[clsid]

You need the Intel Media SDK plugin (http://files2.codecguide.com/intel_libmfxsw.exe) for decoding 3D H.264 MVC video. This plugin will be used by LAV Video decoder.

MadVR handles SBS video as 2D. Your TV should have an option to turn it into 3D.