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

Garteal

17th January 2015, 10:13

Yeah that's a good idea, though I think you may have to pm me the fork URL because github doesn't tell me who forked my branch until a pull request is made.

The enhancements you've made does look really nice! Can't it replace the existing playlist form?

The resize on next file is not a bug actually, it's an option you can disable in MPDN's option menu.
Ah I see thanks. It works good with the option disabled.
And sure, I'll make it a replacer once the next few ideas are added. PM'd the fork. Nothing there yet though so don't get too excited lol.

Zachs

17th January 2015, 11:42

Ah I see thanks. It works good with the option disabled.
And sure, I'll make it a replacer once the next few ideas are added. PM'd the fork. Nothing there yet though so don't get too excited lol.

Yup got your PM. Have to say doom9 is the perfect place for MPDN! In fact, it was doom9's guides that got me started with this whole video encoding thing back in the early days, so I've always wanted to give something back.

mrcorbo

18th January 2015, 00:37

Blackfyre

18th January 2015, 00:49

I have been waiting out to see if the problems may be solved on their own, but it seems that MPDN is unable to play any media file with the HD6770 I am using. No directX version, changing all scalers to be GPU based, using any kind of media container, codec or whatnot has any effect. There is simply this somewhat vague error message: http://i.imgur.com/CDBMVJP.png

I got this error today with 30fps videos after updating to 2.18.3, but didn't happen with 24fps or 25fps videos... I reverted back to the last version I had prior to updating and everything works fine.

Not sure why it happened to be honest. Also SVP wasn't as stable as usual with the latest version. Again, I couldn't figure out why myself. :confused:

Zachs

18th January 2015, 01:02

I had been getting crashes in MPDN during playback and I finally think I have determined the cause. I have 2 AMD GPUs Crossfired in my main PC which I use for gaming as well as media playback. Well, after many attempts of trying different files, changing settings within MPDN, and uninstalling/reinstalling different drivers it occurred to me to try disabling Crossfire and...no crash. I re-enabled Crossfire and the same file plays back for 4 minutes and then MPDN crashes.

This seems to be an isolated issue with MPDN as other media players work fine with Crossfire enabled, even when using madVR.
Which presenter did you use? Try direct3d 9. I wouldn't have thought crossfire needed to be treated differently, since there isn't any direct3d API for it. What sort of crash did you get?
I got this error today with 30fps videos after updating to 2.18.3, but didn't happen with 24fps or 25fps videos... I reverted back to the last version I had prior to updating and everything works fine.

Not sure why it happened to be honest. Also SVP wasn't as stable as usual with the latest version. Again, I couldn't figure out why myself. :confused:
Which old version? I'll have a look and see what's changed. Can you check what the difference is between the old filter list versus the new one?

Anima123

18th January 2015, 01:28

Shiandow, I noticed there's some modifications around SuperRes has been reverted, mind if you share with us what's all these about?

Hope you can continue improving SuperRes, for now it's the main scaling algorithm of this series I am be able to enjoy without restarting the playback in the middle. ;)

mrcorbo

18th January 2015, 03:25

Which presenter did you use? Try direct3d 9. I wouldn't have thought crossfire needed to be treated differently, since there isn't any direct3d API for it. What sort of crash did you get?

I think I tried them all before, but I tried D3D9 just to be sure and it still crashed. The error is:

Unhandled exception at 0x00007FFB69919568 (d3d9.dll) in MediaPlayerDotNet.exe: 0xC0000005: Access violation writing location 0x00000000203F0FF0.

Call stack is: > d3d9.dll!RenderCB() Unknown

Zachs

18th January 2015, 03:43

Can you get me a full stack trace?

Garteal

18th January 2015, 04:06

Yup got your PM. Have to say doom9 is the perfect place for MPDN! In fact, it was doom9's guides that got me started with this whole video encoding thing back in the early days, so I've always wanted to give something back.
And you're doing an amazing job. Been lurking from the early days and it's really shaping up nicely and I see a lot of potential with its extensibility with RenderScripts and PlayerExtensions.

