madVR - high quality video renderer (GPU assisted)

[Soukyuu]

        dith | doubl | upsc
314.07:  yes |  yes  | yes*
314.22:  yes |  yes  | yes*
320.18:  yes |  yes  | yes*
320.49:  yes |  yes  | yes*
327.23:  yes |  yes  | yes*
331.58:   no | yes** | yes***
331.65:   no | yes** | yes***
331.82:   no | yes** | yes***
332.81:   no | yes** | yes***

  * yellow tint on 10bit h264 only
 ** no green channel (and no luma?) on 10bit h264 only
*** green tint on 10bit h264 only

Examples of yellow, green tints and missing green channel.

327.23 is the first driver officially released for win8.1, so I'm glad it works. Reverting to it until the issue is fixed.
Oh and... openCL dithering makes me drop frames, rendering queue is running out very fast. Same applies to all NNEDI3 features.
I guess my GPU is just too slow.

edit: openCL dithering also makes the ctrl+J osd an opaque black box.

@everyone: don't forget to mention your GPU when you report the results (or just put it in your sig)

[djfred93]

Originally Posted by djfred93

MadVR don't load with the latest version, it is stuck at opening the file and it crash on the setting window. The debug work fine but the debug don't have the enable/disable OpenCL processing of DXVA NV12 option. The deinterlacing have framedrop but it's better than the other 0.87 version of MadVR. The deinterlacing worked fine (no framedrops) with the latest deband test and stable version. Thanks anyway for the latest version.

My system : Intel Core i7@920, Ati Radeon HD 5770, Windows 8.1, MPC-HC 1.7.1

Work well with the latest version. Except for deinterlacing, where I have framedrops with jinc3 AR/jinc3 AR but I think it's my graphics card is not powerful enough.

[DarkSpace]

Originally Posted by madshi

I don't think so. I've written a custom pixel shader script for the shifting which is performance optimized for just this purpose. If I offered other algorithms, that would mean a lot extra work, and to be honest, I don't think it's important enough. When shifting, the algorithm is not too important. I don't think e.g. Jinc3AR would look any better even with test patterns for simple 0.5 pixel shifting.

No worries, I myself even mentioned that it's probably unimportant. I'm just very curious in general.

[Budtz]

I was using ffdshow de-banding before 0.87

I have enabled reduce banding artifacts. Is this the same as ffdshows debanding and should i disable that?

what de-banding settings are best for blurays?

thx

[michkrol]

Originally Posted by madshi

"//" comments should be supported. Not tested it, though. I'm strictly opposed to using "/*" or "{" comments for documentation in C++, because doing so means you can't comment out large portions of source code. "//" comments don't come with this problem, so I added support only for "//".

Works great. One line comments should be enough in scripts, just to know what any given rule matches, without much thinking. Thanks again for the release.

[James Freeman]

Originally Posted by za222

It seems like it:
Force Film -> Works
Force Video -> Broken
Deinterlacing Off -> Works

0.86.11 in all of the cases above -> Works

Deinterlacing working perfectly in every mode over here (87.1 official).

332.21 Nvidia Drivers.

[djfred93]

Originally Posted by Budtz

I was using ffdshow de-banding before 0.87

I have enabled reduce banding artifacts. Is this the same as ffdshows debanding and should i disable that?

what de-banding settings are best for blurays?

thx

It's even better than ffdshow's deband so you should disable it.

I think the default setting are the best.

[aufkrawall]

Somehow my DPC latency doesn't get below 500 microseconds (at all, with literally no process or driver running).
Most likely there is some connection to the madVR issues I am experiencing, expecially since they also occur with 0.86, which wasn't the case before.
Sorry for bothering.

[Deim0s]

madshi,

And this did not occur with v0.86.11? It's a new problem with v0.87.x?

Yes, only v0.87.x.

Is it possible that you're running out of GPU RAM?

I do not quite understand the question. My GPU: ASUS GTX770 2GB, during the experiment, from applications that run only MPC-HC.
May I ask you, what do you recommend setting queues for this card? I am using "smooth motion".

Try lowering the GPU queues and/or the number of pre-rendered frames. Does that help?

I did the minimum queues:
CPU queue - 4
GPU queue - 4
Win. mode -> backbuffers - 1
LAV with DXVA CUVID when switching to full screen - black screen.
madVR - log
LAV without DXVA when switching to full screen - black screen.
madVR - log
LAV without DXVA - normal playback
madVR - log
If something else is needed, I will do.

