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

madshi

22nd January 2015, 09:02

If it came from a movie screen shot wouldn't it be 1920x1080 to begin with since like you said 8 lines are garbage and trimmed?

Also the question was why pull the rug from under the player when it knew 1920x1088 was always going to be 1920x1080 in the first place, since by your argument it always is even for PNG?
Some decoders & players don't force 1088 down to 1080, so the screenshot could have come from such a player/decoder.

DirectShow allows resolution changes like that. It can happen in the middle of a stream, too. Of course it would be nicer if it didn't happen. Sometimes the container reports one resolution and the video bitstream decodes to a different resolution. Sometimes aspect ratio handling can result in two different resolutions, depending on whether you round up or down etc. Sometimes [...]. Of course in an ideal world the resolution would be known right at the start and never change again. Anyway. Just trying to explain some of the possible reasons for such resolution changes. I'm not in a position to change any of that, anyway, so I guess I should stop arguing at this point. You asked why, I tried to explain. If you're not happy with the way things are, you can always contact nevcairiel about it. He's the one who can change things.

Anima123

22nd January 2015, 09:04

Are Optimus users still reporting the ms increasing problem when watching long videos?

Unfortunately the problem still there with the latest version. You will need to use SuperRes with NEDI enabled to trigger it though.

Zachs

22nd January 2015, 09:12

Some decoders & players don't force 1088 down to 1080, so the screenshot could have come from such a player/decoder.

DirectShow allows resolution changes like that. It can happen in the middle of a stream, too. Of course it would be nicer if it didn't happen. Sometimes the container reports one resolution and the video bitstream decodes to a different resolution. Sometimes aspect ratio handling can result in two different resolutions, depending on whether you round up or down etc. Sometimes [...]. Of course in an ideal world the resolution would be known right at the start and never change again. Anyway. Just trying to explain some of the possible reasons for such resolution changes. I'm not in a position to change any of that, anyway, so I guess I should stop arguing at this point. You asked why, I tried to explain. If you're not happy with the way things are, you can always contact nevcairiel about it. He's the one who can change things.
Just trying to make some sense out of why it was even reporting 1088 to the player when it knew what the actual size was in the first place and had no intention of supplying the stream in 1088 either.

Edit: appreciate your explanation, but the above still doesn't quite get explained... Anyway, it's fixed so not too bothered by it. Just curious what the rationale might be behind such an implementation.

Zachs

22nd January 2015, 09:13

Unfortunately the problem still there with the latest version. You will need to use SuperRes with NEDI enabled to trigger it though.
Nekromantik tried it on his Optimus system and reported no such issues a couple of pages back.

Zachs

22nd January 2015, 09:16

Thanks for the new version. Using the arrow key to adjust volume seems not working anymore when playing a video in FSE.
Will have a look later.

EDIT: Fixed in next release - apparently all shortcut keys with Shift+Right/Left were not processed in fullscreen mode.

nevcairiel

22nd January 2015, 09:20

Also the question was why pull the rug from under the player when it knew 1920x1088 was always going to be 1920x1080 in the first place, since by your argument it always is even for PNG?

Consider it a test if resolution changes work in the renderer. It did find a bug, didn't it? :p
As madshi already mentioned, actual 1920x1088 content which is intentionally this resolution is practically non-existent, and the only content i've ever seen to use this resolution is 1080p content with missing cropping information.

That it doesn't also change this in the initial media type immediately is mostly an oversight, but a change in resolution doesn't hurt anyone, it can happen with every video for various reasons, so I'm not worried.

Anima123

22nd January 2015, 09:26

Nekromantik tried it on his Optimus system and reported no such issues a couple of pages back.

Nekromantik, could you please share with us how you do the rendering time increasing test, including player configurations, hardware, driver version and the info of the video you're doing testing?

I have tested this on two of my laptops with Optimus, both had exactly the same problem. It should not be a false alarm.

