madVR - high quality video renderer (GPU assisted)

[Mark_A_W]

Hi all,
just recently I've started to test MadVR and the picture quality looks very nice. But I am having a couple of issues I'm hoping someone can assist with?

With MadVR I am getting dropped frames during what I assume to be high bit-rate scenes (Avatar and Saving Private Ryan Blu-ray M2TS files). I am not getting drop outs with other renderers.

My setup is:
Win7 32bit, MPC-HC (1752), FFDShow (Tryouts 3336)
Radeon HD5670, Intel Core2 Duo 2.67ghz (E8200), 3GB RAM

It seems like my gfx or CPU may not be up to it but others seem to be OK.

Also, I am getting a horizontal tear about 1/5th up from bottom, I saw this mentioned elsewhere but have been unable to find it again.

Glad to hear any explanations or recommendations.

What refresh rate are you using?

It needs to be a multiple of 23.976 (24.000 is ok if you use Reclock).

[Thunderbolt8]

madVR still has problems with 720p 50/60 Hz MPEG-2/H.264 stuff resulting in dropped frames with fullscreen.

[namaiki]

Thunderbolt8: Is this relating to the video's frame rate or the screen's refresh rate, or a combination?

[madshi]

madVR still has problems with 720p 50/60 Hz MPEG-2/H.264 stuff resulting in dropped frames with fullscreen.
50p/60p rendering is quite demanding. It needs 2x - 2.5x as much rendering power as movie rendering. Maybe your GPU is too slow?

[madshi]

The third is a problem with a Youtube 480p H264 FLV. CoreAVC as the decoder causes a crash.
http://web.tiscali.it/djsolidsnake86/video.mp4

if anyone want try madvr with this video, there is a very strange problem
Green bar at the top + chroma chifted: (500kB)
http://www.multiupload.com/AOR2BYG2O8
Seems to happen on all videos with height=360.

Green bar to the right: (5.5MB)
http://www.multiupload.com/89XRJLP0V6
This is supposed to be 852x480. madVR adds some green to reach 864, other renderers seem to just upscale it there. Don't know what the DAR really is, it's downloaded from Youtube.
madVR seems very finicky about how it is feed non-MOD16 width video. If the decoder pads the video to MOD16, it's happy, but if the decoder outputs non-MOD16 video directly and expects the video renderer to pad as necessary, it can sometimes cause madVR to crash.
The above problems all had the same cause and should all be fixed in the next madVR build.

I'm having problems with some wmv files. Found a small one that won't play:
http://www.multiupload.com/PFEET9HBGS
Using MPC-HC with internal decoder.
This doesn't play for me with *any* renderer. Not with MPC-HC internal decoder, nor with MS decoder.

madshi here there is the link for the mpeg file
http://web.tiscali.it/djsolidsnake86/1.mpg (look pixellated)
Seems to work just fine here. What problem do you have with this one exactly? Using which decoder?

@madshi: Woops I meant similar to cyberbeing >< about the animorphic source not being displayed right for XviD.

Here's a sample of madVR not displaying the video at the correct aspect ratio, resolution in the properties should read, 720 x 480 (AR 853:480), but only reads as 720 x 480.
VMR and EVR show it the same way as madVR does on my PC. Only Haali's Video Renderer shows it in the correct aspect ratio, and actually I think Haali does it wrong, as weird as it is. The problem is that the decoder first asks madVR "are you happy with aspect ratio 853:480?". madVR replies with "yes". But then the decoder connects with aspect ratio 3:2. madVR uses the aspect ratio of the connection, not the aspect ratio the decoder asked about some time before.

I've discovered that the black screen problem appears to be related to VSFilter,
yet madVR still seems to be at fault for not handling the aspect ratios correctly.

The widespread bug-fixed branch of VSFilter (2.39.5.x) from
http://sourceforge.net/projects/guliverkli2/files/ & the outdated official
branch (2.37) from http://sourceforge.net/projects/guliverkli/files/ cause the
black screen problem.