Been redoing the code design a bit and I'll actually need to be able to fire some code during chapter changes which requires a nice event I can hook to. Maybe a "Playing" event? Right now I'm abusing the PaintOverlay to get things working.

mrcorbo

18th January 2015, 05:08

Can you get me a full stack trace?

I'm not sure how, TBH. MPDN isn't handling the crash and when I select the Debug option from the Windows crash dialog, it presents me with a disassembly of the atiumd64.dll thread. I'm not sure if that is what you are looking for.

DeadlyEmbrace

18th January 2015, 08:36

Hi everyone
First, thanks Zachs for this awesome media player! :thanks:

I have released a new Player extension that allows remote control of MPDN. Simply add the extension as per the instruction in the first post then grab a copy of the sample remote here https://github.com/DeadlyEmbrace/MPDN_RemoteControl At the moment you will have to compile the remote code yourself, I will add a working release in the next day or so.

There are still a few issues (it was written a little hastily) but I will hopefully get those solved in the next few weeks. Feel free to file bugs or make a fork and fix them yourself. :p

Known issue:
- Remote media has to be in a path that is accessible to MPDN and has the same path as the remote can see (a remote share or the PC on which MPDN is running)
- There is no security so any copy of the Remote can connect
- There is no way to disconnect a remote client
- There is no way to change the port that MPDN extension server is running on
- There is no way to build and manage a playlist using the remote

Zachs

18th January 2015, 09:29

I'm not sure how, TBH. MPDN isn't handling the crash and when I select the Debug option from the Windows crash dialog, it presents me with a disassembly of the atiumd64.dll thread. I'm not sure if that is what you are looking for.
Ah this means it's a crash in AMD's driver. You should report the bug. Someone needs to fix bug in that DLL that is trying to write to a memory page that hasn't been allocated.
Hi everyone
First, thanks Zachs for this awesome media player! :thanks:

I have released a new Player extension that allows remote control of MPDN. Simply add the extension as per the instruction in the first post then grab a copy of the sample remote here https://github.com/DeadlyEmbrace/MPDN_RemoteControl At the moment you will have to compile the remote code yourself, I will add a working release in the next day or so.

There are still a few issues (it was written a little hastily) but I will hopefully get those solved in the next few weeks. Feel free to file bugs or make a fork and fix them yourself. [emoji14]

Known issue:
- Remote media has to be in a path that is accessible to MPDN and has the same path as the remote can see (a remote share or the PC on which MPDN is running)
- There is no security so any copy of the Remote can connect
- There is no way to disconnect a remote client
- There is no way to change the port that MPDN extension server is running on
- There is no way to build and manage a playlist using the remote
Thank you so much! I will add a link to your remote client in the OP. I'll probably build it and upload the executable so everyone could use it without having to build from source. Remind me to remove my build when you've got a prebuilt version.

friver

18th January 2015, 10:43

Matching_Mole

18th January 2015, 11:44

Hi,

To the questions of friver, I would add one: it is not possible currently to play Dvd with MPDN?

Zachs

18th January 2015, 12:58

Hello. I've just tried your player, and there are a few things I noticed:
1. Custom audio renderers aren't supported. (I tried Reclock and MpcAudioRenderer from MPC-BE)
2. Snap to Screen Edges function doesn't work at all.
3. In minimal view, there's no title on taskbar. Only icon. http://i.imgur.com/NiwTGs0.png
4. There's no Mitchel-Netravali and Catmull-Rom downscaling algorithms, unlike MadVR settings. Same goes for DXVA2 downscaling
5. What I really like is Maximize-Minimize-Close buttons in minimal mode. Is it possible to show them in fullscreen view too? It would be very convinient to close the player on TV screen with a single mouse click.
6. Is it possible to change mouse and keyboard hotkeys?
7. Is it possible to set on which monitor the player should start? It would be very usefull when using MPDN as an external player in Kodi (XBMC) on multimonitor system. For example, look at /close, /fullscreen, /monitor command arguments in MPC-HC.
8. Is it possible to use MediaInfo.dll in MPDN ?

Sorry for so many questions, I really did use the search before posting
Good luck! I'm looking forward to next versions.