Besides, can anyone with Optimus system confirm this problem? Or better, prove me wrong with your whole configurations so I can solve the problem by just use the proper driver version and maybe the proper configurations?

snowpiercer

22nd January 2015, 16:37

Hello Zachs, hello everyone else, this is my first post here at the forums. I'm actually following these forums and MPDN for quite some time but never got around to actually post something. I'm quite excited to finally say hello and make a first post here!

First of all, i love the MPDN player. I'm a long time fan of the MPC-HC + madVR combi and this is usually my default player, but when the FluidMotion feature was introduced it convinced me to give MPDN a try and so far it's looking really good and promising.

However, the reason i post here for the first time is that i did encounter some bugs and errors:

First, in DX9 and DX10 (and probably DX11 too) when i play audio only (f.e. .flac) in the player and switch to fullscreen, the following error msg pops up: "HRESULT: 0x8876086C, Module SHARPDX.Direct3d9, APICODE D3DERR_invalidcall, message: unknown".

The next bug happens in DX11, after exiting fse (switching back to windowed mode) i got a similar msg, this time: HRESULT 0x887A0005 Module SHARPDX.DXGI. DXGI_ERROR_DEVICE_REMOVED. Afterthis, the MPDN shows only two red lines and won't exit anymore, instead when trying to exit showing "Back buffer has not been created". The audio weirdly still continues to play, but when trying to skip ahead another msg comes up: "Object reference not set to an instance of an object". After a while it just crashes then. It doesn't occur always, but i can reproduce this most of the time. Usually when switching back and forth to fullscreen and windowed multiple times it eventually shows up.

In DX9 and DX10 everything else plays fine (no bugs except full screen with audio only).

Lastly, yesterday i had a really strange bug that might not have to do with MPDN, but it never happened to me in any other player before. All of a sudden, some ~twenty minutes into a video, the sound constantly got extremely scratchy and noisy, louder than the whole audio mix. I had to stop MPDN and unplug/replug my USB soundinterface. I'm using DirectSound in MPDN, same as with MPC-HC.
I don't know if this was just a bad coincidence, because i can't reproduce it right now, but i also never had this happen in MPC-HC before. It also wasn't the video that produced this, so there's probably nothing you can do, but if i encounter this again i'll let you know about it again.

My configuration: MPDN x64 latest (..18.8), latest MPDN plugins, latest official nvidia drivers (not beta drivers).

Hopefully you can look into these errors that have to do with DX11 and fullscreen audio only. So far i really like the player and i'm sure it will only keep getting better and better. Looking forward to watching more content with MPDN, thanks Zachs and everyone else involved!

DeadlyEmbrace

22nd January 2015, 18:46

This is fullscreen exclusive mode we're talking about isn't it? Exclusive mode seems to be very dependent on the GPU drivers and it behaves very differently from Dx9 to 11. On my Windows 7 setup, Dx10 causes all the screens to go black except the one playing the video, while Dx11 works like 9 where all screens continue to work just fine. I'm afraid there's not much I could do about that.

No worries, was just curious. Yes, it was indeed fullscreen exclusive mode. Removing FSE solves the problem. :)

Could you add events for volume change and mute for the extensions? At current the remote has no way to know if the volume was changed directly in MPDN or via another remote.

Zachs

23rd January 2015, 03:16

First, in DX9 and DX10 (and probably DX11 too) when i play audio only (f.e. .flac) in the player and switch to fullscreen, the following error msg pops up: "HRESULT: 0x8876086C, Module SHARPDX.Direct3d9, APICODE D3DERR_invalidcall, message: unknown".

The next bug happens in DX11, after exiting fse (switching back to windowed mode) i got a similar msg, this time: HRESULT 0x887A0005 Module SHARPDX.DXGI. DXGI_ERROR_DEVICE_REMOVED. Afterthis, the MPDN shows only two red lines and won't exit anymore, instead when trying to exit showing "Back buffer has not been created". The audio weirdly still continues to play, but when trying to skip ahead another msg comes up: "Object reference not set to an instance of an object". After a while it just crashes then. It doesn't occur always, but i can reproduce this most of the time. Usually when switching back and forth to fullscreen and windowed multiple times it eventually shows up.