[flashmozzg]

Originally Posted by Deim0s

madshi,
I do not quite understand the question. My GPU: ASUS GTX770 2GB, during the experiment, from applications that run only MPC-HC.
May I ask you, what do you recommend setting queues for this card? I am using "smooth motion".

You can download GPU-Z and monitor your GPU RAM usage during playback.

[Soukyuu]

Stupid question: how do I create/use profiles? I don't see any configuration options for that in the tray icon settings.

[cyberbeing]

NVIDIA GTX 770 + madVR 0.87g | 0.87.1

OpenCL Dither
R304 branch = Functional
R310 branch = Functional
R313 branch = Functional
R319 branch = Functional
R325 branch = Functional
R331 branch = Broken
R334 branch = Broken

OpenCL NNEDI3
R304 branch = Broken
R310 branch = Broken
R313 branch = Broken
R319 branch = Broken
R325 branch = Broken
R331 branch = Broken
R334 branch = Broken

Broken = black screen, frozen frame, and/or hung GPU

R304 branch release tested = 309.00 (10/28/2013)
R310 branch release tested = 310.90 (12/29/2012) & 312.69 (10/28/2013)
R313 branch release tested = 314.22 (03/14/2013)
R319 branch release tested = 321.10 (12/05/2013)
R325 branch release tested = 327.23 (09/12/2013)
R331 branch release tested = 331.40 BETA (09/27/2013) & 332.21 (12/19/2013)
R334 branch release tested = 334.67 (01/15/2014)

Conclusion: NVIDIA R331 branch drivers and newer broke madVR display with OpenCL dither. madVR OpenCL NNEDI3 code may have never been functional on recent NVIDIA GPU architectures (Fermi & Kepler?). Remember my earlier post where I mentioned that your version of the OpenCL code for the Avisynth plugin produce a "failed to allocate OpenCL resources error", while SET's original OpenCL code works fine on my GPU.

[DragonQ]

Originally Posted by madshi

Improved over v0.87.0, or improved over v0.86.11? How is it compared to v0.86.11?

Improved over 0.87. Hard to say whether it's really usable without the 10-bit chrome & image buffers. Certainly not better than 0.86.11. Average stats:

0.87.1 Software:
Deinterlace: 18.65 ms
Split: 18.85 ms
Rendering: 8.64 ms
Present: 0.42 ms
Dropped Frames: 63
Delayed Frames: 2

0.86.11 Software:
Deinterlace: 8.29 ms
Split: 9.15 ms
Rendering: 4.70 ms
Present: 0.17 ms
Dropped Frames: 14
Delayed Frames: 0

0.87.1 DXVA2 Native:
Deinterlace: 13.96 ms
Split: 16.53 ms
Rendering: 8.38 ms
Present: 0.41 ms
Dropped Frames: 4
Delayed Frames: 1

0.86.11 DXVA2 Native:
Deinterlace: 7.58 ms
Split: 8.08 ms
Rendering: 5.02 ms
Present: 0.16 ms
Dropped Frames: 8
Delayed Frames: 0

Using: HD4000, MPC-HC, LAV Filters, Smooth Motion, Bicubic75 Chroma upscaling, Catmull-Rom downscaling, playing 1080i/25 @ slightly under 1080p.

[pie1394]

Originally Posted by madshi

Hmmmm... I've tried all of this on my NVidia 9400 GPU which had problems with black rectangles when using XySubFilter in the past. But no problems here, whatsoever. How can I reproduce these issues? Maybe you can provide me with small samples to test with, in case it has something to do with the samples somehow?

It looks like my HW or OS issue. Somehow P10 no longer works even with 0.86.10 version. Reverting the driver back to 320.49 does not help, either. I guess it is the time to reinstall the OS ... @_@


0.87.1 works fine on my HTPC, with HD7970 + Catalyst 13.12 -- Win7x64SP1. Just noticed the GPU's deinterlacing time is increased around 100%...

[720x480i60]
0.86.10 --> 0.83ms
0.87.1 --> 1.64ms

[1440x1080i60]
0.86.10 --> 1.44ms
0.87.1 --> 4.21ms

