madVR - high quality video renderer (GPU assisted)

[pankov]

madshi,
for the last couple of days I've had a few hangups of the player (Zoomplayer) when I use madVR. They always happen at the end the movie. A few seconds before the end of the file the picture freezes, the audio continues for 4-5 seconds more and then the whole player hangs up. If I close the player or load another file before the end of the movie everything is working fine.
Here is a log file of one hangup/lockup
http://www.mediafire.com/file/mtyjyjmmzmm/madVR%20-%20log.zip
It doesn't happen with all files so here is a sample
http://www.mediafire.com/?zmn2nyyrzat
I'm using Haali's splitter + CoreAVC or FFDShow and there is no such problem if I use another render (EVR/VMR/Haali) - only madVR hangs up.
Anybody else having this problem?

[namaiki]

I'm not quite sure what to say. I think that for MadVR 0.18 and newer, ~24fps on ~60Hz seems a lot more juddery than before (0.17).

[leeperry]

I'm not quite sure what to say. I think that for MadVR 0.18 and newer, ~24fps on ~60Hz seems a lot more juddery than before (0.17).
I also think that 0.18 was easier to stabilize...I've watched many real world movies lately, and their telecine's aren't quite as smooth as anime so it's hard to say for sure. I'll watch Space Chimps for the Nth time.

One thing's for sure, I don't get drastic judder(requiring a reseek) after 45/60 mins anymore...this used to happen w/ VMR9/EVR/etc etc. Now it's about stability, but I still think that windowed mode will always remain a major source of headaches for >45 mins movies...very eager to try exclusive mode at this point, oh my oh my :devil:

EDIT: oops, you can ignore the freezing problem when going windowed>FS before the picture showed up...it works fine in KMP after more testing, and there's an option to avoid freezing at opening in PotP...for some reason installing a new version had disabled it, duh :o

[fps]

I've tested for smoothness with samples form this thread (http://www.avforums.com/forums/streamers-network-media-players/1175436-files-judder-test.html). Only one of those files causes me big problems though.
It's the one with a framerate of 59.940 Hz which should almost much my LCD refresh rate.
I get tons of delayed and dropped frames which are clearly visible. Especially at the beginning of playback there is some "huge stutterness".
According to the OSD it seems for the first 20s or so the queues never fill up and the amount of dropped/delayed frames goes up like crazy.
After about 30s the queues fill up and the number of delayed/dropped frames stays put at 1162/64.
I've attached two screenshots, the first is representing the "empty queues" while the second one shows the stats after no more drops occur.
I tried to play around with all the various settings (number of backbuffers, timing mode, flush settings) but the problem is always the same, just the number of delayed/dropped frames changes a bit.