1. That's a bug that was introduced a few versions ago. It's been fixed in the next release. Thanks for reporting it!
2. It does, doesn't it? - I just tested it.
3. That is an unfortunate requirement to make Windows draw a captionless form.
4. MPDN's bicubic covers both MV and CR scalers - use search to find out which are the corresponding sharpness settings
5. Not easily - will add to my to do list with low priority
6. Yes (but not end-user friendly yet) via Player Extension - see KeyRemap.cs
7. Yes (again, not end-user friendly yet) via Player Extension, simply setting the location of PlayerControl.Form at Initialize() would achieve this
8. Ctrl+Shift+I - see ViewMediaInfo.cs

Hi,

To the questions of friver, I would add one: it is not possible currently to play Dvd with MPDN?

Hmm... did you get an error when you open the video_ts.ifo file?
EDIT: Ah it would appear that LAV Splitter doesn't support video_ts.ifo? However, opening the VOB file directly seems fine.
Does anyone know if LAV Splitter Source could be used to open video_ts.ifo?

romulous

18th January 2015, 13:29

2. It does, doesn't it? - I just tested it.

friver is right - it doesn't work here either. Using 64bit version on Win 7 64bit, snap to top edge is fine (that's when Windows does that automatic resize thing that they introduced with Win 7, Aero Snap or whatever it is called), but snap to left and right edge does not work (can't tell about bottom edge, as MPDN goes under the taskbar).

Zachs

18th January 2015, 13:43

friver is right - it doesn't work here either. Using 64bit version on Win 7 64bit, snap to top edge is fine (that's when Windows does that automatic resize thing that they introduced with Win 7, Aero Snap or whatever it is called), but snap to left and right edge does not work (can't tell about bottom edge, as MPDN goes under the taskbar).
Snap to edges is meant to work like a magnet that aligns the form on the edge of your working area (I.e. it snaps to taskbar too). Were you guys expecting it to behave otherwise?

romulous

18th January 2015, 13:49

Zachs - It doesn't actually do what you describe though (at least on my system, and presumably on friver's as well). It appears to work exactly the first time you try and dock to the edges, but if you then move the MPDN window away from the edge and try again, it stops working. MPDN is the only program that supports dock to edges that doesn't actually do that correctly on my system.

Zachs

18th January 2015, 13:52

Hmm. Is anyone else seeing this problem?

EDIT: Just tested this on more systems with Win8.1 x64 - all of them worked fine. Just to be clear, it only meant to dock when it's placed close enough to the edge of the screen (25 pixels on 96 DPI systems).

cegy

18th January 2015, 13:56

just wondering if its possible to add support for being able to read rar files i do know adding it yourself could be quite hard/not simple to do however my suggestion would be offer the support of reading rar files if it detects "RARFileSource.ax" in the same dir or on the system?

p.s http://www.v12pwr.com/RARFileSource/ will give you the option of being able to read/playback videos from rar's and its also a directshow filter aswell

friver

18th January 2015, 14:06

2. It does, doesn't it? - I just tested it.
3. That is an unfortunate requirement to make Windows draw a captionless form.
4. MPDN's bicubic covers both MV and CR scalers - use search to find out which are the corresponding sharpness settings

Thanks for the reply!

2. No, unfortunately, it doesn't work for me at all. Win 8.1 x64, MPDN x86
3. Well, seems like MPC-HC, MPC-BE and PotPlayer can hide caption, and display a caption in taskbar at the same time, so I think this requirement isn't so strict.
4. Thanks, I didn't know that before.

Zachs

18th January 2015, 16:56

Thanks for the reply!

2. No, unfortunately, it doesn't work for me at all. Win 8.1 x64, MPDN x86
3. Well, seems like MPC-HC, MPC-BE and PotPlayer can hide caption, and display a caption in taskbar at the same time, so I think this requirement isn't so strict.
4. Thanks, I didn't know that before.

2. I haven't seen this problem personally but I'll try to find a system that I can replicate the issue. So far all the systems I have access to behave properly.
3. Form is accessible through player extension, so if you know how to do that, please post an example and I'll incorporate it in a heart beat.
4. That's what search is for.

