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

[Zachs]

Well delayed frames occur when your GPU had failed to present the frame in the vsync MPDN wanted. This can be due to various reasons external to MPDN. But if it's just delayed by one frame on a 75hz display, chances are you won't even notice it.

[christopherw]

Interesting player with some useful potential. Small footprint is a bonus.

I'm having unexpected results with interlaced content though - with identical LAV filter settings, using either DXVA or CUVID, it's not properly deinterlacing. Even with 50/60p enabled and attempting to force either just hardware or just Yadif software, and aggressively deinterlacing, everything is being blend deinterlaced.

The same video files, with MPC-HC and LAV configured identically, play perfectly.

I'm happy to communicate privately and send some example video files so you can attempt to replicate the issue if you wish, PM me through the board.

[burfadel]

Does this happen with the older build as well (i.e. API level 7)?

Yes, I tried the last release with the old extension, and when the media file changes it comes up with the crash dialogue that says MPDN - Media Player .NET has stopped working.

I might try a really ancient version and associated extension and see if something has changed over the versions.

[burfadel]

I found where the issue is introduced, it's the extensions version v1.22.0. I tried numerous MPDN's and extensions, and they all worked fine (they would not crash). I then went back to MPDN v2.44.3.3480 and tried the numerous supported extensions. The v1.21.x series works fine (including v1.21.4), I went previous/next about 60 times trying to get it to crash, perfectly stable! I then tried extension version v1.22.0 (also supported under the same MPDN), and it crashed just like the latest versions, without fail. I then tried extension version v1.21.4 again, and no issues!

So, the issue was definitely introduced in v1.22.0. I hope that makes it easier to track down what could be causing it!

[ryrynz]

So, the issue was definitely introduced in v1.22.0. I hope that makes it easier to track down what could be causing it!

Possibly unrelated but I had mpdn crash on Windows 7 last night when changing files. Not sure what caused it but Icaros crashed also.

[burfadel]

Possibly unrelated but I had mpdn crash on Windows 7 last night when changing files. Not sure what caused it but Icaros crashed also.

It could be? I don't use Icaros so I can't say about that. All I know is that anything before extensions v1.22.0 works perfectly, v1.22.0 or later it crashes when changing files consistently.

[Anima123]

It could be? I don't use Icaros so I can't say about that. All I know is that anything before extensions v1.22.0 works perfectly, v1.22.0 or later it crashes when changing files consistently.

I've experienced similar crashes too. Now I had to quit MPDN and restarted it playing another file in order to avoid the crash.

[burfadel]

I've experienced similar crashes too. Now I had to quit MPDN and restarted it playing another file in order to avoid the crash.

It's good to know that's it's not just me then! I'm sure it's something simple.

[Zachs]

Do you have preload next file enabled in your playlist settings?

If you do, try disabling that to isolate the problem.

[edison]

The program will crash if the speaker/headphone was unpluged.

[burfadel]

Do you have preload next file enabled in your playlist settings?

If you do, try disabling that to isolate the problem.

No luck here. I tried that and it still crashes as before.

[Zachs]

Can you try disable xysubfilter and try again?

[Anima123]

Crash still occurs after disabling subtitle feature.

[burfadel]

Same here, and I also have subtitles disabled by default and double checked to make sure.

[ryrynz]

I sometimes get visual corruption when loading the next file (pink or green lines throughout the image) briefly when preloading is active.'
I haven't been able to reliably reproduce the next file load crashing so far.

[Zachs]

Well I can't seem to be able to replicate the crashing problem. Are you guys using the LAV Filters included with MPDN?

[Anima123]

In recent days I twiddled parameters around SuperRes, since I am not satisfied with the 'artificial' kind effect NNEDI3 produced.

Now I am quite satisfied with Super-xBR as image doubler with Edge Strength 1.00 and Sharpness 0.35, and without 'third pass', the SuperRes configured with the default parameters. Though not perfect, but it gives me natural and vivid images watching a movie from a fare distance.

Tried with other image doublers, some, e.g. the NNEDI3 may better closed look, yet the overall visual pleasure it brings is not as good as with the settings I mentioned.

[Zachs]

So, the issue was definitely introduced in v1.22.0. I hope that makes it easier to track down what could be causing it!

This is strange. v1.22.0 was mainly about the playlist supporting URLs. When it crashes, do you get an error message?