Screenshot 1 (http://img682.imageshack.us/i/89353504.png/)
Screenshot 2 (http://img208.imageshack.us/i/37118545.png//)

My specs:

(1) ATI Radeon HD 4830.
(2) Win 7/32.
(3) Aero on.
(4) 1680x1050@60Hz.
(5) Single monitor setup.
(6) Intel Core2Quad 9400s
(7) ffdshow rev 3472, MPCHC svn 2018

[leeperry]

I'm trying using only one buffer, and it looks pretty good so far! some ppl think that the higher the latency, the higher the jitter. I had some synchronized judder at the beginning, I guess Reclock needs some time to synchronize itself when making drastic settings changes in mVR(I'll come back w/ some logs if it happens again)..but anyway, PotPlayer is really a perfect transport to mVR...amazing combo(make sure to check "open a second thread when opening files to avoid freezing"): http://www.pixelz.fr/b/0/6/fa3e6ea61667785b82ed94e1b2e09t.jpg (http://www.pixelz.fr/b/0/6/fa3e6ea61667785b82ed94e1b2e09.png)

I've also reverted to the "normal" timing model(still running 23.976@96Hz), but did enable the 3 options on top...so many combinations to try!

[BeNooL]

madshi, would it be difficult on your end to add some sort of benchmark that could help us gather data for you....., perhaps when activated, it could cycle through some permutations of different options, gather some stats into a big log for you.

Just an idea. Perhaps it could be used in a future release to help someone obtain "optimal" settings for their particular setup... ie the combination that yields the..... lowest frame drops / or whatever the benchmark may be..

That is an excellent idea!

[pankov]

madshi,
in addition to the lockup I was talking about in my previous post (http://forum.doom9.org/showthread.php?p=1412814#post1412814) I noticed that sometimes madVR doesn't detect the correct composition rate even though I restart the playback and Zoomplayer builds a totally new graph with a new instance of madVR.
In the following scenario:
I have my monitor at 50Hz, then I start Zoomplayer but don't start playback, then I change the refresh rate to 23.976Hz (using Catalyst Control Center, so Windows/Aero knows that I've changed it). Now I play a movie and change back to 50Hz again using CCC. Now it's normal for madVR to get confused but the strange thing is that even after I restart the playback (or play another file) the new madVR instance still thinks that the composition rate is 23.976Hz. Strangely if I start another instance of Zoomplayer with another instance of madVR it too detects the composition rate as 23.976Hz. So to get the correct value I have to close every instance of Zoomplayer which was started before the refresh rate change.
Do you find this normal? Can this be an explanation of the stutter that some users are experiencing?

[Mark_A_W]

madshi

I've been testing v0.21 on and off for days now, both with a 2600XT and now a 4850 (Ya! 3DLUT works!).


And I cannot get super-smooth playback.


I've tried lots of combinations of settings, I seem to get the best results with No. of Backbuffers = 1. But they still aren't perfect.

All other settings don't really seem to matter that much.

(Actually, I haven't set the backbuffers to 8 on the new card..).


So I tried v0.18 again, this time with the 4850 and the 3DLUT. And it just keeps on trucking. It's relentless. Supersmooth.

I know you told me the setting combo in 0.21 which should be the same as 0.18, but it's not.


(1) GPU: ATI 4850
(2) OS: Windows W7 x64
(3) Movies: 1080p mkv files, 23.976 fps (obtained from blurays with eac3to)
(4) Display resolution + refresh rate: 1920x1080, 95.904hz Interlaced with PowerStrip
(5) Dual monitor setup, playing on secondary, Aero OFF
(6) Zoom Player
(7) Video decoder: ffdshow (VC1: wmv9), CoreAVC
(8) madVR 0.21/0.18, 3DLUT ON.
(9) Reclock, no V-sync


And yes, a 4850 is stoopid hot. Damn thing idles at 80 deg C. But that doesn't matter to me, I have a big desktop with lots of fans - the audio/video run through the wall to the Home Theatre.

Cheers

Mark

[leeperry]

I'm also trying older builds these days...0.21 can be dead smooth on one movie, then not smooth at all on the other...I can't seem to be able to find settings that'd give 96Hz über-smoothness reliably :o

Maybe you could learn more from the huge log I provided?

But well, soon enough, D3D exclusive mode will put an end to all this IMHO...and the current windowed mode works amazingly well on 29.97fps@89.91Hz, I'm out of speech.

[janos666]

I start to think that the given (individual) display could also affect the smoothness of the video playback.
I bought a new display (with a fixed-60Hz LCD panel like my older one) and I felt that video playback is much smoother with it. I thought that my subjective sentiment is affected by the new madvr tweak settings and/or that this H-IPS panel has lower response times than my old S-PVA display.
Today I got a warranty-replacement (there was some dead subpixels on the first panel) and I am surprised that 1080p24 video playback doesn't feel smooth anymore.
May be I acclimatized to the lower response time and I feel the permanently existing 3:2 stuttering again. I don't know.

[sneaker_ger]

Is there any way to not let madVR use fullscreen with the newest MPC-HC? It open a second window for me that goes fullscreen. Windows XP, Radeon x1950

/edit: ok, seems to be a problem of mpc-hc, because it was going into fullscreen mode even though the check mark was not checked. Activing and re-deactivating solved the problem.

[oddball]

I am unable to get MadVR to load properly (and indeed it crashes PotPlayer). Using latest build. Not tried older I don't think but will give it a go if I can find an older build. The times I got it to work (I can't rcall how I did it I think I upped it's priority to the top in DFSMgr) it plays back everything all jerky in MPC HC even though it's not putting any strain on the CPU (I have CUDA support).

[Hypernova]

I start to think that the given (individual) display could also affect the smoothness of the video playback.
I bought a new display (with a fixed-60Hz LCD panel like my older one) and I felt that video playback is much smoother with it. I thought that my subjective sentiment is affected by the new madvr tweak settings and/or that this H-IPS panel has lower response times than my old S-PVA display.
Today I got a warranty-replacement (there was some dead subpixels on the first panel) and I am surprised that 1080p24 video playback doesn't feel smooth anymore.
May be I acclimatized to the lower response time and I feel the permanently existing 3:2 stuttering again. I don't know.

Maybe, just maybe, your condition is different between the two time you watch it? I know music feel slower after I finished my run, and it feel faster just after I woke up.

[madshi]

Madshi, I'm noticing that a few of my older videos do not seem to display in the correct Aspect Ratio; they work fine in EVR.
From what I can gather, it looks as if the DAR is not being respected. To be more specific, it seems the "Keep Aspect Ratio" option for MPC-HC is no longer working when in conjunction with MadVR.
With EVR & the aforementioned MPC-HC option enabled, the appearance of certain video will be adjusted according to its DAR; for MadVR, it has no effect whatsoever and the video remains incorrectly sized.

I've included a log & mediainfo output for two such files.
http://www.multiupload.com/JKPZUP3QRK
http://www.multiupload.com/8UW57R41S2
I need a sample.

I can not completely remove the dropped frames on my configuration in Win XP. Only on Win 7, with very weak preferences (upscaling, downscaling) for my configuration.
Do the dropped frames increase all the time? Or are there only dropped frames when the movie starts?

If your 23.976 isn't getting changed by reclock to a speed that fits more evenly into 96.003 then 1 delayed frame seems to be unavoidable IMO.
If madVR detects a delayed frame, that has nothing to do with a mismatch between movie framerate and display refresh rate. A delayed frame means that madVR didn't manage to show a frame at the planned vsync, but only managed to show it one (or more) vsyncs too late.

I've been testing a patched MPC-HC version that avoids creating more than one madVR instance at the same time and I could get it working for both SD and HD. So this was the problem.
I didn't even know that there was a patch being worked on! I still have it on my to do list to make more than madVR instances at the same time work. But it's good to know that you seemingly found a workaround.

Maybe all those settings only make a real difference on slower systems?
Yes, I think your system is simply too damn fast to show any differences between all the tweaking options. Maybe the situation would be different if you were using an ultra high refresh rate, like some others do (for their CRTs).

0.21 with mph hc latest svn, hd4850, and hd files is a little slow in some cases
i have e8400, hd4850, 4gb of ram and win7 x64 with mpc hc latest svn
what are the best settings on madvr 0.21 for my config?
please i have seriously slowdowns with madvr and mpc!
Your GPU should be plenty fast enough. Just play with all the options. You can also try switching back to older madVR versions. If you find a version which works best for you, let me know.

don't suppose there'll ever be support for DVD playback?
I hope it will work sooner or later.

yes, it hangs with 90% of files!
It doesn't seem to hang for most other people? I need to be able to reproduce that on my PC. So if it hangs with some specific files, I need a sample.

for the last couple of days I've had a few hangups of the player (Zoomplayer) when I use madVR. They always happen at the end the movie. A few seconds before the end of the file the picture freezes, the audio continues for 4-5 seconds more and then the whole player hangs up. If I close the player or load another file before the end of the movie everything is working fine.
Here is a log file of one hangup/lockup
According to the log, in the middle of movie playback, Zoomplayer suddenly creates a 2nd madVR instance! Don't know why it does that, but that is responsible for the problem. Looks like a ZP bug to me!

I'm not quite sure what to say. I think that for MadVR 0.18 and newer, ~24fps on ~60Hz seems a lot more juddery than before (0.17).
Maybe your GPU doesn't like the "dithering via math" change? Try disabling dithering. Does that bring smoothness back to 0.17 levels for you?

oops, you can ignore the freezing problem when going windowed>FS before the picture showed up...it works fine in KMP after more testing, and there's an option to avoid freezing at opening in PotP...for some reason installing a new version had disabled it, duh :o
Good to hear. I had downloaded KMP and was not able to reproduce the problem here.

I get tons of delayed and dropped frames which are clearly visible. Especially at the beginning of playback there is some "huge stutterness".
According to the OSD it seems for the first 20s or so the queues never fill up and the amount of dropped/delayed frames goes up like crazy.
After about 30s the queues fill up and the number of delayed/dropped frames stays put at 1162/64.
I've attached two screenshots, the first is representing the "empty queues" while the second one shows the stats after no more drops occur.
I tried to play around with all the various settings (number of backbuffers, timing mode, flush settings) but the problem is always the same, just the number of delayed/dropped frames changes a bit.
Ok, thanks. I think I can improve the frame dropping behaviour a bit. Currently when dropping occurs, madVR sometimes has problems getting the queues filled again.

I noticed that sometimes madVR doesn't detect the correct composition rate even though I restart the playback and Zoomplayer builds a totally new graph with a new instance of madVR.
In the following scenario:
I have my monitor at 50Hz, then I start Zoomplayer but don't start playback, then I change the refresh rate to 23.976Hz (using Catalyst Control Center, so Windows/Aero knows that I've changed it). Now I play a movie and change back to 50Hz again using CCC. Now it's normal for madVR to get confused but the strange thing is that even after I restart the playback (or play another file) the new madVR instance still thinks that the composition rate is 23.976Hz. Strangely if I start another instance of Zoomplayer with another instance of madVR it too detects the composition rate as 23.976Hz. So to get the correct value I have to close every instance of Zoomplayer which was started before the refresh rate change.
Do you find this normal? Can this be an explanation of the stutter that some users are experiencing?
I don't know why this happens. madVR is simply reporting the composition rate. Must be a bug in Aero, or in GPU drivers.

I've been testing v0.21 on and off for days now, both with a 2600XT and now a 4850 (Ya! 3DLUT works!).

And I cannot get super-smooth playback.

I've tried lots of combinations of settings, I seem to get the best results with No. of Backbuffers = 1. But they still aren't perfect.

All other settings don't really seem to matter that much.

(Actually, I haven't set the backbuffers to 8 on the new card..).

So I tried v0.18 again, this time with the 4850 and the 3DLUT. And it just keeps on trucking. It's relentless. Supersmooth.

I know you told me the setting combo in 0.21 which should be the same as 0.18, but it's not.
Weird. Do you see delayed and/or dropped frames with 0.21? Ok, please download these test builds:

http://madshi.net/madVRtest.rar

Contained are 3 different 0.21 test builds. Does any one of them behave like 0.18 (with the settings I told you earlier)?

Maybe you could learn more from the huge log I provided?
Where is that huge log? Don't remember to have seen it. BTW, when you don't have that perfect smoothness, do you see delayed or dropped frames?

I start to think that the given (individual) display could also affect the smoothness of the video playback.
I bought a new display (with a fixed-60Hz LCD panel like my older one) and I felt that video playback is much smoother with it. I thought that my subjective sentiment is affected by the new madvr tweak settings and/or that this H-IPS panel has lower response times than my old S-PVA display.
Today I got a warranty-replacement (there was some dead subpixels on the first panel) and I am surprised that 1080p24 video playback doesn't feel smooth anymore.
May be I acclimatized to the lower response time and I feel the permanently existing 3:2 stuttering again. I don't know.
The display definitely affects motion smoothness. E.g. JVC projectors are reported to be slightly less smooth than Sony projectors during camera pans with a specific speed.

Is there any way to not let madVR use fullscreen with the newest MPC-HC? It open a second window for me that goes fullscreen. Windows XP, Radeon x1950
Just make sure that you have the D3D Fullscreen option turned off in MPC-HC. That option is available in newer MPC-HC builds, in preparation for a future madVR version.

I am unable to get MadVR to load properly (and indeed it crashes PotPlayer). Using latest build. Not tried older I don't think but will give it a go if I can find an older build.
Can you please upload a log file? BTW, all (useful) older madVR versions are already on your harddisk. You just need to rename the files.

The times I got it to work (I can't rcall how I did it I think I upped it's priority to the top in DFSMgr) it plays back everything all jerky in MPC HC even though it's not putting any strain on the CPU (I have CUDA support).
Which is your GPU, OS, CPU, display refresh rate? Aero on/off? Etc...

CUDA can collide with madVR, if your GPU is not fast enough.

[madshi]

It seems the setting that is responsible for the weird looking pans is "copy only 1 backbuffer at a time". This needs to be checked/on always or otherwise, pans won´t be perfectly smooth (at least on my system).
Is there anybody who needs "copy only 1 backbuffer at a time" to be UNCHECKED to get good results? If not, I'd like to remove this option and have it always "checked".

[sneaker_ger]

see my edit, activting and deactivating the fullscreen checkmark solved the problem. Will report the error to the mpc-hc team if I'm able to reproduce it. Thx.

[leeperry]

Where is that huge log?
here: http://forum.doom9.org/showpost.php?p=1412130&postcount=3439

I will try to provide more logs if you want, basically this one ran for ±45 mins so you can see what's going on on my box.
when you don't have that perfect smoothness, do you see delayed or dropped frames?
The same problem I've had since 0.18, nothing increments in the mVR OSD but some frames are delayed...killing the smoothness. I seek back and it's smooth, until 5 mins later when it'll happen again. I've tried every possibly combination in 0.21 :o

[madshi]

The same problem I've had since 0.18, nothing increments in the mVR OSD but some frames are delayed...
If nothing increments in the OSD then the logs don't help, unfortunately.

[leeperry]

If nothing increments in the OSD then the logs don't help, unfortunately.
well, in that very log you can see in my screenshot that there's a delayed frame that wasn't there when the movie started...so it should be visible in the log :)

[pankov]

According to the log, in the middle of movie playback, Zoomplayer suddenly creates a 2nd madVR instance! Don't know why it does that, but that is responsible for the problem. Looks like a ZP bug to me!
madshi,
I have ZP configured to start the next file in the playlist when the current one fininshes. I confirm (with ProcessExplorer) that ZP opens the next one a few seconds before the end of the current one but this doesn't happen if I use EVR or any other render. Only with madVR ZP I get this "early finish". I don't know what ZP uses to check if the current file has finished but it's not working with madVR. Could it be that madVR fools ZP that the playback has finished before it really does? Could it be that the buffering that madVR does is the culprit?


I don't know why this happens. madVR is simply reporting the composition rate. Must be a bug in Aero, or in GPU drivers.
... OK but does madVR use this value for something? Is it only for OSD information or it's really used for some calculations? If it's the latter one then we have a problem.

[namaiki]

Re:I'm not quite sure what to say. I think that for MadVR 0.18 and newer, ~24fps on ~60Hz seems a lot more juddery than before (0.17).

Maybe your GPU doesn't like the "dithering via math" change? Try disabling dithering. Does that bring smoothness back to 0.17 levels for you?


It seems to help (might be smooth, but then seek and it will be juddery again), but it doesn't seem to be the cause.

[cyberlolo]

Is it possible to use the latest MPC-HC internal VC-1 filter with madVR? Actually I have to disable it or use any another renderer...

[leeperry]

ok, I've polished my timings to 96.000Hz(instead of 96.003Hz)...Reclock doing a 24fps adaptation after all. I've also reset its timings and kept the default 0.21 mVR build/settings(except for the XP upload texture thingie), and Alice was as smooth as can be! Of course, its telecine is not perfect...like the nasty dropped frame at 01:07:50 but it's been amazingly smooth anyway. I'll run more testing w/ RocknRolla(perfect transfer!) and report back. It's dead obvious that I need flushing anyway, this doesn't seem to be viable to have them all disabled.

PS: RocknRolla has been dead stable from start to end, totally amazing(the refresh rate started at 96.00036Hz and had slowly reached 96.00028Hz 100 mins later) :cool:

[oddball]

Can anyone tell me how to get MadVR 0.21 to load in MPC-HC or PotPlayer? Right now it does not appear to load in either but does load in Zoom Player. However even though it loads in Zoom Player (and when I had it working in MPC-HC) it is Jerk'O'Vision.

My CPU is hardly being used in Win7 64 with latest Nvidia 257 drivers. So I can't see why it is jerking.

P.S. It jerks more when fullscreen. if in a small window it seems to play smooth. So is this a video card issue or an OS issue or something else?

[naomatrix]

Do the dropped frames increase all the time? Or are there only dropped frames when the movie starts?

In my case on WinXP I have a drop frame in three points play:
1) during the movie starts (3-6 drop frame)
2) during the switch full screen resolution -> windowed mode -> full screen (3-10)
3) during film rewind (2-8)
When playing a movie constantly at full screen (or constantly in windowed mode) no missing frame.
Strange, if I use "Autochange fullscreen monitor mode" in MPC-HC for example:
23.5-24 => 1400х900 32bpp (72Hz)
24.5-25 => 1400х900 32bpp (75Hz)
29.5-30 => 1400х900 32bpp (60Hz)
other renderers Direct3D (VMR9; EVR) does not have drop frame, just a little jitter, but madvr still skip frames, even when I use the LCD monitor mode 1280х800(72Hz) for 720p(23.976) video - without upscaling.
I noticed that the missing frame is then when - render+present time have more than vsync interval.
In general, the renderer displays the image almost perfectly, but it would not have skipped frames according to Your concept of an ideal(bit perfect) rendering.:)