On the other hand it appears that the latest VSFilter from MPC-HC standalone
filters http://sourceforge.net/projects/mpc-hc/files/ does not.

The only difference appears to be a very slight difference in the anamorphic
aspect ratio of VSFilter's output pin.

For the 720x480 16:9 anamorphic sample I sent you, the working version of
VSFilter outputs 720x480 (input 71:40 | output 853:480 aspect ratio = 1.777:1),
and the broken version outputs 720x480 (input 71:40 | output 71:40 aspect
ratio = 1.775:1).

With the 704x480 16:9 anamorphic sample here, the working version of VSFilter
outputs 704x480 (input 4551:2560 | output 4549:2560 aspect ratio = 1.77695:1),
and the broken version output 704x480 (input 4551:2560 | output 4551:2560
aspect ratio = 1.77773:1).

Since madVR is the only render which has problems with the other version of
VSFilter, it appears that you have a bug in your aspect ratio code. Both
versions should have worked, but madVR is borking on small variations of what
is meant to be the exact same aspect ratio.
Your analyzation seems very reasonable. Unfortunately my logs tell me a different story. The pin information you're talking about here is not 100% reliable. There are various situations where "media types" are used. The decoder first asks the renderer if the renderer would be happy with this or that. The decoder replies yes or no. Once the decoder has found a media type the renderer is happy with, the decoder connects to the renderer. For this the decoder can use a different media type once again (and some decoders do). Furthermore, each video frame can come with its own new media type information again. So what does MPC-HC show in its dialogs? It seems to start with the "are you happy with this?" media type, and later replaces it with the connection's (or video frame's?) media type, but only after video playback properly started. Now the two media type information records you've compared are from different situations. One is from the "are you happy?" situation. The other one from after playback started.

I can reproduce the problem you described, but after studying my madVR's extensive logs, I can say that madVR behaves 100% identical with all VSFilter versions. Also VSFilter seems to behave 99.9% identical. All VSFilter versions ask "are you happy with 4551:2560?", but then connect with 4549:2560. There's one minor difference in the media type information between the 2 different VSFilter versions (rcSource/Target initialized or not), but it doesn't really bother madVR. From my logs I can see that madVR behaves the same way with all VSFilter versions. The logs are virtually identical, up to the point where the working VSFilter versions begins to send video frames. At this point the non-working VSFilter version simply doesn't start to send video frames, for unknown reasons. madVR sits idle and waits for VSFilter to finally deliver video frames, but nothing ever arrives. That's why there is a black screen and no video playback.

I appreciate that the problem only occurs with madVR, but I don't see what I could do differently. As I said, madVR behaves the same way with all VSFilter versions, and as far as I can see, madVR behaves correctly. It's just that some VSFilter versions never start delivering frames for reasons unknown to me. I don't know why it works with other renderers and not with madVR, but I don't see anything wrong in madVR's behaviour...

[memmerson]

What settings are you using in MadVR? Also, what resolution are you playing at, and how much memory does your video card have? Is Aero enabled or disabled? Check the frame rate of the video. If it is VFR, how high does the frame rate go?

PC Levels
No LUT
Luma Upscaling SoftCubic50
Luma Downscaling Lanczos4
Chroma Resampling SoftCubic100
Trade Quality for Performance: all unchecked

Basically the options are as default. I have also tried checking all the "Trade Quality" options but that seems to make no difference.

I am playing at 1920x1080 (progressive) @ 23.976hz (23hz in ATI CCC)
512MB RAM on GFX card.
Aero disabled
Frame rate is the same @ 23.976, used the OSD to confirm.
The files I am testing with are not VFR.

What refresh rate are you using?

It needs to be a multiple of 23.976 (24.000 is ok if you use Reclock).

Same, 23.976. I have tried with an without reclock, seems to make no difference.

I am really stumped...

[madshi]

With MadVR I am getting dropped frames during what I assume to be high bit-rate scenes (Avatar and Saving Private Ryan Blu-ray M2TS files). I am not getting drop outs with other renderers.
Maybe you're using DXVA decoding with other renderers? Check the OSD during those frame dropping scenes. How do the queues behave at that time?

Also, I am getting a horizontal tear about 1/5th up from bottom
Known problem with the current build.

[Thunderbolt8]

50p/60p rendering is quite demanding. It needs 2x - 2.5x as much rendering power as movie rendering. Maybe your GPU is too slow?
could be possible, got a radeon mobility 4850 (or a radeon 4770 on my pc). guess its not enought?

is it the same for 50i/60i ? does it depend on how much actual frames are i or p, because sometimes the stream is detected as i, but you dont need any deinterlacing.

[memmerson]

Maybe you're using DXVA decoding with other renderers? Check the OSD during those frame dropping scenes. How do the queues behave at that time?


Known problem with the current build.

Of course! Dammit! I am using the FFDShow DXVA Video decoder with hardware offload enabled... I really should have thought of that...

I will switch to the standard Video decoder and try again.

Thanks

[madshi]

could be possible, got a radeon mobility 4850 (or a radeon 4770 on my pc). guess its not enought?
I would say a desktop 4770 should be plenty fast enough. Don't know about the Mobility.

is it the same for 50i/60i ? does it depend on how much actual frames are i or p, because sometimes the stream is detected as i, but you dont need any deinterlacing.
They key question is how many (progressive) frames per second are delivered to madVR. With video content 50i/60i that's 50p/60p. With movie content it depends. Can be either 24p/25p or 50p/60p, depending on the encoding and deinterlacer etc...

[namaiki]

^640/128 shaders @ 750MHz

mobility 4850 = 800 stream/160 shaders @ 500Mhz


his 5670= 400 stream/80 shaders @775MHz


my 9600m GT = 160 stream/32 shaders D:

My thing can render with default MadVR settings in ~20ms for 1920x1080. 60fps is i think ~15ms, but the 5760 should be fine. memmerson, have you/are you using ffmpeg-mt? I think it should give you a better chance if the video is H.264/AVC.

[memmerson]

memmerson, have you/are you using ffmpeg-mt? I think it should give you a better chance if the video is H.264/AVC.

Thanks namaiki, I didn't realise ffmpeg-mt existed, I've switched the decoder over in ffdshow for h.264 and will give it a try.

Cheers

[yesgrey]

his 5670= 400 stream/80 shaders @775MHz
my 9600m GT = 160 stream/32 shaders D:
My thing can render with default MadVR settings in ~20ms for 1920x1080. 60fps is i think ~15ms, but the 5760 should be fine.
A Nvidia stream processor is ~3x more efficient than an ATI stream processor, so you cannot compare them directly by number of stream processors.
A 5670 has less shader power than your 9600m GT.

[yesgrey]

could be possible, got a radeon mobility 4850 (or a radeon 4770 on my pc). guess its not enought?

A very rough performance comparison:

4770: 640/128 shaders @ 750MHz
performance: 640*750 = 480 000

mobility 4850: 800 stream/160 shaders @ 500Mhz
performance: 800*500 = 400 000

5670= 400 stream/80 shaders @775MHz
performance: 400*775 = 310 000

So, you would be safer with the 4770. ;)

