madVR - high quality video renderer (GPU assisted)

[ashlar42]

I desided to try out the x64 version of MadVr + Smooth motion + 60 Hz to see if this could be as smooth or better than the x86 version + Reclock + 24 Hz on my TV and HTPC. Well it is not. Reclock + 24 Hz for my 23.976 fps content is way more smooth. So I guess I'm stuck with the x86 version then. Any others here who agree?I very humbly suggest you have a look here: http://forum.doom9.org/showthread.php?t=173571
It works even when software decoding audio, not just bistreaming it.

[sneaker_ger]

Question about MVC files : I can't get MPC-HC (neither MPC-BE) + madvr play MVC files in stereo throug my GTX 960 to my Benq projector. I switched to Windows 10 just for its native capability to output MVC 3D through HDMI.
Stereoscopic works flawlessly, but I couln't not make MPCHC+Madvr work. I'm using two display, one with no 3D capability, and one with 3D activated in windows display settings panel.
Any idea how what's wrong? How to know whether madvr is responsible?
Did you tick the Intel MVC decoder option during LAV setup?

[Paul Tronc]

I don't think so. I had a radeon until this week, I was on Windows 7 until end july, I reinstalled Lav past month. Each time I tried to play MVC via MPC+Madvr : fail. I enabled the 3D feature in Madvr, but no change. Is FFDShow causing some trouble?

[clsid]

You can verify with the OSD (Ctrl+J) if madVR gets 3D input. It should show something like "NV12, 8bit, 4:2:0 (3D)".

LAV Video decoder must be connected directly to madVR. You can 't use ffdshow.

[Paul Tronc]

All right, that's it. I know what to do now. Thanks.

[Kotik]

the black crush sound more like an calibration issue with our TV.

TV can do this just by aging.

Would have been my 1st thing to suspect as well. But like i said on the same TV with my AMD gpu black 17 is blinking during the tests, barely but blinking. To make sure my TV is not the one to blame i did increase brightness on TV co trols and the only thing that happened was that lines after 18 became grey instead of black hence the idea of Intel mapping 17 as reference black instead of 16.

As a result there is a black shift on the rest of the pallet. So anyone else with a Skylake GPU that can run the black levels test file and confirm?

[huhn]

I don't think so. I had a radeon until this week, I was on Windows 7 until end july, I reinstalled Lav past month. Each time I tried to play MVC via MPC+Madvr : fail. I enabled the 3D feature in Madvr, but no change. Is FFDShow causing some trouble?

it doesn't work with ffdshow

[Shiandow]

I'd say, try some 720p content on a 1080p screen. It'll be like that.

[ShiftyFella]

Why wouldn't it? madvr scaling algos are great, I do most of my viewing on 1440p monitor, have no issue with 1080p content using SS. If you don't have fast enough gpu doing doubling is probably pointless at such small scaling factor and you're already benefiting from using upscaling refinements

[Paul Tronc]

You can verify with the OSD (Ctrl+J) if madVR gets 3D input. It should show something like "NV12, 8bit, 4:2:0 (3D)".

LAV Video decoder must be connected directly to madVR. You can 't use ffdshow.


Well, I can't get the "(3D)" text on the osd. Something's wrong. I disabled ffdshow, I just use LAV.

This is what madvr says

Filter : madVR - CLSID : {E1A8B82A-32CE-4B0D-BE0D-AA68C772E423}
Module : C:\Program Files (x86)\SVP 4\madVR\madVR64.ax

- Connected to:

CLSID: {008BAC12-FBAF-497B-9670-BC6F6FBAE2C4}
Filter: MPC Video Decoder
Pin: Output

- Connection media type:

Video: dxva 1920x1080 23.976fps

AM_MEDIA_TYPE:
majortype: MEDIATYPE_Video {73646976-0000-0010-8000-00AA00389B71}
subtype: MEDIASUBTYPE_NV12 {3231564E-0000-0010-8000-00AA00389B71}
formattype: FORMAT_VideoInfo2 {F72A76A0-EB0A-11D0-ACE4-0000C0CC16BA}
bFixedSizeSamples: 1
bTemporalCompression: 0
lSampleSize: 3110400
cbFormat: 112