MPC_HC + CoreAVC + EVR - http://i2.imageban.ru/out/2010/07/04/41bde27f340058648137bfa1c1ce33cd.jpg

MPC_HC + CoreAvc + madvr0.21 - http://i2.imageban.ru/out/2010/07/04/e8b7d06bd5d313059a2e01a3a21430bf.jpg

[Mark_A_W]

madshi

I played a bit more with 0.18, and this time I had a few delayed frames (in half an hour).

Then I played with 0.21, and one time I had it rock solid. Then another I had a worrying episode where I was getting a periodic tiny juder (every 5 secs), but it did not increment the delayed frames.


It is just so inconsistent.... I think you are right, the only way to "fix" it is to go exclusive fullscreen. (However the results are generally better than any other renderer.)


But, FWIW, I seem to get the best results with:

- upload render thread = OFF

- copy only 1 backbuffer = OFF

- timing model = NORMAL

- backbuffers = 6 (or 8...unlike the 2600XT card, this does not seem to matter with the 4850 card)

Flushes as per default.


I haven't played with the debug builds yet.

[Trigunflame]

I need a sample.
On my end, both Samples display in the correct AR with MPC-HC when using VMR7,VMR9,EVR & Haali - when using the "Keep Aspect Ratio" option.

Video #1
EVR: http://i.imagehost.org/0301/1_176.jpg
MadVR: http://i.imagehost.org/0023/2_50.jpg
Sample: http://www.megaupload.com/?d=FT3CKJ66

