madVR - high quality video renderer (GPU assisted)

[FoLLgoTT]

Not interpolation, but it repeats frames as many times as necessary to sync 24p to 50/60Hz.

But where is the difference to other renderers? Every renderer has to do repeats if FPS does not equal refresh rate.
When I play a 23,976 file at 47,952Hz I get every picture twice. This can be easily recognized by the moving vsync bar of ReClock which looks as if there are two of them. If I play at 71,928Hz I see three bars and so on...
Only if I play at 23,976Hz (which is possible with my G90) the motion blur is totally gone! It is as smooth as frame interpolation and looks just unbelievable. But on the other hand you'll just get eye cancer by the flickering! :D

[Mark_A_W]

What smoothness do you mean exactly? Does Beliyall's version do a frame interpolation like DNM?

I ask, because with tweaking of the refresh rate I have 0 frame drops and only 1 AC3 packet drop/repeat (S/PDIF pass through) every about 10 hours. So for every movie it is perfect. What can be done better by an external scaler?


No, not interpolation. It's lower jitter I think. The frames arrive closer to when they are supposed to - that's my understanding. Nothing as coarse as a dropped frame.

I'm watching at 96hz interlaced BTW, on an XG-LC CRT projector.

With HR and Reclock I still get tiny little jumps every now and again - just little stutters when it should be smooth. Beliyaal's got the V-sync sorted out in MPC-HC...well, almost.


Edit: Thinking it through..a proper dropped frame on my system is missing for 4 screen refreshes (96hz remember). But if a frame misses the V-sync, it might get shown 5 times instead of 4, and therefore next frame only gets shown 3 times. It's not a whole frame dropped, but I think this may be the tiny, tiny little stutters I sometimes get. Usually a pause/play, or a seek fixes it with HR + Reclock. MPC-HC is just more robust...till it glitches. Just speculating here.

[Mark_A_W]

Not interpolation, but it repeats frames as many times as necessary to sync 24p to 50/60Hz.


Umm...50 or 60hz?

NO!! No way in hell!!!

23.976fps for a digital. 48.952/71.928/95.904hz for a CRT!!!

[honai]

NO!! No way in hell!!!

Then I must be dreaming. I'm playing 23.976 movies on a plasma TV @60Hz, playback is smooth as butter. I tried to set 24Hz in the display driver and my TV picks it up correctly, but the screen flicker is too annoying. 24p->60p works just fine with Beliyaal's modifications. No studder, no jumping, no drops.

[Mark_A_W]

Then I must be dreaming. I'm playing 23.976 movies on a plasma TV @60Hz, playback is smooth as butter. I tried to set 24Hz in the display driver and my TV picks it up correctly, but the screen flicker is too annoying. 24p->60p works just fine with Beliyaal's modifications. No studder, no jumping, no drops.


Unless your Plasma has interpolation, you are getting a 3:2 cadence, and therefore 3:2 judder.

[leeperry]