[madshi]

madVR 0.13 released

http://madshi.net/madVR.zip

* fixed: scanline reading problem with newer NVidia drivers
* fixed: sometimes high CPU consumption when paused
* fixed: one potential cause for motion judder
* fixed: GPU memory leak, when starting multiple videos in 1 player instance
* fixed: CPU memory leak, when starting multiple videos in 1 player instance
* fixed: crashes or artifacts with some movies with odd resolutions
* fixed: initialization error messages were sometimes not correctly shown
* improved (but not fully fixed) tearing problem with 24Hz playback
* changed timing to improve rendering performance
* changed texture allocation to improve rendering performance
* optimized logging performance
* madVR doesn't ship with cr3dlut, anymore
* added capability to automatically download and install yCMS
* playback start is now delayed until 3dlut is created and loaded
* playback is paused during 3dlut creation (if a new 3dlut needs to be created)
* OSD: added 5s max stats
* OSD: added "available texture memory"
* OSD: Ctrl+R resets "dropped frames" (only works when OSD is shown)
* OSD: queues changed from "current value" to "range during last second"
* in Vista and Windows 7 Direct3D9Ex is used now (no lost devices, anymore)
* changed luma upsampling default to Lanczos4
I'm officially tired of stupid windowed mode. Tearing, dropped frames, rendering fighting with presentation. Presentation blocking rendering. You name it. It's simply a stupid solution, technically.

