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

[Zachs]

Ah build machine issue. Used a different one to release 2.25.4. I'll fix it in the next build.

[Zachs]

I think I've fixed both performance regression and XySubFilter crashing / subtitles not working issues with the latest release (version 2.25.5).
Do let me know if it fixes the problems.

[Anime Viewer]

I've noticed that using Script Chain: Deband -> NNEDI3 -> SuperRes is producing fast render times than Deband -> SuperRes (with NNEDI3 selected as doubler within). Anyone have a theory why that would be? (I'd think if working correctly they should be the same, or if anything the selection within SuperRes to be faster. Is it perhaps because of passes (independent selection only doing one pass while selection inside SuperRes would lead it to be applied the same number of times as passes selected), or maybe just a SuperRes bug?
Edit: Actually I'm guessing this is in part to the not being able to select optimizer (and neurons) for NNEDI3 in SuperRes while it can be selected in independent NNEDI3 script - which I know is already being worked on...

[burfadel]

In regards to this change:
v2.24.1 Changelog:
Graphics adapter ID now shows the name of the adapter and its attached monitor

I was wondering whether it would be better to put the monitor name first, instead of the graphics adaptor? The resaon I ask is I am running Windows 10 TP, and the graphic driver name is so long it fills the entire drop down box. Because of this, you cannot see the name of the monitor when selecting where to output. Monitor names are almost always quite short.

I have an AMD R9-280X (Tahiti XTL) which is a new stepping of the HD 7970 GHz Edition, and as such it is often reported as the 7900 Series driver. This is due to the Device Adaptor ID, the GPU is actually Tahihi XTL (the graphics BIOS even says so). Quite common for R9-280X cards. It says 'Engineering Sample' because it has full WDDM 2.0 support in the driver. Only those adaptors with fully WDDM 2.0 support are labelled as such in the driver (I checked) :).

Anyways, here is what the box looks like on my machine currently:
http://oi57.tinypic.com/2133hc9.jpg

As you can see, the display name takes up the whole selection box, masking the name of the monitor. The whole name of the display driver is:
AMD Radeon HD 7900 Series (Engineering Sample - WDDM v2.0)
meaning that even without 'Engineering Sample' it would still cut off the monitor name due to the WDDM v2.0 label. I'm not sure whether the WDDM v2.0 label, minus 'Engineering Sample' will rename once the official drivers are released, but it's possible that it may. Also, other graphics adaptors from Nvidia and Intel may face a similar truncation of the 'Graphics Adaptor' selection in MPDN.

I see it as more important to have the monitor name first, since people may have different monitors connected to the same card.

A completely separate query, are you going to go over to SharpDX version 3.0 when it is released, for DirectX 12 support? It would be nice, but apparently the library has changed a bit so would require some rewriting, and apparently support for anything less than DirectX 11 has been removed? I guess if this is the case, you could have SharpDX 3.0 used when presentaton API is 'DirectX 11' or 'DirectX 12' (which should cover most cards), and have SharpDX v2.6.3 utilised with 'DirectX 9Ex' or 'DirectX 10' is selected as the API. This legacy support could be in the form of a special 'Legacy' extension mode (separate from the normal extension download), such that you only download it if needed? :). Just an idea.

Thanks for the great work :).

[Anima123]

Just tested SuperRes + NNEDI3, still suffers from rendering time gradually increasing. Basically, SuperRes cannot use any doubler without rendering time increasing.

[ryrynz]

Just tested SuperRes + NNEDI3, still suffers from rendering time gradually increasing. Basically, SuperRes cannot use any doubler without rendering time increasing.

Have you tried changing any of the settings to 0? Or using fast mode to rule out any particular parts of SuperRes that might be causing it?

[Zachs]

In regards to this change:

I was wondering whether it would be better to put the monitor name first, instead of the graphics adaptor? The resaon I ask is I am running Windows 10 TP, and the graphic driver name is so long it fills the entire drop down box. Because of this, you cannot see the name of the monitor when selecting where to output. Monitor names are almost always quite short.

