Media Player .NET (MPDN) - D3D HQ GPU Video Renderer [v2.49.0/v1.31.0 27 Dec 2018]

[Anima123]

When using nnedi3 as image doubler, the resulted image has a lot of little cubic as mosaic, look like the following
https://www.dropbox.com/s/mukmjum4o9...osaic.png?dl=0

There's no similar problem with madVR.

nVidia 880M with 350.30 driver, windows 8.1 64-bit.

[Zachs]

Does this happen with all the files or just this?

[Anima123]

Just tested with lower resolution videos, no this effect.

The one that I found that has this problem is when upscaling 1024x576 -> 1920x1080. Not sure other resolutions been affected though.

[Zachs]

Just created an image with a resolution of 1024x576 to test. I'm not seeing the mosaic effect with either NNEDI3 implementation. LAV Video Decoder set to NV12 only to simulate the typical video file output format. I've also tried with the various settings of different scalers, with or without super res etc.

NVS 4200M with 353.30, Win8.1 64-bit too.

EDIT: Are you by any chance using Bicubic 100 AR chroma upscaling? I think I found a problem with it but I don't understand why... It seems setting sharpness to 99 fixes it, if that's the same problem.

EDIT2: Nevermind. Found the cause. Will be fixed in the next release. As a temporary workaround, don't use the same settings for upscaler and downscaler. For example, if you use bicubic 100 for upscaler, and you want to use the same for downscaler, select 99 for sharpness instead. It's to do with how MPDN caches weights for render scripts.

[Zachs]

Originally Posted by Volfield

https://mega.nz/#!pZ0QXbDA!Dg2YFWksp...psmc7y9y3UQHeU

I just tested your config file with Image Quality set as trade-off mode and it works fine... Not sure why you're seeing the problem. That's especially strange since both Image Quality and Render Performance modes use the UNORM textures thus share the exact same code.

[Belphemur]

Originally Posted by Volfield

Is there any way for me to help you find solution?

P.S. screenshots include

Which version of XySubFilter are you using ?

[aufkrawall]

Shiandow, do you want to take a look at this sample?
It has severe banding which gives your deband filter a real struggle.
http://www18.zippyshare.com/v/0Jil84gy/file.html

[Shiandow]

Originally Posted by aufkrawall

Shiandow, do you want to take a look at this sample?
It has severe banding which gives your deband filter a real struggle.
http://www18.zippyshare.com/v/0Jil84gy/file.html

You need something more than a debanding filter to get rid of banding that bad. Heck even I am not sure if some of it may not have been intentional (the circular band accros Turkey and Syria sure seems to be). It might be better to use a denoising filter for this.

[aufkrawall]

madVR deband with most aggressive settings takes mostly care of it.
I think the banding accross Turkey and Syria is because of some kind of vignette effect. Yes, it's terrible content, but I think it's still "unwanted" banding.

[Volfield]

Originally Posted by Belphemur

Which version of XySubFilter are you using ?

XysubFiler 3.1.0.705

[Shiandow]

Originally Posted by aufkrawall

madVR deband with most aggressive settings takes mostly care of it.
I think the banding accross Turkey and Syria is because of some kind of vignette effect. Yes, it's terrible content, but I think it's still "unwanted" banding.

Well I agree that it's unwanted, I'm just not sure how to classify it, it really seems to be closer to 'noise' than simple banding. If it had occurred in a reliable source I'd have concluded that it was meant to be there. It's also interesting to note that MadVR set to high starts to remove the 'intentional' band across Turkey and Syria, and even MadVR doesn't successfully remove all the banding.

By the way, if you haven't tried it already, there's been a very recent update to the debanding filter which might help a little (although fixing this image is till beyond it). It should be available in the next release of the extensions, or you can just download the source.

Anyway, thanks for the feedback!

[Marnes]

Originally Posted by Zachs

Yes this is the right place to report bugs.

I have tested this several times (over 10 times) and couldn't replicate it. If only a reboot can make it go away, that suggests it's something persistent that would go beyond the life-time of a user-mode application. As such it's unlikely to be an MPDN bug.

Guess it must be a video driver problem or something then...