Edit: Reported bugs not looked into yet:

(1) stuttering in Avatar when using 3DLUTs (#2435)
(2) DVD playback: Macrovision fail

[kostik]

Thaaanks!!!
Works like a charm just had it checked. Plays much smoother on my system than previous builds and the picture looks great. Waiting just for yesgrey3 to fix a little bug and everything is going to be great.

[fastplayer]

* fixed: sometimes high CPU consumption when paused
Thanks a bunch for that one!
It was really annoying :)

[leeperry]

I'm officially tired of stupid windowed mode. Tearing, dropped frames, rendering fighting with presentation. Presentation blocking rendering. You name it. It's simply a stupid solution, technically.
glad to read you saying this, as I came to the same conclusions...and thanks for the new version!

but the first time I tried to go windowed>FS in KMP, the computer froze for 30 secs and then I got this: http://thumbnails30.imagebam.com/8260/17ce9782594554.gif (http://www.imagebam.com/image/17ce9782594554)

and I've tried to go windowed<>FS again, it's crawling/freezing like hell to do so. 0.12 worked perfectly fine, I run a 8800GS on XP SP3 using the 195.62 drivers.

I've also tried to use the debug version, but where's the log supposed to be?

[noee]

Athlon II X4, HD2600XT, CCC10.3, Win7 x64 Ult, Aero ON, MPC-HC/FFDshow/Reclock (no vsynch), dual monitor, playback on secondary, LG HDTV 24/60 capable.

madVR settings to defaults, using 3Dlut for SD and HD playback.

All of my HD material is 60i ~19kbps, no issues
My SD material is all AVC in MKV, 23.976. Playback at 60Hz, no issues. When I set to 24Hz, playback gets jumpy and stutters and frames get dropped.

However, when I pause/play a few times, eventually it will "synch" up and playback properly for a minute or two, then back to stuttering and some dropped frames. Have tried other upscalers and without 3Dlut, same behavior.

Stats Shot Here (http://www.pix01.com/gallery/FCECA598-D338-4EEF-A549-9FE26CEDBEFE/madVR/6124162500.jpg)

* in Vista and Windows 7 Direct3D9Ex is used now (no lost devices, anymore)

This is working great, thanks.

I realize I'm on the "low-end" of the spectrum, but perhaps this can be helpful. Seems really close for this older card.

[madshi]

Thaaanks!!!
Works like a charm just had it checked. Plays much smoother on my system than previous builds and the picture looks great. Waiting just for yesgrey3 to fix a little bug and everything is going to be great.
Thanks a bunch for that one!
It was really annoying :)
Thanks for the feedback!

but the first time I tried to go windowed>FS in KMP, the computer froze for 30 secs and then I got this: http://thumbnails30.imagebam.com/8260/17ce9782594554.gif (http://www.imagebam.com/image/17ce9782594554)
Can you reproduce this? Or was it a one time problem? I can do windowed<->FS in MPC-HC in XPSP3 without any problems, using my Radeon 3850.

and I've tried to go windowed<>FS again, it's crawling/freezing like hell to do so. 0.12 worked perfectly fine
Is just the switch slow, or does video playback stutter all the time, after you go to FS?

BTW, is the judder problem still there? Please test that, it might be fixed in this version.

I've also tried to use the debug version, but where's the log supposed to be?
The log file is written to your desktop to a file named "madVR - log.txt".