A completely separate query, are you going to go over to SharpDX version 3.0 when it is released, for DirectX 12 support? It would be nice, but apparently the library has changed a bit so would require some rewriting, and apparently support for anything less than DirectX 11 has been removed? I guess if this is the case, you could have SharpDX 3.0 used when presentaton API is 'DirectX 11' or 'DirectX 12' (which should cover most cards), and have SharpDX v2.6.3 utilised with 'DirectX 9Ex' or 'DirectX 10' is selected as the API. This legacy support could be in the form of a special 'Legacy' extension mode (separate from the normal extension download), such that you only download it if needed? :). Just an idea.

I will see what I can do to improve the drop-down. Showing monitor name first is a quick fix but long monitor names will have the same problem.

With regards to SharpDX 3.0, I'm still trying to find out more about it. It's still too early to even try SharpDX 3.0 yet.

[trandoanhung1991]

I think I've fixed both performance regression and XySubFilter crashing / subtitles not working issues with the latest release (version 2.25.5).
Do let me know if it fixes the problems.

Performance regression still happening.

Same settings, same pre-NNEDI3 extensions, 25.3 gives me 14-15ms, 25.5 gives me 19-21ms.

[Shiandow]

I've noticed that using Script Chain: Deband -> NNEDI3 -> SuperRes is producing fast render times than Deband -> SuperRes (with NNEDI3 selected as doubler within). Anyone have a theory why that would be? (I'd think if working correctly they should be the same, or if anything the selection within SuperRes to be faster. Is it perhaps because of passes (independent selection only doing one pass while selection inside SuperRes would lead it to be applied the same number of times as passes selected), or maybe just a SuperRes bug?
Edit: Actually I'm guessing this is in part to the not being able to select optimizer (and neurons) for NNEDI3 in SuperRes while it can be selected in independent NNEDI3 script - which I know is already being worked on...

Well NNEDI3 already scales the image to the correct final size, so using SuperRes after NNEDI3 is the same as just using NNEDI3 since SuperRes doesn't need to do anything. This is obviously faster than using NNEDI3 and SuperRes. Although it might make sense to change that behaviour, I'll see what I can do.

[Anima123]

Have you tried changing any of the settings to 0? Or using fast mode to rule out any particular parts of SuperRes that might be causing it?

Tried all kinds of settings already, just no luck.

[Shiandow]

Tried all kinds of settings already, just no luck.

Well if anything setting "passes" to 0 should have helped. Just to be sure, the CPU/RAM usage doesn't increase does it?

[Zachs]

Shiandow, are you still seeing performance regression with the latest build?

[Zachs]

Performance regression still happening.

Same settings, same pre-NNEDI3 extensions, 25.3 gives me 14-15ms, 25.5 gives me 19-21ms.
Can you try build 3066 to see if that also has the same performance regression for you?

[Shiandow]

Shiandow, are you still seeing performance regression with the latest build?

Yeah, it's still there. The XySubFilter issues are gone though.

[Zachs]

Hmm. I'll have another look at the changes in 3067. Maybe I've missed something.

[Anima123]

Well if anything setting "passes" to 0 should have helped. Just to be sure, the CPU/RAM usage doesn't increase does it?

It does not. I guess set passes to 0 is equivalent to disable SuperRes instead? The other settings to 0 does not make the rendering time increasing stop if either image doublers enabled.

[Zachs]

I think I've fixed the performance regression issue - can you try build 3070 in the MPDN "Test Builds" folder (http://mpdn.zachsaw.com/Test%20Builds/)?

[Shiandow]

That seems to have done it, the render time / GPU usage is now the same as it was in build 3066.

[nekromantik]

Its a shame AMD not fixed the dual graphics bug.
If you choose AMD card in settings you get no video still.
At least Optimus you get video out! ha

Quick question, this new version, do we only need to use Super Res plus NEDI or do we still use built in NEDI in SuperRes?

[Shiandow]

Quick question, this new version, do we only need to use Super Res plus NEDI or do we still use built in NEDI in SuperRes?