On a different note, will there be improvements to startup speed and such soon? I've been a big fan of mpdn for a while now because the image quality is so good, resource usage is low and the fluid motion filtering is just perfect, but I didn't realize until I installed potplayer that mpdn easily takes 5x as long to open and start playing. Even with my fast ssd, mpdn takes kinda annoyingly long to open when you're trying to go through many files. I tried to look for a replacement for fluid motion (the main reason I don't want to use other players anymore) but all that's available is interframe (haloing artifacts and different end goal) and other avisynth stuff (tedious to set up).

[burfadel]

Not sure what version of NET Framework it is compiled in. Not sure if compiling with NET Framework 4.6 (Windows 10) would change performance any.

[aufkrawall]

Originally Posted by Shiandow

Well I agree that it's unwanted, I'm just not sure how to classify it, it really seems to be closer to 'noise' than simple banding. If it had occurred in a reliable source I'd have concluded that it was meant to be there. It's also interesting to note that MadVR set to high starts to remove the 'intentional' band across Turkey and Syria, and even MadVR doesn't successfully remove all the banding.

Yes, still some banding can be perceived. However, I think the high setting is a good compromise between sustaining detail and fighting banding.
My interpretation of this map would be that it's not supposed to contain any banding. There are many gradients, which I think should be smooth and are just meant as eye candy.

Originally Posted by Shiandow

By the way, if you haven't tried it already, there's been a very recent update to the debanding filter which might help a little (although fixing this image is till beyond it). It should be available in the next release of the extensions, or you can just download the source.

Anyway, thanks for the feedback!

Will try the next extensions, I'm really bad with anything text/script-related.
I hope my feedback can be helpful in some way.

[Marnes]

Would it be possible to invert the color scheme on the status bar when the black theme is enabled btw? The black-on-white bar is a bit of an eye sore right now while everything else is dark.

I feel I should point out that I do appreciate Zach's and everyone else's (if anyone, I've no clue about the project's scale) work on mpdn It's a great player

[aufkrawall]

Originally Posted by Zachs

BTW, while we're on the subject, has anyone noticed the SM5 NNEDI3 is now around 10% faster with the same neurons vs OpenCL with the recent Nvidia drivers? At least on my Fermi cards, it was neck and neck (with SM5 just a touch faster) when we first implemented it. We haven't updated the NNEDI3 code and the only thing that's changed would've been the drivers. Just wondering if anyone's noticed the speed improvements.

With Maxwell 2.0, OpenCL is still a bit faster, but they are almost equal. In my memory, the gap was wider, maybe SM5 has really improved by driver.
My benchmark results (720p -> WQHD 64 neurons, chroma bicubic, max quality mode, everything else turned off, GTX 980 OC 353.49 driver on Windows 10):

OpenCL:
~20,5ms
~47% GPU usage
1126mhz

SM5:
prefer vector:
~22,7ms
~50% GPU usage
1126mhz

prefer scalar:
~24ms
~54% GPU usage
1278mhz

madVR result is interesting too, it's quite faster:
~13,9ms (maybe can't be compared directly)
~34% GPU usage
1126mhz

Both renderers used D3D11 and the same settings/queue lengths, as far as this can be possible.

[Zachs]

You'll need to cripple MPDN a bit for a fair comparison. MadVR doesn't have a max quality mode.

[aufkrawall]

Is MPDN's processing queue using more than 16 bit in max quality mode?

[huhn]

http://forum.doom9.org/showpost.php?...75&postcount=3

looks like max quality is still using 32 bit float.

[foxyshadis]

Originally Posted by aufkrawall

Yes, still some banding can be perceived. However, I think the high setting is a good compromise between sustaining detail and fighting banding.
My interpretation of this map would be that it's not supposed to contain any banding. There are many gradients, which I think should be smooth and are just meant as eye candy.


Will try the next extensions, I'm really bad with anything text/script-related.
I hope my feedback can be helpful in some way.

My interpretation is that it's not possible to correct all encoding defects. I actually don't see any problem with the green nations, perhaps because mine is set a little higher than yours, but the blue water is horrifying. That looks like round-off, encoding, further processing, then round-off and re-encoding. What it does dither well (the green area) still improves the quality, even if it doesn't improve it maximally.