23.976fps for a digital. 48.952/71.928/95.904hz for a CRT!!!
does 72.928 even work?
29.97@89.91 is a no-no in MPC(Beliyaal's or not) :
http://www.image-load.eu/out.php/t157959_beli2.png (http://www.image-load.eu/out.php/i157959_beli2.png)
Then I must be dreaming. [...] 24p->60p works just fine with Beliyaal's modifications. No studder, no jumping, no drops.
drugs are bad hummm'kay :p

[Beliyaal]

The only thing my fixes do is make sure that the are as few stutters as possible. Normal renderers will stutter several times when the audio/video sync "passes" the VSync. Or it will stutter continuously if the refresh rate matches movie FPS exactly, and the audio/video sync is in line with the VSync.

[Beliyaal]

does 72.928 even work?
29.97@89.91 is a no-no in MPC(Beliyaal's or not) :
http://www.image-load.eu/out.php/t157959_beli2.png (http://www.image-load.eu/out.php/i157959_beli2.png)

drugs are bad hummm'kay :p

That is the fault of VMR9 audio/video sync. EVR Custom would work perfectly in that case.

[honai]

Unless your Plasma has interpolation, you are getting a 3:2 cadence, and therefore 3:2 judder.

What? If my PC sends 60 fps progressive to the tv (HDMI), and the tv runs at 60 fps (i.e. non-interlaced), how would that involve any pulldown? Remember, this has nothing to do with tv tuners or compressing NTSC fields over low-bandwidth transports. HDMI can transport 1080p60 just fine, no 3:2 cadences necessary.

[FoLLgoTT]

No, not interpolation. It's lower jitter I think. The frames arrive closer to when they are supposed to - that's my understanding. Nothing as coarse as a dropped frame.

Hmm, this sounds not logical to me. The output refresh rate is fix. The frames are displayed always at the same time, because of the vertical synchronisation. If not there is a drop or repeat. It can be only coarse, not fine.

I'm watching at 96hz interlaced BTW, on an XG-LC CRT projector.

It is a time ago that I tried interlaced on ATI cards. I always had little problems with judder and problems with resolution. The overlay did an additional vertical low pass filtering. With VMR9 it was fine, but there were stutter that I could not get rid off.
Why don't you use 47,952Hz? Are you that sensitive to flickering? :)

With HR and Reclock I still get tiny little jumps every now and again - just little stutters when it should be smooth.

Then something is wrong. When the vsync slider is set up correctly there is absolutely no judder with Reclock, no big and no small. I'm very sensitive to this and my PAL setup (VMR9 windowless under Vista) runs flawlessly. With NTSC DVD's ReClock had problems a long time, because the reported FPS sometimes changed between 29,97Hz and 23,976Hz. But with Blu-ray in H.264/VC-1 it also runs without judder now. There is no need to resync with pause/play anymore.

[leeperry]

That is the fault of VMR9 audio/video sync. EVR Custom would work perfectly in that case.
indeed, you're right :eek:

http://www.image-load.eu/out.php/t158564_evr.png (http://www.image-load.eu/out.php/i158564_evr.png)

that's on XP SP3 in accurate+alternative VSYNC mode w/ a GF9600 and EVR 6.0.6002.16497(is that the newest build BTW?) + Reclock@89.910Hz

any chance you could add a stat to know whether there's been any dropped frames please? and could you work your magic on HR/mVR too? coz HR doesn't care for the VSYNC position(which makes Reclock hiccup) and the mVR presenter in the regular MPC HC is also very unstable(like they all are in MPC HC when Reclock's being used :o).

PS: but then I have another problem w/ EVR, when I close MPC it remains as a process and I have to kill it...it also happens to many ppl on HCFR..

[FoLLgoTT]

The only thing my fixes do is make sure that the are as few stutters as possible. Normal renderers will stutter several times when the audio/video sync "passes" the VSync. Or it will stutter continuously if the refresh rate matches movie FPS exactly, and the audio/video sync is in line with the VSync.

Ok, if I got it right you implemented some kind of vsync correction like in ReClock. The only difference is that if picture and sound are out of sync there are still drops/repeats in picture until ReClock is used and drops/repeats audio instead. Right?

[Brazil2]

What's the diff between bicubic and softcubic?
And between such as 50, 60, 70...?
I would like too to have some tips and advices about the different luma and chroma resampling options.
As I'm not a specialist about these things, I'm not sure about which ones to use. I've read some are faster than some other ones, some may introduce ringing, some are supposed to be higher quality (but slower) than some other ones, etc.

So it would be nice if someone could summarize and clarify that for us :)


A choice of PC/TV levels is superb, however still second my request for future choice between 601/709 (i.e. it should be automatic based on resolution but with an option to change it from the mVR dialog).
I second that :)

[Mixer73]

What? If my PC sends 60 fps progressive to the tv (HDMI), and the tv runs at 60 fps (i.e. non-interlaced), how would that involve any pulldown? Remember, this has nothing to do with tv tuners or compressing NTSC fields over low-bandwidth transports. HDMI can transport 1080p60 just fine, no 3:2 cadences necessary.

Wrong - 24 frames can't divide into 60 frames so you have to do 3:2 cadence, so the frames look like this:

111223334455566

A lot of people watch Blu-ray this way and never know any better - but once you have seen 24p native, you cannot ever watch 24p/60p again. Its most obvious on panning shots.

[Beliyaal]

any chance you could add a stat to know whether there's been any dropped frames please? and could you work your magic on HR/mVR too? coz HR doesn't care for the VSYNC position(which makes Reclock hiccup) and the mVR presenter in the regular MPC HC is also very unstable(like they all are in MPC HC when Reclock's being used :o).
I have plans for an OSD that reports glitches of every kind. I have no control over HR/mVR. That is up to the authors of those renderers to fix.

Ok, if I got it right you implemented some kind of vsync correction like in ReClock. The only difference is that if picture and sound are out of sync there are still drops/repeats in picture until ReClock is used and drops/repeats audio instead. Right?
That is correct. However I don't think it works exactly like Reclock, because the algorithm works for all combinations of refresh/movie FPS. For example 23.976 at 60 Hz, 24 FPS at 59.94 Hz and 59.94 FPS at 24 Hz. That is the number of stutters are minimized, not eliminated.

[Egh]

hah! this "glitch" every hour
Actually, I even wonder how ppl can be watching movies in MPC...it constantly drops frames w/o Reclock by design(23.976@60Hz anyone? :D), so I guess I have my answer :o


You sure that Haali renderer drops frames? Even if it does it, it is still smooth enough for me. With anime content, there's a good bonus: most of the times two adjacent frames are same (for 23.976fps) so dropping either of them doesn't make any visible difference.

[nijiko]

Important Bug Report!!!

When playing RMVB files, each 40 mins continuous playback, movies will change colors, and player immediately crash.
mplayerc.exe craches because of madvr.ax.
Codec:RealSplitter + ffdshow video + coreaac
System:XP SP3 32bit, DX9 41

[lobothefoots]

Hi,
first I'd like to thanks madshi for his work for the audio/video community.

I use ZP6 and I set one of the controls like that :
double click = exit fullscreen

I noticed a bug with v0.4 and v0.6, I can only double click when there is black bars, I can't double click in the picture anymore. Can you fix that please?

I'd like to ask if you could write in the first post your recommanded setting for mid quality and high quality rendering because not everyone is a video guru and I, for exemple, don't understand most of the settings :p

[leeperry]

I have no control over HR/mVR. That is up to the authors of those renderers to fix.
well OK, but you know how to let EVR/VMR9 always catch the VSYNC fliptime and make sure that they never miss it...this code couldn't be used for HR/mVR? Reclock is clueless about the fliptime, the video renderer is clueless about Reclock...so the only solution is that the player starts the playback right on the money :confused:

[BatKnight]

:( That's bad. Anybody else with this problem?

What happens if you change your refresh rate to e.g. 60Hz, does detection still fail? Thanks!
Playing a mkv 72op 25fps with a refresh rate of 75Hz, madVR says strange refresh rates, as:
106.04204Hz (1s)

Hz change continously and 1s stays the same.

Vista 32 / MPC-HC 1059 / Radeon 4350 via HDMI to LCD at 1920x1080@60Hz / madVR 0.6

I have the same problem as Mike5. My refresh rate is 60Hz, but it is detected with various Hz that keep changing and the number inside the brackets is always 1s

Bat

[Mark_A_W]

Hmm, this sounds not logical to me. The output refresh rate is fix. The frames are displayed always at the same time, because of the vertical synchronisation. If not there is a drop or repeat. It can be only coarse, not fine.



It is a time ago that I tried interlaced on ATI cards. I always had little problems with judder and problems with resolution. The overlay did an additional vertical low pass filtering. With VMR9 it was fine, but there were stutter that I could not get rid off.
Why don't you use 47,952Hz? Are you that sensitive to flickering? :)



Then something is wrong. When the vsync slider is set up correctly there is absolutely no judder with Reclock, no big and no small. I'm very sensitive to this and my PAL setup (VMR9 windowless under Vista) runs flawlessly. With NTSC DVD's ReClock had problems a long time, because the reported FPS sometimes changed between 29,97Hz and 23,976Hz. But with Blu-ray in H.264/VC-1 it also runs without judder now. There is no need to resync with pause/play anymore.

Did you read my musing on what may be happening at a higher refresh rate like 96hz?

Anyhoo, Beliyaal responded with what his renderer does. When the V-sync crosses the doodar, you get a stutter.

Interlaced works fine on my system. No resolutions issues. MPC jitter is higher than double the progressive res with half the refresh rate, but still low.


And no, Reclock is good, a lot better than a vanilla system, but not perfect. You think it is, then you see something smoother and you realise your mistake :)

[Egh]

BTW, update on the previous multi-monitor rate detection:

funny enough i changed Hz on my CRT from 100Hz to 85Hz and it mVR now detects it properly, i.e. 4 digits precision and keeps for minutes. Whilst on the very same display with 100hz it never keeps the rate even for 10s. Odd ;)

[Mark_A_W]

I think most of us are having rate detection issues (?).

[FoLLgoTT]

Did you read my musing on what may be happening at a higher refresh rate like 96hz?

I'm sorry, I just read it too late.

OK, I understand what you tried to say. Even if the v-sync bar runs smoothly the cadence of movie pictures can be still erroneous. But it is just a hypothesis, right?

Let's think a bit further. If this cadence errors always occur on any system although ReClock's v-sync correction is turned on a 3:1:2:2:... cadence with 48/50Hz should be much more visible than your 5:3:4:4... cadence with 96Hz. The single judder is *stronger* than on a 3:2 pulldown. I could be wrong, but I cannot imagine that I (and other judder sensitive people) would not have noticed this.

I need a proof! :)
Sadly no renderer can write a log file with the outputted pictures (repeats/drops etc.). Or maybe we have to measure a special b/w flashing video with a photo diode and analyze the recorded stream...

