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

[BRM]

Regarding the subtitle issue:

https://www.youtube.com/watch?v=ZSXNdbWjJwk&feature=youtu.be

[Anima123]

Just tried lower render queue to 8 and MPDN just crashed when I tried to get into FSE, using SuperChromaRes + SuperRes with NEDI enabled.

Edit: Sorry, I just rebooted my laptop and did some quick tests, no crash now (it seems my OS hasn't reboot for quite some time).

I have lowered render queue to 8, and then Direct 3D backbuffer to 8, and yet no luck.

The nVidia card with my Laptop is 880M which has 8G memory, so it hardly could be lack of memory that caused the issue.

Speaking of render queue, if set render queue to 20, I only got filled of 15/20, when using SuperChromaRes + SuperRes (NEDI disabled, 5 round).

Edit: And when render queue get maximized, the playback of the video became stuttering even the statistics said it's perfect.

[Zachs]

Regarding the subtitle issue:

https://www.youtube.com/watch?v=ZSXNdbWjJwk&feature=youtu.be

It's not enabled and it could be due to several reasons. For example, have you set it up properly to enable subtitle?

Speaking of render queue, if set render queue to 20, I only got filled of 15/20, when using SuperChromaRes + SuperRes (NEDI disabled, 5 round).

Edit: And when render queue get maximized, the playback of the video became stuttering even the statistics said it's perfect.

Wow I didn't even know they are up to 8gb for VRAM these days. They still have to copy that to the system ram for the igp to display to the screen though which kinda defeats the benefits of the whole 8gb VRAM in a way. In that case it had nothing to do with running out of video memory. How much system ram have you got just out of curiosity?

[Blackfyre]

Wow I didn't even know they are up to 8gb for VRAM these days. They still have to copy that to the system ram for the igp to display to the screen though which kinda defeats the benefits of the whole 8gb VRAM in a way. In that case it had nothing to do with running out of video memory. How much system ram have you got just out of curiosity?

Haha Zachs we've had videocards with 8GB RAM for a while now. The GTX Titan X came out with 12GB VRAM a week ago (it's way out of my budget), costs around $1600 here in Australia.

[Zachs]

Wow. OK. But this is a laptop though. And Optimus no less.

[ryrynz]

Wow. OK. But this is a laptop though. And Optimus no less.
I was a little surprised also but considering I've got an 850m with 4GB on it here at work.. 8 isn't much of a stretch. I believe the desktop ram is a fair bit faster though which is why you'd see more ram on mobile.

[BRM]

It's not enabled and it could be due to several reasons. For example, have you set it up properly to enable subtitle?

What do you mean? I do have Xysubfilter, and it's set to load subtitles automatically, which I would expect it to do, especially given that it's a mkv file, although it would be pleasant to be able to load external subtitles as well.


https://i.imgur.com/yz6fvTN.png

[Zachs]

I was a little surprised also but considering I've got an 850m with 4GB on it here at work.. 8 isn't much of a stretch. I believe the desktop ram is a fair bit faster though which is why you'd see more ram on mobile.

VRAM or system ram? I have been googling but nothing came up with 8gb video ram for Optimus system.

Edit: wow how wrong was I! A little more googling and I found one that has 16gb gddr5 VRAM!

[Zachs]

What do you mean? I do have Xysubfilter, and it's set to load subtitles automatically, which I would expect it to do, especially given that it's a mkv file, although it would be pleasant to be able to load external subtitles as well.

Well for starters, make sure you do have the correct version of XySubFilter installed i.e. 64bit if you're using 64bit MPDN.

[trandoanhung1991]

I'm having some troubles with the latest build.

1. Sometimes the video will get stuck for no reason, but the audio stream will continue to play and I have to seek to get it working again. Also when this happens, if I back out of FSE mode it'll cause a crash with OutOfMemory error.

2. There's a delay of 200ms between video and audio. Doesn't happen with MPC-HC.

3. It says out of memory even though when monitored it's only using 2GB of VRAM, when I have 4GB.

[Zachs]

I managed to replicate issue #1. But it doesn't result in out of memory error though. Anyway I think it's a consequential error from it freezing in the first place.

