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

[madshi]

There's no advantage using this player. Not trying to pry people away from their beloved madVR, just sharing this player as an alternative. There are some features that MPDN have and not madVR such as fast downscaling, Jinc downscaling, 4-tap Lanczos Spline Jinc upscaling, 10- and 16-bit output modes. MadVR has a lot more features tough like what you mentioned 3DLUT, NNEDI3, linear light scaling etc.
FWIW, Jinc downscaling and 10bit output has been on my to-do-list for a long time, it's just a question of time when these will come to madVR.

MPDN isn't as good as madVR in the picture quality department (namely it's missing advanced features but madVR wasn't written in one day either) but it works across a wider spectrum (namely downscaling from 4k). The goal of MPDN is not for the pedantic ones who want utmost quality regardless of cost but one for the pragmatists who want decent quality and at a reasonable cost.
I don't like this part of your comment much, to be honest. Probably you didn't mean it this way, but you do sound as if madVR were for pedantic users, only, and not for those who want decent quality at a reasonable cost. That's not really the case at all.

As mentioned before, madVR is currently written in such a way that all sources are converted to RGB first. I didn't anticipate that this would slow downscaling down *that* much. So I might have to reconsider this decision for downscaling (at least if certain conditions are met, e.g. if there are no pre-scale custom shaders active and if linear light downscaling is deactivated etc). I haven't decided yet.

[huhn]

not working as intended.

directx 9 can drop frames like crazy after i resized or switch to full screen. directx 10.1 doesn't drop frames at start or after some resizing it does a wrong pullup every 0.5 - 1.0 sec so a huge lag is to seen.

I guess this is a windows 10 problem no one else reported something like this.

[Zachs]

FWIW, Jinc downscaling and 10bit output has been on my to-do-list for a long time, it's just a question of time when these will come to madVR.


I don't like this part of your comment much, to be honest. Probably you didn't mean it this way, but you do sound as if madVR were for pedantic users, only, and not for those who want decent quality at a reasonable cost. That's not really the case at all.

As mentioned before, madVR is currently written in such a way that all sources are converted to RGB first. I didn't anticipate that this would slow downscaling down *that* much. So I might have to reconsider this decision for downscaling (at least if certain conditions are met, e.g. if there are no pre-scale custom shaders active and if linear light downscaling is deactivated etc). I haven't decided yet.

I absolutely don't mean madVR is for pedantic users only but what I was trying to point out was MPDN doesn't cater for these people at the moment and that I wouldn't add any features unless it doesn't penalise those who don't want it. That was the point I was trying to make for MPDN. What is wrong with letting people choose to use MPDN if madVR doesn't do the job for them? Or do you feel that MPDN is completely worthless that no one should even bother?

I wasn't trying to convince you to implement it the way I feel should be implemented. I was only stating my own believes for the direction I would take MPDN. I apologise if it sounded like I was criticising madVR but I wasn't. I merely wanted to point out there are certain things I would do and have done differently. Everyone believes in different things and that is perfectly fine with me. That's the beauty of the world we live in.

[kostik]

Will it be possible to resize the video ? (Pan&Scan)?
Everything else is pretty much works good :)

[madshi]

What is wrong with letting people choose to use MPDN if madVR doesn't do the job for them?
I didn't say anything like that. I just wanted to make sure that readers of this thread don't get a wrong impression about which user groups madVR might be intended/optimized for.

[Zachs]

not working as intended.

directx 9 can drop frames like crazy after i resized or switch to full screen. directx 10.1 doesn't drop frames at start or after some resizing it does a wrong pullup every 0.5 - 1.0 sec so a huge lag is to seen.

I guess this is a windows 10 problem no one else reported something like this.

Not Win10 problem!

I just encountered this myself!

[Zachs]

Will it be possible to resize the video ? (Pan&Scan)?
Everything else is pretty much works good :)

Ah no, the only thing you could do is change aspect ratio.

[ajp2k11]

Not Win10 problem!

I just encountered this myself!

I get strange stutters every few seconds if I set my display to 120Hz, 60Hz is much smoother. Is this the same problem? Doesn't matter if I use DX9 or DX10.1, fullscreen or not. Using Win 8.1 with an AMD 6650M. MadVR is smooth at 120Hz (if I can get it to work at all).

[Zachs]