VIDEOINFOHEADER:
rcSource: (0,0)-(1920,1080)
rcTarget: (0,0)-(1920,1080)
dwBitRate: 0
dwBitErrorRate: 0
AvgTimePerFrame: 417083

VIDEOINFOHEADER2:
dwInterlaceFlags: 0x00000081
dwCopyProtectFlags: 0x00000000
dwPictAspectRatioX: 16
dwPictAspectRatioY: 9
dwControlFlags: 0x00002581
- VideoChromaSubsampling: 5
- NominalRange : 2 (16-235)
- VideoTransferMatrix : 0 (Unknown, used BT.709)
- VideoLighting : 0
- VideoPrimaries : 0
- VideoTransferFunction : 0
dwReserved2: 0x00000000

BITMAPINFOHEADER:
biSize: 40
biWidth: 1920
biHeight: 1080
biPlanes: 1
biBitCount: 12
biCompression: dxva
biSizeImage: 3110400
biXPelsPerMeter: 0
biYPelsPerMeter: 0
biClrUsed: 0
biClrImportant: 0


This is what the splitter says :

Filter : MPC MPEG Source - CLSID : {1365BE7A-C86A-473C-9A41-C0A6E82C9FA3}

- Connected to:

CLSID: {008BAC12-FBAF-497B-9670-BC6F6FBAE2C4}
Filter: MPC Video Decoder
Pin: Video

- Connection media type:

Video: H.264/AVC 1920x1080 23.976fps

AM_MEDIA_TYPE:
majortype: MEDIATYPE_Video {73646976-0000-0010-8000-00AA00389B71}
subtype: MEDIASUBTYPE_AVC1 {31435641-0000-0010-8000-00AA00389B71}
formattype: FORMAT_MPEG2_VIDEO {E06D80E3-DB46-11CF-B4D1-00805F6CBBEA}
bFixedSizeSamples: 0
bTemporalCompression: 1
lSampleSize: 1
cbFormat: 318

VIDEOINFOHEADER:
rcSource: (0,0)-(1920,1080)
rcTarget: (0,0)-(1920,1080)
dwBitRate: 0
dwBitErrorRate: 0
AvgTimePerFrame: 417083

VIDEOINFOHEADER2:
dwInterlaceFlags: 0x00000000
dwCopyProtectFlags: 0x00000000
dwPictAspectRatioX: 16
dwPictAspectRatioY: 9
dwControlFlags: 0x00000000
dwReserved2: 0x00000000

MPEG2VIDEOINFO:
dwStartTimeCode: 0
cbSequenceHeader: 186
dwProfile: 0x00000064
dwLevel: 0x00000029
dwFlags: 0x00000004

BITMAPINFOHEADER:
biSize: 40
biWidth: 1920
biHeight: 1080
biPlanes: 1
biBitCount: 24
biCompression: AVC1
biSizeImage: 6220800
biXPelsPerMeter: 0
biYPelsPerMeter: 0
biClrUsed: 0
biClrImportant: 0

Extradata: [removed]
- Enumerated media type 0:

Set as the current media type

- Enumerated media type 1:

Video: H.264/AVC 1920x1080 23.976fps

AM_MEDIA_TYPE:
majortype: MEDIATYPE_Video {73646976-0000-0010-8000-00AA00389B71}
subtype: MEDIASUBTYPE_H264 {34363248-0000-0010-8000-00AA00389B71}
formattype: FORMAT_MPEG2_VIDEO {E06D80E3-DB46-11CF-B4D1-00805F6CBBEA}
bFixedSizeSamples: 0
bTemporalCompression: 1
lSampleSize: 1
cbFormat: 321

VIDEOINFOHEADER:
rcSource: (0,0)-(1920,1080)
rcTarget: (0,0)-(1920,1080)
dwBitRate: 0
dwBitErrorRate: 0
AvgTimePerFrame: 417083

VIDEOINFOHEADER2:
dwInterlaceFlags: 0x00000000
dwCopyProtectFlags: 0x00000000
dwPictAspectRatioX: 16
dwPictAspectRatioY: 9
dwControlFlags: 0x00000000
dwReserved2: 0x00000000