DeadlyEmbrace

18th January 2015, 17:57

Thank you so much! I will add a link to your remote client in the OP. I'll probably build it and upload the executable so everyone could use it without having to build from source. Remind me to remove my build when you've got a prebuilt version.

Thanks :D
Awesome to be able to contribute something. Have fixed the Authorization issue and will work on the remaining issue during the week. Will probably make a release once the middle three errors are fixed.

Do you have any suggestion for how I can interact with the playlist? Have though of creating one in the remote, but that isn't a very good way of doing it...

nekromantik

18th January 2015, 18:14

@Anima123

I just watched a 41 min file with x64 latest MPDN with x64 LAV and superres+superchromares NNDIE3 enabled and got no render time increase.
Using Direct3D 11 output.

@zachs
Cant get display rate changer to work.
I add w1280p24 to the list but when playing file it dont not do anything.

fairchild

18th January 2015, 20:20

When using a script chain and using say SuperChromaRes and SuperRes, the correct sequence is the SuperChromaRes first then the SuperRes (since chroma gets resizes first/always?)

Zachs

18th January 2015, 23:09

Thanks :D
Awesome to be able to contribute something. Have fixed the Authorization issue and will work on the remaining issue during the week. Will probably make a release once the middle three errors are fixed.

Do you have any suggestion for how I can interact with the playlist? Have though of creating one in the remote, but that isn't a very good way of doing it...

I think you could simply change the playlist form to add methods such as AddFiles, RemoveFiles, GetPlaylist etc (these methods could simply be refactored from existing code). This way the remote playlist will be synchronised with the playlist extension's list.

@Anima123

I just watched a 41 min file with x64 latest MPDN with x64 LAV and superres+superchromares NNDIE3 enabled and got no render time increase.
Using Direct3D 11 output.

@zachs
Cant get display rate changer to work.
I add w1280p24 to the list but when playing file it dont not do anything.

Try it without the filter first and see if everything works fine - i.e. Tick 'activate display changer' only and leave everything else unchecked. If that works, then make sure the material you are watching is indeed p24, not p23 (==> 23.976)

When using a script chain and using say SuperChromaRes and SuperRes, the correct sequence is the SuperChromaRes first then the SuperRes (since chroma gets resizes first/always?)

That's correct. If you find your GPU to be too weak, you can remove SuperChromaRes and simply have SuperRes as the sole render script and it'll still work - in this case, it uses MPDN's Chroma Upscaler.

mrcorbo

18th January 2015, 23:10

Ah this means it's a crash in AMD's driver. You should report the bug. Someone needs to fix bug in that DLL that is trying to write to a memory page that hasn't been allocated.

OK, will do.

I also found that when the main player window is active, MPDN is now responding to the keyboard shortcuts for play next/previous playlist item and play next/previous file in folder twice, effectively skipping two ahead on each press (it actually advances to the next file then immediately advances again). Chapter navigation is working fine. If you activate the playlist window, playlist navigation returns to normal.

nekromantik

19th January 2015, 00:47

Try it without the filter first and see if everything works fine - i.e. Tick 'activate display changer' only and leave everything else unchecked. If that works, then make sure the material you are watching is indeed p24, not p23 (==> 23.976)
.

Ok
Thanks for the help!

Zachs

19th January 2015, 01:06

OK, will do.

I also found that when the main player window is active, MPDN is now responding to the keyboard shortcuts for play next/previous playlist item and play next/previous file in folder twice, effectively skipping two ahead on each press (it actually advances to the next file then immediately advances again). Chapter navigation is working fine. If you activate the playlist window, playlist navigation returns to normal.

Will take a look. Thanks!

SamuelMaki

19th January 2015, 02:09

Hey! I get the following error when trying to use the 32-bit version with ffdshow postprocessing: Failed to render the file "path-to-file.avi". Using 64-bit version with 64-bit ffdshow work just fine. The reason I want 32-bit, is to be able to use Avisynth (Interframe interpolation)

E: Played around with the graphstudionext and there is no problem what so ever.

Zachs

19th January 2015, 02:18