In DX9 and DX10 everything else plays fine (no bugs except full screen with audio only).

Lastly, yesterday i had a really strange bug that might not have to do with MPDN, but it never happened to me in any other player before. All of a sudden, some ~twenty minutes into a video, the sound constantly got extremely scratchy and noisy, louder than the whole audio mix. I had to stop MPDN and unplug/replug my USB soundinterface. I'm using DirectSound in MPDN, same as with MPC-HC.
I don't know if this was just a bad coincidence, because i can't reproduce it right now, but i also never had this happen in MPC-HC before. It also wasn't the video that produced this, so there's probably nothing you can do, but if i encounter this again i'll let you know about it again.

My configuration: MPDN x64 latest (..18.8), latest MPDN plugins, latest official nvidia drivers (not beta drivers).

Hopefully you can look into these errors that have to do with DX11 and fullscreen audio only. So far i really like the player and i'm sure it will only keep getting better and better. Looking forward to watching more content with MPDN, thanks Zachs and everyone else involved!

The first one is fixed in the next release.

The one about Dx11 crashing going in and out of full screen exclusive mode is a driver bug. That said, I've made MPDN show the error and then terminate when the abort button is pressed. This will be how MPDN handles critical errors from now on.

The last one about your sound card shouldn't be due to MPDN since it does its the audio graph no differently to other DirectShow players now.

No worries, was just curious. Yes, it was indeed fullscreen exclusive mode. Removing FSE solves the problem. :)

Could you add events for volume change and mute for the extensions? At current the remote has no way to know if the volume was changed directly in MPDN or via another remote.

Done in v2.18.9.

Anime Viewer

23rd January 2015, 03:55

Options | General | Window. Uncheck resize window to fit when opening media.

Anyone else have their video open in extremely small windows (ex: 393x221 pixels)? I'm not sure why all videos seem to be opening in that shrunk size by default. If I go to View -> Fit to 100% video the video takes on its default size that it should have opened with (ex: 1280x720).

Anywhere in the configuration files I should look for this screwed up resolution that it seems to like opening files in if the "Resize window to fit when opening media" and "Reset window size when closing media" boxes are unchecked?

Zachs

23rd January 2015, 05:17

Anyone else have their video open in extremely small windows (ex: 393x221 pixels)? I'm not sure why all videos seem to be opening in that shrunk size by default. If I go to View -> Fit to 100% video the video takes on its default size that it should have opened with (ex: 1280x720).

Anywhere in the configuration files I should look for this screwed up resolution that it seems to like opening files in if the "Resize window to fit when opening media" and "Reset window size when closing media" boxes are unchecked?

Can't replicate your issue - when both of those are unchecked, window size doesn't change at all when opening / closing video files.

Zachs

23rd January 2015, 13:04

Attn: All PlayerExtension developers

There's an upcoming change that will affect all MPDN PlayerExtension developers. After discussing with Shiandow, it was decided that IPlayerControl should be accessible globally in the scripts for various reasons.

