madVR - high quality video renderer (GPU assisted)

[vivan]

Originally Posted by madshi

Ouch, that looks nasty. Can I have a small sample, please? Which zoom factor did you use?

It happens on any video (of any type, not just anime) with any scaling factor. With higher scailng factor it even more noticeable.

240p -> 768p
http://4.firepic.org/4/images/2012-0...0mg4p4cr4n.png
http://4.firepic.org/4/images/2012-0...48scksndvj.png

418p -> 768p
http://4.firepic.org/4/images/2012-0...a6q02qm8j2.png
http://4.firepic.org/4/images/2012-0...5ifhsrbpae.png

720p -> 768p
http://4.firepic.org/4/images/2012-0...r5e16r19zs.png
http://4.firepic.org/4/images/2012-0...qx4h0xqf69.png

I don't think sample can help, but anyway - http://www.mediafire.com/?5sm8qxhgx208gj4

Originally Posted by madshi

I can see a big problem in the frame counter, and a rather small problem in the "f" of the "Aufkäufer"

There's same problem (aliasing?) everywhere. E.g. 4x zoom of fragment of his image:
http://3.firepic.org/3/images/2012-0...ef8p1h7hc7.png
http://3.firepic.org/3/images/2012-0...yz8opgfkat.png
I'm not sure - maybe there is something with your display, because it's very noticeable...

And that's what I get with your image (2x downscaled and than upscaled again with madVR):
http://2.firepic.org/2/images/2012-0...up9zcambix.png
http://2.firepic.org/2/images/2012-0...2mkobmpyaf.png
I don't see such "effect" on your comparison, so it's clearly a bug (maybe some special settings are needed, but mine are all default).

[ryrynz]

Tested on my HD 4000 and my Radeon 5850 as well. Blockiness abound when anti-ringing is enabled.

Originally Posted by vivan

maybe there is something with your display, because it's very noticeable...

He has been out of madVR development for awhile...

[madshi]

Just to confirm: The new Lanczos algorithm *without* anti-ringing filter works fine, and the blocking only occurs if you activate the anti-ringing filter, correct? Look here:

http://madshi.net/Tantei Gakuen Q.png

This is how your anime source looks on my PC when upscaling with anti-ringing enabled. It seems that the problem is not a logic fault in the anti-ringing filter. Instead it seems that the pixel shader code the HLSL compiler outputs totally fails to work correctly with your GPU/OS, while it works in my situation. This is confusing, don't know how that can happen. HLSL is supposed to create pixel shader code which works on all OSs and GPUs. So the big question for me now is how I can reproduce the problem, because it doesn't happen on my PC. Will check my HTPC later...

Those of you who get this blocking issue, which OS and GPU are you using? And those who DON'T get this blocking issue, which OS and GPU are you using? We'll need to find out whether the blocking issue depends on the OS or the GPU, or the combination of both.

[ryrynz]

Originally Posted by madshi

Those of you who get this blocking issue, which OS and GPU are you using? And those who DON'T get this blocking issue, which OS and GPU are you using? We'll need to find out whether the blocking issue depends on the OS or the GPU, or the combination of both.

Having this issue across three PCs all running Windows 7 Ultimate x64 using HD 3000, HD 4000 and Radeon HD5850 graphics.

And yes without anti-ringing, everything is fine.

[madshi]

Ok, so maybe it depends on the OS? I've developed and tested this on XPSP3.

[ryrynz]

Sounds logical. Time to upgrade Madshi unfortunately I don't have an XP system to test on.

[vivan]

Originally Posted by madshi

Just to confirm: The new Lanczos algorithm *without* anti-ringing filter works fine, and the blocking only occurs if you activate the anti-ringing filter, correct?

Yes.

Originally Posted by madshi

Look here:

It's awesome!

Originally Posted by madshi

Those of you who get this blocking issue, which OS and GPU are you using?

I have 2 PC, both are W7 x64. GPU's are Intel HD 3000 and nVidia 540M on notebook, ati 5870 on desktop.

UPD: I don't have XP here too...

About speed. I'm using windowed mode, 1366x768 is screen resoultion. GPU is Intel HD 3000 integrated into i5-2410M CPU.
Scaling settings are default (no linear light, lanczos4 for luma, softcubic100 for chroma).
With v0.82.5 I get about 16.6 ms rendering time (on the edge of 1/60), so 60 fps video has only few drops.
With test version I get about 18.1 ms rendering time, so 60 fps video lags...