The audio video delay I cannot replicate on any of my systems. I suggest you check your settings.

[trandoanhung1991]

I managed to replicate issue #1. But it doesn't result in out of memory error though. Anyway I think it's a consequential error from it freezing in the first place.

The audio video delay I cannot replicate on any of my systems. I suggest you check your settings.

The out of memory error happens if you switch between full screen and windowed and back a few times when the video freezes.

The audio delay, I found out, happens because of ReClock. It doesn't detect the video stream, so it can't sync up and somehow causes the audio delay.

[Zachs]

BTW it doesn't happen if you use direct 3d 9ex right?

It's due to the workaround I implemented to avoid device removed error.

[thogil]

Could we have a 'Never' option for Always on Top? The behaviour seems to have changed a couple builds ago, and now I am having difficulty keeping MPDN from showing on top of MBT. It appears that top-most re-asserts itself whenever a video is started or stopped.

[Blackfyre]

VRAM or system ram? I have been googling but nothing came up with 8gb video ram for Optimus system.

Edit: wow how wrong was I! A little more googling and I found one that has 16gb gddr5 VRAM!

Haha didn't know you were talking about Optimus... I found this:

NVIDIA® GeForce® GT 630M with NVIDIA® Optimus™ technology, 26 GB of dedicated DDR3 VRAM, supporting NVIDIA® CUDA™, PhysX™, PureVideo® HD technology, OpenEXR High Dynamic-Range (HDR) technology, Shader Model 5.0, Microsoft® DirectX® 11, OpenGL® 4.1, OpenCL™ 1.1

Here's the link (but it's an old GT 630M and it's DDR3 vRAM)

http://panam.gateway.com/s/notebook/2012/Gateway/NV/NV56R/NV56Rsp2.shtml

[ryrynz]

Here's the link (but it's an old GT 630M and it's DDR3 vRAM)


That will be a typo. The 620m had 16GB and that would be the same for the 630m.

[Zachs]

Could we have a 'Never' option for Always on Top? The behaviour seems to have changed a couple builds ago, and now I am having difficulty keeping MPDN from showing on top of MBT. It appears that top-most re-asserts itself whenever a video is started or stopped.

There's already an option to disable "Always on Top" - isn't that working for you?

[Zachs]

The out of memory error happens if you switch between full screen and windowed and back a few times when the video freezes.

The audio delay, I found out, happens because of ReClock. It doesn't detect the video stream, so it can't sync up and somehow causes the audio delay.

Video freezing issue should now be fixed with v.4.

ReClock really needs to have a manual mode that allows you to adjust ref clock according to what MPDN has detected. I posted on their forum a while ago asking if it's possible to allow manual entry for each refresh rate but got no response.

[burfadel]

I suspect it might be the case that others have a sub-optimal choice here as well. Certainly looks good with Direct 3D 11, 'Render in maximum quality', 16 taps for JINC+anti ringing, slightly stronger random dithering with no coloured noise, 16-bit output (TV is set to 12-bit, so is actually feasible over 10-bit), deband --> superRes --> SuperChromares --> Image processor (lumasharpen shader from SweetFX, and he unsharp shader from JanWillem32 shader pack). I don't think it's overkill :)

EDIT: Just realised the adaptor thing I mentioned before this edit! It's a bit obvious now, the TV is adaptor 1, the screen is adaptor 0. If '0' is selected for the TV, it doesn't enter exclusive mode (hence black transparent progress bar), and likewise with the screen with it set to '1' (TV).

Maybe a change in terminology would save any possible confusion or incorrect setting for others?

[thogil]

There's already an option to disable "Always on Top" - isn't that working for you?

I did wonder about the wording of the option, but I must be missing something, as I cannot see an option to disable it?

http://i.imgur.com/piOs6ku.jpg

[Zachs]

I suspect it might be the case that others have a sub-optimal choice here as well. Certainly looks good with Direct 3D 11, 'Render in maximum quality', 16 taps for JINC+anti ringing, slightly stronger random dithering with no coloured noise, 16-bit output (TV is set to 12-bit, so is actually feasible over 10-bit), deband --> superRes --> SuperChromares --> Image processor (lumasharpen shader from SweetFX, and he unsharp shader from JanWillem32 shader pack). I don't think it's overkill :)