I get strange stutters every few seconds if I set my display to 120Hz, 60Hz is much smoother. Is this the same problem? Doesn't matter if I use DX9 or DX10.1, fullscreen or not. Using Win 8.1 with an AMD 6650M. MadVR is smooth at 120Hz (if I can get it to work at all).

Do you get dropped frames when that happens? And is present times up in the teens (more than 10ms)?

[ajp2k11]

Do you get dropped frames when that happens? And is present times up in the teens (more than 10ms)?

No dropped frames. Pretty sure present times are more than 10ms, I use Jinc upscaling and my GPU is pretty old so... not at home right now so I can't check the exact times.

[huhn]

the present times are stable for me.

it MPDN presenting 120 frame on a 120 hz screen or is it leaving this task to "aero" or directx vsync and just give it 24 frame a sec?

[huhn]

No dropped frames. Pretty sure present times are more than 10ms, I use Jinc upscaling and my GPU is pretty old so... not at home right now so I can't check the exact times.

are you using windows 7 without aero?
it is totally normal to get very high present times in this case was always the case with madVR.

[ajp2k11]

are you using windows 7 without aero?
it is totally normal to get very high present times in this case was always the case with madVR.

Nope, using Win 8.1... not sure about my present times though, will have to check tonight.

[Zachs]

@huhn

24 frame a sec but it's based on directshow "reference time", not your system time. The reference time is from your audio source, and it is rather inaccurate and it gets adjusted quite frequently but that is what MSDN's documentation asks renderers to sync to. However, the behavior is completely different for Dx9 and Dx10 render paths! So that isn't the problem there.
Did you say at some stage that it worked for you in FSE mode but not windowed?
The problem I'm seeing is completely different then. I get a period where frames keep getting dropped after switching out from FSE mode. My present time goes to 20ms and frames drop like mad.

[huhn]

@huhn

24 frame a sec but it's based on directshow "reference time", not your system time. The reference time is from your audio source, and it is rather inaccurate and it gets adjusted quite frequently but that is what MSDN's documentation asks renderers to sync to. However, the behavior is completely different for Dx9 and Dx10 render paths! So that isn't the problem there.
Did you say at some stage that it worked for you in FSE mode but not windowed?
The problem I'm seeing is completely different then. I get a period where frames keep getting dropped after switching out from FSE mode. My present time goes to 20ms and frames drop like mad.

so the audio clock can be a problem too? I use a ESI Prodigy X-Fi NRG R in this PC i try the onboard later can only hurt my ears.

the problem is it sometimes works so my reports are maybe totally wrong. because i didn't managed to break it in the first 5 tries.

in the last test directx 9 fullscreen and windows was the mode that can drops frames like crazy I check for the present times later but all mode showed choppy playback.
this screen I posted earlier http://abload.de/img/untitledmni96.png shows the frame dropping issue but the present times are fine in the last 5 sec.

[ajp2k11]

Nope, using Win 8.1... not sure about my present times though, will have to check tonight.

Just checked, present times below 1ms.

[SamuelMaki]

Hey! I have a problem with external subtitles (.srt and .sub files at least). I do select them with directvobsub, but only the embedded subtitles work. Is this a feature/to-do or have I missed something? Embedded subtitles work just fine, and the tray icon appears, only the "open" dialog in directvobsub doesn't. Using x64 version and have x64 LAV and x64 Directvobsub installed properly.

Also the LAV-splitters choises are ignored (loading italian audio and subtitles when selected english on LAV).

[Zachs]

Just a quick update for all the testers (I'm very appreciative, thank you!)

I believe there could be 2 issues here with the stuttering issue.

The first one, I have replicated on both NVIDIA and AMD GPUs. Intel GPU does not have this problem.
Namely, after coming out of FSE mode, I can't present anything for a few seconds (some times a lot longer on NVIDIA cards).
This I have attributed it to bad drivers as it is not returning from my Present() call even after I have made sure it is a new VBlank (again this happens only for a few seconds after exiting from FSE mode). The net result is you get a lot of dropped frames for that few seconds and after which Present times will go back to the sub 1ms it should be. This issue, I have implemented a workaround.

The second issue may be related to 120Hz monitors only. I am not so sure about this particular one as I don't have a 120Hz monitor to test with, but I do have a 75Hz monitor. On that monitor, I couldn't replicate the problem. It could be due to the same problem too, so give the new version (2.5.3) a try.

[Zachs]

Hey! I have a problem with external subtitles (.srt and .sub files at least). I do select them with directvobsub, but only the embedded subtitles work. Is this a feature/to-do or have I missed something? Embedded subtitles work just fine, and the tray icon appears, only the "open" dialog in directvobsub doesn't. Using x64 version and have x64 LAV and x64 Directvobsub installed properly.

Also the LAV-splitters choises are ignored (loading italian audio and subtitles when selected english on LAV).

External subs should work. You need to make sure the file names are exactly as per your media file except for the extension though. The other thing I would check is make sure your DirectVobSub has the external sub paths setup properly.

Regarding LAV-Splitter choices, I didn't even know there's such a thing, so I made it default to the first track for both audio and sub :)
I'll look into that one.