Athlon II X4, HD2600XT, CCC10.3, Win7 x64 Ult, Aero ON, MPC-HC/FFDshow/Reclock (no vsynch), dual monitor, playback on secondary, LG HDTV 24/60 capable.

madVR settings to defaults, using 3Dlut for SD and HD playback.

All of my HD material is 60i ~19kbps, no issues
My SD material is all AVC in MKV, 23.976. Playback at 60Hz, no issues. When I set to 24Hz, playback gets jumpy and stutters and frames get dropped.
Huh, that's weird! Was it the same way with v0.12? Or did you have smooth playback with 24Hz when using v0.12?

However, when I pause/play a few times, eventually it will "synch" up and playback properly for a minute or two, then back to stuttering and some dropped frames. Have tried other upscalers and without 3Dlut, same behavior.
That sounds like your GPU is too slow. However your stat shots seems to say that your GPU is fast enough. Strange...

[namaiki]

For me, (9600m GT, Windows 7 64-bit, 1920x1080) if I have Aero enabled, 24fps on 60Hz will cycle through smooth, then stutter during playback (using Reclock), though 30fps on 60Hz is fine. I didn't notice such a thing on 0.12, but if I have Aero disabled, 0.13 is fine as well as far as I can tell so far.

[racerxnet]

Launch MPC-HC and I get a green screen with audio. Back to version .12 and all is well. Win XP SP3, E8200 CPU, ATI 3870. Deleted the file and tried to reload with the same problem. HMMM.

Thanks,

MAK

[madshi]

if I have Aero enabled, 24fps on 60Hz will cycle through smooth, then stutter during playback
That confuses me. "cycle through smooth" and "stutter" contradicat each other. Does it cycle through smooth or does it stutter?

Launch MPC-HC and I get a green screen with audio. Back to version .12 and all is well. Win XP SP3, E8200 CPU, ATI 3870. Deleted the file and tried to reload with the same problem. HMMM.
Does that happen with all kinds of video files, or just with some specific ones? I have XPSP3 and a ATI 3850, so my setup is very similar to yours, but still I don't have the problem you're seeing. So I'm wondering whether it may affect only some video files?

[leeperry]

Can you reproduce this? Or was it a one time problem? I can do windowed<->FS in MPC-HC in XPSP3 without any problems, using my Radeon 3850.

Is just the switch slow, or does video playback stutter all the time, after you go to FS?

BTW, is the judder problem still there? Please test that, it might be fixed in this version.


The log file is written to your desktop to a file named "madVR - log.txt".
ok I've put the logs here: http://www.mediafire.com/file/zkvmdzzxvlo/madVR_log.rar

I tried to go windowed<>FS several times in a row...each time it was crawling/freezing as explained.

I've had KMP freezing for 30 secs again, so I can reproduce it yes. And sometimes I get that mVR error msg on the top left of the screen when going FS>windowed but it only shows up for a half-second or so.

to be perfectly clear, when going windowed>FS, it will either stutter or freeze the computer for 30" or just make the picture crawl/stutter, and when going FS>windowed it will only do the latter and then play at the right speed.

I will try to test the judder problem, and report back :cool:

[namaiki]

That confuses me. "cycle through smooth" and "stutter" contradicat each other. Does it cycle through smooth or does it stutter?

Sorry, I meant it is smooth and then without me doing anything, it starts stuttering, then is smooth again and keeps on going like that.

edit: Oddly enough, the issue seems to have mostly disappeared by itself...

[madshi]

I tried to go windowed<>FS several times in a row...each time it was crawling/freezing as explained.

I've had KMP freezing for 30 secs again, so I can reproduce it yes. And sometimes I get that mVR error msg on the top left of the screen when going FS>windowed but it only shows up for a half-second or so.

to be perfectly clear, when going windowed>FS, it will either stutter or freeze the computer for 30" or just make the picture crawl/stutter
But after 30" is will play smoothly again?