Regarding the Image Doubling function on the above 720x480i60 contents to 1920x1080p60 display mode, even HD7970 is not quick enough to handle 60fps. It needs more than 17ms (Debanding_with_AngleDetect + NNEDI3 2x + Jinc3AR) processing time vs 6.2ms (Debanding_with_AngleDetect + Jinc3AR)

[Deim0s]

flashmozzg,

You can download GPU-Z and monitor your GPU RAM usage during playback.

I can do this by using open source ProcessHacker.
If it helps madshi, here are the results:
When starting playback in windowed mode
After switching to full screen mode and get a black screen

[PetitDragon]

Originally Posted by cyberbeing

Conclusion: NVIDIA R331 branch drivers and newer broke madVR display with OpenCL dither. madVR OpenCL NNEDI3 code may have never been functional on recent NVIDIA GPU architectures (Fermi & Kepler?). Remember my earily post where I mentions your version of the OpenCL code for the Avisynth plugin produce a "failed to allocate OpenCL resources error", while SET's original OpenCL code works fine on my GPU.

At the early beginning I was wondering too why new madVR doesn't work, while SEt's plugin just works fine.

[michkrol]

Originally Posted by Soukyuu

Stupid question: how do I create/use profiles? I don't see any configuration options for that in the tray icon settings.

Open settings, left click any settings group (processing/scaling ...), click create profile group. I'm sure you'll work it out from there
When created, the profiles get switched automagically with your auto-select rules or by customizable key shortcuts. Be sure to read the help for auto-select rules scripting.

[PixelH8]

Originally Posted by cyberbeing

NVIDIA GTX 770 + madVR 0.87g

OpenCL Dither
R304 branch = Functional
R310 branch = Functional
R313 branch = Functional
R319 branch = Functional
R325 branch = Functional
R331 branch = Broken
R334 branch = Broken

OpenCL NNEDI3
R304 branch = Broken
R310 branch = Broken
R313 branch = Broken
R319 branch = Broken
R325 branch = Broken
R331 branch = Broken
R334 branch = Broken

R304 branch release tested = 309.00 (10/28/2013)
R310 branch release tested = 310.90 (12/29/2012) & 312.69 (10/28/2013)
R313 branch release tested = 314.22 (03/14/2013)
R319 branch release tested = 321.10 (12/05/2013)
R325 branch release tested = 327.23 (09/12/2013)
R331 branch release tested = 331.40 BETA (09/27/2013) & 332.21 (12/19/2013)
R334 branch release tested = 334.67 (01/15/2014)

Conclusion: NVIDIA R331 branch drivers and newer broke madVR display with OpenCL dither. madVR OpenCL NNEDI3 code may have never been functional on recent NVIDIA GPU architectures (Fermi & Kepler?). Remember my earily post where I mentions your version of the OpenCL code for the Avisynth plugin produce a "failed to allocate OpenCL resources error", while SET's original OpenCL code works fine on my GPU.

^This. My own testing mirrors this exactly.

On my system with the 560 Ti, the last driver to have OpenCL error diffusion working is 327.23.
Every version after this is total FAIL. Something went very wrong indeed. Nothing in the release notes for 331.40 indicate any changes that would adversely affect OpenCL applications but who knows? Maybe whoever compiled the latest drivers forgot to flip the OpenCL switch.

On the plus side, Nvidia does make installing and uninstalling drivers as pain-free as possible, so there's that.

EDIT: I forgot to mention I was using the latest 0.87.1 build of madvr. Also, I'm not 100% sure if this is only a problem that affects Fermi cards and newer so I really have to get my GTS 250 system up and running to find out for sure. I also have a stockpile of drivers going back to 2009, so let the good times roll.

[noee]

Originally Posted by pie1394

Just noticed the GPU's deinterlacing time is increased around 100%...

I notice the same thing using a 1080i video:

.86: Queues all full, no drops, deint=7.3ms
.87.1: Render and present queues struggle ~3-4, 50+ drops after 2 min of playback, deint=18.13ms

HD6570

Edit: Should add, this is a VC1 video using DXVA2 decode

[DragonQ]

Originally Posted by noee

I notice the same thing using a 1080i video:

.86: Queues all full, no drops, deint=7.3ms
.87.1: Render and present queues struggle ~3-4, 50+ drops after 2 min of playback, deint=18.13ms

HD6570

Edit: Should add, this is a VC1 video using DXVA2 decode

Glad it's not just me and not just Intel GPUs!