[Zachs]

@huhn @ajp2k11
Can you try v2.5.3 to see if it helps with the frame drop and stuttering issues?

I have introduced a new windowed mode rendering path for both D3D9 and D3D10.
There's now an additional option in the Video Renderer settings page to choose "New windowed mode rendering path".
This "new" path is actually the one I've been using all the time (with fixes I mentioned in the earlier post), so basically I've added an "old" rendering path to MPDN.
Anyway, if you could try both old and new paths with both D3D9 and D3D10, I'd truly appreciate it!
Some systems work better with the old path in D3D9 while doesn't make a difference in D3D10 and some prefer the new path.

[ajp2k11]

@huhn @ajp2k11
Can you try v2.5.3 to see if it helps with the frame drop and stuttering issues?

I have introduced a new windowed mode rendering path for both D3D9 and D3D10.
There's now an additional option in the Video Renderer settings page to choose "New windowed mode rendering path".
This "new" path is actually the one I've been using all the time (with fixes I mentioned in the earlier post), so basically I've added an "old" rendering path to MPDN.
Anyway, if you could try both old and new paths with both D3D9 and D3D10, I'd truly appreciate it!
Some systems work better with the old path in D3D9 while doesn't make a difference in D3D10 and some prefer the new path.

I will try it when I get home tonight, thanks! :)

[Zachs]

OK I've just tried an earlier version of NVIDIA drivers 340.52 -- it is definitely an NVIDIA drivers bug.

This is with D3D9.

Old rendering path:

With the earlier drivers, switching from FSE back to windowed mode never causes long present times but can occasionally still stutter.
Latest drivers, it blocks present() when stutter occurs - this behavior was changed from previous driver version to the current one.
However, they still haven't fixed that issue where FSE mode to windowed mode would cause long present times.

New rendering path:

Both drivers report low present() times and smoothness issue only noticeable when viewing rolling credits.

For D3D10, latest drivers can appear as if it has that pull up issue huhn mentioned when switching back to windowed from FSE mode.
Old driver is hardly noticeable.

FSE mode isn't affected by all of these.

AMD & Intel both seem happy with either rendering paths including D3D10 ones.

@huhn @ajp2k11: Can you guys verify the above and see if that's the same issue you are having?

EDIT: Just tested madVR with default settings and its behavior is exactly the same as MPDN's new rendering path for this particular issue.

[SamuelMaki]

External subs should work. You need to make sure the file names are exactly as per your media file except for the extension though. The other thing I would check is make sure your DirectVobSub has the external sub paths setup properly.

Regarding LAV-Splitter choices, I didn't even know there's such a thing, so I made it default to the first track for both audio and sub :)
I'll look into that one.

Tried that already, have no way to enable the external subtitles since the "subtitles" section show only embedded ones. Made the path simple and used simple filenames (same on both), but still doesn't work. When I select "no subtitles", it does show "undetermined, no subtitles" in the directvobsub window. So basically it does load the external one when chosen "no subtitles" in the player, but hides the subtitles as well?

I don't know, just a hunch :P Maybe do some simple drag and drop system for subtitles or make the open/browse dialog to work on directvobsub if you can? Seems a lot more faster than running with madVR+mpc-hc in my opinion otherwise.

[Zachs]

Ah you mean that media has embedded subs and you are trying to use external sub instead right?
That's one thing I haven't anticipated. I'll take a look at that too!

[SamuelMaki]

Ah you mean that media has embedded subs and you are trying to use external sub instead right?
That's one thing I haven't anticipated. I'll take a look at that too!