EDIT: Just realised the adaptor thing I mentioned before this edit! It's a bit obvious now, the TV is adaptor 1, the screen is adaptor 0. If '0' is selected for the TV, it doesn't enter exclusive mode (hence black transparent progress bar), and likewise with the screen with it set to '1' (TV).

Maybe a change in terminology would save any possible confusion or incorrect setting for others?

Your render chain should be in this order: SuperChromaRes --> Deband --> SuperRes --> ImageProcessor.

Regarding adapter numbering, it's the one Direct3D expects, and usually corresponds with Windows via "Identify my displays" / "Identify" under Control Panel's Display | Screen resolution settings.

I did wonder about the wording of the option, but I must be missing something, as I cannot see an option to disable it?

http://i.imgur.com/piOs6ku.jpg

Main menu bar --> Window --> Always on Top.

[burfadel]

Your render chain should be in this order: SuperChromaRes --> Deband --> SuperRes --> ImageProcessor.

Regarding adapter numbering, it's the one Direct3D expects, and usually corresponds with Windows via "Identify my displays" / "Identify" under Control Panel's Display | Screen resolution settings.


Ah okay, that makes sense :), although it's not the same as 'Identify my displays'. In that, it's screen 1 and 2, and in the adaptor list it is 0 and 1.

Thanks for the correct render order, I thought I might have got it wrong!

[Zachs]

Oh it's actually the same, just that one is zero based and the other is one based. Programmers tend to assume they're the same lol :)

[aufkrawall]

Nice development lately.

However, is it allowed regarding copyright to post a single image out of a movie/series for image quality comparisons?

[trandoanhung1991]

I suspect it might be the case that others have a sub-optimal choice here as well. Certainly looks good with Direct 3D 11, 'Render in maximum quality', 16 taps for JINC+anti ringing, slightly stronger random dithering with no coloured noise, 16-bit output (TV is set to 12-bit, so is actually feasible over 10-bit), deband --> superRes --> SuperChromares --> Image processor (lumasharpen shader from SweetFX, and he unsharp shader from JanWillem32 shader pack). I don't think it's overkill :)

EDIT: Just realised the adaptor thing I mentioned before this edit! It's a bit obvious now, the TV is adaptor 1, the screen is adaptor 0. If '0' is selected for the TV, it doesn't enter exclusive mode (hence black transparent progress bar), and likewise with the screen with it set to '1' (TV).

Maybe a change in terminology would save any possible confusion or incorrect setting for others?

Wow, what kind of GPU do you have :eek:

Does MPDN work with SLI?

[aufkrawall]

SuperRes needs much less GPU performance than NNEDI3 64, so most likely a normal R9 290 wouldn't have any problems (apart from producing heat).

[burfadel]

Oh it's actually the same, just that one is zero based and the other is one based. Programmers tend to assume they're the same lol :)

Actually interestingly enough, the computer screen is adaptor 0 and the TV adaptor 1, but the TV is display 1 through 'Identify' in the screen resolution settings, and the computer monitor 2. This is because the TV connects via HDMI, and it's the availability of connectors on the display card (1 HDMI, 1 DVI, 2 mini-displayport). As my screen doesn't have displayport it's connected via DVI, and becomes 'screen 2'.

Now, in the screen resolution settings (the Windows settings I mean, where you click 'Identify' for the screens), you can arrange the screens in any order you like. Such that for me, screen 2 is on the left.

So MPDN calls screens 'display adaptors', may 'display screen' would be better since 'display adaptor' can be used to describe a video card as well. Also starting from 1 instead of 0 might be good :). I also believe that MPDN is effectively numbering the screens left to right, which means the display list is back to front for me and others in my situation.

I hope that wasn't too confusing!

[Zachs]

Graphics adapter is a terminology used by Direct3D 9 and it is what it requires when you initialize it. MPDN started out as a D3D9 video renderer so I've used that same convention since the first version. I'll probably change this at some point.