Hey! I get the following error when trying to use the 32-bit version with ffdshow postprocessing: Failed to render the file "path-to-file.avi". Using 64-bit version with 64-bit ffdshow work just fine. The reason I want 32-bit, is to be able to use Avisynth (Interframe interpolation)

If it works in 64-bit and not 32, then the 32-bit path of your system setup since MPDN doesn't treat 32/64-bit any differently when it comes to directshow.

SamuelMaki

19th January 2015, 02:31

If it works in 64-bit and not 32, then the 32-bit path of your system setup since MPDN doesn't treat 32/64-bit any differently when it comes to directshow.

What you mean with that? MPDN is on a folder "C:\MPDN\" and ffdshow is installed properly as well (and works on the graphstudio).

Zachs

19th January 2015, 02:42

What you mean with that? MPDN is on a folder "C:\MPDN\" and ffdshow is installed properly as well (and works on the graphstudio).

By that I mean MPDN is reliant on your system's DirectShow filters to be setup correctly - and when 64-bit works and not 32-bit or vice versa, there can be only one explanation - one or more DirectShow filters has been setup incorrectly or misbahaving.

Did you go through the troubleshooting guide? i.e. disabling subtitles, connect LAV video and audio decoders to LAV splitter source, then ffdshow to video decoder's output and finally to any renderers for testing? If you can setup such a graph in graph studio (make sure it's the 32-bit graphstudio in your case), and MPDN still fails, then it's a genuine bug.

SamuelMaki

19th January 2015, 03:03

By that I mean MPDN is reliant on your system's DirectShow filters to be setup correctly - and when 64-bit works and not 32-bit or vice versa, there can be only one explanation - one or more DirectShow filters has been setup incorrectly or misbahaving.

Did you go through the troubleshooting guide? i.e. disabling subtitles, connect LAV video and audio decoders to LAV splitter source, then ffdshow to video decoder's output and finally to any renderers for testing? If you can setup such a graph in graph studio (make sure it's the 32-bit graphstudio in your case), and MPDN still fails, then it's a genuine bug.

I did all those, no change, though now I get BEX64 error on the x64 version too :confused: Reinstalled nvidia gpu drivers, but didn't help. Going to run sfc /scannow now if I have something corrupted in my system...
E: Which didn't found anything... I didn't see any links for "old builds", you have some of those around? I could try older version since this configuration has worked flawlessly in the past.
EE: Removed every directshow filter except LAV and now both 32-bit and 64-bit work in directx9 old windowed mode only. If I change to new windowed mode, I get the "failed to render file" error. Scratch that, now it works in new windowed mode too... Seems very random.

Zachs

19th January 2015, 03:20

I did all those, no change, though now I get BEX64 error on the x64 version too :confused: Reinstalled nvidia gpu drivers, but didn't help. Going to run sfc /scannow now if I have something corrupted in my system...
E: Which didn't found anything... I didn't see any links for "old builds", you have some of those around? I could try older version since this configuration has worked flawlessly in the past.

What's a BEX64 error?
Are you saying graph studio had no problem connecting the filters I described but MPDN is still showing the error failed to render file?

Zachs

19th January 2015, 03:23

EE: Removed every directshow filter except LAV and now both 32-bit and 64-bit work in directx9 old windowed mode only. If I change to new windowed mode, I get the "failed to render file" error

New windowed mode is completely not related to the failed to render file error - one is in the renderer, the other is in directshow graph connection. The code that makes any difference for windowed mode settings doesn't even called yet if you see the "Failed to render file" error.

SamuelMaki

19th January 2015, 03:27

What's a BEX64 error?
Are you saying graph studio had no problem connecting the filters I described but MPDN is still showing the error failed to render file?

I did get "software stopped working" with BEX64 as the error message, but now I don't get that anymore so cannot copy the whole message :/ And no problems on graphic studio, even ffdshow+avisynth worked on it. This is recent problem, which I believe might be related to updating (I used to run perfectly fine with last years before christmas build).

cyberbeing

19th January 2015, 03:27

BEX errors usually occur when something triggers Data Execution Prevention (DEP).

Zachs

