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

[aufkrawall]

I unfortunately can't test with AMD.

Btw: I just used the updater for the installed version for the first and I'm really impressed how well designed the routine is.
Not bad, guys!

[Belphemur]

I unfortunately can't test with AMD.

Btw: I just used the updater for the installed version for the first and I'm really impressed how well designed the routine is.
Not bad, guys!

I'm happy to read this!
I redesigned it completely to make it the easiest to use and as informative as possible :)

[videonerd]

Hi Zachs, I am using the latest 64 bit version on 8.1 + nvidia 970. I notice that when I open MPDN, i get a split second spark / screen corruption on the screen. Also when I close the application, a much larger split second spark / screen corruption as it closes - any idea what may be causing this? No screen corruption during playback or otherwise though.

Thank you!

[Zachs]

Does the screen corruption go beyond MPDN window? If it does, it's almost certainly an issue outside of MPDN's control. Could be the driver or hardware.

[Zachs]

I'm happy to read this!
I redesigned it completely to make it the easiest to use and as informative as possible :)

Great job Belphemur! I too love the new updater.

BTW, MPDN now has an Extensions API version (4 currently) - I think we could use this now to match the extensions to the player. Any thoughts on how we could do this? I was thinking a text file that has the following entries on the MPDN server.

[API2]
Player=2.39.0...2.39.3
Extensions=1.14.0, 1.14.1

[API3]
Player=2.40.0
Extensions=1.15.0

[API4]
Player=2.41.0
Extensions=1.16.0

You could also use this file to check for the latest version for both the player and extensions as it should be a relatively small download, or have a server side script to extract just the latest versions from this file. The added benefit of having this file would be that when I upload a new version, I don't have to make sure I do all at once - i.e. I can upload the player, then do an extensions release, and user won't be notified of a new update until I actually update this text file. This way we guarantee nothing slips in between the time I release a new player and a new extensions version.

Users who use standalone editions could also simply lookup this file and they'll know which is the latest extensions for the player version they're currently using.

[Dlget]

i updated to 355.60.
I noticed crash when using MPC-BE.So i started testing MPDN
But same issue with MPDN.

Whenever i try fullscreen,player crashes.

[videonerd]

Does the screen corruption go beyond MPDN window? If it does, it's almost certainly an issue outside of MPDN's control. Could be the driver or hardware.

Yes it does extend beyond the window. May I know what gpu / hardware initialization happens at startup for MPDN?

[Belphemur]

Great job Belphemur! I too love the new updater.

BTW, MPDN now has an Extensions API version (4 currently) - I think we could use this now to match the extensions to the player. Any thoughts on how we could do this? I was thinking a text file that has the following entries on the MPDN server.

[API2]
Player=2.39.0...2.39.3
Extensions=1.14.0, 1.14.1

[API3]
Player=2.40.0
Extensions=1.15.0

[API4]
Player=2.41.0
Extensions=1.16.0

You could also use this file to check for the latest version for both the player and extensions as it should be a relatively small download, or have a server side script to extract just the latest versions from this file. The added benefit of having this file would be that when I upload a new version, I don't have to make sure I do all at once - i.e. I can upload the player, then do an extensions release, and user won't be notified of a new update until I actually update this text file. This way we guarantee nothing slips in between the time I release a new player and a new extensions version.

Users who use standalone editions could also simply lookup this file and they'll know which is the latest extensions for the player version they're currently using.

I have a better idea:

I can get the minimum player version required for the Extension from the changelog.

But I would need the player to advertise its compatibility with the Extensions version, this could be done very easily, modify the changelog.txt (and would make sense also):

v2.41.0 Changelog:
Works with Extension version: 1.16.0
MPDN Extensions API version 4
Fixed OpenCL compatibility issue with newer Nvidia drivers
Added option to force the use of the new OpenCL interop API


In case of multiple use a COMMA to separate them.

v2.41.0 Changelog:
Works with Extension version: 1.16.0, 1.16.1, 1.16.2
MPDN Extensions API version 4
Fixed OpenCL compatibility issue with newer Nvidia drivers
Added option to force the use of the new OpenCL interop API


Easy to parse for me, only one change for you and still the same file to change at each new version. Ho and there is no need to update retroactively the compatibility for the MPDN Changelog.