Anyhoo, Beliyaal responded with what his renderer does. When the V-sync crosses the doodar, you get a stutter.

Do you mean ReClock v-sync display? If yes, I agree. But this should not happen.

And no, Reclock is good, a lot better than a vanilla system, but not perfect. You think it is, then you see something smoother and you realise your mistake :)

I saw 23,976Hz. THIS is smooth! :D
Have you tried this? This smoothnes really makes you cry. Absolutely no motion blur anymore.

[Mark_A_W]

I'm sorry, I just read it too late.

OK, I understand what you tried to say. Even if the v-sync bar runs smoothly the cadence of movie pictures can be still erroneous. But it is just a hypothesis, right?

Let's think a bit further. If this cadence errors always occur on any system although ReClock's v-sync correction is turned on a 3:1:2:2:... cadence with 48/50Hz should be much more visible than your 5:3:4:4... cadence with 96Hz. The single judder is *stronger* than on a 3:2 pulldown. I could be wrong, but I cannot imagine that I (and other judder sensitive people) would not have noticed this.

I need a proof! :)
Sadly no renderer can write a log file with the outputted pictures (repeats/drops etc.). Or maybe we have to measure a special b/w flashing video with a photo diode and analyze the recorded stream...



Do you mean ReClock v-sync display? If yes, I agree. But this should not happen.