Video #2
EVR: http://j.imagehost.org/0115/1_75.jpg
MadVR: http://i.imagehost.org/0154/2_26.jpg
Sample: http://www.megaupload.com/?d=6H5WE2IJ

[oddball]

OK I got it loading in MPC-HC (I had various filters blocked). But it's still juddering like crazy. I tried older versions too. I am using CoreAVC 2.0 with CUDA enabled. But whether CUDA is on or off it makes no difference to the juddering. SD or HD. It actually plays a little smoother in Zoom Player. But not completely smooth.

[ianken]

OK I got it loading in MPC-HC (I had various filters blocked). But it's still juddering like crazy. I tried older versions too. I am using CoreAVC 2.0 with CUDA enabled. But whether CUDA is on or off it makes no difference to the juddering. SD or HD. It actually plays a little smoother in Zoom Player. But not completely smooth.

For me the juddering was purely a lack of GPU beefcake. The 9300 integrated on my HTPC is just not macho enough. And since I have it in a custom heat pipe fan-less enclosure replacing the GPU is not an option, the one slot I have hosts a TV tuner.

On my gaming rig (which has GPU beefcake to spare) this renderer shines.

[oddball]

So a G210 is not fast enough? Even if I turn off CUDA it still stutters and does not seem to lean on the CPU at all.

[Blue_MiSfit]

CUDA just does the decoding (which actually happens on a dedicated ASIC, not the GPU per-se). MadVR uses the GPU itself ;)

[namaiki]

CUDA just does the decoding (which actually happens on a dedicated ASIC, not the GPU per-se). MadVR uses the GPU itself ;)

CUDA uses VRAM (so does Aero). I have a 256MB 9600M GT and at 1920x1080, I can't use CUDA and MadVR at the same time or there will be major lag. 256MB just barely covers 1920x1080 (~235MB).

However, also try change resizers to Bilinear or so to see if it is a case of not enough GPU core speed.

[iSunrise]

So a G210 is not fast enough? Even if I turn off CUDA it still stutters and does not seem to lean on the CPU at all.
I guess it is just barely enough, if at all. Your G210 only has 16 CUDA cores (shader processors) and only a 64bit memory interface (madshi´s 9400M has a 128bit interface) which is the bare minimum, but still sufficient for decoding with the integrated VP4 video decoding engine, when you are using, e.g. DXVA. madVR does not work that way, though.

You can try to check the load on your card (while playing a demanding file) with GPU-Z, where you can see the actual load that is on your GPU, your memory controller or (this does not apply with madVR) your video engine.