MPEG2VIDEOINFO:
dwStartTimeCode: 0
cbSequenceHeader: 189
dwProfile: 0x00000064
dwLevel: 0x00000029
dwFlags: 0x00000004

BITMAPINFOHEADER:
biSize: 40
biWidth: 1920
biHeight: 1080
biPlanes: 1
biBitCount: 24
biCompression: H264
biSizeImage: 6220800
biXPelsPerMeter: 0
biYPelsPerMeter: 0
biClrUsed: 0
biClrImportant: 0

Extradata: [removed]


Finally, this is what the decoder says (truncated) :

Filter : MPC Video Decoder - CLSID : {008BAC12-FBAF-497B-9670-BC6F6FBAE2C4}

- Connected to:

CLSID: {1365BE7A-C86A-473C-9A41-C0A6E82C9FA3}
Filter: MPC MPEG Source
Pin: Video - AVC (H.264), High Profile, Level 4.1, 1920x1080, 23.976 fps (1011,e0,00)

- Connection media type:

Video: H.264/AVC 1920x1080 23.976fps

[ryrynz]

I don't like content in e.g. 900p on 1080p screens, it just doesn't look right.

Pick a good upscaler or upscaler/downscaler combo and it'll look better than 1:1. It's quite noticeable with 1080 content on 4K screens but that is a rather large upscale. High quality upscaled content should be more preferable rather than less.

[Aleksoid1978]

Paul Tronc
Upload file or short sample - look's like it don't contain MVC(H.264 3D) stream, only H.264 2D.

P.S. About MPC-BE - built-in video decoder only recently adding support decode MVC stream. I think you using old version that it's can do. Install LAV and prefer it in MPC-BE.

[Paul Tronc]

@Aleksoid1978 : I've tried with MPC-HC 32 last build and MPC-BE 64 from june, but OK I'll update them, and maybe I'll add MPC-BE 32 to be sure. I forgot to precise that in the info properties of my SSIF file, MPC-HC show "Video : Stereo ... MVC", and in VLC I can see 2 video tracks. I'll try to find a SSIF sample, but I think my bluray SSIF is legit MVC 1080p. It's a pity that Stereoscopic player's trial period has been over for months.

By the way : you have the same PC setup than me. It could be interesting to compare how far you set madvr and other post processing filters with this CPU+GPU power.

[chros]

But like i said on the same TV with my AMD gpu black 17 is blinking during the tests, barely but blinking. To make sure my TV is not the one to blame i did increase brightness on TV co trols and the only thing that happened was that lines after 18 became grey instead of black hence the idea of Intel mapping 17 as reference black instead of 16.
That indeed confirms that Intel drivers do something strange.
Intel Input Range (Full RGB) ----> Intel Quantization (Full RGB)
What happens if you modify only these 2 settings?
Are you sure that they are doing anything at all? (e.g. bug in the drivers)
For example, I don't have any options regarding these settings in my intel driver, so I used "madLevelsTweaker.exe" in madvr (per display setting) to apply full range output.

[ShiftyFella]

Not sure, I've been living the pixel-perfect life for too long. ;)

I don't like content in e.g. 900p on 1080p screens, it just doesn't look right. 1440p is a pretty high resolution though, so I thought with some good up-scaling it wouldn't be as noticeable.

What image doubling settings are you using, on what GPU? Rendering times?

I'm curious what 1080p content would look like with quadruple luma res with some SuperRes. I'm currently on a GTX 1080.
Maybe you didn't use good scaler? Pixel perfect is not good enough:D bd50 files without any doubling on my tv look like crap and in general blurays are muddy and not sharp at all imo, I notice this even more on my monitor, as I sit much closer and resolution difference is more noticeable there. Doing doubling of 1080p on 1080p is essentially the same as doing it for 1440p screen, only difference is down scaling factor is less. I can see where you coming from as depending on the algo used it might work better with certain scaling factors or if madvr tried to do what video games do when they output lower res then your screen but madvr still renders that content at native res of the monitor and scaling algos are good enough where mixed resolutions of content\screen is not an issue.