[burfadel]

I was using the latest LAVFilters 0.66.0-31 which works perfectly with all other media players, and even all versions of MPDN with the extensions prior to v1.22.0. However, I just tried a fresh install of MPDN (clean install option) and extensions (same, clean install), installing the version of LAV Filters that came with MPDN. Same result, crash on changing media files.

Something between the extensions in v1.21.4 and v1.22.0 is causing the crash. Was the compile environment exactly the same for v1.21.4 and v1.22.0? Since it is such a specific fault (only with extensions v1.22.0 and later) and for me doesn't affect anything else, I still suspect the issue lies with one of the commits. It could either be the commit itself, or something in the commit that causes something in MPDN to go awry?

Is it possible for you to compile a few different test MPDN extensions omitting some of the different commits between v1.21.4 and v1.22.0 to see which commit is causing the issue?

Thanks

[Zachs]

Interesting player with some useful potential. Small footprint is a bonus.

I'm having unexpected results with interlaced content though - with identical LAV filter settings, using either DXVA or CUVID, it's not properly deinterlacing. Even with 50/60p enabled and attempting to force either just hardware or just Yadif software, and aggressively deinterlacing, everything is being blend deinterlaced.

The same video files, with MPC-HC and LAV configured identically, play perfectly.

I'm happy to communicate privately and send some example video files so you can attempt to replicate the issue if you wish, PM me through the board.

Could you cut a small section and post it somewhere so others could have a look at it too?

[burfadel]

This is strange. v1.22.0 was mainly about the playlist supporting URLs. When it crashes, do you get an error message?

No, just the standard crash error message that I was quick enough to capture :)

http://oi59.tinypic.com/168by92.jpg

and then:

http://oi57.tinypic.com/2ldkjkl.jpg

[Zachs]

Is it possible for you to compile a few different test MPDN extensions omitting some of the different commits between v1.21.4 and v1.22.0 to see which commit is causing the issue?

You can try grabbing the source code version from GitHub. You can get the incremental updates from https://github.com/zachsaw/MPDN_Extensions/compare/1.21.4...1.22.0

Can you try v1.22.0 (source version) and see if that fails as well? If it does, replace playlist*.* with the ones from v1.21.4.

[Zachs]

No, just the standard crash error message that I was quick enough to capture :)

http://oi59.tinypic.com/168by92.jpg

and then:

http://oi57.tinypic.com/2ldkjkl.jpg

You should be able to get the error message from EventViewer.

[Anima123]

I got this from EvenViewer:

Faulting application name: MediaPlayerDotNet.exe, version: 2.45.0.3555, time stamp: 0x5627415f
Faulting module name: VideoFrameServicesNative.dll, version: 0.0.0.0, time stamp: 0x55c2b55f
Exception code: 0xc0000005
Fault offset: 0x0000000000004370
Faulting process id: 0x14f4
Faulting application start time: 0x01d10f7964c41c3c
Faulting application path: C:\Program Files\MPDN\MediaPlayerDotNet.exe
Faulting module path: C:\Program Files\MPDN\Native\x64\VideoFrameServicesNative.dll
Report Id: b063df52-7b6c-11e5-8272-f81654b0da87
Faulting package full name:
Faulting package-relative application ID:

EventData as following:
MediaPlayerDotNet.exe
2.45.0.3555
5627415f
VideoFrameServicesNative.dll
0.0.0.0
55c2b55f
c0000005
0000000000004370
14f4
01d10f7964c41c3c
C:\Program Files\MPDN\MediaPlayerDotNet.exe
C:\Program Files\MPDN\Native\x64\VideoFrameServicesNative.dll
b063df52-7b6c-11e5-8272-f81654b0da87