madVR heavily uses the GPU´s shaders (all work is done via GPU shaders, see the first post of page 1 (http://forum.doom9.org/showpost.php?p=1271414&postcount=1)) to bypass any shortcomings that are completely out of madshi´s hands and to make sure that you get the highest quality out of your content and pass it on to your display.

[ryrynz]

Might be an idea to state some minimum requirements.
This way we can perhaps avoid discussing performance on low end graphics further.

[namaiki]

My Intel 4500MHD can play video using MadVR perfectly* if the Bilinear resizer is used. I'm pretty sure that GPU is worse than what most people have.

[oddball]

So I assume my GPU is underpowered?

http://img815.imageshack.us/img815/1130/gpu1.jpg
http://img812.imageshack.us/img812/9117/gpu2.jpg

[namaiki]

Yes, GPU load is too high. Try use a different resizing algorithm for luma.

[oddball]

Out of curiosity what would be the minimum spec Nvidia card to use on default madVR settings? A GT240?

[namaiki]

I dunno, but my 9600M GT can do it (32 cuda cores). It has just enough power to push 1920x1080x30fps.

[leeperry]

my GPU is underpowered?
720p h264 via CoreAVC CUDA on a 384MB 9600GSO(rebadged 8800GS): http://thumbnails31.imagebam.com/8715/8e56ff87141959.jpg (http://www.imagebam.com/image/8e56ff87141959)

I chose it over the 9600GT coz the latter only has 64SP, wherehas the 8800GS has 96. I've also reflashed its BIOS to disable the 2D/3D clocks thingie, as I don't want it to fire up in the middle of a movie(I've seen it happening on an HD3850 w/ HR) :devil:

48/64SP might be the minimum to get it all working nicely.

[oddball]

Hmm. What does the 2D/3D clock thingie do? Would that be causing my G210 to drop frames in DXVA mode or the odd random stutters I get every so often (Unrelated to MadVR I know)? BTW your message is already on Google search lol. Anyhow putting all settings to their lowest did not help a great deal it still stutters more than DXVA playback using EVR CP. Maybe if I upgrade my GPU at a later date it will be better. Also 0.18 plays a little smoother than 0.21 for some reason.

[namaiki]

..but why is memory use so high in oddball's GPU status pic?

[iSunrise]

Out of curiosity what would be the minimum spec Nvidia card to use on default madVR settings? A GT240?
Yes, for current worksloads (H.264@1080p@60Hz) and with the scaling options that are currently available within madVR, you should be perfectly fine.

Hmm. What does the 2D/3D clock thingie do? Would that be causing my G210 to drop frames in DXVA mode or the odd random stutters I get every so often (Unrelated to MadVR I know)? BTW your message is already on Google search lol. Anyhow putting all settings to their lowest did not help a great deal it still stutters more than DXVA playback using EVR CP. Maybe if I upgrade my GPU at a later date it will be better. Also 0.18 plays a little smoother than 0.21 for some reason.
You could try to create an application profile in the NVIDIA driver for [your player].exe and set "Power Management Mode" to "Prefer maximum performance", which will then always run your graphics card at the highest defined clock speeds while running [your player].exe. Without that option the default is "Adaptive", which means that depending on the current load your GPU clocks will be monitored constantly and be adapted while playing.

However, since your card seems to be too slow anyway, this doesn´t help at all, unfortunately.

..but why is memory use so high in oddball's GPU status pic?
It kinda looks like while taking that screenshot he had CoreAVC´s CUDA enabled. This will totally kill smoothness on his card, since it will demand even more memory and it puts a lot of stress on the 64bit memory controller, the GPU core and the video decoding engine.

@oddball:
You could try to use ffdshow (ffmpeg-mt) with max. threads and keep CoreAVC out of the loop completely. That way the decoder load would be on your CPU, while the GPU has it´s full resources available for madVR. At least that´s what most people in this thread do and it does seem to work perfectly. But even for that your GPU may be too slow, can´t really tell from here.

[oddball]

Will overclocking the card make any difference? EDIT: I switched to ffdshow for decoding and now MadVR does not show under MPC-HC filters as loaded. Just the standard Video Render.

EDIT2: Nevermind I had ffdshow outputting a different colorspace so MadVR would not load. Sorted. Testing.

EDIT3: Well that kinda works. But. The idea was to take the load off the CPU to begin with when I got this G210 recently. I should have spent a little more obviously on a better card. I was looking for a fanless single slot solution though. When loaded on the CPU it gets very heavy playing a 1080P m2ts test peice. As soon as any background activity kicks in it drops frames all over the place. Also it requires ReClock to run smooth on my 24P HDTV. If I don't use ReClock and go with direct to SPDIF it drops frames very quickly. I have a feeling MPC-HC's 24FPS matching could be an issue there. I notice it tries to play 24FPS for 23.976FPS even when not selected as an option under the fullscreen menu (or that could just be the DXVA renderer when that is in use instead of MadVR. I am not sure).

[Razoola]

I have a gt240. A very nice card for the price. BTW I advise you get the DDR5 version if you can and not the DDR3 one. Also, if your using reclock use the bitstream option and not the resampler if you can, that will save you many CPU cycles.

[oddball]

Yeah well looks like there are no fanless GT 240's with DDR5. Anyhow I don't want to go throwing more money at the system for now. I'll make do with DXVA for the time being as the increase in image quality I see is marginal with Bicubic PS2.0 enabled. It would have been nice to have MadVR running smoothly with default settings but the tradeoff in performance (and having to change various codec settings) puts me off. Nice to have if you have the 'oomph' though :)

[madshi]

I have ZP configured to start the next file in the playlist when the current one fininshes. I confirm (with ProcessExplorer) that ZP opens the next one a few seconds before the end of the current one but this doesn't happen if I use EVR or any other render. Only with madVR ZP I get this "early finish". I don't know what ZP uses to check if the current file has finished but it's not working with madVR. Could it be that madVR fools ZP that the playback has finished before it really does? Could it be that the buffering that madVR does is the culprit?
madVR lets the decoder run faster than it normally does. So the decoder might be confused. Not sure exactly if that influences the graph's "playback position". If so, there's not much I can do about it, or else the whole queue logic would not work.

How do you know that ZP does not create a 2nd EVR instance, as well?

So the problem only occurs when using seamless playback with playlists?

... OK but does madVR use this value for something? Is it only for OSD information
It's only for informational purposes. madVR strictly only uses the self-calculated display refresh rate information (first line in the OSD).

It seems to help (might be smooth, but then seek and it will be juddery again), but it doesn't seem to be the cause.
Weird. Then I don't know for sure why v0.17 would work better for you than newer builds. Maybe it's the frame drop/delay logic. I plan to improve that a bit in a future version. So there is still some hope to get playback smoothness back to v0.17 levels for you. Seems that you are the only one having best results with v0.17, though. Most other people seem to prefer v0.18 or v0.21.

Is it possible to use the latest MPC-HC internal VC-1 filter with madVR? Actually I have to disable it or use any another renderer...
Do you mean the VC-1 decoder or splitter? Does either one not work?

ok, I've polished my timings to 96.000Hz(instead of 96.003Hz)...
That's always a good idea!

In my case on WinXP I have a drop frame in three points play:
1) during the movie starts (3-6 drop frame)
2) during the switch full screen resolution -> windowed mode -> full screen (3-10)
3) during film rewind (2-8)
When playing a movie constantly at full screen (or constantly in windowed mode) no missing frame.
That's just fine. I'm actually considering "hiding" dropped frames in these 3 situations, because I simply don't consider dropped frames a problem in these special situations.

I played a bit more with 0.18, and this time I had a few delayed frames (in half an hour).

Then I played with 0.21, and one time I had it rock solid. Then another I had a worrying episode where I was getting a periodic tiny juder (every 5 secs), but it did not increment the delayed frames.
So what is your final verdict? v0.18 is not better than v0.21 for you, after all?

But, FWIW, I seem to get the best results with:
- upload render thread = OFF
- copy only 1 backbuffer = OFF
Are you sure about the "copy only 1 backbuffer"? Is it a noticeably improvement for you? I'm asking because I'd really like to get rid of this option and have it always ON.

I haven't played with the debug builds yet.
They're not actually debug builds. They're v0.21 release builds with simply one small change each, which should bring these v0.21 builds nearer to what v0.18 did. If you now say that you can't see a difference between v0.18 and v0.21, anymore, then testing these test builds makes no sense. If you still do see a difference between v0.18 and v0.21 then please test the 2 special builds and let me know if one of the 2 builds behaves like v0.18 or if both behave like v0.21 in terms of smoothness.

On my end, both Samples display in the correct AR with MPC-HC when using VMR7,VMR9,EVR & Haali - when using the "Keep Aspect Ratio" option.
With the first sample I have incorrect AR with MPC-HC with ffdshow tryouts and AVI splitter on XPSP3, too. Tried EVR and EVR-Custom. The 2nd sample doesn't download. I'm getting the complaint "the file is currently not available".