You need to choose NEDI in the SuperRes setting itself, otherwise it will first scale the image using NEDI and use SuperRes the rest of the way. However SuperRes can do more if it knows what the original image looked like so it works better if it can use NEDI internally.

There should be some more advanced support for this soon, allowing you to change NEDI/NNEDI3's settings, or even create your own prescaler.

[nekromantik]

You need to choose NEDI in the SuperRes setting itself, otherwise it will first scale the image using NEDI and use SuperRes the rest of the way. However SuperRes can do more if it knows what the original image looked like so it works better if it can use NEDI internally.

There should be some more advanced support for this soon, allowing you to change NEDI/NNEDI3's settings, or even create your own prescaler.

Thanks :thanks:

[nekromantik]

I chose NNEDI3 in SuperRes alone without any other scripts and Im getting high render times 50 - 60ms compared with older version NNEDI 20 - 30 using SuperChromaRes and SuperRes NNEDI.
Is this normal?

[Shiandow]

I chose NNEDI3 in SuperRes alone without any other scripts and Im getting high render times 50 - 60ms compared with older version NNEDI 20 - 30 using SuperChromaRes and SuperRes NNEDI.
Is this normal?

By NNEDI do you mean NEDI or NNEDI3? Because it wouldn't be weird for NNEDI3 to be a lot slower than NEDI. You may also be suffering from the performance regression form build 3067, which should be fixed soon (it's already fixed in the "beta" version 3070).

[nekromantik]

By NNEDI do you mean NEDI or NNEDI3? Because it wouldn't be weird for NNEDI3 to be a lot slower than NEDI. You may also be suffering from the performance regression form build 3067, which should be fixed soon (it's already fixed in the "beta" version 3070).

Yes I mean that ha

I was using the test version.
Maybe the updated Nvidia drivers slowed it down. Even on NEDI its slower then before.

[Shiandow]

Yes I mean that ha

I was using the test version.
Maybe the updated Nvidia drivers slowed it down. Even on NEDI its slower then before.

How much slower? And does GPU usage also increase?

[nekromantik]

How much slower? And does GPU usage also increase?

Not checked GPU usage.

SuperChromaRes + SuperRes NNDI used to give me 20-30 render times for 720 > 1080. but now Im getting 30 to 40.

[Zachs]

Not checked GPU usage.

SuperChromaRes + SuperRes NNDI used to give me 20-30 render times for 720 > 1080. but now Im getting 30 to 40.

You need to check GPU clock, as it could very well be that it no longer needs to run at max clock rate, so you see an increase in render time.

[Shiandow]

There's now a new version of the renderscripts on github, where you can configure NEDI / NNEDI3, as well as add your own prescaler (not recommended if you don't know what you're doing). Also if you haven't tried SuperRes + NEDI recently, it's become a lot faster with MPDN's new scalers.

It's recommended to use these with the latest MPDN (v2.25.6), the links don't seem to have been updated yet, but I expect they will be soon.

[Zachs]

Done. Just updated the links.

[Anima123]

I can confirm that SuperRes + NEDI is a lot faster than before. Now it took 30 minutes for a 576p 23.976 fps video playback start stuttering due to rendering time increase, which used to be 12 minutes or so.

It would be really nice to see the algorithm been improved, which would be perfect once the rendering time increase no longer be a problem, either in nVidia's driver or in the algorithm itself.

[nekromantik]

I can confirm that SuperRes + NEDI is a lot faster than before. Now it took 30 minutes for a 576p 23.976 fps video playback start stuttering due to rendering time increase, which used to be 12 minutes or so.

It would be really nice to see the algorithm been improved, which would be perfect once the rendering time increase no longer be a problem, either in nVidia's driver or in the algorithm itself.

Im surprised you keep seeing the render time increase.
Mine stays the same and Im on Optimus 860m. Could just be a issue with your specific card.

[Zachs]

I remember he said it happened on both his Optimus laptops. No one else with an Optimus laptop could replicate the issue though.

[Zachs]

I was wondering whether it would be better to put the monitor name first, instead of the graphics adaptor?