As such, you'll find the latest changes in my work branch on github as examples (EDIT: Shiandow will announce what you need to change in a little while, if any) - so if you could, please update your code (shouldn't take more than a few seconds). MPDN v2.19.0 test version is available for download here (http://zachsaw.com/downloads/mpdn_test/) (Developers only!!!).

Shiandow

23rd January 2015, 13:41

As such, you'll find the latest changes in my work branch on github as examples (EDIT: Shiandow will announce what you need to change in a little while, if any) - so if you could, please update your code (shouldn't take more than a few seconds). MPDN v2.19.0 test version is available for download here (http://zachsaw.com/downloads/mpdn_test/) (Developers only!!!).

Well I made the necessary changes in my work branch (https://github.com/Shiandow/PlayerExtensions/commits/Work), but if you don't like to merge with that (since you've made some other changes for instance) then you can easily do it yourself by replacing all "IPlayerControl" variables with the static PlayerControl, and removing the IPlayerControl argument from the IPlayerExtension.Initialize method (and maybe some other methods, but it should be relatively straightforward from there on).

DeadlyEmbrace

23rd January 2015, 17:02

Well I made the necessary changes in my work branch (https://github.com/Shiandow/PlayerExtensions/commits/Work), but if you don't like to merge with that (since you've made some other changes for instance) then you can easily do it yourself by replacing all "IPlayerControl" variables with the static PlayerControl, and removing the IPlayerControl argument from the IPlayerExtension.Initialize method (and maybe some other methods, but it should be relatively straightforward from there on).

Cool. I've merged your branch with mine and did some cleanup on my code. I've refactored some code in my brach so the merge ended up being a nightmare.

@Zachs Thanks for the events. :thanks:

Garteal

24th January 2015, 12:51

Thanks for the heads-up. I thought it was kinda a strange approach having to do it the initial way. Glad to see the concept (design) improve. Will be updating and continuing work on the extension.

Zachs

24th January 2015, 13:06

DeadlyEmbrace

24th January 2015, 13:40

More event requests. :)
Could you please add an event for when the selected active subtitle is changed and a similar one for when the active audio track is changed?

Zachs

24th January 2015, 13:43

More event requests. :)
Could you please add an event for when the selected active subtitle is changed and a similar one for when the active audio track is changed?

LOL I figured - just saw your commits. :)
Will do that for the next release.
Can you compile a list of events you think would be useful so I could do them all in one go?

DeadlyEmbrace

24th January 2015, 13:59

LOL I figured - just saw your commits. :)
Will do that for the next release.
Can you compile a list of events you think would be useful so I could do them all in one go?

Awesome, thanks.
I'll give it some thought. From a quick look over it seems those are the only ones atm though.

Zachs

24th January 2015, 14:01

Yeah I had a quick look myself and it seems to be the only ones missing. I'll add those and release a .1 in a while - since ryrynz also found FSE re-enter delay not working.

Done. v2.19.1 released.

DeadlyEmbrace

24th January 2015, 20:01

Hi everyone

New version of the MPDN Remote is available (v1.1.0)
- Display and select audio track(s)
- Display and select subtitle track(s)
- Display and select chapter(s)
- Adjusting of volume
- Mute/unmute
- Bugfixes

The new remote will work with the current extension, but most of the features won't be available. As soon as the updated extension is merged with the current PlayerExtensions all functionality will be available.

Available here: https://github.com/DeadlyEmbrace/MPDN_RemoteControl/releases/download/v1.1.0/MPDN_RemoteControl_v1.1.0.zip

Zachs

24th January 2015, 23:19

I've just merged Deadly's new remote code so all functionalities should now work if you re-download player extensions.

Will update OP later with remote client v1.1.0.

Thanks so much deadly!

Anime Viewer

25th January 2015, 03:04

@AnimeViewer

I've just implemented multi-subpic support for XySubFilter, along with some optimizations on how the frame is delivered to the renderer for v2.19.0.
Happy to say on my system, the queue only goes down by 3 frames from maximum at most with that test clip you uploaded.

Happy to say my queues stay nice and high (not dropping at all until the video is over from what I noticed) with that test video. Nice Job on making a fix for that Subtitle issue!

On a not so good note. I'm now noticing a "Sequence contains no elements" error when I open a video, maximize the window, or shrink it back to its default size. Any suggestions for trouble shooting?

After I copied the new player, new scripts, and new player extensions I got a couple of other error (shown in the attached picture). The one on the far left occurred when opening files. The top right one occurred when trying to close files (the only way to close it was by ending the task in task manager). Both of those were solved by recopying the render-script files again. The only remaining error is the "sequence" one.

