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

[ryrynz]

Originally Posted by foxyshadis

riddle me this: Is deband best used at native resolution or after resize?

Everything I've seen online recommends debanding after resizing for better quality.

[huhn]

Originally Posted by ryrynz

Everything I've seen online recommends debanding after resizing for better quality.

debanding at source resolution make way more sense.

resizing adds ringing and and other artefacts and the banding error is spread over a usually larger number of pixel because you are usually upscaling so it is way harder to fix.

[Zachs]

Originally Posted by Anime Viewer

I double click to enter FSE (I'll try using ALT+Enter to see if it has the same effect). It does happen every time (except for the one file I previously noted) I enter FSE with Direct3D 11 or 10.1 selected (it doesn't seem to happen with 9Ex). It happens immediately once full screen occurs it doesn't appear a single frame plays in fullscreen before the freeze. *Edit: odd ; my tests today don't seem to be freezing. I'm not sure what to attribute the problem going away to, but its nice that the problem is gone (hopefully it will stay that way)...

I know you said the problem is gone but if you encounter MPDN locking up again entering FSE mode, you should now get a crash after a max of 60 seconds (usually much faster though) whenever MPDN locks up. It was actually not working before as I had the conditionals set the wrong way around - i.e. it worked in debug mode but not in release mode when I intended it to work only in release mode. This is now fixed.

[Anime Viewer]

Originally Posted by Zachs

I know you said the problem is gone but if you encounter MPDN locking up again entering FSE mode, you should now get a crash after a max of 60 seconds (usually much faster though) whenever MPDN locks up. It was actually not working before as I had the conditionals set the wrong way around - i.e. it worked in debug mode but not in release mode when I intended it to work only in release mode. This is now fixed.

Interesting you should mention that. I installed the new version (2.27.0), and had it remove all configuration settings. The first video I tried (one of the ones that crashed it before) it crashed again when I went full screen. This time a (windows?) crash box popped up reporting MPDN had stopped responding with the option to close it. The bad news is the problem is back, but the good news is it now closes out properly when that happens. I thought the settings I set after the install of 2.27 were the same as the previous version, but I'll have to tinker around to see if I'm able to get it back to a non-crash state for FSE+D3D11 and determine where the problem is...

[Zachs]

Originally Posted by Anime Viewer

Interesting you should mention that. I installed the new version (2.27.0), and had it remove all configuration settings. The first video I tried (one of the ones that crashed it before) it crashed again when I went full screen. This time a (windows?) crash box popped up reporting MPDN had stopped responding with the option to close it. The bad news is the problem is back, but the good news is it now closes out properly when that happens. I thought the settings I set after the install of 2.27 were the same as the previous version, but I'll have to tinker around to see if I'm able to get it back to a non-crash state for FSE+D3D11 and determine where the problem is...

Good! Could you get the dump for me please?

[Anime Viewer]

Originally Posted by Zachs

Good! Could you get the dump for me please?

Here is what I pulled from Windows Event Viewer Details. If you need me to look up something else in that error log let me know.

Log Name:      Application
Source:        Application Error
Date:          5/27/2015 5:37:41 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Sager-NP9150
Description:
Faulting application name: MediaPlayerDotNet.exe, version: 2.27.0.3100, time stamp: 0x5565b10c
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x00000000
Fault offset: 0x00007ffd87273969
Faulting process id: 0x2500
Faulting application start time: 0x01d09879e1159c4b
Faulting application path: E:\Program Files\MediaPlayerDotNet\MediaPlayerDotNet.exe
Faulting module path: unknown
Report Id: 29f8b9bc-046d-11e5-bf55-4e53504f4f46
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-05-27T12:37:41.000000000Z" />
    <EventRecordID>117903</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Sager-NP9150</Computer>
    <Security />
  </System>
  <EventData>
    <Data>MediaPlayerDotNet.exe</Data>
    <Data>2.27.0.3100</Data>
    <Data>5565b10c</Data>
    <Data>unknown</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>00000000</Data>
    <Data>00007ffd87273969</Data>
    <Data>2500</Data>
    <Data>01d09879e1159c4b</Data>
    <Data>E:\Program Files\MediaPlayerDotNet\MediaPlayerDotNet.exe</Data>
    <Data>unknown</Data>
    <Data>29f8b9bc-046d-11e5-bf55-4e53504f4f46</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