I saw 23,976Hz. THIS is smooth! :D
Have you tried this? This smoothnes really makes you cry. Absolutely no motion blur anymore.


I have no proof, I'm just speculating. I do know that Reclock + HR is not perfect. Very good, but not perfect, at least on my system.

The ideal solution does not require Reclock at all (or only as a WASAPI/KS renderer).

And I cannot stand 48 or 50hz on a CRT projector, the flicker drives me bananas. 24hz would be torture. My projector won't sync to it anyway (30hz is lower limit).

[leeperry]

I do know that Reclock + HR is not perfect.
on Vista I guess? w/ Aero enabled, it constantly hiccuped because Aero was forcing the VSYNC every few secs...and w/ Aero disabled it was indeed pretty poor.

I honestly think that I'll still be running XP in the next coming years :D

hopefully madshi will also look into XP support, because the stupid OS is clueless about VSYNC positioning...which makes things a lot more complicated :o

Beliyaal has found a way to let VMR9/EVR never miss the VSYNC on XP, but can't adapt it for HR/mVR apparently :(

[THX-UltraII]

What about the settings of madvr. Which are best to choose/what do they do?:

use 3dlut?
luma/chroma resampling? (which setting is best to pick when you play mostly 1080p material with a fast pc?)

don t use dithering? check or uncheck?
use 10 bit luma/chroma? in which case do you check these?
disable anti-tearing fix? in which case do you check this?

[pirlouy]

I use ZP6 and I set one of the controls like that :
double click = exit fullscreen

I noticed a bug with v0.4 and v0.6, I can only double click when there is black bars, I can't double click in the picture anymore. Can you fix that please?

I also have hotkeys problems with MPC HC. Some don't work.