Edit: And the .Net Runtime Error as following:
Application: MediaPlayerDotNet.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at B.c.a(IntPtr, UInt32, UInt32, IntPtr, UInt32, IntPtr, UInt32, IntPtr, UInt32)
at B.c.a(IntPtr, UInt32, UInt32, IntPtr, UInt32, IntPtr, UInt32, IntPtr, UInt32)
at Mpdn.D3D9VideoRenderer.VideoRenderer.A(IntPtr)
at Mpdn.D3D9VideoRenderer.VideoRenderer.A(Int64, IntPtr, System.Collections.Generic.IList`1<IntPtr>, System.Collections.Generic.IList`1<System.Drawing.Size>, System.Collections.Generic.IList`1<SharpDX.RectangleF>, Boolean)
at B.K.c(B.I)
at B.K.f(Boolean)
at B.K.A(System.Action`1<Boolean>)
at B.K.s()
at MediaPlayerDotNet.MainForm.A(System.Drawing.Size)
at MediaPlayerDotNet.MainForm.A(Boolean, Boolean, Boolean)
at MediaPlayerDotNet.MainForm.OpenMedia(System.String, Boolean, Boolean, Boolean)
at MediaPlayerDotNet.MainForm.C(System.Object, System.EventArgs)
at System.Windows.Forms.ToolStripItem.RaiseEvent(System.Object, System.EventArgs)
at System.Windows.Forms.ToolStripMenuItem.OnClick(System.EventArgs)
at System.Windows.Forms.ToolStripItem.HandleClick(System.EventArgs)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(System.Windows.Forms.MouseEventArgs)
at System.Windows.Forms.ToolStrip.OnMouseUp(System.Windows.Forms.MouseEventArgs)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(System.Windows.Forms.MouseEventArgs)
at System.Windows.Forms.Control.WmMouseUp(System.Windows.Forms.Message ByRef, System.Windows.Forms.MouseButtons, Int32)
at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.ToolStrip.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.ToolStripDropDown.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
at A.k.A(System.String[])

[Zachs]

Thank you!

Does this occur when you have preload next file disabled?

EDIT: Reproduced the error. Only happens when you have reset window size when closing media enabled.

EDIT2: Can you guys confirm if disabling the option fixes the issue?

[burfadel]

Thank you!

Does this occur when you have preload next file disabled?

EDIT: Reproduced the error. Only happens when you have reset window size when closing media enabled.

EDIT2: Can you guys confirm if disabling the option fixes the issue?

Yes, works fine with the reset windows size when closing disabled! Strange that it only occurred with extensions v1.22.0 and not v1.21.4 (under the previous MPDN version)?

The event view log for me shows basically the same as anima123:
Fault bucket 120342797506, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: MediaPlayerDotNet.exe
P2: 2.45.0.3555
P3: 5627415f
P4: VideoFrameServicesNative.dll
P5: 0.0.0.0
P6: 55c2b55f
P7: c0000005
P8: 0000000000004370
P9:
P10:

[Zachs]

Excellent!

Fixed in next release.

[burfadel]

Excellent!

Fixed in next release.

I also just found that enabling 'Reclock' under 'Audio Script' causes the same crash, the details are the same in the event viewer as the other crash.

[Zachs]

I also just found that enabling 'Reclock' under 'Audio Script' causes the same crash, the details are the same in the event viewer as the other crash.

With or without reset window size?

[Anima123]

Without 'reset window size closing media', I got these error messages when trying to playback a video file:
TITLE: SharpDX Error
------------------------------

An unexpected error 'SharpDX.SharpDXException' has occurred.

------------------------------
ADDITIONAL INFORMATION:

HRESULT: [0x80004005], Module: [General], ApiCode: [E_FAIL/Unspecified error], Message: Unspecified error
(SharpDX)

------------------------------
BUTTONS:

&Abort
------------------------------


And yes, I am using 'Reclock' together with Sanear Audio Renderer.

Edit: disable 'Reclock' does not make the error go away.
Edit2: reboot windows 8.1 seems to fix this error, you might want to ignore this post.

[burfadel]

With or without reset window size?

Without reset window size. It causes the exact same error details in the same file as with the reset window size option, so I guess if you fixed that it might have also fixed this issue?

The other thing I noticed with disabling the reset window size option is that manually changing media files seems to be very snappy, smooth, and seamless now. It could just be psychological, but I am sure that changing between files seems to be improved.

EDIT:
It seems that selecting any option under Audio Script causes the same crash (same details), whether it is reclock, DynamicRangeCompressor, Script Chain, or Script Group. This crash even occurs when nothing is enabled under script chain or script group, simply selecting it will cause the crash. I suspect though that if the error is fixed with the reset window size that these other issues may also hopefully be fixed (seeing as the crash is in the same file with the same crash details).

[Zachs]

Without reset window size. It causes the exact same error details in the same file as with the reset window size option, so I guess if you fixed that it might have also fixed this issue?