[Razoola]

madshi, I can confirm madVR v013 indeed fixes the issues with some nvidia cards running newer drivers. madVR is now working for me fine, thanks for the new version.

[leeperry]

But after 30" is will play smoothly again?
nope, when it's been frozen for 30" and comes back, I get 1fps or so.

[noee]

Huh, that's weird! Was it the same way with v0.12? Or did you have smooth playback with 24Hz when using v0.12?

On .12, with Aero ON, smooth playback, but occasional tearing. With Aero OFF, lots of stuttering.

With .13, no tearing, but now the stuttering.

I just realized I have CnQ turned on. I will play around with the power settings and scaler options, see if that makes a difference.

[racerxnet]

Does that happen with all kinds of video files, or just with some specific ones? I have XPSP3 and a ATI 3850, so my setup is very similar to yours, but still I don't have the problem you're seeing. So I'm wondering whether it may affect only some video files?

I am launching Media Portal with MPC as the external player and launching the VOB file of the movie by clicking on the title. I have a 3800 series ATI card as well. Not sure what is wrong. MadVr registers fine.

MAK

[madshi]

I am launching Media Portal with MPC as the external player and launching the VOB file of the movie by clicking on the title.
Which decoder are you using? Can you try a different video as a test? E.g. one with h264?

[racerxnet]

Which decoder are you using? Can you try a different video as a test? E.g. one with h264?

I am using the Nvidia decoder at this time. Is there a link to a h.264 file as you requested. I have about 500+ standard DVD's ripped to the drive, so I don't fool around with other formats at this time. Maybe another decoder to try?

Thanks,

MAK

[Frank K Abbott]

I'm getting unstable playback and stuttering when playing with CoreAVC, using 3dlut and yCMS and the default upsampling and downsampling settings with a 720p or 1080p file. ATi Mobility Radeon 4570 1GB. C2D @ 2.66Ghz.

[leeperry]