[burfadel]

Graphics adapter is a terminology used by Direct3D 9 and it is what it requires when you initialize it. MPDN started out as a D3D9 video renderer so I've used that same convention since the first version. I'll probably change this at some point.

Ah ok, no worries!

[Zachs]

It's done. v2.24.1.

[trandoanhung1991]

Quick question:

Should I disable Luma/Chroma Upscaling if I use SuperChromaRes and SuperRes? It seems redundant to upscale using an expensive algorithm like Lanczos and then upscaled again via SuperRes.

Or am I understanding it incorrectly? Cause coming from madVR, I understood that upscaling can be performed either by Lanczos/Jinc/etc or NNEDI3. But here it seems to be that things are going to be upscaled twice if I use RenderScript.

[aufkrawall]

Is there a reason why MPDN Jinc is much softer than Jinc of madVR?

MPDN Jinc4 AR (+deband):
http://abload.de/thumb/mpdndebandj4arzla34.png (http://abload.de/image.php?img=mpdndebandj4arzla34.png)

madVR Jinc3 AR (+deband):
http://abload.de/thumb/madvrdebandj3arg6ljr.png (http://abload.de/image.php?img=madvrdebandj3arg6ljr.png)

MPDN Jinc16 AR (without deband):
http://abload.de/thumb/mpdnjinc16arn8xhr.png (http://abload.de/image.php?img=mpdnjinc16arn8xhr.png)

Due to this, e.g. the cage in the lower right corner seems significantly darker with MPDN. Is this intended?

------------