http://oi60.tinypic.com/vfv8ua.jpg

Edit: I have both the 64-bit and 32-bit versions installed, and the 32-bit doesn't generate the error. Only the 64-bit appears to generate the error.

Edit: I've done some searching, and it appears the sequence error may be related to coding and a SingleOrDefault entry:
http://stackoverflow.com/questions/1324199/sequence-contains-no-elements
https://social.msdn.microsoft.com/Forums/en-US/527391ea-c0f4-488d-b0d2-94a11f483179/error-sequence-contains-no-elements?forum=linqprojectgeneral

romulous

25th January 2015, 03:21

I'm now noticing a "Sequence contains no elements" error when I open a video

Same. Play from Pause also triggers it.

Zachs

25th January 2015, 04:46

Replicated the problem and fixed in next release.

EDIT: Fixed and released v2.19.2.

Dazog

25th January 2015, 20:19

SamuelMaki

26th January 2015, 02:44

Started to crash when opening files with ffdshow post processing enabled again. Here is the windows crash message:
Ongelman tunniste:
Ongelmatapahtuman nimi: APPCRASH
Sovelluksen nimi: MediaPlayerDotNet.exe
Sovelluksen versio: 2.19.2.2937
Sovelluksen aikaleima: 54c467f6
Vikamoduulin nimi: StackHash_0a9e
Vikamoduulin versio: 0.0.0.0
Vikamoduulin aikaleima: 00000000
Poikkeuskoodi: c0000005
Poikkeuksen poikkeama: 00000000
Käyttöjärjestelmän versio: 6.1.7601.2.1.0.256.1
Aluekohtaisten asetusten tunnus: 1035
Lisätietoja 1: 0a9e
Lisätietoja 2: 0a9e372d3b4ad19135b953a78882e789
Lisätietoja 3: 0a9e
Lisätietoja 4: 0a9e372d3b4ad19135b953a78882e789
Hopefully that is MPDN bug and not ffdshow one? (Since it is dead project) Sorry for the Finnish gibberish, hopefully you make some sense out of it.

EDIT: Actually this was some sort of bug since reinstalling ffdshow and avisyth.dll fixed it (I did lack the .dll on syswow64 after updating MPDN for some reason unknown to me...). Seems to happen with every update as far as I can tell. Are you sure MPDN is not touching any avisynth related files? Though now I know which file to put in which folder I can happily just copy paste it after every update anyway.

Shiandow

26th January 2015, 11:49

Zachs

27th January 2015, 04:22

Could we get a "On Top while playing video" option?

Meaning when we pause the video, the player won't be on top of all other open windows.

Also In Minimalist mode, we don't have a way to tell how far we are into a video. No time displayed. Can we can option for that?

Thank you again, for all the hard work. Awesome player.

You can always choose to show status bar even in minimalist mode.
Always on top only when playing option would be a good feature to add.

Started to crash when opening files with ffdshow post processing enabled again. Here is the windows crash message:

Hopefully that is MPDN bug and not ffdshow one? (Since it is dead project) Sorry for the Finnish gibberish, hopefully you make some sense out of it.

EDIT: Actually this was some sort of bug since reinstalling ffdshow and avisyth.dll fixed it (I did lack the .dll on syswow64 after updating MPDN for some reason unknown to me...). Seems to happen with every update as far as I can tell. Are you sure MPDN is not touching any avisynth related files? Though now I know which file to put in which folder I can happily just copy paste it after every update anyway.

MPDN doesn't know you've updated it, or that you're even using Avisynth with it... So no, it has nothing to do with MPDN I'm afraid.

Blackfyre

27th January 2015, 07:49

Just a heads up, I pushed an update to the renderscripts that improved the speed of the debanding algorithm quite a bit. In theory this change could change the image quality slightly but as far as I can tell this effect is not noticeable.