The same stack trace as well?

[burfadel]

Here are the crash results for each of the four audio render options:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: MediaPlayerDotNet.exe
P2: 2.45.0.3555
P3: 5627415f
P4: VideoFrameServicesNative.dll
P5: 0.0.0.0
P6: 55c2b55f
P7: c0000005
P8: 0000000000004370
P9:
P10:

I only pasted it once because all four crash reports are absolutely identical (well apart from the report ID further down, which makes sense since it's a different crash event).

and the associated .NET error (same for all of the crashes, include the reset window size option):

Application: MediaPlayerDotNet.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at B.c.a(IntPtr, UInt32, UInt32, IntPtr, UInt32, IntPtr, UInt32, IntPtr, UInt32)
at B.c.a(IntPtr, UInt32, UInt32, IntPtr, UInt32, IntPtr, UInt32, IntPtr, UInt32)
at Mpdn.D3D9VideoRenderer.VideoRenderer.A(IntPtr)
at Mpdn.D3D9VideoRenderer.VideoRenderer.A(Int64, IntPtr, System.Collections.Generic.IList`1<IntPtr>, System.Collections.Generic.IList`1<System.Drawing.Size>, System.Collections.Generic.IList`1<SharpDX.RectangleF>, Boolean)
at B.K.c(B.I)
at B.K.f(Boolean)
at B.K.A(System.Action`1<Boolean>)
at B.K.s()
at MediaPlayerDotNet.MainForm.A(System.Drawing.Size)
at MediaPlayerDotNet.MainForm.A(Double)
at MediaPlayerDotNet.MainForm.A(Mpdn.IMedia, Boolean, Boolean, Boolean)
at MediaPlayerDotNet.MainForm.OpenMedia(Mpdn.IMedia, Boolean, Boolean, Boolean)
at Mpdn.Extensions.PlayerExtensions.Playlist.PlaylistForm.OpenMedia(Boolean)
at Mpdn.Extensions.Framework.PlayerExtension`2[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].PlayerKeyDown(System.Object, Mpdn.PlayerControlEventArgs`1<System.Windows.Forms.KeyEventArgs>)
at System.EventHandler`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Invoke(System.Object, System.__Canon)
at Mpdn.PlayerControl.OnKeyDown(System.Windows.Forms.KeyEventArgs ByRef)
at MediaPlayerDotNet.MainForm.A(System.Object, System.Windows.Forms.KeyEventArgs)
at System.Windows.Forms.KeyEventHandler.Invoke(System.Object, System.Windows.Forms.KeyEventArgs)
at System.Windows.Forms.Control.OnKeyDown(System.Windows.Forms.KeyEventArgs)
at System.Windows.Forms.Control.ProcessKeyEventArgs(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Form.ProcessKeyPreview(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control.ProcessKeyMessage(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control.WmKeyChar(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
at A.k.A(System.String[])


I notice the line Mpdn.D3D9VideoRenderer.VideoRenderer.A(IntPtr), even though I have the presentation API set as Direct3D 11. When I press Ctrl+J for the stats when the video's are playing it does say Direct3D 11. Is that right?

[Zachs]

Ah disable "Resize window to fit when opening media" too and see if it still crashes.
If it doesn't then it's the same issue that I've fixed.

And yes D3D9VideoRenderer is really just because MPDN started out as just a D3D9 renderer and when I added D3D 10 and 11, I just left it as it is.

[burfadel]

The 'reset window size when closing media' causing the crash regardless of any other setting, and 'resize window to fit when opening media' causes the crash when any of the options is selected under the audio renderer, but is fine if 'none' is selected.

So I guess the issue is fixed with the next build, so all good!

[Zachs]

Should be fixed now in v2.45.1.

[burfadel]

Should be fixed now in v2.45.1.

Yes it seems to be! That's including the audio render options etc as well.

Thanks :)

[burfadel]

There is a new issue, however it seems to be related to the previous issue. It only occurs when 'Reset window size when closing media' is selected as well as an Audio renderer option. When you change from windowed mode to exclusive mode, more often than not when going back to exclusive mode the picture will stop, but the audio will continue. You just need to move the progress slider and it seems to correct itself. Well, apart from the one time when I was testing it when the whole program froze, but the audio continued! I had to use the task manager to close it. Sorry, no event viewer information this time as the program didn't actually crash. Just a video playback freeze.

Only an issue with that option and any audio renderer option selected (I use the reclock option). If either are selected on their own there doesn't seem to be an issue.

[djsolidsnake86]

image quality is better thant using mpc hd with madvr?

[Dreamland]

I think MPDN is the best player for quality video ! great!

[djsolidsnake86]

I think MPDN is the best player for quality video ! great!

doesn't support madvr
what is the output?

[Dreamland]

Madvr + MPC-HC is very good..but has not the same quality video of MPDN
my opinion watching in my Eizo monitor
(excuse me for my bad english ) I.m italian

[djsolidsnake86]

Madvr + MPC-HC is a very good..but has not the same quality video of MPDN
my opinion
(excuse me for my bad english ) I.m italian

come fai a dirlo?
how do you know that

[Dreamland]

mettendo a confronto un video con Madvr + MPC-HC e lo stesso video con MPDN
piu contrasto, colori piu vivi,l'immagine sembra anche piu pulita e fluida..
tanti settaggi con Madvr ma MPDN è uscita sempre vincente
(sempre secondo me)
se vuoi sapere i miei settaggi , te li dico senza problemi

[burfadel]

Madvr + MPC-HC is very good..but has not the same quality video of MPDN
my opinion watching in my Eizo monitor
(excuse me for my bad english ) I.m italian

how do you know that

I'm sure he is well aware oh his own opinion of things :). Dreamland, what you said makes perfect sense, and I agree!

@Zachs
That new issue I mentioned a couple of posts back, I can't seem to replicate it now! It was doing it without fail last night, but now I just can't seem to get it to do it with the same settings. I haven't restarted my computer or done anything else in the meantime, so I'm not sure what's going on there.

If anyone at all has the issue of the video pausing but audio continuing when going from windowed mode to exclusive mode (only happened when certain settings were selected) please report it. Issues will only be fixed if they are known!

[burfadel]

Okay, seems to be a bit temperamental. If I go to windows mode, do something on the computer like write this out in Chrome), then go back to the player and put it in exclusive mode, it may have paused video playback with the sound continuing, but it's not consistent. However, it doesn't seem to do it at all without the two settings I mentioned earlier selected. It's a difficult one to reproduce! I'm sure the first time it happened that I didn't have Chrome or anything open...

[Anima123]

burfadel, would you please try rebooting OS and see if this problem is still there? Sometimes rebooting can solve some kind of odd ones.

[Zachs]

Does it happen if you enter FSE mode with alt enter?

[ryrynz]

Encountered a few situations where switching between windowed and FSE modes results in the picture freezing and audio continuing. I've had it when going either way.
When performing a double click again to fix it the video then stutters quite badly for a few seconds before playing back as normal.
New windowed mode, D3D9Ex, HD Graphics 4000. Thought I'd mention it here before doing any further investigation into D3D modes, different systems etc.

I've also experienced a second or so pause of the video occasionally after seeking whilst using the arrow keys, the audio has no delay.

Anyone else experienced either of these?

[burfadel]

Encountered a few situations where switching between windowed and FSE modes results in the picture freezing and audio continuing. I've had it when going either way.
When performing a double click again to fix it the video then stutters quite badly for a few seconds before playing back as normal.
New windowed mode, D3D9Ex, HD Graphics 4000. Thought I'd mention it here before doing any further investigation into D3D modes, different systems etc.

I've also experienced a second or so pause of the video occasionally after seeking whilst using the arrow keys, the audio has no delay.

Anyone else experienced either of these?

Yes, me! The first one at least. I'm using Direct3D 11, R9-280X, exclusive mode etc, but the symptoms sound identical. It seems to be a bit hard to reproduce though, it doesn't happen all the time.

Under options --> general, do you have either of the resize options selected, if so, which?

Also, do you have any option at all selected under 'Audio Renderer' --> 'Audio Script'?

If so to any of the above, set audio script to 'none' and see if the behaviour continues. If so, try deselecting the resize options and see if the problem is resolved. The reason for this is a crash bug was recently fixed that affected these options, but I believe there is still some residual related 'buggyness'...

Of course, if your trials regarding these settings prove fruitful, report back which one was the offending options for you. Unfortunately for me it only occurs sometimes, which makes testing difficult. It is an annoying bug though!