I'd like to ask if you could write in the first post your recommanded setting for mid quality and high quality rendering because not everyone is a video guru and I, for exemple, don't understand most of the settings :p
I too don't understand anything at vocabulary used in general in this forum. :-)
Default options are surely the best setting. Just one note, I think Madshi advised to try this "3dlut" which could bring some stuff in future, but it's not an obligation.

[honai]

Can someone confirm that madVR works w/ the onboard nVidia 9400 GPU?

[Mark_A_W]

on Vista I guess? w/ Aero enabled, it constantly hiccuped because Aero was forcing the VSYNC every few secs...and w/ Aero disabled it was indeed pretty poor.

I honestly think that I'll still be running XP in the next coming years :D

hopefully madshi will also look into XP support, because the stupid OS is clueless about VSYNC positioning...which makes things a lot more complicated :o

Beliyaal has found a way to let VMR9/EVR never miss the VSYNC on XP, but can't adapt it for HR/mVR apparently :(

No Aero.

Aero causes havoc with multi-monitors.

[leeperry]

No Aero.
I know, you told me ;)
but HR is smoother on XP than on Vista w/ Aero disabled.

[Quark.Fusion]

No Aero.

Aero causes havoc with multi-monitors.

What havoc? How I can see it?

[nijiko]

Bug Report:

Crash with playing .bik (Bink) files.

BTW, where is the author now? 3 days I haven't seen him...
I'm w8ing 4 the new 0.7 release...

[73ChargerFan]

Madshi does have a life outside of this forum.

[Thunderbolt8]

get used to it that updates, unless there are severe bugs, only come once a week - at the weekend (sunday).

[nijiko]

Madshi does have a life outside of this forum.

Aha, I'm just joking.
I know madshi he may be busy in real life.
But I just hope the new version that more better very much.

[Spec-Chum]

Where do I download this "real life"? Is it free?

[nijiko]

You can buy The Sims from EA.

[Leak]

Where do I download this "real life"? Is it free?
I think you access it by shutting down Second Life... :p

(Or maybe WoW...)

np: Pole - Alles Gute (Round Black Ghosts 2)

[Mark_A_W]

What havoc? How I can see it?


Jumps and stutters. Didn't seem to matter if the monitor was primary or secondary, if there were two active, running Aero ruined smooth playback.


However with one monitor, Aero seems to really help.

[nlnl]

madshi
Have you seen this http://www.fourcc.org/fccyvrgb.php#mikes_answer very informative page on RGB/YUV Pixel Conversion (including sample code showing how to perform YCrCb to RGB conversion with a Fragment Shader (Pixel Shader) in OpenGL)?

And this http://www.glennchan.info/articles/technical/chroma/chroma1.htm and this http://www.glennchan.info/articles/technical/chromata/chromata.html on advanced сhroma subsampling ?

Are you going to implement resizing using fashionable "linear light" ?
Thank you for the renderer! :thanks:

[TinTime]

Just an update on the issue I mentioned here (http://forum.doom9.org/showpost.php?p=1275796&postcount=439) and here (http://forum.doom9.org/showpost.php?p=1275936&postcount=467), as I've now tried it with MPC HC.

For an AVC stream the issue occurs with Zoom Player, CoreAVC and madVR v0.6.

It doesn't occur with:
Zoom Player, CoreAVC, madVR v0.4
Zoom Player, ffdshow, madVR v0.6
MPC HC, CoreAVC, madVR v0.6

Also, whilst seeking within the video using Zoom Player, CoreAVC and madVR v0.6 causes the issue on my 1440x900 monitor, it doesn't cause the problem with the same PC on my 1920x1080 HDTV. It still occurs when starting playback on the HDTV though :confused:. MPC HC and Zoom Player must be doing something differently.

[dann23]

hello.
i'm using madvr with windows media player 11. every time i close the player i'm getting memory could not be read errors.
there's also another problem. in fullscreen media player has a bar which appears every time I move the mouse. it's the bar with play/stop controls. very usefull but with madvr every time i move the mouse the movie changes aspect ration(when the bar appears and when disappears. this doesn't happen with video mixing render because the movie it's not resised. and i can;t use double click to enter or exit full screen mode with madvr but video mixing works.

[nijiko]

WMP11 can't load madVR at all.

[nlnl]

Nvidia 9400 +512m, Intel 8300, Vista 32, AERO, ffdshow mt, MPC-НС 1065
madVR 0.6 reports:
1) bilinear/bilinear
avrg gpu rendering time 11.87
2) catmul/catmul
avrg gpu rendering time 24.73
3) lancsoz4/lancsoz4
avrg gpu rendering time 58.6
For details see attachments.