Edit: And some tweaks to the SuperRes / SuperChromaRes algorithms.

Great job man, thanks. Testing with SVP now, it seems much less intensive than before, worked flawlessly so far, but need to do more testing before I update the article.

Anima123

27th January 2015, 21:36

Shiandow,

Mind if you can share with us how's the CalculateSize() supposed to work. I am a little bit confused what it will act if after the 1st round using NEDI, the currentSize already bigger than the targetSize.

I will try the new algorithm later today, with NEDI enabled, to see how it performed. Looks like you already changed how NEDI is utilized in SuperRes to limit it to only the first round.

Shiandow

27th January 2015, 22:03

Shiandow,

Mind if you can share with us how's the CalculateSize() supposed to work. I am a little bit confused what it will act if after the 1st round using NEDI, the currentSize already bigger than the targetSize.

What CalculateSize() tries to do is to cut the scaling process into equally sized pieces, making sure that the amount it needs to scale is within certain limits (or as close as it can get). The sizes it picks don't change if NEDI has been used, and in most cases it will simply downscale NEDI to what it thinks is the right size. If there's only one pass then it might decide to upscale, and I just realised that this causes an error if you scale exactly 200%. I should probably fix that.

I will try the new algorithm later today, with NEDI enabled, to see how it performed. Looks like you already changed how NEDI is utilized in SuperRes to limit it to only the first round.

That's always been how it worked, the main difference is that NEDI is now done in the L*a*b colourspace, which might improve quality a bit. Anyway, let me know what you think, it's very hard to estimate how all the small changes impact each other.

Edit: Bug should be fixed now.

Anima123

27th January 2015, 23:26

In the previous version of SuperRes, the image quality reached its max until round 6. I have tried 8 rounds and 10 rounds, it only makes the quality worse. 4-5 seemed a reasonable choice with the previous version.

I will check the latest version, with respect to the image quality, later today.

Blackfyre

28th January 2015, 00:29

Shiandow

28th January 2015, 00:43

I'd like to make a suggestion - multiple chain scripts... is it possible?