[cyberbeing]

Anti-ringing causes the picture to block on my NVIDIA GT 440 DDR5 (@ 864Mhz Core | 1728Mhz RAM) as well.

Win7 SP1 x64
304.48 Driver

Test build Lanczos is also ~33-50% slower (higher GPU load) compared to 0.82.5 Lanczos, which isn't good.

Lanczos3 0.82.5: 15% GPU Load
Lanczos3 Test: 21% GPU Load

Lanczos4 0.82.5: 18% GPU Load
Lanczos4 Test: 24% GPU Load

Lanczos8 0.82.5: 24% GPU Load
Lanczos8 Test: 35% GPU Load

720x480 -> 1600x900

[sneaker_ger]

I, too, get the blocking with activated anti-ringing filter:
Win 7 x64
HD 5850
Catalyst 12.6

[ryrynz]

Looks like it may be worth keeping a legacy Lanczos option.

[cyberbeing]

Lanczos 3 Anti-ringing filter bug

Lanczos 3 Normal

I re-encoded the '4-Star Chart.mp4' test pattern to 960x540, and played it back @1600x900 on my monitor.

[madshi]

cyberbeing, XP or win7? Anybody still on XP to double check?

[madshi]

Originally Posted by cyberbeing

NVIDIA GT 440 DDR5 (@ 864Mhz Core | 1728Mhz RAM)

Win7 SP1 x64
304.48 Driver

Test build Lanczos is also 33-50% slower (higher GPU load) compared to 0.82.5 Lanczos, which isn't good.

Is that with anti-ringing or without? I would have expected a 440 to be faster with the new Lanczos algorithm. What do the madVR OSD average render times say, in windowed mode?

[cyberbeing]

That's without the anti-ringing.

8ms with the Test Build using Lanczos3 720x480->1600x900

6ms with 0.82.5 using Lanczos3 720x480->1600x900

Originally Posted by madshi

cyberbeing, XP or win7?

Those images were taken on Win7 x64.

[Hprd]

I get the blocking too. Win 7 SP1 64 bit Geforce 275 w/ 301.42 drivers. Doesn't matter if I have madvr decode the video, or ffdshow. I even reset madvr to defaults with the .bat file after I updated to the test build.
Is there anybody here where this anti-ringing thing actually works (aside from Madshi of course, lol)?

[ryrynz]

The appropriate question is, is there anyone here besides Madshi that's still running a 10 year old OS?

leeperry where are you!?

[chros]

Originally Posted by cyberbeing

Anti-ringing causes the picture to block on my NVIDIA GT 440 DDR5 (@ 864Mhz Core | 1728Mhz RAM) as well.

Win7 SP1 x64
304.48 Driver

Test build Lanczos is also ~33-50% slower (higher GPU load) compared to 0.82.5 Lanczos, which isn't good.

Originally Posted by shimaflarex

The new Lanczos algorithm is way slower for me.
With the old algorithm, rendering times were about aprox. 23ms for a 480p video stretched to 1600x900.
With the new, it is about 44ms (anti-ringing turned off).
The anti-ringing feature seems to cause major blocking in the same situation (the source is anime btw).
My GPU is a Geforce 8500GT.

Same here for me too (for specs see my signature with desktop config):

MadVR 8.2.5 Lanczos4:
Formula1 720p 50fps GPU: 56-58% FPU: 40-44% MCU: 17-18%
Awake 720p 23.976fps GPU: 28-29% FPU: 15-20% MCU: 10%
Planetes 720p 23.796fps GPU: 27-28% FPU: - MCU: 8-9%

MadVR 8.2.5 Lanczos4_new:
Formula1 720p 50fps GPU: 78-80% FPU: 40-44% MCU: 17-18%
Awake 720p 23.976fps GPU: 47-48% FPU: 15-20% MCU: 10%
Planetes 720p 23.796fps GPU: 45-46% FPU: - MCU: 8-9%

MadVR 8.2.5 Lanczos4_new_anti-ringing:
Awake 720p 23.976fps GPU: 83-87% FPU: 15-20% MCU: 10%

[vivan]

I've made request on one tracker, so here is comment from there.

User with Windows XP SP3 (and GeForce 8600 GT GPU) experiences the same problem:

[ryrynz]

Guess that's that theory out the window. Could be something up with Madshi's system.

[madshi]

Weird. I guess I should be able to reproduce the problem on my HTPC then. I'll try later...