That's exactly what I am doing! Thanks for working on it, waiting eagerly for the fix, since this is something kinda lot of people from "smaller countries" experience when trying to watch import movies.

[huhn]

OK I've just tried an earlier version of NVIDIA drivers 340.52 -- it is definitely an NVIDIA drivers bug.

This is with D3D9.

Old rendering path:

With the earlier drivers, switching from FSE back to windowed mode never causes long present times but can occasionally still stutter.
Latest drivers, it blocks present() when stutter occurs - this behavior was changed from previous driver version to the current one.
However, they still haven't fixed that issue where FSE mode to windowed mode would cause long present times.

New rendering path:

Both drivers report low present() times and smoothness issue only noticeable when viewing rolling credits.

For D3D10, latest drivers can appear as if it has that pull up issue huhn mentioned when switching back to windowed from FSE mode.
Old driver is hardly noticeable.

FSE mode isn't affected by all of these.

AMD & Intel both seem happy with either rendering paths including D3D10 ones.

@huhn @ajp2k11: Can you guys verify the above and see if that's the same issue you are having?

EDIT: Just tested madVR with default settings and its behavior is exactly the same as MPDN's new rendering path for this particular issue.

a lot better still not always perfect. it took me awhile to run in any problems.

[Zachs]

a lot better still not always perfect. it took me awhile to run in any problems.

Yeah it's an NVIDIA bug. I can reproduce the exact same problem on madVR too when switching back from FSE mode. It doesn't report present times to be high too like my new render path but you can notice jerky playback especially on rolling credits. The old rendering path of MPDN reported the true present times (only with NVIDIA's latest drivers) but that means it also tried to correct it by dropping frames, which made the situation worse. By ignoring present time (as with the older NVIDIA drivers), MPDN pretends that everything is fine. It is still not smooth with the latest drivers (blame NVIDIA), but there is nothing more that could be done from an application's perspective.

Someone needs to report the bug to NVIDIA. :)

EDIT: You'll notice further improvements if you switch back to geforce drivers v340.52.

@ajp2k11

I bet you have an NVIDIA card with latest drivers too? :)

[ajp2k11]

Yeah it's an NVIDIA bug. I can reproduce the exact same problem on madVR too when switching back from FSE mode. It doesn't report present times to be high too like my new render path but you can notice jerky playback especially on rolling credits. The old rendering path of MPDN reported the true present times (only with NVIDIA's latest drivers) but that means it also tried to correct it by dropping frames, which made the situation worse. By ignoring present time (as with the older NVIDIA drivers), MPDN pretends that everything is fine. It is still not smooth with the latest drivers (blame NVIDIA), but there is nothing more that could be done from an application's perspective.

Someone needs to report the bug to NVIDIA. :)

EDIT: You'll notice further improvements if you switch back to geforce drivers v340.52.

@ajp2k11

I bet you have an NVIDIA card with latest drivers too? :)

Nope, I have an AMD 6650M with Catalyst 14.9 drivers but maybe it's not the same problem? I only see stuttering when using 120Hz display mode, can easily be seen when there's movement. Haven't noticed any when running in 60Hz. Not a major problem but it's nice to be able to use 120Hz since it's a multiple of 24. I'll try and provide some better debug info this weekend...

[Zachs]

Is that on the latest version of mpdn though?

[ajp2k11]

Is that on the latest version of mpdn though?

Nope, I'll try the new version this weekend... thanks!

[Hera]

Is dxva2n support missing or did I set things up wrong? Using this with LAV filter (testing right now), Video decoder says "DXVA2 (native)" is "Available". (DX 10.1, Win 8.1, NV 660).
EDIT: Just found my answer - "MPDN isn't written with using DXVA at any stage in mind", well that is a performance bummer.

Anyway, some suggestions,
Going to "File" then "Open" brings up a dialog which then brings up a Windows dialog.
After choosing a file in the Windows dialog, the MPDN dialog remains and you have to close it.
Four clicks.
Suggestion, "Open" should bring up Windows dialog directly then when I choose a file in the Windows dialog, it should start playing the file.
Two clicks.

Ease of setup,
Can you include subtitle renderer as part of MPDN (I fathom this is a legal question)? Requiring separate download and install is a negative in my opinion.

Options,
Some questions that the options menu can answer:
(1) "What is faster?" (2) "What this does?" (3) "What is this options recommended for?"