For me; with my chain script, adding SuperRes to it with 2 Passes & NEDI disabled in SuperRes configuration works fine with 24FPS and 25FPS files + SVP (can't do more than 2 passes). But 30FPS videos cannot be done, not even with 1 Pass. My videocard can't handle it (HD7970). So it would be great if for example I can tap numpad 1 and switch to chainscript 1 (when watching 24fps and 25fps videos) and tap numpad 2 to switch to chainscript 2 which doesn't have SuperRes added with the rest of my scripts.

If you go to the playerextensions there is a player extension called "Renderscript presets" that allows you to configure multiple script chains, you can then switch between them by selecting the one you want. Unfortunately there's no hotkey for switching presets yet, the whole system still needs some work. You may also need to select the "Preset" renderscript for this to work, this should be done automatically but I noticed it doesn't always do so.

Edit: you could also do it all automatically using a custom render script, but that's still a bit complicated.

Blackfyre

28th January 2015, 00:55

If you go to the playerextensions there is a player extension called "Renderscript presets" that allows you to configure multiple script chains, you can then switch between them by selecting the one you want. Unfortunately there's no hotkey for switching presets yet, the whole system still needs some work. You may also need to select the "Preset" renderscript for this to work, this should be done automatically but I noticed it doesn't always do so.

Edit: you could also do it all automatically using a custom render script, but that's still a bit complicated.

Thanks for the info... I just noticed that it doesn't work with 25fps and 30fps... only 24fps @ 1080p movies (which have the black bars at the top and bottom, aka 1920x800). Which are being scaled up to my monitor resolution 1440p.

720p @ 24fps wasn't even possible. My videocard isn't strong enough I guess anyway. So I disabled it. I'll just add SuperRes to the chain script when I watch a video that should work with it and remove it when it's not needed.

Anima123

28th January 2015, 01:57

Shiandow, a pm for you has been sent.

Zachs

28th January 2015, 03:43

Thanks for the info... I just noticed that it doesn't work with 25fps and 30fps... only 24fps @ 1080p movies (which have the black bars at the top and bottom, aka 1920x800). Which are being scaled up to my monitor resolution 1440p.

720p @ 24fps wasn't even possible. My videocard isn't strong enough I guess anyway. So I disabled it. I'll just add SuperRes to the chain script when I watch a video that should work with it and remove it when it's not needed.

When you said it doesn't work with 25fps and 30fps, do you mean the preset not working or you encounter frame drops because your GPU isn't fast enough?

Anima123

28th January 2015, 04:49

shaolin95

28th January 2015, 05:27

Guys what am I doing wrong?
I am using the latest x86_2_19_4_2940 with the RenderScripts (MPDN v2.19.0 and above) but it does not work. When I open the player I get this error I attached.
With my other versions I never got that error so not sure what I am missing.

Zachs

28th January 2015, 05:29

Can't see your PNG attachment - pending approval.
What error is it?

EDIT: Make sure you download both Render Scripts and Player Extensions from the OP download section, and no the separate release from GitHub as they no longer work separately. At some stage, we'll be looking to move Render Scripts into the Player Extensions branch on GitHub to prevent confusions.

Anima123

28th January 2015, 07:03

Error like the following:
[code]TITLE: SharpDX Error
------------------------------

An unexpected error 'SharpDX.SharpDXException' has occurred.

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

HRESULT: [0x887A0005], Module: [SharpDX.DXGI], ApiCode: [DXGI_ERROR_DEVICE_REMOVED/DeviceRemoved], Message: The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action.
(SharpDX)

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

&Abort
------------------------------
[/doe]
with version 2.19.4.

Besides, playing back with the latest version, the player will get out of FSE mode when trying to seek the video. This does not occur with 2.19.2.

Zachs

28th January 2015, 07:57

Yeah I think it was introduced in 2.19.3. Will get it fixed.

Zachs

28th January 2015, 11:33

Should be fixed now with v2.19.5.

Just for the record, DXGI_ERROR_DEVICE_REMOVED means MPDN has run into a driver bug and there's not much that could be done.

Shiandow

28th January 2015, 14:21

Just tested the new SuperRes a little bit, this time even without NEDI enabled, the rendering time increasing really fast.

Shiandow, would you please revisit this issue if you have time to do that?

Edit: Quite weird. To playback a 720x404 29.976 file, the rendering time increased quite fast. However, when playback a 576p file, it's steady.

That suggests that the problem is caused by allocating too much textures, the new CalculateSize() will allocate a few more textures for larger scaling factors. Perhaps I should add an option to disable that part.

Edit: Does it get even worse when you add debanding?

Anima123

28th January 2015, 21:42

That suggests that the problem is caused by allocating too much textures, the new CalculateSize() will allocate a few more textures for larger scaling factors. Perhaps I should add an option to disable that part.

Found a guy who has similar problems of Optimus + nVidia 880M system, which was also related to texture usage.
http://us.battle.net/heroes/en/forum/topic/13733923564

It seems that it's the drivers fault, am I right? We will just have to wait until nVidia give us a 'perfect' driver version.

Edit: Does it get even worse when you add debanding?

I will test if debanding has any affect on rendering time later today. From my experience, the new debanding code is much more faster than previous version.

Blackfyre

28th January 2015, 21:58

Yeah I agree new debanding is much faster... Also it's not like AMD release perfect drivers. Both AMD & nVidia have been having driver issues.

Edit: Also on a side note, is it possible to add streaming support? for example I have a program called SopCast, in the settings for SopCast I select an external media player, and choose MPC. This allows me to stream a tv channel using Madvr, but I can't set MPDN, it won't run every time. It doesn't have the ability to run a url?

Zachs

28th January 2015, 23:19