19th January 2015, 03:38

SamuelMaki

19th January 2015, 03:47

Ah ok, anything that triggers DEP will be in unmanaged code.
The most recent change that has anything to do with unmanaged code would've come from adding support for Direct3D 11.
Can you try D3D9Ex and see if the problem persists? But like I said, this is not going to help with the failed to render file error though.

As crazy as it sounds everything works just fine now. Installed ffdshow back and it loads as well without problems. Oh well, sorry to have wasted your time.

Zachs

19th January 2015, 03:50

As crazy as it sounds everything works just fine now. Installed ffdshow back and it loads as well without problems. Oh well, sorry to have wasted your time.

LOL glad it worked out finally! :)

romulous

19th January 2015, 11:11

2. I haven't seen this problem personally but I'll try to find a system that I can replicate the issue. So far all the systems I have access to behave properly.

Zachs: How quickly do you move your mouse? I notice that when I move my mouse really slowly, MPDN is much more reliable in snapping to the desktop edge. When I move my mouse at normal speed, that is when it seems to become problematic. Maybe it is a visual thing - maybe MPDN is actually grabbing to the edge (and is thus technically working), but because of the speed of the mouse movement, it then immediately gets pushed past the edge of the desktop making it appear it hasn't worked.

Zachs

19th January 2015, 11:23

It should only snap when you release the mouse button, shouldn't do anything otherwise.

romulous

19th January 2015, 11:46

It should only snap when you release the mouse button

That may be the problem (it seems to me to be an unusual way to do it). Anyway, here is a video capture of various attempts at me snapping to the desktop edge, you might be able to see something. Note that in the video, the left hand side of the video is the left hand edge of the desktop, and that I never remove my finger from the mouse button the entire time (as far as I recall, I don't have to remove my finger from the mouse for other apps, though my memory may be faulty on that). I start off by moving the mouse very slowly - and in fact it works the first time - but after that, I start to build up to my normal mouse movement speed and that is when it starts to fail.

https://dl.dropboxusercontent.com/u/105555957/MPDN%20Snap.wmv (1.12MB)

kostik

19th January 2015, 12:05

Awesome job, been using it since almost the beginning.
I guess the ability to use 3dlut files or something like it (or even better), would be the last step and a major one.
Thanks for everyone working on this project, I wish I had the knowledge to help , maybe in the future :)

Zachs

19th January 2015, 12:44

3dlut requires 3d texture upload that isn't available yet via renderscript at this moment.
Hopefully I'll have some time to get to implementing the necessary APIs to allow this to happen in the future...

Zachs

19th January 2015, 12:58

That may be the problem (it seems to me to be an unusual way to do it). Anyway, here is a video capture of various attempts at me snapping to the desktop edge, you might be able to see something. Note that in the video, the left hand side of the video is the left hand edge of the desktop, and that I never remove my finger from the mouse button the entire time (as far as I recall, I don't have to remove my finger from the mouse for other apps, though my memory may be faulty on that). I start off by moving the mouse very slowly - and in fact it works the first time - but after that, I start to build up to my normal mouse movement speed and that is when it starts to fail.

https://dl.dropboxusercontent.com/u/105555957/MPDN%20Snap.wmv (1.12MB)

This isn't what I'm getting at all - are you sure you haven't got other software on your system snapping it while you're moving the window? On all my systems, the MPDN window doesn't snap until I release it near the edge.

romulous

19th January 2015, 13:13

Not as far as I know (if any of the apps I have running affect snapping, it isn't an advertised feature of them and certainly not why I am running them). What I will have to do is to run the same test with all the background apps on my system shutdown (well, as many of them as is possible anyway) and see if I get the same result.

ryrynz

19th January 2015, 21:28

As soon as the mouse cursor hits the edge of the desktop (wherever the mouse is located on the MPDN window) I see the docking animation. I will try out some other systems, but this looks to be working as intended.

What MPDN doesn't do is the type of edge docking that say Zoomplayer does. By bringing the window to the desktop edge the player snaps to the screen without any sort of maximizing at all, just sticky edges really, maybe Romulous is looking for that feature.