Just released v2.25.7 - the drop down for the graphics adapter selection should now auto expand to show the full description and monitor name. If you hover your mouse cursor over the drop down box, you'll also get a popup hint that shows you the full text if it's truncated.

[Zachs]

just to let you know subtitles doesn't work on this build or the last beta build. after testing i always had to revert back to 2.25.3. Shiandow are you also going to add which optimization to choose from?

Just a heads up, Shiandow's updated the scripts on GitHub and SuperRes is now fully featured when used with NNEDI3.

[burfadel]

Just released v2.25.7 - the drop down for the graphics adapter selection should now auto expand to show the full description and monitor name. If you hover your mouse cursor over the drop down box, you'll also get a popup hint that shows you the full text if it's truncated.

Thanks! Much appreciated :).

[Anima123]

Im surprised you keep seeing the render time increase.
Mine stays the same and Im on Optimus 860m. Could just be a issue with your specific card.

Sadly that the render time increase is real for me, it happened on both of my laptops, one is nVidia 640m and the other is with 880m.

Any help on this is much appreciated. Maybe there's some settings with nVidia control center that I've missed?

[nekromantik]

Sadly that the render time increase is real for me, it happened on both of my laptops, one is nVidia 640m and the other is with 880m.

Any help on this is much appreciated. Maybe there's some settings with nVidia control center that I've missed?

Nope I not changed any Nvidia settings. Only settings in Nvidia panel are DX gfx and what programs use Nvidia gpu. I disabled all intel video settings though.

[Anima123]

I disabled all intel video settings though.

Can you give me more details on that? It might be related with the problem I encountered somehow.

[nekromantik]

Can you give me more details on that? It might be related with the problem I encountered somehow.

In Intel Control panel, go to video settings and set everything to application instead of driver. And if there is a option to switch it off then do that.

[Dazog]

Bug:
If i skip video with the seek bar and have Auto-hide Control bar checked, the bar doesn't auto hide.

I have to uncheck the option and recheck it for it to auto-hide

[Zachs]

Bug:
If i skip video with the seek bar and have Auto-hide Control bar checked, the bar doesn't auto hide.

I have to uncheck the option and recheck it for it to auto-hide

Fixed in next release.

EDIT: Done - v2.25.8.

[ryrynz]

Give us some info on DWM handling vsync? Compatibility option?

[Zachs]

Oh that's basically disabling vsync in windowed mode and let DWM handle vsync (it already does). The default is basically what it was in previous MPDN versions.

[Belphemur]

With the Help of Zachs, I created a new PlayerExtension that will download and load automatically subtitles from OpenSubtitles.org.

You can find it in the Github repository with the other Extensions and Renderer.

To avoid annoying user that don't use subtitle, you need to activate it in the Option menu :

http://i.imgur.com/4PFyeGI.jpg

Screenshot:
http://i.imgur.com/mSsDf8S.jpg

[ryrynz]

Oh that's basically disabling vsync in windowed mode and let DWM handle vsync (it already does). The default is basically what it was in previous MPDN versions.

Any use cases where it is preferable to enable it?

Neat lil extension there Belphemur.

[Garteal]

Nice extension Belph. Looking forward to give it a try.
Suggestion: could add some way of filtering the languages available.

[Belphemur]

Nice extension Belph. Looking forward to give it a try.
Suggestion: could add some way of filtering the languages available.

I'm planning to add in the Configuration menu a possibility to select which language to fetch.

[Shiandow]

Hi everyone!

The extensions have been updated again, I've improved the Script Chain both internally and externally. It should now be somewhat easier to chain together the renderscripts you want.

I've also fixed some issue which was making it very slow to change the render chain, so switching between different renderscripts should be a lot faster.

[ryrynz]

Got an error latest MPDN and extensions pack.

Object reference not set to an instance of an object. (Extensions)

[Zachs]

Delete your RenderScripts config folder - there's a conflict that causes this error.
%localappdata%\MediaPlayerDotNet\RenderScripts.x86 (or x64)