Might be an idea to state some minimum requirements.
This way we can perhaps avoid discussing performance on low end graphics further.
I wish it was that easy. Performance differs *a lot*, depending on scaling algorithm, movie framerate, movie resolution, display resolution etc. Even very low end GPUs seem to work with madVR fine, as long as you stick with Bilinear scaling and playback only movie content (24fps).

Furthermore, performance is not final yet. Fullscreen exclusive mode should improve performance a bit, and maybe I can squeeze out some more performance by optimizing the shader code, too. So there's simply no way right now to say: "GPU xyz is too slow". You always have to ask: For which content, with which scaling algorithm, with which movie framerate, with which resolution etc...

Out of curiosity what would be the minimum spec Nvidia card to use on default madVR settings? A GT240?
I have a gt240. A very nice card for the price. BTW I advise you get the DDR5 version if you can and not the DDR3 one.
As I'm always saying: If you care about max image quality, and if you plan on using future madVR versions with max quality options, you want to get the fastest card you can afford and which fits your thermal requirements. The current madVR version only has very basic processing capabilities built in, because currently I'm focusing on playback smoothness and stability. There are more demanding algorithms I'm planning for future versions (don't ask me what kind of algorithms and when), and for that you'll need every bit of GPU performance you can get. The more the merrier.

Will overclocking the card make any difference?
Maybe a bit. But your best bet is to switch chroma and luma scaling to Bilinear.

The idea was to take the load off the CPU to begin with when I got this G210 recently. I should have spent a little more obviously on a better card. I was looking for a fanless single slot solution though.
I know what you're talking about. I have a totally passive HTPC myself, but with a clever case heatpipe system and gigantic external heat sinks. I will probably buy a 5750 sooner or later and attach it to the case's heatpipe system. I think that should work for me.

[leeperry]

That's always a good idea!
Well, the hardcore test is to reboot..this will rule out any Reclock timings dependency, as this testimonial seems to match my experience: http://forum.slysoft.com/showpost.php?p=269382&postcount=3

But I'm always rolling audio interfaces, players, mVR versions...so it's hard to fault anyone tbh :o

OTOH, I've just watched "Shutter Island" in 23.976fps@96.000Hz, and it's been dead smooth for 2H straight(default 0.21 build/settings except for the XP upload texture)! I think I've seen a delayed frame near the end, I planned on double-checking at the end but it seems that CTRL+R doesn't work if you don't have the OSD enabled...could you please allow it to reset the rejected frames numbers even if the OSD isn't being currently shown?
if you plan on using future madVR versions with max quality options, you want to get the fastest card you can afford. [..] There are more demanding algorithms I'm planning for future versions
This sure would be nice: http://techreport.com/articles.x/16617/3

The demos on their website are pretty darn amazing, but it isn't quite done in realtime: http://www.vreveal.com/video_demos
What does the 2D/3D clock thingie do? Would that be causing my G210 to drop frames in DXVA mode or the odd random stutters I get every so often (Unrelated to MadVR I know)?
It never hurts to lock the 2D/3D clocks, whatever in software(drivers profile) or hardware(BIOS mod)...what card do you have? it seems shared, like an IGP? why only 8X PCI-E? anyway, yes...grab a second hand 8800GS or so? I'm sure you can get a 64SP card for quite cheap...and you want at least GDDR3 and a 192bit bus width, 64bit is really a nasty bottleneck.

I recently got a cheap aluminium VF1000, damn this thing doesn't break a sweat in 5V :cool:

[Trigunflame]

With the first sample I have incorrect AR with MPC-HC with ffdshow tryouts and AVI splitter on XPSP3, too. Tried EVR and EVR-Custom. The 2nd sample doesn't download. I'm getting the complaint "the file is currently not available".
Try this: http://www.multiupload.com/HJ5JISVUJB

Are you saying that the sample displayed incorrect AR on your system, even with EVR/EVR-Custom?
And you do have the "Keep Aspect Ratio" option enabled? Perhaps this is specific to Win7 if you're not seeing the problem on XP?

Note, I did try and establish as controlled a test environment as I could.. and the results seem to be the same.

1) Uninstalled MadVR, FFDSHOW-Tryouts & MPC-HC
2) Installed MPC-HC x86 r2099 (http://www.xvidvideo.ru/component/docman/doc_download/4023-media-player-classic-homecinema-x86-svn-2099-----with-installer.html)
3) Installed FFDSHOW-Tryouts x86 IC11 r3488 (http://www.xvidvideo.ru/component/docman/doc_download/3989-ffdshow-tryouts-project-svn-3488-x86-sse-icl11.html)
4) Installed MadVR 0.21 (http://madshi.net/madVR.zip)
5) Cleared all modified settings from the above softwares. Everything is set to their respective defaults.

Video demonstration of various output filters & their results.
http://www.youtube.com/watch?v=xNL3A8f7jPI

Note: I didn't capture the haali result in the interest of time.

Summary:
Keep Aspect Ratio: Enabled

EVR-Custom - Player Window is Resized to "Correct" the AR.
EVR - Player Window is Resized to "Correct" the AR.
Haali - Player Window is Resized to "Correct" the AR.
MadVR - Player Window is Not Resized, nor is Video Image resized to the correct AR.

Keep Aspect Ratio: Disabled

EVR-Custom - Player Window is Not Resized, nor is Video Image resized to the correct AR.
EVR - Player Window is Not Resized, But the Video Image Is resized to "Correct" the AR.
Haali - Player Window is Not Resized, nor is Video Image resized to the correct AR.
MadVR - Player Window is Not Resized, nor is Video Image resized to the correct AR.


Pin Info:

Sample.avi

EVR & EVR-CustomFilter : Enhanced Video Renderer - CLSID : {FA10746C-9B63-4B6C-BC49-FC300EA5F256}

- Connected to:

CLSID: {04FE9017-F873-410E-871E-AB91661A4EF7}
Filter: ffdshow Video Decoder
Pin: Out

- Connection media type:

Video: YV12 528x480 (13:10) 29.97fps

AM_MEDIA_TYPE:
majortype: MEDIATYPE_Video {73646976-0000-0010-8000-00AA00389B71}
subtype: MEDIASUBTYPE_YV12 {32315659-0000-0010-8000-00AA00389B71}
formattype: FORMAT_VideoInfo2 {F72A76A0-EB0A-11D0-ACE4-0000C0CC16BA}
bFixedSizeSamples: 1
bTemporalCompression: 0
lSampleSize: 380160
cbFormat: 112

VIDEOINFOHEADER:
rcSource: (0,0)-(528,480)
rcTarget: (0,0)-(528,480)
dwBitRate: 0
dwBitErrorRate: 0
AvgTimePerFrame: 333666

VIDEOINFOHEADER2:
dwInterlaceFlags: 0x00000000
dwCopyProtectFlags: 0x00000000
dwPictAspectRatioX: 13
dwPictAspectRatioY: 10
dwControlFlags: 0x00000000
dwReserved2: 0x00000000