My gpu is 290x and setting for 1080p24 content are Chroma: ReconSoft SR1, Doubling: Luma NNEDI3 128N Chroma NNEDI3 16N, Upscaling JincAR AR+SL, Upscaling refinement CE 0.7 ED 0.9 Refine after ever 2x step , Downcaling SSIM 1D 100% AR Relaxed LL, Error Diffusion 2. Render times are around 36-37ms, if I use super-xbr instead of NNEDI3 render times are down to 12ms. I still prefer NNEDI3 over super-xbr, as I feel it rids of aliasing much better but super-xbr with SR1 can be really good and on some content maybe even better then NNEDI3

[sneaker_ger]

@Aleksoid1978 : I've tried with MPC-HC 32 last build and MPC-BE 64 from june, but OK I'll update them, and maybe I'll add MPC-BE 32 to be sure.
Did you tick the Intel MVC decoder option during LAV setup now? Re-install LAV or it won't be able to decode MVC's second view.

Did you tick the Intel MVC decoder option during LAV setup?

[Aleksoid1978]

@Aleksoid1978 : I've tried with MPC-HC 32 last build and MPC-BE 64 from june, but OK I'll update them, and maybe I'll add MPC-BE 32 to be sure. I forgot to precise that in the info properties of my SSIF file, MPC-HC show "Video : Stereo ... MVC", and in VLC I can see 2 video tracks. I'll try to find a SSIF sample, but I think my bluray SSIF is legit MVC 1080p. It's a pity that Stereoscopic player's trial period has been over for months.

By the way : you have the same PC setup than me. It could be interesting to compare how far you set madvr and other post processing filters with this CPU+GPU power.

1 - download library from here http://mpc-be.org/Intel_MSDK/ libmfxsw32.dll - for 32 bit and libmfxsw64.dll for 64 bit. Place in folder with MPC-BE.
2 - Go Options->Internal Filters->Video Decoders and check H264 (MVC 3D).

[Shiandow]

Could it be that bad?

I feel like it isn't a very fair comparison though, considering 720p is such a low resolution from the start.


Well, the resolution isn't really what determines the quality, the scaling factor is more important. Scaling 720p to 1080p has a scaling factor of 1.5, while scaling 1080p to 1440p has a scaling factor of 1.33. I think these are close enough that there won't be a noticeable difference in quality between a 720p picture scaled to a 1080p screen or a 1080p image scaled to a 1440p screen.

[Paul Tronc]

About upscaling 1080p to 1440p : using jinc or NNEDI3 upscaling (without doubling), I prefer the pixel perfect 1080p result than the 1440p upscale. I tried doubling once, wasn't impressed about the result.

[huhn]

how are you using nnedi3 without doubling?

[aufkrawall]

I got 1440p as well and I don't notice any difference between 1080p NNEDI3 (it's always doubling, btw., at least per axis) and Jinc upscaling with real content.
Putting SuperRes 3 on top of Jinc and imho it looks ~indistinguishable from native 1440p for filmed content.

Btw: With my GTX 1070 and default queue lengths of 8, I sometimes get presentation glitches. Setting queues to 16 seems to make glitches disappear completely, even while heavy borderless fullscreen switching on and off.
Haven't checked yet if this might be related to DXVA2 CB.

[Paul Tronc]

how are you using nnedi3 without doubling?

Oups, I made a confusion, sorry

[kalston]

1080p to 1440p (27") with Jinc AR looks amazing in my experience. Never had any issue with any of my BDs or any other content (coming from a 1080p screen).

[Kotik]

That indeed confirms that Intel drivers do something strange.

What happens if you modify only these 2 settings?
Are you sure that they are doing anything at all? (e.g. bug in the drivers)
For example, I don't have any options regarding these settings in my intel driver, so I used "madLevelsTweaker.exe" in madvr (per display setting) to apply full range output.

I think u dont have these options cause ur TV doesnt send the "Support Full RGB" capability over EDID. In case it does and u applied the registry hack (madVR levels tweak) these settings wont be available unless u revert these settings. In other words Intel Control panel wont make these options available if the reg hack is active or if ur tv doesnt send the "Support Full RGB" info. To find out u can revert the tweak and install latest Intel drivers.

Now back to topic, Intel...... well its even more broken than my initial evaluation. DXVA decoding will produce worst level results than software decoding.

Steps to reproduce: Set LAV to software decoding and run the black clipping test file. 18 will be the 1st bar to blink so 16 + 17 are considered are reference black.... now set LAV to DXVA (Native or CB) and observe that now 16 + 17 + 18 are not blinking. So DXVA on Intel is even worse....

Imagine that i decided to go for a SkyLake cause they got 23.976 fixed, just to find out that they got levels totaly f..ed up.

Back to my R7 240 for me. Each time i believe that finally there is something better than AMD regarding HTPC i discover that messing with my system was a terrible idea :-) I just wonder how hard can it be to get basics working but then again it took Intel many years to fix 23.976 so maybe i ask for too much.
If someone could confirm my findings i would be greatfull.