[Zachs]

Originally Posted by Anime Viewer

Here is what I pulled from Windows Event Viewer Details. If you need me to look up something else in that error log let me know.

Ah not that one - The windows one is pretty useless. I meant the MPDN dump file in %localappdata%\MediaPlayerDotNet\*.dump.

[Anime Viewer]

Originally Posted by Zachs

Ah not that one - The windows one is pretty useless. I meant the MPDN dump file in %localappdata%\MediaPlayerDotNet\*.dump.

Yeah, I thought that was a pretty useless looking error report. I checked %localappdata%\MediaPlayerDotNet\ , but I didn't see any file(s) with a .dump extension there.

Like the previous windows log this one is probably pretty useless too, but this always seems to follow the error log report as the next report in the system:

Log Name:      Application
Source:        Windows Error Reporting
Date:          5/27/2015 5:38:14 AM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Sager-NP9150
Description:
Fault bucket 94746202975, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: MediaPlayerDotNet.exe
P2: 2.27.0.3100
P3: 5565b10c
P4: MediaPlayerDotNet
P5: 2.27.0.3100
P6: 5565b10c
P7: 3ea
P8: f
P9: Debugger.Break
P10: 

Attached files:
C:\Users\***\AppData\Local\Temp\WERC366.tmp.WERInternalMetadata.xml
C:\Users\***\AppData\Local\Temp\WERCF10.tmp.appcompat.txt
C:\Users\***\AppData\Local\Temp\WERCF30.tmp.dmp
C:\Users\***\AppData\Local\Temp\WERD0D7.tmp.WERDataCollectionFailure.txt

These files may be available here:
C:\Users\***\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_MediaPlayerDotNe_7582a8bebb5aa47c432efd010f3a12a1dcbcb3_73e57eb4_1dc94057

Analysis symbol: 
Rechecking for solution: 0
Report Id: 29f8b9bc-046d-11e5-bf55-4e53504f4f46
Report Status: 4104
Hashed bucket: 7a289c426c2e45f2a04efb3925513ac6
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-05-27T12:38:14.000000000Z" />
    <EventRecordID>117905</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Sager-NP9150</Computer>
    <Security />
  </System>
  <EventData>
    <Data>94746202975</Data>
    <Data>5</Data>
    <Data>CLR20r3</Data>
    <Data>Not available</Data>
    <Data>0</Data>
    <Data>MediaPlayerDotNet.exe</Data>
    <Data>2.27.0.3100</Data>
    <Data>5565b10c</Data>
    <Data>MediaPlayerDotNet</Data>
    <Data>2.27.0.3100</Data>
    <Data>5565b10c</Data>
    <Data>3ea</Data>
    <Data>f</Data>
    <Data>Debugger.Break</Data>
    <Data>
    </Data>
    <Data>
C:\Users\***\AppData\Local\Temp\WERC366.tmp.WERInternalMetadata.xml
C:\Users\***\AppData\Local\Temp\WERCF10.tmp.appcompat.txt
C:\Users\***\AppData\Local\Temp\WERCF30.tmp.dmp
C:\Users\***\AppData\Local\Temp\WERD0D7.tmp.WERDataCollectionFailure.txt</Data>
    <Data>C:\Users\***\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_MediaPlayerDotNe_7582a8bebb5aa47c432efd010f3a12a1dcbcb3_73e57eb4_1dc94057</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>29f8b9bc-046d-11e5-bf55-4e53504f4f46</Data>
    <Data>4104</Data>
    <Data>7a289c426c2e45f2a04efb3925513ac6</Data>
  </EventData>