so I've updated to the WHQL 197.77 drivers(XP SP3/384MB 96SP 8800GS), and I've tried to go windowed/fs a few times...after 2 or 3 times it froze the player completely(but didn't lock up the computer), you can see that the end of the log is desperately looking for VSYNC: http://www.mediafire.com/file/m2qymnmzjti/madVR_log1.rar
and I've got many files that give this, and that's it: http://thumbnails29.imagebam.com/8262/fed60382613685.gif (http://www.imagebam.com/image/fed60382613685)

the picture doesn't move and trying to seek freezes KMP..log file: http://www.mediafire.com/file/tzhoywn2jti/madVR_log2.rar
the same file works fine w/ 0.12, it's one of my test samples for judder: http://thumbnails28.imagebam.com/8262/07cba082613956.gif (http://www.imagebam.com/image/07cba082613956)

[pankov]

leeperry,
I suppose your sample is a nice pan around and I'd like to have it so I can test and compare results.
Can you upload it somewhere and share a link?

[namaiki]

Sorry, I meant it is smooth and then without me doing anything, it starts stuttering, then is smooth again and keeps on going like that.

edit: Oddly enough, the issue seems to have mostly disappeared by itself...

Sorry again, I do seem to be experiencing the above problem with ~24fps stuff on 60Hz monitor. As before, ~30fps stuff plays fine.

[Hypernova]

namaiki,

Did you try changing scaling method to something easier or check some option to compensate for performence? I don't have 30fps files to test because most of the video I watch is 24fps. I too get some stuttering with 0.13 for some files while 0.12 does not. With 0.12, I can set all to spline64 and it always smooth, but with 0.13 I have to either change chroma to softcubic100 or disable anti-tearing to get smooth playback for 1080p. I guess it's because the new codes put more strain on the GPU rather than a bug.

[namaiki]

I was using the same scalers in 0.12 as well, but yeah changing the scaler to bilinear will make it play smooth. But since 30fps plays fine, I don't think it's because it's slower.

[cyberbeing]

(1) stuttering in Avatar when using 3DLUTs (#2435)

When using Bilinear for at 1920x1080 without scaling, the max rendering time (5s) jumps from its nominal 20ms all the way up to 55ms during that scene. If I used Spline36 instead, the max (5s) peaks at 110ms when nominally it is only 24ms avg & 36ms max (5s). Since the Frame Interval is 41.71ms, that is why I was getting massive dropped frames.

So there you go, something is causing a huge 3DLUT rendering lag for certain content. Since both Avatar and Advent Children are 3DCG, and both had this issue in a single scene, I'm beginning to think 3DCG content has something to do with it.

_________

On another subject, what does Available Texture Memory represent? It always says something between 600-1000MB, yet my GFX card only has 512MB of frame-buffer. It doesn't appear to be available system memory either, since in that case the number would be too low. Does it represent 50% of available system memory or something?
________

Bug report

MPC-HC, 1920x1080 video, 1920x1080 display resolution. Massive lag and occasional crash when going from Fullscreen to Windowed.

Black screen VSfilter (guliverkli2) aspect ratio problem is still not fixed.

_________

The good news is that madVR 0.13 appears to be faster. I'll get back to you on whether the number of dropped frames has improved.

Max Stats (5s) Rendering time > Movie Frame Interval = A few dropped frames.
Average Rendering time appears to be completely irrelevant as far as dropped frames are concerned.

712x304 bug appears to be fixed.
Youtube H.264 FLV problem appears to be fixed.

[namaiki]

I was curious about 'Available Texture Memory' as well. My 9600m GT has 256MB memory and if I go over that (checking using GPU-z), it will start lagging immensely, but MadVR always seems to report the figure as 2014MB. I have 4GB RAM.

[madshi]

I am using the Nvidia decoder at this time. Is there a link to a h.264 file as you requested. I have about 500+ standard DVD's ripped to the drive, so I don't fool around with other formats at this time. Maybe another decoder to try?
Yeah, please try another decoder. There are lots of MPEG2 decoders to choose from. So it'd be very important for me to know whether the problem occurs with all decoders or just with one.

I'm getting unstable playback and stuttering when playing with CoreAVC, using 3dlut and yCMS and the default upsampling and downsampling settings with a 720p or 1080p file. ATi Mobility Radeon 4570 1GB. C2D @ 2.66Ghz.
Which OS are you using? Aero on/off? Did the previous madVR version run better for you?

so I've updated to the WHQL 197.77 drivers(XP SP3/384MB 96SP 8800GS), and I've tried to go windowed/fs a few times...after 2 or 3 times it froze the player completely(but didn't lock up the computer), you can see that the end of the log is desperately looking for VSYNC: http://www.mediafire.com/file/m2qymnmzjti/madVR_log1.rar
It seems that refresh rate detection fails to work properly on your PC with 0.13. This might be a consequence of the changes I implemented to make newer NVidia drivers work.

Does the display refresh rate indicator in the OSD show correct information? Does it behave differently to 0.12?

and I've got many files that give this, and that's it
I've tried CoreAVC, DivX, MPC-HC internal decoder and ffdshow. None of these decoders show that problem for me. Which decoder are you using? Can you please make sure that you have the latest version of that decoder installed?

what does Available Texture Memory represent?
See here:

http://msdn.microsoft.com/en-us/library/bb174378%28VS.85%29.aspx

I'd say it's probably the combined amount of GPU RAM + AGP/PCIe memory or something like that. It's definitely not system RAM.

Bug report

MPC-HC, 1920x1080 video, 1920x1080 display resolution. Massive lag and occasional crash when going from Fullscreen to Windowed.
Will look into this.

Black screen VSfilter (guliverkli2) aspect ratio problem is still not fixed.
I've written a looooong comment about that, just look a few posts before the 0.13 announcement!

Max Stats (5s) Rendering time > Movie Frame Interval = A few dropped frames.
Average Rendering time appears to be completely irrelevant as far as dropped frames are concerned.
I can't confirm that. I'm having smooth playback on my Geforce 9400 HTPC, although max rendering times are always above movie frame interval.

That said, in windowed mode rendering and presentation does fight with each other. So it's possible that if rendering blocks the GPU too long, madVR might not be able to present the next frame soon enough, which would result in a dropped frame. This problem will go away in fullscreen exclusive mode, and hopefully also in Aero when I implement a special rendering path for it.

[cyberbeing]

I've written a looooong comment about that, just look a few posts before the 0.13 announcement!
I see it now, very weird. I guess this won't be fixed unless someone familiar with the VSFilter code can give you some insight. Not that it is an extremely pressing issue since the MPC-HC VSFilter works.


I can't confirm that. I'm having smooth playback on my Geforce 9400 HTPC, although max rendering times are always above movie frame interval.

Hmm... So you get absolutely zero dropped frames even when max rendering times are above the movie frame interval?

Could the difference I'm seeing be related to me owning an older GPU? My 7800GTX 512MB was from before the era of unified shaders which began with the 8800GTX. Would that contribute to this problem?

http://msdn.microsoft.com/en-us/library/bb174378%28VS.85%29.aspx

I'd say it's probably the combined amount of GPU RAM + AGP/PCIe memory or something like that. It's definitely not system RAM.
This isn't accurate at all for determining available GPU Frame-buffer. Awhile back when beta-testing CS4 for Adobe, I asked about just this and they said there is no mechanism built-in Windows for determining available (free and used) video memory. You would really need code your own in a method similar to RivaTuner or GPU-Z if you want accurate numbers. I believe they query the low-level ATI and NVIDIA driver APIs or something.

[madshi]

Hmm... So you get absolutely zero dropped frames even when max rendering times are above the movie frame interval?
Yes. I do get dropped frames with Lanczos4 resampling, but I don't if I don't resample at all. And max rendering times are always higher for me than the movie frame interval.

Could the difference I'm seeing be related to me owning an older GPU? My 7800GTX 512MB was from before the era of unified shaders which began with the 8800GTX. Would that contribute to this problem?
My integrated GPU is even older/slower than yours, I think.

This isn't accurate at all for determining available GPU Frame-buffer.
That's why I didn't call it "available GPU memory". It is what it is. And it was useful for me in finding a GPU memory leak, which 0.12 was suffering from.

[torpedo]

madVR 0.13 gives a great improvment. Thx, madshi.
One question: It seems the current madVR does not support (If I was not wrong) interlaced video. Have you schduled for support of interlaced video?

Edit: Yes I'm wrong. madVR supports interlaced video. But the compatibilities currently are not goog enough. May the culprit is decoder or some other stuff.

[Mark_A_W]

No problems here, so far. Playback is smooth. Will test more.

Pause CPU issue is fixed.

Thanks for CTRL+R :)

[vucloutr]

great! i can finally use madVR with my cheap GeForce 8200 which has only 8 Shader Processors.

:thanks:

[mark0077]

New version working great for me, thanks Madshi. Keep up the good work.

[6233638]

0.13 is no longer smooth for me with Bicubic75 chroma on bluray video with a 9400M.

Madvr reports no dropped frames though max rendering time was around 48ms and frame time is 41ms.

Average rendering is 28ms, in 0.12 this was enough to be 100% smooth as long as the HUD was turned off.

[racerxnet]

Madshi,

I am now using the Arcsoft decoder and .013 works well. I was using the Nvidia Purevideo decoder prior and all worked fine. Evidently Purevideo and .013 don't get along. Is there a fix in the works for this?

MAK

[mark0077]

Madshi just one small issue. For example when playing 24fps blu-ray, and when I double click mpc-hc window to resize to fullscreen, or go back to windowed mode, instead of the small images being made fullscreen immediately, it seems to go through a two phase resize process where it looks like its scaled horizontally to fill the screen first, then like 0.2 of a second later, it fills the screen vertically.

Just a small niggle, but it looks kind of strange when the image is the wrong aspect ratio for that split second :P