P.S I did try playing with different levels combos. They result in either totally washed out picture (so they are actually working) or they demonstrate exactly the same issue (madvr limited--->intel full---->tv limited).

[digitech]

guys in your experience, do you think that svp or any frame interpolation is added to the MadVR video chain it really affects video quality? im deciding if i get rid of svp in my htpc

[Q-the-STORM]

guys in your experience, do you think that svp or any frame interpolation is added to the MadVR video chain it really affects video quality? im deciding if i get rid of svp in my htpc


depends...

if you run 24fps and interpolate to 60fps, SVP will definitely hurt quality, since it has to drop every second original frame...
if you interpolate to 48fps or 72fps etc (multiples of 24) it will not hurt quality, other than interpolated frames being softer in general...
you have to decide if you want to sacrifice a bit of sharpness for smoothness...

but obviously if you don't have good hardware and have to use lanczos when using SVP when you could have used nnedi3 or superxbr without SVP, that would be a qualitydrop in general... how noticeable would depend on your content...

I used SVP for 2 years, but since I bought a new 2160p TV, I dropped it.... to my eyes, my new TV has better interpolation than SVP and forcing madVR to upscale 60frames to 2160p would force me to use worse settings..

[cnckane]

Hi!

I would like to use AMD video enhancements (color, brightness) with madvr but as soon as I switch to fullscreen I can see the picture changes to darker.
I noticed it only happens with 1080p videos (I have an 1080p monitor so no upscaling needed), because if I set image upscaling to DXVA lower res videos are working well with the AMD video settings.

[huhn]

try DXVA native

[Paul Tronc]

You can verify with the OSD (Ctrl+J) if madVR gets 3D input. It should show something like "NV12, 8bit, 4:2:0 (3D)".

LAV Video decoder must be connected directly to madVR. You can 't use ffdshow.

Here I am. I did reinstall LAV with intel MVC checked. Now the display switch to 24Hz with a red /green cast.

http://image.prntscr.com/image/d84bdc3e78b74940adfbe752db901e0d.png


http://image.prntscr.com/image/db39548546194e45ae0b723f88167c0f.png

http://image.prntscr.com/image/fbebb39c862f4bb08faaf86cdf2b7c02.png

EDIT : Finally I got it working, I have to disable the dual screen before launching a SSIF file, because it causes what you can see on my screenshots. Stereoscopic player didn't show this bug.
Thank you to all people who helped.

[Sunset1982]

last night I watched a movie an suddenly my whole screen went green. Had to restart the file, then it worked flawless. Someone did have similar problems in the past?


Happened while using RX480, 16.9.1, latest lav, madvr 0.90.24

[cnckane]

try DXVA native

I'm using native now I tried copy-back but still the same.

[deado]

Just thought I would post my Nvidia GPU experiences with NNEDI3.

GTX 680, 780 and 960 = Works in MPC-HC x64, green or grey blocky artifacts in 32-bit
GTX 1060, 1070 = Works in all.

Different versions of Nvidia drivers, Mpc-hc and madvr seemed irrelevant. Glad I upgraded to Pascal. Need 32-bit player for Reclock.

[Betroz]

Just thought I would post my experience with NNEDI3.

GTX 680, 780 and 960 = Works in MPC-HC x64, green artifacts in 32-bit
GTX 1060, 1070 = Works in all.

Glad I upgraded to Pascal. Need 32-bit player for Reclock.

The newest nVidia drivers are more optimized for Pascal. For older cards, use older drivers.

[foozoor]

This is what I can see from the web these days and I really am worried about this.