Sorry to disappoint but performance critical parts are actually in ASM and C / C++. C# merely provides the glue logic and it isn't very good at that too with GC stopping all managed threads when it feels like it (which means all MPDN's time critical threads are also in C++).

I can only share it as closed source or don't share it at all (for reasons I can't disclose). If you want to learn about writing a video renderer, there are plenty of resources on the net to get you started.

Oh yeah, C++ is too complicated (for me) compared to unsafe C# code. Also, have you tried native .net native? I hope you'll reconsider; it would be a major bummer if development stopped and no one could take over.

[huhn]

it's not rare that DXVA uses more power than normal software decoding making it pretty useless for normal content like a BD on system with a dedicated GPU.

and this is closed software. for a reason the creator knows but didn't want to tell us.

[Zachs]

@Hera

Quick Open File menu added in v2.6.1.

A setup package will be used some time in the future when I get some time to do it.

If someone wants to do a write up for the options, I'd be happy to assist and post the link on the OP but I don't want to clutter the options page further.

.NET native won't make a difference to MPDN's performance (GC will still be present and like I said before, performance critical parts are in ASM). And you do know it's not available for desktop apps yet, don't you? :)

[ajp2k11]

Tried v2.5.3 this weekend and it's smooth at 120Hz, even with "prefer new renderer" checked... weird?

[Zachs]

@ajp2k11

Not really weird :) It's because the new rendering path has some tweaks done to it too!
Glad to know it's working for ya!

[ajp2k11]

@ajp2k11

Not really weird :) It's because the new rendering path has some tweaks done to it too!
Glad to know it's working for ya!

Ah ok, I see! Works very well for me, good subjective quality but not too heavy for my laptop. It has become my default player now, thanks! :)

[aufkrawall]

Have you tried Custom Resolution Utility to prevent Nvidia bugs with D3D10 FSE?

Hoping for Catmull-Rom LL downscaling, smooth motion and NNEDi stuff. :)

[Zachs]

Have you tried Custom Resolution Utility to prevent Nvidia bugs with D3D10 FSE?

Hoping for Catmull-Rom LL downscaling, smooth motion and NNEDi stuff. :)

Yes it is the custom res utility that got me close to 23.976Hz in the first place but D3D10 FSE mode has a mind of its own and decides to ignore the custom settings. Its D3D9 implementation has no such issues. This is definitely due to the lack of test coverage on NVIDIA's part.

MPDN has Catrom but does not do LL scaling (my understanding is that LL only benefits in extreme downscaling of >= 400%). To get catrom, use bicubic with sharpness of 100 (this is equivalent to catrom mathematically).

I'm not a big fan of smooth motion (that's an understatement :)) but SVP is readily available as a postprocessing filter.

[aufkrawall]

Can't confirm, it shows 23,97xHz in player OSD in D3D10 FSE on a Geforce 9600 GT.
I meant the tool CRU, not Nvidia driver custom resolution tool:
http://www.monitortests.com/forum/Thread-Custom-Resolution-Utility-CRU
http://abload.de/thumb/crujrkvf.jpg (http://abload.de/image.php?img=crujrkvf.jpg)
It's important to untick the extension block checkbox and to do a restart after setting up resolutions.

Or are you referring to some command line switches for auto resolution change, since I can't find that functionality in the MPDN GUI. :)

[Zachs]

Can't confirm, it shows 23,97xHz in player OSD in D3D10 FSE on a Geforce 9600 GT.
I meant the tool CRU, not Nvidia driver custom resolution tool:
http://www.monitortests.com/forum/Thread-Custom-Resolution-Utility-CRU
http://abload.de/thumb/crujrkvf.jpg (http://abload.de/image.php?img=crujrkvf.jpg)
It's important to untick the extension block checkbox and to do a restart after setting up resolutions.

Or are you referring to some command line switches for auto resolution change, since I can't find that functionality in the MPDN GUI. :)

9600GT - that's the exact card I was testing it on!

I tested with both CRU and nvidia custom res.
While in windowed mode, MPDN shows my custom refresh rate. But once I go into FSE mode, MPDN's display rate rapidly changes to approach the new rates (which is the default rate).

What driver version are you using anyway? I'd love to get D3D10 to work on my 9600GT too, especially since it fully supports 10-/16-bit output mode.