It would be also great if we had something similar like NNEDI3 with MPDN (even greater if it wouldn't rely on OpenCL).
SuperRes comes with significantly more aliasing and doubled contoures (very bad for e.g. cartoons) in comparison.
MPDN SuperRes:
http://abload.de/thumb/mpdndebandsuperresytuxd.png (http://abload.de/image.php?img=mpdndebandsuperresytuxd.png)

madVR NNEDI3 64 neurons (fast GPUs can handle it):
http://abload.de/thumb/madvrnnedi364k9uwj.png (http://abload.de/image.php?img=madvrnnedi364k9uwj.png)

[Blackfyre]

@aufkrawall

I think a long time ago I read somewhere in this thread that Jinc in MPDN is half of what it is in Madvr because it uses a different algorithm (or something along those lines, I'm not sure)... So if you're using Jinc4 in Madvr, you need to set Jinc8 in MPDN to achieve the same result.

[Zachs]

Quick question:

Should I disable Luma/Chroma Upscaling if I use SuperChromaRes and SuperRes? It seems redundant to upscale using an expensive algorithm like Lanczos and then upscaled again via SuperRes.

Or am I understanding it incorrectly? Cause coming from madVR, I understood that upscaling can be performed either by Lanczos/Jinc/etc or NNEDI3. But here it seems to be that things are going to be upscaled twice if I use RenderScript.

MPDN's internal upscalers are disabled automatically when you use SuperChromaRes and SuperRes. RenderScripts take precedence over MPDN's own scalers.

Is there a reason why MPDN Jinc is much softer than Jinc of madVR?
Due to this, e.g. the cage in the lower right corner seems significantly darker with MPDN. Is this intended?


First of all MPDN's Jinc is different to madVR's. I have madVR's Jinc on my todo list but it's been given a lower priority seeing that NEDI is much better at getting rid of aliasing and is sharper at the same time while being computationally only as expensive as Jinc3.

Secondly, Blackfyre is correct too - for any other scalers, they are similar to madVR but MPDN count taps in the same way as AviSynth (6 taps is equivalent to madVR's 3).

It would be also great if we had something similar like NNEDI3 with MPDN (even greater if it wouldn't rely on OpenCL).
SuperRes comes with significantly more aliasing and doubled contoures (very bad for e.g. cartoons) in comparison.
MPDN SuperRes

Is that with NEDI enabled?

MPDN's RenderScript API supports DirectCompute 5.0, so it is definitely possible but so far no one has taken up the task of using it for anything useful yet.

My direction with MPDN isn't to make it exactly the same as madVR but to create a video player and renderer that the community can extend via scripts and plugins, much like what Winamp did for audio back in the days.

[huhn]

nnedi3 with directcompute was terrible slow madshi already tried it to avoid general issue with nvidia back in the time and AMD interop issue. the openCL version was a lot faster.

[aufkrawall]

First of all MPDN's Jinc is different to madVR's. I have madVR's Jinc on my todo list but it's been given a lower priority seeing that NEDI is much better at getting rid of aliasing and is sharper at the same time while being computationally only as expensive as Jinc3.

Ok. So for now, it's normal that also with 16 taps, there is less sharpness?


Is that with NEDI enabled?

Yes.


My direction with MPDN isn't to make it exactly the same as madVR but to create a video player and renderer that the community can extend via scripts and plugins, much like what Winamp did for audio back in the days.
I really appreciate your idea and efforts and hope that the community will invent great stuff with it, similar to AviSynth.

[Zachs]

Ok. So for now, it's normal that also with 16 taps, there is less sharpness?

I really appreciate your idea and efforts and hope that the community will invent great stuff with it, similar to AviSynth.

Yup. It's just a different scaler.

[aufkrawall]

Talking of AviSynth: Is there a chance that MPDN will become open source some day?

[Zachs]

No plans at this time but never say never.

[burfadel]

v2.24.1 Changelog:
Graphics adapter ID now shows the name of the adapter and its attached monitor

Thanks! Works perfectly :).

[trandoanhung1991]

So to update my situation with the Spriggan file:

Apparently somehow the 1820 width was confusing MPDN and causing it to scale up the res which caused huge rendering times (my opinion). Once I reencode the video and changed the width to 1920 the rendering times went back to normal.

[Zachs]

It's not confusing MPDN. When you have a 1820 input and you want to display it on a 1920 target, a renderer has to scale it.

Since scaling 720 to 1920 is more expensive than 360->1920, I'd say the same holds true for 720 vs 1820.

[ryrynz]

Perhaps an option to not scale based on user resolution preferences would be worthwhile? If target resolution is < 10% of source file then don't scale for example.

[Zachs]

I don't think other renderers would treat it any differently would they?

[ryrynz]

Have yet to see one that would treat it any differently. This is also where madVR's scaling profiles come in quite handy.

[Slimcut217]

Hi,

Thanks for your work, it's my new default video player, works great with the svp motion plus.

I just would like to solve when the player does this
http://abload.de/img/mpdny0s7v.png

with some movies, mainly the ones in 1080p. It works with other players.

I've read regular troubleshooting problems and it isn't one of them, so i apologize if the answer has already been asked.

[Anime Viewer]

Hi,

Thanks for your work, it's my new default video player, works great with the svp motion plus.

I just would like to solve when the player does this
http://abload.de/img/mpdny0s7v.png

with some movies, mainly the ones in 1080p. It works with other players.

I've read regular troubleshooting problems and it isn't one of them, so i apologize if the answer has already been asked.

Is the video resolution and your screen resolution both 1080p? What scripts do you have running? (Any resize ones...its possible there may be a bug in the specific script). (Also what order are your scripts set to run - if you're using more than one).

[Slimcut217]

Is the video resolution and your screen resolution both 1080p? What scripts do you have running? (Any resize ones...its possible there may be a bug in the specific script). (Also what order are your scripts set to run - if you're using more than one).

You were totally right, it was a script render problem, well spotted. I was using super res and i just change it for super chroma res, now it works perfectlly, thanks to you.

Have a nice day

[Zachs]

You were totally right, it was a script render problem, well spotted. I was using super res and i just change it for super chroma res, now it works perfectlly, thanks to you.

Have a nice day

This sounds strange as it shouldn't cause the image to appear that way. What was the exact sequence of script chain you used? And was that 1080p video -> 1080p screen?

[iron2000]

Having subtitle problems here too.
Some mkvs load subs but some don't.

I notice when theres some subtitle selection in the LAV Spliter tray icon menu then the subtitle will not display in the player.

By the way where are the settings of MPDN saved?
If in registry, what path/key loacation?