BITMAPINFOHEADER:
biSize: 40
biWidth: 528
biHeight: 480
biPlanes: 3
biBitCount: 12
biCompression: YV12
biSizeImage: 380160
biXPelsPerMeter: 0
biYPelsPerMeter: 0
biClrUsed: 0
biClrImportant: 0

pbFormat:
0000: 00 00 00 00 00 00 00 00 10 02 00 00 e0 01 00 00 ............à...
0010: 00 00 00 00 00 00 00 00 10 02 00 00 e0 01 00 00 ............à...
0020: 00 00 00 00 00 00 00 00 62 17 05 00 00 00 00 00 ........b.......
0030: 00 00 00 00 00 00 00 00 0d 00 00 00 0a 00 00 00 ................
0040: 00 00 00 00 00 00 00 00 28 00 00 00 10 02 00 00 ........(.......
0050: e0 01 00 00 03 00 0c 00 59 56 31 32 00 cd 05 00 à.......YV12.Í..
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................


HaaliFilter : Haali Video Renderer - CLSID : {760A8F35-97E7-479D-AAF5-DA9EFF95D751}

- Connected to:

CLSID: {04FE9017-F873-410E-871E-AB91661A4EF7}
Filter: ffdshow Video Decoder
Pin: Out

- Connection media type:

Video: YUY2 576x480 (13:10) 29.97fps

AM_MEDIA_TYPE:
majortype: MEDIATYPE_Video {73646976-0000-0010-8000-00AA00389B71}
subtype: MEDIASUBTYPE_YUY2 {32595559-0000-0010-8000-00AA00389B71}
formattype: FORMAT_VideoInfo2 {F72A76A0-EB0A-11D0-ACE4-0000C0CC16BA}
bFixedSizeSamples: 1
bTemporalCompression: 0
lSampleSize: 552960
cbFormat: 112

VIDEOINFOHEADER:
rcSource: (0,0)-(0,0)
rcTarget: (0,0)-(528,480)
dwBitRate: 0
dwBitErrorRate: 0
AvgTimePerFrame: 333666

VIDEOINFOHEADER2:
dwInterlaceFlags: 0x00000000
dwCopyProtectFlags: 0x00000000
dwPictAspectRatioX: 13
dwPictAspectRatioY: 10
dwControlFlags: 0x00000000
dwReserved2: 0x00000000

BITMAPINFOHEADER:
biSize: 40
biWidth: 576
biHeight: -480
biPlanes: 1
biBitCount: 16
biCompression: YUY2
biSizeImage: 552960
biXPelsPerMeter: 0
biYPelsPerMeter: 0
biClrUsed: 0
biClrImportant: 0

pbFormat:
0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0010: 00 00 00 00 00 00 00 00 10 02 00 00 e0 01 00 00 ............à...
0020: 00 00 00 00 00 00 00 00 62 17 05 00 00 00 00 00 ........b.......
0030: 00 00 00 00 00 00 00 00 0d 00 00 00 0a 00 00 00 ................
0040: 00 00 00 00 00 00 00 00 28 00 00 00 40 02 00 00 ........(...@...
0050: 20 fe ff ff 01 00 10 00 59 55 59 32 00 70 08 00 þÿÿ....YUY2.p..
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................


MadVRFilter : madVR - CLSID : {E1A8B82A-32CE-4B0D-BE0D-AA68C772E423}

- Connected to:

CLSID: {04FE9017-F873-410E-871E-AB91661A4EF7}
Filter: ffdshow Video Decoder
Pin: Out

- Connection media type:

Video: YV12 528x480 29.97fps

AM_MEDIA_TYPE:
majortype: MEDIATYPE_Video {73646976-0000-0010-8000-00AA00389B71}
subtype: MEDIASUBTYPE_YV12 {32315659-0000-0010-8000-00AA00389B71}
formattype: FORMAT_VideoInfo2 {F72A76A0-EB0A-11D0-ACE4-0000C0CC16BA}
bFixedSizeSamples: 1
bTemporalCompression: 0
lSampleSize: 380160
cbFormat: 112

VIDEOINFOHEADER:
rcSource: (0,0)-(528,480)
rcTarget: (0,0)-(528,480)
dwBitRate: 0
dwBitErrorRate: 0
AvgTimePerFrame: 333666

VIDEOINFOHEADER2:
dwInterlaceFlags: 0x00000000
dwCopyProtectFlags: 0x00000000
dwPictAspectRatioX: 11
dwPictAspectRatioY: 10
dwControlFlags: 0x00000000
dwReserved2: 0x00000000

BITMAPINFOHEADER:
biSize: 40
biWidth: 528
biHeight: 480
biPlanes: 1
biBitCount: 12
biCompression: YV12
biSizeImage: 380160
biXPelsPerMeter: 0
biYPelsPerMeter: 0
biClrUsed: 0
biClrImportant: 0

pbFormat:
0000: 00 00 00 00 00 00 00 00 10 02 00 00 e0 01 00 00 ............à...
0010: 00 00 00 00 00 00 00 00 10 02 00 00 e0 01 00 00 ............à...
0020: 00 00 00 00 00 00 00 00 62 17 05 00 00 00 00 00 ........b.......
0030: 00 00 00 00 00 00 00 00 0b 00 00 00 0a 00 00 00 ................
0040: 00 00 00 00 00 00 00 00 28 00 00 00 10 02 00 00 ........(.......
0050: e0 01 00 00 01 00 0c 00 59 56 31 32 00 cd 05 00 à.......YV12.Í..
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................



Sample2.avi

EVR & EVR-CustomFilter : Enhanced Video Renderer - CLSID : {FA10746C-9B63-4B6C-BC49-FC300EA5F256}

- Connected to:

CLSID: {04FE9017-F873-410E-871E-AB91661A4EF7}
Filter: ffdshow Video Decoder
Pin: Out

- Connection media type:

Video: YV12 720x576 (16:9) 25.00fps

AM_MEDIA_TYPE:
majortype: MEDIATYPE_Video {73646976-0000-0010-8000-00AA00389B71}
subtype: MEDIASUBTYPE_YV12 {32315659-0000-0010-8000-00AA00389B71}
formattype: FORMAT_VideoInfo2 {F72A76A0-EB0A-11D0-ACE4-0000C0CC16BA}
bFixedSizeSamples: 1
bTemporalCompression: 0
lSampleSize: 622080
cbFormat: 112

VIDEOINFOHEADER:
rcSource: (0,0)-(720,576)
rcTarget: (0,0)-(720,576)
dwBitRate: 0
dwBitErrorRate: 0
AvgTimePerFrame: 400000

VIDEOINFOHEADER2:
dwInterlaceFlags: 0x00000000
dwCopyProtectFlags: 0x00000000
dwPictAspectRatioX: 16
dwPictAspectRatioY: 9
dwControlFlags: 0x00000000
dwReserved2: 0x00000000

BITMAPINFOHEADER:
biSize: 40
biWidth: 720
biHeight: 576
biPlanes: 3
biBitCount: 12
biCompression: YV12
biSizeImage: 622080
biXPelsPerMeter: 0
biYPelsPerMeter: 0
biClrUsed: 0
biClrImportant: 0

pbFormat:
0000: 00 00 00 00 00 00 00 00 d0 02 00 00 40 02 00 00 ........Ð...@...
0010: 00 00 00 00 00 00 00 00 d0 02 00 00 40 02 00 00 ........Ð...@...
0020: 00 00 00 00 00 00 00 00 80 1a 06 00 00 00 00 00 ........€.......
0030: 00 00 00 00 00 00 00 00 10 00 00 00 09 00 00 00 ................
0040: 00 00 00 00 00 00 00 00 28 00 00 00 d0 02 00 00 ........(...Ð...
0050: 40 02 00 00 03 00 0c 00 59 56 31 32 00 7e 09 00 @.......YV12.~..
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

HaaliFilter : Haali Video Renderer - CLSID : {760A8F35-97E7-479D-AAF5-DA9EFF95D751}

- Connected to:

CLSID: {04FE9017-F873-410E-871E-AB91661A4EF7}
Filter: ffdshow Video Decoder
Pin: Out

- Connection media type:

Video: YUY2 768x576 (16:9) 25.00fps

AM_MEDIA_TYPE:
majortype: MEDIATYPE_Video {73646976-0000-0010-8000-00AA00389B71}
subtype: MEDIASUBTYPE_YUY2 {32595559-0000-0010-8000-00AA00389B71}
formattype: FORMAT_VideoInfo2 {F72A76A0-EB0A-11D0-ACE4-0000C0CC16BA}
bFixedSizeSamples: 1
bTemporalCompression: 0
lSampleSize: 884736
cbFormat: 112

VIDEOINFOHEADER:
rcSource: (0,0)-(0,0)
rcTarget: (0,0)-(720,576)
dwBitRate: 0
dwBitErrorRate: 0
AvgTimePerFrame: 400000

VIDEOINFOHEADER2:
dwInterlaceFlags: 0x00000000
dwCopyProtectFlags: 0x00000000
dwPictAspectRatioX: 16
dwPictAspectRatioY: 9
dwControlFlags: 0x00000000
dwReserved2: 0x00000000

BITMAPINFOHEADER:
biSize: 40
biWidth: 768
biHeight: -576
biPlanes: 1
biBitCount: 16
biCompression: YUY2
biSizeImage: 884736
biXPelsPerMeter: 0
biYPelsPerMeter: 0
biClrUsed: 0
biClrImportant: 0

pbFormat:
0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0010: 00 00 00 00 00 00 00 00 d0 02 00 00 40 02 00 00 ........Ð...@...
0020: 00 00 00 00 00 00 00 00 80 1a 06 00 00 00 00 00 ........€.......
0030: 00 00 00 00 00 00 00 00 10 00 00 00 09 00 00 00 ................
0040: 00 00 00 00 00 00 00 00 28 00 00 00 00 03 00 00 ........(.......
0050: c0 fd ff ff 01 00 10 00 59 55 59 32 00 80 0d 00 Àýÿÿ....YUY2.€..
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................


MadVRFilter : madVR - CLSID : {E1A8B82A-32CE-4B0D-BE0D-AA68C772E423}

- Connected to:

CLSID: {04FE9017-F873-410E-871E-AB91661A4EF7}
Filter: ffdshow Video Decoder
Pin: Out

- Connection media type:

Video: YV12 720x576 25.00fps

AM_MEDIA_TYPE:
majortype: MEDIATYPE_Video {73646976-0000-0010-8000-00AA00389B71}
subtype: MEDIASUBTYPE_YV12 {32315659-0000-0010-8000-00AA00389B71}
formattype: FORMAT_VideoInfo2 {F72A76A0-EB0A-11D0-ACE4-0000C0CC16BA}
bFixedSizeSamples: 1
bTemporalCompression: 0
lSampleSize: 622080
cbFormat: 112

VIDEOINFOHEADER:
rcSource: (0,0)-(720,576)
rcTarget: (0,0)-(720,576)
dwBitRate: 0
dwBitErrorRate: 0
AvgTimePerFrame: 400000

VIDEOINFOHEADER2:
dwInterlaceFlags: 0x00000000
dwCopyProtectFlags: 0x00000000
dwPictAspectRatioX: 5
dwPictAspectRatioY: 4
dwControlFlags: 0x00000000
dwReserved2: 0x00000000

BITMAPINFOHEADER:
biSize: 40
biWidth: 720
biHeight: 576
biPlanes: 1
biBitCount: 12
biCompression: YV12
biSizeImage: 622080
biXPelsPerMeter: 0
biYPelsPerMeter: 0
biClrUsed: 0
biClrImportant: 0

pbFormat:
0000: 00 00 00 00 00 00 00 00 d0 02 00 00 40 02 00 00 ........Ð...@...
0010: 00 00 00 00 00 00 00 00 d0 02 00 00 40 02 00 00 ........Ð...@...
0020: 00 00 00 00 00 00 00 00 80 1a 06 00 00 00 00 00 ........€.......
0030: 00 00 00 00 00 00 00 00 05 00 00 00 04 00 00 00 ................
0040: 00 00 00 00 00 00 00 00 28 00 00 00 d0 02 00 00 ........(...Ð...
0050: 40 02 00 00 01 00 0c 00 59 56 31 32 00 7e 09 00 @.......YV12.~..
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................





The major differences (there are others) that I see immediately are:

Sample.avi

EVR/EVR-Custom/HaaliVideo: YV12 528x480 (13:10) 29.97fps

VIDEOINFOHEADER2:
dwPictAspectRatioX: 13
dwPictAspectRatioY: 10
MadVRVideo: YV12 528x480 29.97fps

VIDEOINFOHEADER2:
dwPictAspectRatioX: 11
dwPictAspectRatioY: 10

Sample2.avi

EVR/EVR-Custom/HaaliVideo: YV12 720x576 (16:9) 25.00fps

VIDEOINFOHEADER2:
dwPictAspectRatioX: 16
dwPictAspectRatioY: 9
MadVRVideo: YV12 720x576 25.00fps

VIDEOINFOHEADER2:
dwPictAspectRatioX: 5
dwPictAspectRatioY: 4



There seems to be something amiss with "Video" & "VIDEOINFOHEADER2" in MadVR.
Perhaps MPC-HC relies on these values being correct for the "Keep Aspect Ratio" setting to work properly?
I'm not sure what else I can do to help you figure out what is causing the problem, if you have any further ideas - let me know.

[cyberlolo]

Do you mean the VC-1 decoder or splitter? Does either one not work?

I'm not sure, but I think it's the decoder, not the splitter. What I mean is the filter that can be enabled/disabled in the options->internal filters setting dialog of MPC-HC. In the right pane of that window, there's a option named "VC1 (FFmpeg)", but if I enable it, MPC-HC just doesn't play any VC1 video with madVR, although it do with any other renderer. If I disable it, then it works with madVR too. Why?