MPDN doesn't do auto res change, so if refresh rate changes when going into FSE mode, then it's the driver doing it. I'll give it another try with CRU but your screen shot doesn't show manual timing? I had to set manual timing to get close to 23.976Hz (my TV reports 23Hz mode properly so I only need CRU to set the card up via manual timing to get closer to my audio ref clock).

[huhn]

both on windows 8?

you may read this
http://bugs.madshi.net/view.php?id=90

[Zachs]

Not only Win8. My win7 is the same. Only with D3D10 rendering path though. D3D9 has no problem.

[aufkrawall]

I'll give it another try with CRU but your screen shot doesn't show manual timing? I had to set manual timing to get close to 23.976Hz (my TV reports 23Hz mode properly so I only need CRU to set the card up via manual timing to get closer to my audio ref clock).
What timings do you suggest?
I'm using a LCD monitor with bypass panel and with my usual timings (which are said to have more frequent vblank) I can't hit 23.976 very precisely, neither with LCD standard.
Driver is plain 340.52 and OS is Windows 8.1. Hopefully I'll have a GM204 card again next week.

[jkauff]

Downloaded the latest MPDN last night and tried it for the first time. For 1080p, it's as good as or better than madVR (nothing touches madVR on doubled SD). Nice work!

I have one feature request. Please add "resume playback at last position" to the General Options. Quick Open File and Recent Files are less useful without it.

[Anime Viewer]

I don't know if its been previously mentioned in the thread (I did a quick search, but didn't turn it up), but I think a useful feature for the MPDN player somewhere down the line would be the play next in folder option (and possibly a loop at end of of folder) that is common in quite a few other players.




Edit: Just wanted to add a note about how impressed I am with the current version of MPDN. Back in late September I posted about problems I had with what was then version x64_2_1_0_1424. With the current version x64_2_6_3_1912 I have none of those problems. Before I couldn't run in fullscreen using Direct3D 10.1 render mode now I have no problem running in that mode (as long as I don't put a check in the Use new windowed mode rendering path when possible box). I can't credit my gpu (dated 9/18/2014, so it hasn't changed), so I credit the changes made to MPDN during that time. Given its very good image quality, fast render times, 0 dropped frames, 0 presentation glitches, and smooth video playback (smooth video during panning/scrolling scenes) it is currently my preferred media player.

http://r18.imgfast.net/users/1813/58/83/10/smiles/779362.gif

I'd use it all the time if it had a few more basic features (like noted above). ;)

Please add "resume playback at last position" to the General Options.
I'd find that useful as well. As far as I know that's something lacking in a lot of video players (including MPC).

[Zachs]

I have one feature request. Please add "resume playback at last position" to the General Options. Quick Open File and Recent Files are less useful without it.

Good idea!

I don't know if its been previously mentioned in the thread (I did a quick search, but didn't turn it up), but I think a useful feature for the MPDN player somewhere down the line would be the play next in folder option (and possibly a loop at end of of folder) that is common in quite a few other players.


Along with that, I've got playlist on my todo list as well. It will tie in quite well with playlist.

Just a heads up, MPDN v2.7.0 has been released and features 12- and 16-tap Lanczos and Jinc. It's also massively faster. First time I've been able to use Jinc 16-tap (or its equivalent) on my GTX560 without it sounding like a plane taking off! :)

[toniash]

Wouldn't it be possible to release your renderer alone (as Madvr)? I'm very happy with the rendering part but the player lacks many features that others have.
Only dreaming ..:):)

[italospain]

Wouldn't it be possible to release your renderer alone (as Madvr)? I'm very happy with the rendering part but the player lacks many features that others have.
Only dreaming ..:):)

i have the same dream :p

[Zachs]

Wouldn't it be possible to release your renderer alone (as Madvr)? I'm very happy with the rendering part but the player lacks many features that others have.
Only dreaming ..:):)

There's actually a few reasons for MPDN to have its own player but the technical one is .NET isn't exactly DirectShow filter friendly. MPDN needed a lot of tricks to get .NET to play nice, it's going to be quite difficult to make it into a pure DirectShow renderer.

[BetA13]

Do you plan shader support in future releases?
i really like this player so far, it has so much less performance impact on my system, finally i can watch movies with madvr but without having teh gpu at 60% all the time...

i do really miss shader support....

greetz BetA