[Zachs]

I have a better idea:

I can get the minimum player version required for the Extension from the changelog.


In the future when the extensions API no longer changes so frequently, we may end up with changelogs for every version of MPDN that shows a long list of compatible MPDN extensions version...

It also doesn't cover the fact that we could release several versions of extensions without a new MPDN release.

[Zachs]

Yes it does extend beyond the window. May I know what gpu / hardware initialization happens at startup for MPDN?

Initialise Direct3D and OpenCL (if it's available).

[Zachs]

I've managed to improve startup time yet again. This time on my system, startup time (subsequent ones - first startup is always erratic for every app) has been reduced to ~250ms *with* the full MPDN extensions.

[Belphemur]

In the future when the extensions API no longer changes so frequently, we may end up with changelogs for every version of MPDN that shows a long list of compatible MPDN extensions version...

It also doesn't cover the fact that we could release several versions of extensions without a new MPDN release.

Using the API.txt file doesn't change that. At every new version of MPDN, you'll still need to update the file and to add the new version of the extensions.

We could do this differently and using the idea of Range with an hyphen:

v2.41.0 Changelog:
Works with Extension version: 1.16.0-1.17.0
MPDN Extensions API version 4
Fixed OpenCL compatibility issue with newer Nvidia drivers
Added option to force the use of the new OpenCL interop API

Only one number to change.

In case of several release of the extensions, there is no problem at all, since each extension release does tell for which player it's meant to work with. (The Updater will simply parse the "MPDN v2.41.0 and above." part of the body of the release, and since you put it in bold, it's even easier to be sure to parse the right one).

MindMap UseCase:
http://i.imgur.com/CKJtRkF.png

[Zachs]

Let's take the following sequence of events as a hypothetical use-case.


v2.41.0 Changelog:
Works with Extension version: 1.16.0
MPDN Extensions API version 4
Fixed OpenCL compatibility issue with newer Nvidia drivers
Added option to force the use of the new OpenCL interop API


Release MPDN Extensions v1.17.0 (I understand it is not necessary to update the changelog, but more on that later)


v2.41.0 Changelog:
Works with Extension version: 1.16.0-1.17.0
MPDN Extensions API version 4
Fixed OpenCL compatibility issue with newer Nvidia drivers
Added option to force the use of the new OpenCL interop API


Release MPDN v2.41.1 .2 and .3


v2.41.3 Changelog:
Works with Extension version: 1.16.0-1.17.0
Fix bug 2

v2.41.2 Changelog:
Works with Extension version: 1.16.0-1.17.0
Fix bug 1

v2.41.1 Changelog:
Works with Extension version: 1.16.0-1.17.0
Improved startup speed

v2.41.0 Changelog:
Works with Extension version: 1.16.0-1.17.0
MPDN Extensions API version 4
Fixed OpenCL compatibility issue with newer Nvidia drivers
Added option to force the use of the new OpenCL interop API


Release MPDN Extensions 1.17.1


v2.41.3 Changelog:
Works with Extension version: 1.16.0-1.17.1
Fix bug 2

v2.41.2 Changelog:
Works with Extension version: 1.16.0-1.17.1
Fix bug 1

v2.41.1 Changelog:
Works with Extension version: 1.16.0-1.17.1
Improved startup speed

v2.41.0 Changelog:
Works with Extension version: 1.16.0-1.17.1
MPDN Extensions API version 4
Fixed OpenCL compatibility issue with newer Nvidia drivers
Added option to force the use of the new OpenCL interop API


This gets messy pretty quickly. If I don't update retroactively, then it's confusing for users who look at the changelog to try and figure out which version of extensions their existing player is compatible with (e.g. they want to test an old version with its latest compatible extensions).

[Belphemur]

This gets messy pretty quickly. If I don't update retroactively, then it's confusing for users who look at the changelog to try and figure out which version of extensions their existing player is compatible with (e.g. they want to test an old version with its latest compatible extensions).

I see your point, then we just put the minimum compatible version of the extension, like you're doing for the Extension with the Player Version.


v2.42.0 Changelog:
Works with Extension from version: 1.17.0
Change of API

