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

[Shiandow]

Originally Posted by huhn

well you missed something important here.

this only makes sense when your screen is perfectly calibrated to 2.2 but... just calibrate it to 2.4 if that is what you want.
and gamma should be chosen on room ambient light.

the current "standard" is BT 1886 BTW.

My screen happens to be pretty close to a 2.2 power curve, which is good for webpages and text, but not so good for video. I agree that ambient light means you need a slightly different gamma, which is why I've added a hotkey to enable/disable the gamma conversion.

Originally Posted by Hrxn

SSIM? As in SSIM Downscaler?

Well, I've seen/heard this before, but never found an convincing explanation so far. What is the point of the downscaling step? How does it really improve anything?

Most downscaling methods end up softening the image. The SSIM downscaler basically sharpens the image just enough to make it as sharp as the original. It's subtle, but it is noticeable.

[pose]

Shiandow, what is the best Luma scaler to use in combo with SSSR (hybrid mode) in your opinion? I do 720p -> 1080p mostly.

[donger]

aaand frames tearing out of nowhere
this on top of ZERO help in here on the forum = uninstalled

[huhn]

so zero help means ignoring the dev that tried to help?

[stax76]

Problem is there is only one core dev and he is offline since a couple of months, I was once offline 1,5 years, I hope he is fine.

[Zachs]

Originally Posted by stax76

Problem is there is only one core dev and he is offline since a couple of months, I was once offline 1,5 years, I hope he is fine.

There's actually two Devs. And I'm not really offline. Lol.

Just been busy with work. There's not much I wanted to do to improve the player anyway that is beyond what needs to be done within the core app. It's so extensible that anyone could add features to it.

[Zachs]

Originally Posted by stax76

What could be the reason if the player don't start? I just hear some error beep.

Did you ever figure out what was wrong? The only thing I could think of is that NGEN generated incorrect code on your machine, which could only happen if you have had hardware...

[stax76]

I was just trying to say you haven't been posting since a few months. Who is the other core dev then? I didn't notice anybody seriously trying to help. I've not figured out what is wrong, I was hoping a dev will tell what to do. Please note that when I first tried the player when it was new the exact same problem was happening and it had something to to with the subtitle filter so obviously there was no properly working error handling.

[Zachs]

There's Shiandow too.

When you said it beeped when you tried starting the player, did you mean the player window itself wouldn't even appear? If so that's way before anything to do with MPDN. The first thing MPDN does is it shows the player window, before it loads Configs etc.

[stax76]

I was thinking Shiandow makes plugins and don't work on the core.

The window is only visible a few milliseconds.

[Zachs]

Hmm did you try running MPDN without extensions? If you have a clean VM (download one from MS if you don't), you could try it in there. MPDN runs fine with the default settings even in a VM.

[stax76]

I tried the portable and the installer both x64 and x86, it works in my vmware client Win 7 but not on my system Win 10, in Visual Studio it shows:

Exception thrown at 0x7498B802 in MediaPlayerDotNet.exe: Microsoft C++ exception: std::exception at memory location 0x00EFE914.

There is nothing logged in the Windows Event Log.

Suggestion: Upload a build with debug symbols.

[stax76]

Is Windows 10 officially supported and have you tested it on Windows 10 1703? Has anybody got it working on Windows 10 1703?

[mrcorbo]

Originally Posted by stax76

Is Windows 10 officially supported and have you tested it on Windows 10 1703? Has anybody got it working on Windows 10 1703?

It works here on the latest Fast-Ring Insider build, FWIW.

[Garteal]

I've been using MPDN since release with zero issues on Windows 10 (including build 1703). Whatever problems you're having is something interfering on your end. The least you can do is provide some detail of what you have tried, your setup, what processes are running, etc. I mean you're a dev and all, you know what you can do to help us help you.

[stax76]

I'm just starting as player dev , it was the 4K display and/or 288 DPI setting, half of the players don't support it I forgot, one of the many reasons I get into player development.

[Zachs]

Originally Posted by stax76

I'm just starting as player dev , it was the 4K display and/or 288 DPI setting, half of the players don't support it I forgot, one of the many reasons I get into player development.

What? So you knew what the problem was all along?

[stax76]

I did not know it along, I didn't spend much thought on it until being reminded being a dev and that if I don't help myself probably nobody will.

[Garteal]

You need to work on your reading comprehension.

Anyway, 4k works fine. The issue is that 288DPI you have set. I've tried a few other odd custom DPI values thinking there's an issue with odd custom values, but what I tested worked fine.

[Shiandow]

Originally Posted by stax76

I was thinking Shiandow makes plugins and don't work on the core.

The window is only visible a few milliseconds.

For future reference I am now also a dev for the core code. But my changes so far has been mostly limited to some new timing code for the renderer (and also some dithering code, but I recently found out the actual rendering uses a different code path which still used the old ditherers).

Originally Posted by stax76

Suggestion: Upload a build with debug symbols.

Unfortunately right now not all parts of the core code can be made open source (and therefore need to be obfuscated, so no debug symbols).