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

[edison]

Is there any way to reset all settings.

[Zachs]

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

[Zachs]

Originally Posted by Belphemur

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]

Originally Posted by Zachs

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]

Originally Posted by diimaan

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]

Originally Posted by Zachs

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:

[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]

Originally Posted by Zachs

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]

Originally Posted by diimaan

Am I doing something wrong?

Delete %localappdata%\MediaPlayerDotNet that should sort it.

[Zachs]

Originally Posted by 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.

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

Originally Posted by diimaan

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]

Originally Posted by Belphemur

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:

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]

Originally Posted by Zachs

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]

Originally Posted by Zachs

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]

Originally Posted by Belphemur

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]

Originally Posted by diimaan

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.