v2.41.3 Changelog:
Works with Extension from version: 1.16.0
Fix bug 2

v2.41.2 Changelog:
Works with Extension from version: 1.16.0
Fix bug 1

v2.41.1 Changelog:
Works with Extension from version: 1.16.0
Improved startup speed

v2.41.0 Changelog:
Works with Extension from version: 1.16.0
MPDN Extensions API version 4
Fixed OpenCL compatibility issue with newer Nvidia drivers
Added option to force the use of the new OpenCL interop API


This way the user are not getting confused, the version is clear and if they want to test an old version, they know from which version of Extension they can start (and check when that min version changed).

[Dlget]

i updated to 355.60.
I noticed crash when using MPC-BE.So i started testing MPDN
But same issue with MPDN.

Whenever i try fullscreen,player crashes.


I found solution.
Nvidia 3D vision is making this problem.
Disabled 3D vision & everything works fine

[madshi]

Yes, I've seen NVidia 3D vision turned on causing problems before.

[diimaan]

When I try to put the example scripts(AudioScripts) in the Extension folder, it shows a warning and the filters are not getting loaded.

I am running the 2.41.1

[Anima123]

I am not sure it's the right place to report.

When playing back with MPDN for some time, the newly installed windows 10 will stuck into a BSOD indicating VIDEO_MEMORY_MANAGEMNET_INTERNAL error, at least with fullscreen exclusive mode. It may happened when quiting the player or switching back to windows mode.

Read from another forum about this issue, someone said a game with fullscreen causes the same BSOD, I suspect that fullscreen exclusive mode would trigger it. I didn't have time to do tests to confirm that though.

[Zachs]

When I try to put the example scripts(AudioScripts) in the Extension folder, it shows a warning and the filters are not getting loaded.

I am running the 2.41.1

Make sure you're using the source code version of the extension, not the binary or the installer.

[Zachs]

I am not sure it's the right place to report.

When playing back with MPDN for some time, the newly installed windows 10 will stuck into a BSOD indicating VIDEO_MEMORY_MANAGEMNET_INTERNAL error, at least with fullscreen exclusive mode. It may happened when quiting the player or switching back to windows mode.

Read from another forum about this issue, someone said a game with fullscreen causes the same BSOD, I suspect that fullscreen exclusive mode would trigger it. I didn't have time to do tests to confirm that though.

You might want to report that in the NVIDIA driver feedback forum. I haven't encountered this on my NVS4200M though.

[edison]

Is there any way to reset all settings.

[Zachs]

Yes. Just delete the %localappsettings%\MediaPlayerDotNet folder.

[Zachs]

v2.42.0 Changelog:
Works with Extension from version: 1.17.0
Change of API

v2.41.3 Changelog:
Works with Extension from version: 1.16.0
Fix bug 2

v2.41.2 Changelog:
Works with Extension from version: 1.16.0
Fix bug 1

v2.41.1 Changelog:
Works with Extension from version: 1.16.0
Improved startup speed

v2.41.0 Changelog:
Works with Extension from version: 1.16.0
MPDN Extensions API version 4
Fixed OpenCL compatibility issue with newer Nvidia drivers
Added option to force the use of the new OpenCL interop API



This still seems to have a lot of duplicate lines of "Works with Extension from version: 1.16.0".

Would it be possible to simply use "MPDN Extensions API version 4" instead? And in the MPDN Extensions release notes, I'll add that line too. And each time the API version changes, MPDN changelog still also have that line.

[diimaan]

Make sure you're using the source code version of the extension, not the binary or the installer.

I used the Gain.cs and Silencer.cs!

[Zachs]

I used the Gain.cs and Silencer.cs!
I meant you can't mix the .cs files with the .DLL files. You have to use the entire MPDN extensions in its source form.

[Belphemur]

This still seems to have a lot of duplicate lines of "Works with Extension from version: 1.16.0".

Would it be possible to simply use "MPDN Extensions API version 4" instead? And in the MPDN Extensions release notes, I'll add that line too. And each time the API version changes, MPDN changelog still also have that line.

That line will also get duplicated everywhere into the Changelog.txt, it doesn't change that. But I agree it's a cleaner way to advertise the compatibility.

