View Full Version : Media Player .NET (MPDN) - D3D HQ GPU Video Renderer [v2.49.0/v1.31.0 27 Dec 2018]
Keiyakusha
6th May 2015, 01:44
Hmm it doesn't support multi video streams yet. Haven't come across any clips that contain more than one video stream. Any chance you could get me a sample?
Certainly, but I haven't visited this forum for quite a while and don't know what is ok to post, what is not. So I'll PM it to you, if you don't mind.
ryrynz
6th May 2015, 02:03
Zach, reverting to Nvidia's driver 347.88 fixes the out of memory error.
Ah, that might be a 750ti specific bug in Nvidia's driver then because I'm running the latest 350.12 and I didn't get this problem at all.
Ah okay, I see what you guys meant now. Same issue is still present upon maximizing and resizing the window and going to fullscreen.
I'll see what else I can do to work around this bug.
EDIT: Found out what the problem is - it was my bad :o Turns out I made a tiny little error in the OpenCL NNEDI3 render script so I've reverted MPDN back to v2.25.15 and fixed the script. This should now work properly with the latest scripts from github. Oh and it should now be even faster.
ryrynz
6th May 2015, 08:25
~checks Zach's homepage~ .15? Didn't I download .16? He hasn't updated his homepage.. but doesn't he link from his homepage?
~checks forum~ Ahh, reverting builds and improving performance, that's a + 0.1 surely.. ah renderscipt based changes.. Roll on 2.26!
Hahaha... .16 didn't do anything, so I went back to.15.
There'll be a proper .16 later today which fixes a bug when you chain up multiple OpenCL scripts...
ryrynz
6th May 2015, 09:15
Zach, reverting to Nvidia's driver 347.88 fixes the out of memory error.
Ah, that might be a 750ti specific bug in Nvidia's driver then because I'm running the latest 350.12 and I didn't get this problem at all.
Oh it fixed it alright.. and I found an even bigger bug, OpenCL NNEDI3 silently just fails to work and MPDN behaves as if it hasn't even been selected.
Huh? Strange! I haven't seen anything like that!
ryrynz
6th May 2015, 10:17
Happens only with max render performance set, I've resolved the out of memory error with a clean graphics driver install, guess it's best to do that every time..
Yup. Replicated. Not sure if I should spend any time fixing it though - max render performance should only be used with systems that is so low end even hardware bilinear is a little too much for it... In fact, it doesn't even have enough precision to convert YUV to RGB properly!
ryrynz
6th May 2015, 12:26
Well if you think it's useful.. BTW do you experience any benefit to enabling render performance? It didn't really do much for me, GPU usage was pretty much the same.
I'm getting about 0.5ms less rendering time on the HD 4000 uses a slightly less memory as well, guess it's worth having there.
It's mainly for tablets SoC with LPDDR3 - i.e. very low memory bandwidth systems. On those systems, you could choose to sacrifice quality for features like Fluid Motion.
EDIT: BTW, DirectCompute won't work with Max Performance selected either. I think I'll just update the scripts so they fallback to MPDN scalers when Max Perf is selected. There's really no reason to use OpenCL or DirectCompute if your GPU has to run with Max Performance.
any idea on how to stop delayed frames?
mrcorbo
7th May 2015, 00:29
Have you checked your event logs for anything useful?
Try deleting ScriptAsmCache.(32 or 64) in %localappdata%\MediaPlayerDotNet. Maybe something got corrupted there?
Heck, might aswell delete it all if that doesn't work and see if that helps.
I tried this and no joy. Thanks for the suggestion, though.
mrcorbo
7th May 2015, 00:36
Try with the latest version - I found a problem that may have been related (not very confident it's what you're seeing though).
Still get the crash. Thanks for giving it a shot. Since no one else is seeing this, it's got to be something weird with my system.
any idea on how to stop delayed frames?
It shouldn't happen if you don't go near the limits. Delayed frames happen when the GPU is so busy it doesn't even have time to present the frame when it was asked.
Still get the crash. Thanks for giving it a shot. Since no one else is seeing this, it's got to be something weird with my system.
Does it happen if you close the file with CTRL+C first?
mrcorbo
7th May 2015, 01:17
Does it happen if you close the file with CTRL+C first?
No. But that exits fullscreen and being in fullscreen is part of the trigger. The other seems to be either having the menu open or the exit option specifically as alt+f4-ing exits with no crash.
Hmm, perhaps I could do something to make sure it exits full screen exclusive mode first before closing. It only happens in exclusive mode right?
Hmm i'm getting delayed frames still with these settings on an amd 290
dx9ex
no fluid
no dithering
bicubic no ar for all scalers
no render scripts
8 bit
max render performance
What is your present duration like? It should be less than 1ms. If not you could play around with new render path on/off, DWM sync on/off, go into full screen exclusive mode to see if it changes present duration.
ryrynz
7th May 2015, 01:52
No. But that exits fullscreen and being in fullscreen is part of the trigger. The other seems to be either having the menu open or the exit option specifically as alt+f4-ing exits with no crash.
Not display driver related is it? Try a clean install? or previous versions?
Have you checked your .NET installation with the repair tool?
What is your present duration like? It should be less than 1ms. If not you could play around with new render path on/off, DWM sync on/off, go into full screen exclusive mode to see if it changes present duration.
I tried all that and i still get delayed frames. Average render times is between 6-7ms
What was your present time?
That looks OK. Besides the delayed frame count, does it actually feel like it's stuttering when you have fluid motion enabled?
I only notice it when its a lot of delayed frames. When its 1 delayed frame I don't notice it.
Max present duration is also less than 1ms?
Max present is very random its 6-15ms
That's the problem!
The only time I've seen that is if the hardware is overclocked a little too much, or a driver that is misbehaving.
I tried stock settings for my gpu and its still the same Max present times. So you think its a driver issue?
Try different driver versions perhaps? My old ATI card had this problem too but changing those settings I pointed out earlier, I managed to find some that the driver was happy with. Oh maybe try direct 3d 11 too. But in exclusive mode I've never seen it with any GPUs.
Oh and try changing back buffer counts too.
mrcorbo
7th May 2015, 13:30
Hmm, perhaps I could do something to make sure it exits full screen exclusive mode first before closing. It only happens in exclusive mode right?
No, it does it even if exclusive mode is disabled. I think MPDN exits exclusive mode when you activate the right-click menu anyway, or at least it seems like it does.
mrcorbo
7th May 2015, 13:39
Not display driver related is it? Try a clean install? or previous versions?
Have you checked your .NET installation with the repair tool?
I haven't tried different drivers yet. The crashes have been in ntdll.dll or clr.dll, so probably .NET related. I'll check out the repair tool when I have some time. Thanks.
Just a quick heads up. I've updated the OpenCL NNEDI3 scripts on github. Let me know if it's faster / slower for you.
Anime Viewer
8th May 2015, 04:02
Just a quick heads up. I've updated the OpenCL NNEDI3 scripts on github. Let me know if it's faster / slower for you.
The updated OpenCL NNEDI3 is completely unusable for me. When I first tried to set it I got a black screen (no video) with 3-4ms being listed. When I exited MPDN, went back in changed to the original NNEDI3 (to confirm it still worked), and then tried to go back to OpenCL NNEDI3 it had a frozen video screen and the hour glass spinning indefinitely. I couldn't escape the freeze or shut down MPDN, and had to log off then re-log in to get it to close.
Hmm, might have encountered an NVIDIA OpenCL compiler bug there. I don't have access to my 560 GTX at the moment so I think I'll revert the changes until I can fully test it on NV's latest drivers.
EDIT: I tested this on an NV 8400GS with driver v341.44 and it's fully working... What version are you running by the way?
EDIT2: Anyone else with the same problem?
ryrynz
8th May 2015, 05:53
EDIT2: Anyone else with the same problem?
Can confirm you borked it.
OK I'll revert it then, at least until I get a chance to test it on my 560 GTX.
It does run on your Intel HD4000 though right?
ryrynz
8th May 2015, 06:02
Yup, fine on HD graphics.
Anima123
8th May 2015, 06:11
Same here as 'Anime Viewer'.
Yeah looks like a bug in NV's newer drivers.
ryrynz
8th May 2015, 10:39
Yeah looks like a bug in NV's newer drivers.
Shame, it sped up NNEDI3 16 taps on my HD4000 by over 20%, getting similar performance gains on Nvidia would deliver better performance than madVR (at least on my card)
Still can't recommend it for Intel though it's almost twice as slow as the shader version 'prefer vector & small code'. I would quite like to see what NNEDI3 performance is like on Skylake's GT4e.
Ah it was never meant to speed up NV hardware!
Are you saying MPDN's OpenCL NNEDI3 is slower than madVR on your card? That's not the case on my 560GTX...
Btw I've uploaded the changes to GitHub, reverting only NV's code path.
I'd like to get some feedback on whether AMD users are gaining/losing performance from the changes at all. As for Intel, it is ~20% faster.
Anime Viewer
8th May 2015, 13:23
Hmm, might have encountered an NVIDIA OpenCL compiler bug there. I don't have access to my 560 GTX at the moment so I think I'll revert the changes until I can fully test it on NV's latest drivers.
EDIT: I tested this on an NV 8400GS with driver v341.44 and it's fully working... What version are you running by the way?
I'm running v350.12 (which uses OpenCL 1.2). Your v341.44 runs OpenCL 1.1 correct? There probably is a good chance that the problem is related to how Nvidia's OpenCL 1.2 and 1.1 differ as opposed to something else in the driver. I wouldn't be surprised if the other people who are encountering the same problem as me are running Nvidia's OpenCL 1.2 as well.
Running it with my Intel 4000 gpu NNEDI3 was still unusable (running at 246ms by itself, and 300ms as part of a script chain with debanding and superchromares).
Well it won't do 720p on my Intel HD4600 but for lower res upscaling it works just fine. It's those lower res sources that arguably need NNEDI3 more than the higher res ones.
flacattack
9th May 2015, 02:35
Starting with the newer builds (around April 30th), I get a blank screen when trying to use SuperRes with my r9 290x. The other scripts work perfect.
InvalidArgument=Value of '0' is not valid for 'SelectedIndex'.
Parameter name: SelectedIndex
Shiandow
9th May 2015, 03:03
You probably need to reset SuperRes's settings. There should be a "SuperRes.config" file somewhere, you can just delete that. Or if it's in a script chain you can just remove it and then add it back again.
flacattack
9th May 2015, 04:26
Worked like a charm, thank you Shiandow!
ryrynz
9th May 2015, 05:16
Hey Zach, feature request! Reset to defaults! :)
That was always in the plan but it's not that easy. There are a few 'reset to defaults' that I'd like to see - within each render script / player extension, and a global one that resets all of MPDN's config to default as well as one that wipes both MPDN, render scripts and player extensions config. Haven't figured out a way to do that yet...
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.