"AERO on" improves smoothness!

[madshi]

Besides, 3dlut uses 96MB * 4 = 384MB HDD space. It's so crazy...
If you look at the cost of 1TB drives, 384MB cost you about 3 Cents. We're not living in year 1990, anymore!

Just curious, this will always be not supported?
DXVA will never be supported by madVR.

What's the diff between bicubic and softcubic?
And between such as 50, 60, 70...?
I've already explained that before in this thread.

I just gave madVR a first try. I noticed that madVR is rendering at 60 fps (measured with FRAPS), although the movie is only 24 fps.
This is the current madVR display logic. It will probably change, once I finally get to work on the whole "smooth playback" etc stuff...

Well, madVR 0.6 is definitely a step to the right direction. Start-up time is greatly improved!
You're the only one who has commented on 0.6 improvements - thanks!

A choice of PC/TV levels is superb, however still second my request for future choice between 601/709 (i.e. it should be automatic based on resolution but with an option to change it from the mVR dialog).
I'm only implementing the basic controls right now. Tweaks like that are low priority and may come later...

Next time could you put the lut name changes in the changelog?
Will do. I don't expect further changes anytime soon, though.

In madVR 0.6 the resampling isn't working properly when video resolution = display resolution. By that I mean it is for some reason resampling textures when no resize is needed. The resampling textures latency when changing between resize algorithms will change drastically even in this no resize situation.
I can't reproduce this.

If I choose Spline64 for luma and Bilinear for chroma, resample latency is ~9ms.
That was a bug. When bilinear or nearest neighbor was used for chroma resampling, luma was always resampled, too. That will be fixed in madVR 0.7.

Speaking of the refresh rate detection, it still isn't working perfectly over here with 0.6 even after your improvements. Very often at times between 1s and 12s it always seems to reset back to 1s, yet rarely it seems to go on forever without issue. Whether it works well or not seems completely random with no correlation with resolution or refresh rate. On the positive side, the values reported do seem accurate and don't fluctuate much (+/- 0.00010Hz) even when it resets itself back to 1s. Would you consider this acceptable enough or are you expecting it to never reset itself?
Probably good enough.

Just tried v0.6, and it's smooth. Very, very smooth. Wow.
madVR with its currently display logic can be very smooth if you have a good match between display refresh rate and source frame rate, and if your graphics card is plenty fast. In all other cases playback is not smooth at all.

I like the PC/TV levels buttons. Except they're backwards. Well...actually they are the right way round if you ask me, but everyone else does it backwards, so there is a defacto standard.
My controls are for *output* levels. CoreAVC has both input and output levels. Haali's Renderer only has controls for *input* levels (which I find backwards). That's why the controls sometimes behave unexpected. IMHO output level control is what we really need, because 99.99% of all content has video input levels, anyway. So controls for input levels is mostly useless, as far as I can see...

ATI or NVIDIA what is better?
I guess you can't go wrong either way, as long as the graphics card is new/fast enough. madVR uses Direct3D shader hardware, only, so the output quality should be identical on all graphics cards. You may want to decide on things like performance per dollar, performance per Watt, features (LPCM audio transport via HDMI) etc...

thxz. What about the settings of madvr. WHich are best to choose/what do they do?:

use 3dlut?
luma/chroma resampling? (which setting is best to pick when you play mostly 1080p material with a fast pc?)

don t use dithering? check or uncheck?
use 10 bit luma/chroma? in which case do you check these?
disable anti-tearing fix? in which case do you check this?
First of all, do not ask the same question twice in the same thread. Next time you do that I will ignore your question.

Which luma/chroma resampling filters you choose depends a bit on your personal taste, but also on the speed of your graphics card. I've posted a personal opinion about the filters in an older post here in this thread, you may want to search for that one. Or just try out the filters and choose which you like most. Many people like Lanczos, because it's the sharpest of the bunch, but it also has the most ringing.