New use cases using API version:
http://i.imgur.com/IpokSJV.png

[burfadel]

I notice the version of Mediainfo in the native\x64 folder is pretty old, version 0.7.72 whereas the latest is 0.7.76. I replaced the one that comes with MPDN with the newer one, it works fine.

[diimaan]

I meant you can't mix the .cs files with the .DLL files. You have to use the entire MPDN extensions in its source form.

I have deleted all files in Extensions folder and %programdata% too. Extracted the scripts from MPDN_Extensions-master.zip file. Am I doing something wrong?

MPDN still shows extensions are incompatible. I tried a clean install as well.

[ryrynz]

Am I doing something wrong?


Delete %localappdata%\MediaPlayerDotNet that should sort it.

[Zachs]

I notice the version of Mediainfo in the native\x64 folder is pretty old, version 0.7.72 whereas the latest is 0.7.76. I replaced the one that comes with MPDN with the newer one, it works fine.

I'll get the DLLs updated for the next release.

I have deleted all files in Extensions folder and %programdata% too. Extracted the scripts from MPDN_Extensions-master.zip file. Am I doing something wrong?

MPDN still shows extensions are incompatible. I tried a clean install as well.

What version of MPDN are you running? As stated on the GitHub page, prerequisites: MPDN v2.41.0 and above.

[Zachs]

That line will also get duplicated everywhere into the Changelog.txt, it doesn't change that. But I agree it's a cleaner way to advertise the compatibility.

New use cases using API version:
http://i.imgur.com/IpokSJV.png

Ah I meant just the one line only when the API level changes. The added benefit of doing so is that the existing changelog is already written in such a way starting from API level 3.

[Belphemur]

Ah I meant just the one line only when the API level changes. The added benefit of doing so is that the existing changelog is already written in such a way starting from API level 3.

Sounds good, I'll make the updater assume the player use the same version as the current extension when the string is not detected in the changelog. We can do the same for the extension in fact.

I'll work on it in the following week.

String to be used:
In the changelog of the player --> "MPDN Extensions API version 4"
In the changelog of the extension --> "**API Version 4**"

Good for you ?

[diimaan]

I'll get the DLLs updated for the next release.



What version of MPDN are you running? As stated on the GitHub page, prerequisites: MPDN v2.41.0 and above.

My mistake I deleted from appdata folder only not programdata!

Running 2.41.1! Is there a binary for example scripts? I want to try them.

I liked the Tomsteady 32 bit floating point arithmetic normalizer with gain from PotPlayer, which actually is a winamp plugin Tomsteady ported into PotPlayer. It gives reasonable boost without distortion on DTS/AC3 tracks.

Can we do something similar with the mpdn?

[Zachs]

Sounds good, I'll make the updater assume the player use the same version as the current extension when the string is not detected in the changelog.

I'll work on it in the following week.

Thanks Belphemur!

BTW, I've reworded the changelog for MPDN and release notes for MPDN extensions to use the phrase "Extensions API Level" instead of extensions version. I'll stick with that exact phrase whenever I release a new update.

EDIT: LOL I just saw your edits.

[Zachs]

My mistake I deleted from appdata folder only not programdata!

Running 2.41.1! Is there a binary for example scripts? I want to try them.

I liked the Tomsteady 32 bit floating point arithmetic normalizer with gain from PotPlayer, which actually is a winamp plugin Tomsteady ported into PotPlayer. It gives reasonable boost without distortion on DTS/AC3 tracks.

Can we do something similar with the mpdn?

I'm sure it's possible now with Audio Scripts. Just need someone to port it to MPDN. If you know any audio expert who'd like to be MPDN's Audio Script dev, feel free to let me know! It could use some Audio Scripts...

[Zachs]

Some of my thoughts on Audio Scripts:

I'd like to be able to get MPDN to use Winamp's DSP plugins without any modifications - does anyone have any experience with Winamp DSP plugins?
Is this possible at all? And legally, is it allowed?

[nevcairiel]

I don't know if there are any official places left to download the Winamp SDK now that Winmap is dead, but there was an SDK to build DSP plugins, so you can equally just use that to use DSP plugins.
Laws cannot really prevent that.

[Zachs]