lansurge's question from ranpha's website
Where is Madshi? He didn’t post anymore on Doom9.
That’s quite strange! Especially that next GPU generation arrived.
Is he working on a totally new renderer powered by DirectX12 or Vulkan?

ranpha's answer from his website
Don’t really think that would happen, else only Windows 10 users can use it.
Even LAV FIlters development has slowed down considerably for quite some time already.

anon from an imageboard website
I think mpc-hc is going to die/be suspended really soon.
The development of lavfilters (the main part of mpc-hc) has slowed down for quite some time.
Even madshi doesn't release any new madVR anymore.
Furthermore windows is now a true mess and includes tons of spyware and unwanted programs that are almost impossible to remove without disconnecting his computer from internet.


Do you have less dubious information to give us?

[huhn]

nothing unusual is going on right now.

this is not the first time this is happening.

[YxP]

This is what I can see from the web these days and I really am worried about this.



Do you have less dubious information to give us?

You are talking with over-enthusiastic people who get each other worked up over nothing. Both mpc-hc and lav nightlies are about 2 months old.

[Sunset1982]

it's nothing unusual. Madshi sometimes takes a timeout to concentrate on programming or his real life maybe. But he'll be back, that's for sure. Madvr is his baby, so I think he'll move on with this project.

[Warner306]

When madshi goes back to his real life, even for three weeks, someone suggests he is done programming?

People need to have more patience. Monthly releases would be fine for most of us given how mature madVR has become.

The man has to have a real job where he earns real money.

[JarrettH]

As someone who has followed madvr from its earliest stages - madshi always returns.

We should be more worried about MPC-HC as it's coming up to a year from the last release and the development team are listed as mostly inactive on the website. I'm not interested in following nightlies.

[aufkrawall]

People could simply put their mind at ease by checking his doom9 forum profile, he's been online even today.
And this program probably is bug-free for most of its users (just like LAV Filters, btw.).

[Sarasa]

Well People sometime forget that it need time to implement new function or improve them, and after that finding if it doesn't crash/bug, etc... ;)

And they also forget that sometime programmer need to do something else to not "burn" them-self :)

[CarlosCaco]

The newest nVidia drivers are more optimized for Pascal. For older cards, use older drivers.



Do you know what driver version should be good with madVRfor a GTX 570 on Windows 8.1?

[Stereodude]

People could simply put their mind at ease by checking his doom9 forum profile, he's been online even today.
And this program probably is bug-free for most of its users (just like LAV Filters, btw.).
FWIW, he's actively posting on other forums about other topics. madVR seems to be working well for most people, so I'm not sure why his lack of posting here day in and day out is of concern to some. He's not getting paid for this. Besides, usually when he disappears for a while he comes back from his secret underground lair with some new killer new feature.

[Betroz]

Do you know what driver version should be good with madVRfor a GTX 570 on Windows 8.1?

Try 327.23 and use DX9 Windowed mode. Or try the 353.xx drivers.

[chros]

Do you know what driver version should be good with madVRfor a GTX 570 on Windows 8.1?
I'm using 355.98 with my mobile Kepler based GPU, yours is Fermi, so you can give it a try as well.

[Sunset1982]

Is windowed overlay mode possible with latest amd cards / crimson or is it still just nvidia/intel which can do this?

[Ge'in]

@ Madshi

Have you look at this paper ?
http://arxiv.org/pdf/1501.00092v3.pdf
It's about SuperRes on CNN

Github : https://github.com/nagadomi/waifu2x
Test on web site : http://waifu2x.udp.jp/index.fr.html

[Anima123]

This has been reviewed several months ago.

As I remembered, it's too complicated to be used in real time, as a doubler in madVR for example.

[AngelGraves13]

Here's an image of the pixelation and corruption that appears sometimes when using Jinc with SuperRes for Chroma. Changing Chroma to anything else removes issue. Also rewinding the file fixes the issue.

https://s17.postimg.org/3u9h4382z/2016_09_16.png (https://postimg.org/image/3u9h4382z/)

[Asmodian]

This has been reviewed several months ago.

As I remembered, it's too complicated to be used in real time, as a doubler in madVR for example.

I thought it wasn't that interesting because while it isn't any harder than NNEDI3 but also not any better; it offers similar quality to super-xbr.