</Event>

If you think any of those files dumped in the Temp directory may be of use let me know, and I can provide them.

[Zachs]

What files have you got in there?

Edit: your MPDN config, not temp folder obviously.

[ryrynz]

Just had MPDN crash myself (stopped responding) at the time I was deleting some files off another drive whilst it was just sitting there on the desktop. Windows logged the error, no MPDN dump file.
Have ticked the debug dialogue box now.. will see if it happens again.

[Zachs]

OK hang detection clearly isn't working then. It should've created a dump file.
And I'll add an option to enable it only when necessary.

[toniash]

Originally Posted by Shiandow

I've made some changes to the debanding script again. I've added grain and made it somewhat better at preserving detail. To remove particularly bad banding it's now reasonably safe to increase the "margin" to 1, or even higher.

What about madvr's version?
I'm locked in XP and can't use MPDN

[huhn]

Originally Posted by toniash

What about madvr's version?
I'm locked in XP and can't use MPDN

you can replace the deband hlsl data from the renderer extension with the one in madVR.

you find them under legal stuff\Shiandow\Deband

this should work but never tried it my self.

BTW. this is the wrong threads for madVR "problems"

[Shiandow]

Originally Posted by toniash

What about madvr's version?
I'm locked in XP and can't use MPDN

You should realyl ask those questions in the MadVR thread. In fact madshi already posted that he would update MadVR's version as well.

Originally Posted by huhn

you can replace the deband hlsl data from the renderer extension with the one in madVR.

you find them under legal stuff\Shiandow\Deband

this should work but never tried it my self.

BTW. this is the wrong threads for madVR "problems"

That doesn't work, there are some subtle differences between the shaders, and the way they are used. Hopefully it'll be possible some day, but that could be a while.

[huhn]

Originally Posted by Shiandow

That doesn't work, there are some subtle differences between the shaders, and the way they are used. Hopefully it'll be possible some day, but that could be a while.

i replaced it and it still works.
but i'm not going to continue on this topic here you have your own thread right?

[toniash]

Originally Posted by huhn

i replaced it and it still works.
but i'm not going to continue on this topic here you have your own thread right?

Ok thanks!

[Zachs]

Apart from the app hang detection bug, how are you guys finding the improved "Improve chroma reconstruction" option?
From my own tests, I can see clear improvements.

[Anime Viewer]

Originally Posted by Zachs

Apart from the app hang detection bug, how are you guys finding the improved "Improve chroma reconstruction" option?
From my own tests, I can see clear improvements.

As long as I set the Video Input Colormetric to one of the PC Ranges it looks fine, but if my system mis-detects the video, and sets it to one of the TV Ranges (while set to automatic) then I get the results I previously posted.

Can't say I've seen the clear improvements you mention, but then again I don't know what I'd be looking for to have changed. (I already thought video looked pretty good before it). Are there any particular style of scenes (with particular effects occurring) you'd say are something where the difference should jump out at us?

[Zachs]

A fully saturated red is the best way to see the changes. Previously you'll get some random pixels appearing overly bright on other parts of the red that is duller.

[Anime Viewer]

Originally Posted by Zachs

A fully saturated red is the best way to see the changes. Previously you'll get some random pixels appearing overly bright on other parts of the red that is duller.

I paused a scene where there are a couple of different shades of red, but I'm not seeing a difference between it being enabled/disabled.
Does the video have to be running in Full Screen Exclusive Mode for the improvement to happen?
How about settings? Any particular ones that might make it stand out more, or where other effects might make it less noticeable? (For example: with or without render scripts running, with or without debanding, with or without dithering, with any particular Presentation API (D3D 11, 10.1, 9Ex), with any particular color settings (ex: PC Range BT 601, 709 or 2020, Full or Limited Output, 8,10,or 16 bit bit depth, using any particular up/down scalers?