Ah good to know. I remember that too, not just for DSP plugins. For all sorts of plugins. Winamp is my inspiration for MPDN actually.
I'll try to find if I could get hold of that old SDK...

[Magik Mark]

Zachs is it possible to put controls for contrast, brightness, hue & saturation?

[foozoor]

Why not include the certificate inside the installer?

Why not add some performance presets?
I think a lot of noobs make dummy things with rendering scripts.

Where can I find the mpdn logo svg/ai file or highres png?
This is to create some wallpapers. ;)

[aufkrawall]

Some people have some weird configuration with their TV expecting interlaced input.
Would it be difficult to interlace output via render script?

[burfadel]

I'll get the DLLs updated for the next release.

Thanks for that :).

[Belphemur]

Why not include the certificate inside the installer?

Why not add some performance presets?
I think a lot of noobs make dummy things with rendering scripts.

Where can I find the mpdn logo svg/ai file or highres png?
This is to create some wallpapers. ;)

For the first question I can answer it.
Because in some system you won't be able to even run the installer if the certificate is not in the Trusted CA of the system.

Which means, the certificate need to be provided separately.

[elraffa]

hi.. I would like to know how to increase the brightness in MPDN.. or if there is any pixel shader for it... thanks

Enviado desde mi GT-S5360 usando Tapatalk 2

[aufkrawall]

Why has still no Radeon user tested if new interop works for them?

[Zachs]

Zachs is it possible to put controls for contrast, brightness, hue & saturation?

hi.. I would like to know how to increase the brightness in MPDN.. or if there is any pixel shader for it... thanks

Enviado desde mi GT-S5360 usando Tapatalk 2

Not something I'd put in MPDN itself, but ImageProcessor script can be used for such a thing (I suspect 3DLUT is a little over the top for you?). You just need to find the right hlsl file from the net. It's not something I use personally and I feel those controls are best adjusted on your display, not the source.

Why not add some performance presets?
I think a lot of noobs make dummy things with rendering scripts.

Where can I find the mpdn logo svg/ai file or highres png?
This is to create some wallpapers. ;)

Performance presets are simply .rs files (loaded via Scripted Render Chain) - you'd have one for each performance preset. Why haven't we got that yet? Because I have a long list of bugs to fix and things to implement and improve and I just haven't got time to do it. If anyone wants to contribute, please feel free to do so.

Ah there isn't any vector/highres MPDN logo file.

[x7007]

Hi,

Where do I copy the dtsdecoderdll.dll file ? is there a newer version better than 1.1.0.9 ? the file name suppose to be dtsdecoderdll.dll or dtsdecoder.dll

[huhn]

Hi,

Where do I copy the dtsdecoderdll.dll file ? is there a newer version better than 1.1.0.9 ? the file name suppose to be dtsdecoderdll.dll or dtsdecoder.dll

you don't need it anymore lavfilter plays DTS HD now for some time.

Is there a huge difference for you in GPU load, clocks and render times with prefer scalar over OpenCL?
Why has still no Radeon user tested if new interop works for them?
was out of internet I'm sorry.

my AMD card is currently not in a PCIe 3.0 x16 slot have to test this later.

i will test both things soon.

edit1:
MPDN 2.41.0.3220 (alternate weight access method test build)
prescale
nnedi3 256/256 480p -> 1080p 62% GPU ~30ms
openCL
nnedi3 256/256 480p -> 1080p 100% GPU ~42ms

prescale is worlds faster.

edit2:
MPDN 2.41.2.3353 with extension from the first post
i guess this version has the openCL fix. my GTX 760 died so i don't have a way to test this fix to make sure.
openCL
nnedi3 256/256 480p -> 1080p 100% GPU ~49ms
so it is slower than the old test version but is works. i haven't checked it visually. not a huge things for me the other version is way faster anyway.

[huhn]

Some people have some weird configuration with their TV expecting interlaced input.
Would it be difficult to interlace output via render script?

the driver should interlaced the progressive input frame.
and to be totally honest i don't things the picture will be any good if the TV needs interlaced as in input.

[aufkrawall]

Thanks for testing, huhn. "Always use new OpenCL Intertop API" option was checked?
If yes, AMD driver still seems to do copyback?