All the other options like dithering, 10bit, anti-tearing fix etc obviously run under the category "trade quality for performance". So if you check any of these options, you do lost image quality, but gain performance. If your graphics card is fast enough, you will want to make sure that all these options are *un*checked. Use these options only, if your graphics card can't handle the load...

Not sure to have understood. I tried to set screen resolution to 1024x1024@60Hz with PowerStrip and, after a restart, Windows XP accepted it. But madVR keeps reporting "graphics card only supports power of 2 textures".
There's nothing you can do, except maybe trying the latest BIOS and drivers of your graphics card. Or hoping that madVR will someday support such limited hardware as yours.

Am I missing something? I am trying to get MadVR to work but no matter what I do, I get an “opening 3dlut file failed” message.
Have you deleted the cr3dlut subfolder or any files in it? Normally madVR creates the 3dlut files automatically. It could be an NTFS security rights problem. Anyway, just disable the "use 3dlut" option in the control panel, that should fix the problem, if you don't need the 3dlut special features, anyway. If you do need them, you may want to create 3dlut files manually.

What? If my PC sends 60 fps progressive to the tv (HDMI), and the tv runs at 60 fps (i.e. non-interlaced), how would that involve any pulldown? Remember, this has nothing to do with tv tuners or compressing NTSC fields over low-bandwidth transports. HDMI can transport 1080p60 just fine, no 3:2 cadences necessary.
If the original movie is 24fps and your display is 60Hz then you can't get perfectly smooth playback. The simple reason for that is that for 24fps sources each frame should be displayed for exactly 1000/24*1.001 milliseconds, while a 60Hz display displays each frame for exactly 1000/60*1.001 milliseconds. Now if your graphics card drives the display with 60Hz, your graphics card will have to repeat the 24fps movie frames multiple times. Ideally it will repeat each even frame 3 times and each odd frame 2 times (or vice versa). That will give you the typical 3:2 motion judder. Many people are used to this judder and don't notice it at all.

If you actually made your graphics card switch video frames at exactly 1000/24*1.001 milliseconds while still driving your display with 60Hz, you'd get major tearing. If you switch only during VSync blank, you have no other choice than to show each other frame 2 or 3 times.

When playing RMVB files, each 40 mins continuous playback, movies will change colors, and player immediately crash.
I've played a lot of movies already with madVR and never got a crash after 40 minutes playback time yet. Not sure what you mean with RMVB files, though? I've played MKV, TS and m2ts files with h264, MPEG2 and VC-1 codecs...

Crash with playing .bik (Bink) files.
Can I get a sample, please?

Have you seen this http://www.fourcc.org/fccyvrgb.php#mikes_answer very informative page on RGB/YUV Pixel Conversion (including sample code showing how to perform YCrCb to RGB conversion with a Fragment Shader (Pixel Shader) in OpenGL)?
There's nothing new to me on that page.

And this http://www.glennchan.info/articles/technical/chroma/chroma1.htm and this http://www.glennchan.info/articles/technical/chromata/chromata.html on advanced сhroma subsampling ?
I already know that article.

Are you going to implement resizing using fashionable "linear light" ?
That's already on the list of potential features.

Just an update on the issue I mentioned here (http://forum.doom9.org/showpost.php?p=1275796&postcount=439) and here (http://forum.doom9.org/showpost.php?p=1275936&postcount=467), as I've now tried it with MPC HC.

For an AVC stream the issue occurs with Zoom Player, CoreAVC and madVR v0.6.

It doesn't occur with:
Zoom Player, CoreAVC, madVR v0.4
Zoom Player, ffdshow, madVR v0.6
MPC HC, CoreAVC, madVR v0.6
Was able to reproduce the issue with Zoom Player and CoreAVC. Should be fixed in madVR 0.7.

Nvidia 9400 +512m, Intel 8300, Vista 32, AERO, ffdshow mt, MPC-НС 1065
madVR 0.6 reports:
1) bilinear/bilinear
avrg gpu rendering time 11.87
2) catmul/catmul
avrg gpu rendering time 24.73
3) lancsoz4/lancsoz4
avrg gpu rendering time 58.6
For details see attachments.

"AERO on" improves smoothness!
Interesting numbers. Which source format was that (resolution + framerate) and which display format (resolution + refresh rate)? For chroma resampling I recommend SoftCubic100, which is less demanding than Lanczos. Could you please try Lanczos3 for Luma and SoftCubic100 for chroma? Also I'd be interested in numbers if you play the video in its original resolution, so that luma doesn't have to be resampled at all.

Thanks!

[madshi]

madVR 0.7 released

http://madshi.net/madVR.zip

* fixed: video size/position was incorrect with Zoom Player & CoreAVC
* precompiled shaders are now loaded from "shaders.dat" (for testing)
* various shaders files are shipped created with different compiler versions
* OSD now shows 4 different display refresh rate estimates (for testing)
* fixed: with bilinear chroma resampling luma was always resampled, too
This is more of an interim release. Many of the changes (or "new" features) are mainly targeted at locating the cause of these 2 problems:

(1) display refresh rate calculation fails to work correctly
(2) GPU load is noticeable higher compared to madVR 0.4 on older hardware

If you have one of the above 2 problems, please help me by providing the following feedback:

(1) If display refresh rate calculation doesn't work properly for you (open OSD by pressing "Ctrl+J"), please post the first 4 lines of the OSD. There are now 3 display refresh rate estimates and one final refresh rate calculation. The first estimate is supposed to oscillate a lot and be about 3% too high. The 2nd estimate is also supposed to oscillate a lot, but should oscillate around the correct value. The 3rd estimate should be roughly accurate and not oscillate that much. The final number basically is the same as the 3rd estimate, but it accumulates calculations over time to improve accurateness.

(2) If you experienced a higher GPU load with madVR 0.6 compared to madVR 0.4 (if you did, you probably have older hardware), please try out the different Direct3D shader compiler versions. You can do so by replacing the "shaders.dat" file in the madVR root directly with one of the various "shadersXX.dat" files in the "madVR\shaders" subdirectory. The replacement file must be copied to the madVR root folder and renamed to "shaders.dat". The "shaders.dat" file contains all pixel shaders madVR uses. The "XX" number of the "shadersXX.dat" files in the "shaders" subdirectory specifies which compiler version was used for creating the "shaders.dat" file. madVR 0.4 had been using version "35" (which is identical to version "36"), while madVR 0.6 and 0.7 are using compiler version "41" by default. I *hope* that by replacing "shaders.dat" with an older version you can get back the lower GPU load of madVR 0.4. If you have newer hardware, there's probably not much of a difference between the various shader versions. On my ATI HD3850 36 and 41 produce roughly identical GPU loads. However, some other compiler versions produce slightly higher loads. So those of you with GPU load problems please try the various shader versions and let me know which works best for you. Thanks!

[Thunderbolt8]

hm stats from a movie (quite grainy movie)

display 59.XXXHz
movie 23.976 fps
1920, 1080
vsync interval 16.73ms
movie frame interval 41.71ms
avrg gpu rendering time 47.XXms
max gpu rendering time 47.XXms

doesnt run smoothly on that c2q with 7600GT (AGP), so how can I determine this from the numbers? is it like that that the avrg gpu rendering time value has to be lover than the movie fram interval value for fluent playback?

edit: when I enable all those "performance for quality settings" then the avrg gpu rendering time drops to ~30ms and it looks almost fluent (max gpu rendering time sometimes still higher than movie framerate interval; creating 10bit textures fails, uses 8bit instead)
with 0.7 for the same movie its

avrg gpu rendering time 41,XXms
max gpu rendering time mostly between 40ms and 50ms (sometimes it can also spike a bit higher though)

still not really fluent, but seems like I gained some speed ;)

[FoLLgoTT]

@madshi
Great work! :)


(1) If display refresh rate calculation doesn't work properly for you (open OSD by pressing "Ctrl+J"), please post the first 4 lines of the OSD.

When I run at 50Hz the first 4 lines are:

display estimate 1: 50Hz
display estimate 2: 50Hz
display estimate 3: usually 75Hz, rarely 50Hz
display : usually 75Hz, rarely 50Hz

[nuhi]

Hey madshi, great work.
Just one tiny remark, if you would please correct the label background colors, attached screenshot.
You probably keep your Windows at Classic colors so that is not seen but if you enable Visual styles you'll see it too.
Simple change label/checkbox FlatStyle property to System instead of Standard, then it will support Visual style coloring as well.

Thanks.