madVR - high quality video renderer (GPU assisted)

[moophone]

*LOVE* the auto-resolution switcher. Would it be possible to add in a tiny bit of intelligence to the auto-switcher to switch to refresh rates that make sense for us projector owners? e.g. I want to keep my resolution at 1080 because without lens memory switching to 720 doesn't make sense. So if a 720p50 source is detected and 1080p50 is in the list it will switch to 1080p50. It makes more sense to be at 1080p50 then staying at 1080p23 when watching 720p50 source :)

Keep up the great work, madshi!!!!

[pankov]

So does it work, did you test it? Haven't got many "it works" or "it doesn't work" reports yet...

I've just done a quick test and I have a little problem.
I've configured madVR to use the following switches
1080p50, 1080p59, 1080p60
but madVR simply refuses to switch to 1080p59 even though the video I start is a 59.940 1080i recording and I do have 59Hz as a selection in Windows / NV Control Pannel / UltraMon.
It either switches to 1080p60 or to 1080p50 if I leave only 1080p50, 1080p59 in the settings.
here is a log showing the problem
http://www.mediafire.com/?u5a3maf9hk6oq52
it happens on both my monitors.
Other framerates (23.976 and 50) work fine. I'll continue testing and report after if I find more problems.
Otherwise madshi, :thanks: a lot

Not sure about that. There will come some more in the future. Any more opinions on that?
The perfect would be to remember it's previous state but I guess that's an overkill at the moment. For the moment I'd prefer the options tree to be expanded than to be contracted by default

[sneaker_ger]

Is it supposed to go back to the original res when the video stops?

No. Madshi has already commented on that above.

[SamuriHL]

No. Madshi has already commented on that above.

Ah, missed that one. :thanks:

[leeperry]

Maybe if you post a log I can see what's wrong.
Your wish is my command. (http://www.mediafire.com/?n31e2l5nnkwc4u3) In all 3 logs, the refresh rate switches froze PotP :o

[yesgrey]

Those of you with glitch problems please test this build and report back if there's any improvement.
For me what solved the presentation glitches were the new 270.61 drivers. Now I don't have any presentation glitches except a couple when starting the playback. All versions work fine.

[sneaker_ger]

For me they didn't, still had glitches with 270.61. Only the "glitch-hack" version fixed the problem.

[pankov]

madshi,
I've just stumbled on a problem with v0.57.
I know that you can't see a lot from the log file when there is crash (ZoomPlayer simply vanishes) but I just thought it's better to let you know that v0.57 crashes while v0.56 plays just fine the same file with the same config.
Here are the logs from the two different versions
http://www.mediafire.com/?3lk8awytknha1a7

[Hprd]

The automatic resolution changing (even in it's limited form) works pretty darned good. Although setting "48p" (1920x1200p48 to be exact) (for 23.976 fps 4:3 videos) in the filename doesn't work, as 1920x1200p48 was "valid". No biggie though.

Would be cool on a future version if there would be changes per aspect ratio, or invidiual customly set resolution changes (would change to a certain resolution per some specification, or combination of specifications is what i mean, similar to ffdshow's resizing) maybe. Also, maybe have an option to change to a customly defined resolution on close, as in some cases keeping the resolution is nice, other's slightly inconvienent. Now i'm sure you have ideas similar to this planned (and other ppl have mentioned similar things as well), but just thought i'd throw in my 2 cents ;)

Also, as for glitches and whatnot. I didn't really test anything, but feel any glitches i may see (with the refresh rate sycned the the fps of the video anyways, which are quite minimal then, if not eliminated on some videos) are due to my system in some way, and nothing with madvr, so I don't think that i can help test any of these issues.

[dansrfe]

One question and one comment:

1) What is the exact purpose of the automatic display changer? As per my understanding it changes the refresh rate of the display to match whatever settings the user has input? (e.g. Monitor has refresh rates of 24Hz & 60Hz, default is set to 60Hz. madVR is fed a 1080p24 video and madVR changes the default refresh rate to 24Hz for playback?)

2) I had some 720p files that would drop frames when resized to fullscreen and those don't anymore. I think it has to do with the frame rate detection change. Before they were detected as 25 fps now it shows as 29.976 which is the actual fps.

Awesome work madshi! :)

[mr.duck]

I'm currently using TriXX (http://www.techpowerup.com/forums/showthread.php?t=133783), which let's me keep the clocks from going over 200/300. Voltage control doesn't work for my card though, but maybe for yours?

What a great little program. Looks like settings work after Trixx has been closed (clocks vary between your Trixx settings and the card's defaults for idle). FYI you can get it lower than 200/300 by applying that setting and then restarting the program. After some research, some people get the voltage control working by going from v4.0 to 3.0.4 beta.

The voltage control didn't work at first but I found a way round it. Install ATI tray tools. Make a profile called "IDLE" and set clocks and voltage correctly for idle. 157/300 0.950v for me. Then when the computer starts you can load that profile with a shortcut by adding this after the atitray.exe in the target...

/LDOV "IDLE" /EXIT

Now when you run Trixx, the voltage control slider can be set :). At least that is exactly what it does on my machine.

[jdl]

If you create a debug log for me I can have a look at why it doesn't go to exclusive mode. Try to keep the log short, please, as in: Delete any old logs. Then start MPC-HC so that it doesn't go exclusive (although it should). Let it play for 5 seconds in windowed mode. Then exit MPC-HC. Then zip and upload the log somewhere.


Thanks....here is the log.

http://www.megaupload.com/?d=FMZIIKJP

[Mark_A_W]

Here's a special new test build which *may* help reducing presentation glitches with high refresh rates:

http://madshi.net/madVRglitchHack.rar

This test build contains a wild hack which only works properly if you set "after last render step" to "flush & wait". Without that you'll get nasty results.

Those of you with glitch problems please test this build and report back if there's any improvement.

This test build needs Vista or Windows 7. For XP this test build doesn't behave differently compared to v0.56 or v0.57.

Thanks!

I'll test tonight!! (I'm half a day out of sync with you guys..down here at the arse end of the world..)

I'm wondering right now whether those glitch problems mostly happen with NVidia cards.

Those of you with glitch problems, are you using NVidia or ATI?


Ati for me, but I've got the interlaced 96i res, so I'm odd (and don't expect effort expended just for me).



madshi, on the Dscaler IVTC issue, do you have it set to "change to 23.976fps" rather than "keep 29.97fps "? I forget the exact wording, but reclock reports the wrong rate if this setting is wrong.

Nevcairiel will the 23/29fps thing with HD-DVD sourced VC-1 issue with LAVsplitter cause an issue here?

[midiboy]

Hi Madshi,

as much as I like refresh rate changing and I am very thankful you implemented it ... can you please add two options to disable it

- in windowed mode
- in general

I just see potential problems for situations where you want to playback videos on monitors that do not support certain refreshrates or if you want to use other refresh rate changing methods (like Autofrequency etc).

Thanks a lot !
Alex

[nevcairiel]

Nevcairiel will the 23/29fps thing with HD-DVD sourced VC-1 issue with LAVsplitter cause an issue here?

Depends on the decoder entirely, but those situations will always be troublesome for refresh rate switchers.

@madshi:
With 0.56 i had 0 glitches on my NVIDIA, no matter what i played (24p @ 23.976Hz, 25p @ 50Hz, 30p/60i @ 59.940Hz). No dropped frames and no glitches.

After reading about the glitches in 0.57, i didn't try it yet, just wanted to watch some movie last night and not play around. :p

Also, how does the refresh rate switcher react to media type changes? Say i connect with 29.97fps, then my decoder notices, "oh hey this is interlaced" and modifys the media type to say 59.94fps. Does it change again?

Additionally, without testing it yet, people report it changes resolution as well? Can that be avoided? I want all my output at 1080p with different refresh rates, otherwise whats the point of madVRs scalers when it changes to another resolution and lets the TV scale? :)

[Mark_A_W]

I actually think we need to establish some requirements for a refresh rate changer.

Things I'd like:

- A table/list setup, where for various framerates you can select which resolution to use. ONLY resolutions in the table/list get used!!! This last bit is important to avoid sending the wrong res to a device and having it turn off (EDID should prevent this but...).
I don't like the XBMC setup where it picks whatever IT decides is the best match, there is no control. It does work fine on my Plasma (2nd HTPC), but it's asking for trouble if you ask me.

- Powerstrip support :) Calling the Windows GDI res (is that the name?) will get it wrong for Powerstrip users. Again, I might be the only one, so maybe this can be ignored (I'm happy with one res anyway).

[fairchild]

can you please add two options to disable it

- in windowed mode
- in general

You don't have to use it. If you leave the section blank, it doesn't do any refresh or resolution changing.

madshi, just watched an hour long 720p/23.976 x264 clip at my usual 1080p/60 resolution and had zero drops/delays/glitches. Using everything at defaults, aside from changing to my preferred scalers (bicubic75 for luma up/down) So everything is as smooth as usual on my setup. :thanks:

[Gleb Egorych]

Here's a special new test build which *may* help reducing presentation glitches with high refresh rates:

http://madshi.net/madVRglitchHack.rar

This test build contains a wild hack which only works properly if you set "after last render step" to "flush & wait". Without that you'll get nasty results.

Those of you with glitch problems please test this build and report back if there's any improvement.

This test build needs Vista or Windows 7. For XP this test build doesn't behave differently compared to v0.56 or v0.57.

Thanks!
This build fixed glitches for me too. 0.57hack and 0.56 are smooth with 8 pre-rendered frames. Although 0.57hack has glitches on 60fps videos with 4 and 6 pre-rendered frames (so does 0.56), number of those glitches is significatly low than with 0.56. Win7, 8800GT, FW 270.61 WHQL.

[madshi]

Yes (IIRC).
Ok, thanks.

I don't understand anything.

When I install 270.61 driver, presentation glitch appears with madvr 0.57 without the hack (with 196.21 I don't have glitches even with madvr 0.51 until 0.57). With hack, like you said, I don't have glitch but problem with sound.

I decide to make backup before installing 270.61 and I tested 196.21,266.58 and 270.61 drivers. Now with ou without hack, I don't have glitches and I don't have any problem with sound.

I don't know why the comportment of madvr or my computer is erratic tonight. It's not comprehensible :confused:

I will test tomorrow to see if there is still problem or not with vista.
Yeah, I've had somewhat similar experiences: Sometimes no glitches occur and sometimes they do, without any real explanation why.

Sorry, I should have been more precise. Auto-changer is working perfectly in my case.
Cool.

The perfect solution should be something like this:
if there is no new movie starting in the next 5-10 seconds - switch to original refresh rate ... but I guess this is more a function of the player not the renderer.
I'm not sure if I can implement something like that. Depends on whether the media player just closes the madVR instance or also unloads the madVR.ax from memory.

IMHO the best option would be to memorize the state when it was closed.
Yeah, that would be the nicest solution.

Would it be possible to add in a tiny bit of intelligence to the auto-switcher to switch to refresh rates that make sense for us projector owners? e.g. I want to keep my resolution at 1080 because without lens memory switching to 720 doesn't make sense. So if a 720p50 source is detected and 1080p50 is in the list it will switch to 1080p50. It makes more sense to be at 1080p50 then staying at 1080p23 when watching 720p50 source :)
Are you saying that madVR chooses 1080p23 for a 720p50 movie instead of 1080p50? If that happens, that's a bug. Can you create a log for me, please, which shows madVR choosing 1080p23 for a 720p50 movie? Also, what is the exact list of display modes you allowed madVR to switch to?

I've configured madVR to use the following switches
1080p50, 1080p59, 1080p60
but madVR simply refuses to switch to 1080p59 even though the video I start is a 59.940 1080i recording and I do have 59Hz as a selection in Windows / NV Control Pannel / UltraMon.
Yeah, that's a bug. The problem is that madVR's refresh rate logic tries to match the movie frame rate (which in your case is "29") to the refresh rate (which in your case is "59"). Since I'm not using the full numbers (29.970) but the short ones (29), madVR finds no match (2 * 29 = 58). I'll fix that in the next build.

Your wish is my command. (http://www.mediafire.com/?n31e2l5nnkwc4u3) In all 3 logs, the refresh rate switches froze PotP :o
Thanks, will look at this later...

I've just stumbled on a problem with v0.57. I know that you can't see a lot from the log file when there is crash (ZoomPlayer simply vanishes) but I just thought it's better to let you know that v0.57 crashes while v0.56 plays just fine the same file with the same config.
You'll have to recheck with the next build once it's out (may take a couple of days). I plan to revert back to the v0.56 presentation logic. Maybe that fixes the crash. If not, let me know.

The automatic resolution changing (even in it's limited form) works pretty darned good. Although setting "48p" (1920x1200p48 to be exact) (for 23.976 fps 4:3 videos) in the filename doesn't work, as 1920x1200p48 was "valid". No biggie though.
The filename tokens are supposed to tell madVR which framerate the movies have, not which refresh rate to change to. I've yet to see a movie with a true 48p framerate. So the proper solution is to write "24p" into the movie filename. madVR will then automatically choose a 48p display mode if there's only a 48p and no 24p mode.

Would be cool on a future version if there would be changes per aspect ratio, or invidiual customly set resolution changes (would change to a certain resolution per some specification, or combination of specifications is what i mean, similar to ffdshow's resizing) maybe. Also, maybe have an option to change to a customly defined resolution on close, as in some cases keeping the resolution is nice, other's slightly inconvienent. Now i'm sure you have ideas similar to this planned (and other ppl have mentioned similar things as well), but just thought i'd throw in my 2 cents ;)
I don't plan to offer individual custom framerate -> refresh rate configurations at this point in time. Maybe in some (far away) future version, but definitely not anytime soon.

1) What is the exact purpose of the automatic display changer? As per my understanding it changes the refresh rate of the display to match whatever settings the user has input? (e.g. Monitor has refresh rates of 24Hz & 60Hz, default is set to 60Hz. madVR is fed a 1080p24 video and madVR changes the default refresh rate to 24Hz for playback?)
Yes, exactly.

Thanks....here is the log.
Hmmmm... Sorry. Just noticed that the log only contains the information I need if you enable the OSD (Ctrl + J). Can you please create another log with active OSD? Thanks...

madshi, on the Dscaler IVTC issue, do you have it set to "change to 23.976fps" rather than "keep 29.97fps "? I forget the exact wording, but reclock reports the wrong rate if this setting is wrong.
Can you explain this a bit more detailed?

can you please add two options to disable it

- in windowed mode
- in general
Simply leave the edit box empty. That disables automatic display mode changing for that monitor.

I'm not sure if disabling refresh rate changing in windowed mode makes much sense. E.g. imagine you start a movie in windowed mode with the display set to 1080p60. The movie is 24p. So you'll get non-smooth playback. Now you switch to exclusive mode. madVR switches to 1080p24. Smooth playback. Now you right click on the video to do something with the context menu. madVR goes to windowed mode, and thus switches back to 60p. Then you close the context menu. madVR goes back to exclusive mode and switches back to 1080p24.

That's not really a good idea because changing display modes takes time, and some displays take several seconds to resync to a different mode.

how does the refresh rate switcher react to media type changes? Say i connect with 29.97fps, then my decoder notices, "oh hey this is interlaced" and modifys the media type to say 59.94fps. Does it change again?
Displays usually don't do 29Hz/30Hz. So the optimal mode for both 29.97fps and 59.94fps is 59.94Hz. Which means that there's no real difference, anyway. Same with 25fps vs. 50fps. Only few displays support 25Hz. So the usual mode will be 50Hz for both 25fps and 50fps. In other words: Single rate or double rate deinterlacing should usually make no difference to the automatic display mode changer.

That said, as I wrote in the release notes, the current version of the display mode changer is rather simple and stupid. It only changes display mode before the start of playback. It doesn't react to media type changes. And it also doesn't check timestamps. I just thought that a quickly written stupid display mode changer would still be way better than none at all.

Additionally, without testing it yet, people report it changes resolution as well? Can that be avoided?
Of course. You just tell madVR which exact display modes you want to use and madVR will always select one from that list. If all modes in your list have the same resolution madVR will never switch resolution. In other words: madVR is *capable* of changing resolution in addition to refresh rate, but it will do that only if you want it to!

I actually think we need to establish some requirements for a refresh rate changer.

Things I'd like:

- A table/list setup, where for various framerates you can select which resolution to use. ONLY resolutions in the table/list get used!!! This last bit is important to avoid sending the wrong res to a device and having it turn off (EDID should prevent this but...).
madVR strictly only uses display modes which you explicitly allowed it to switch to. So wrong res can never happen.

I don't like the XBMC setup where it picks whatever IT decides is the best match, there is no control.
And I don't like setups where there are a million options to let you fine tune every funny situation that will never occur in real life in a million of years. I understand that you want max control. But what I want is ease of use. So it is quite possible that I will at times sacrifise some control if that makes the user interface much simpler.

That said, I've not decided yet how the "final" display mode changer user interface will look like. I just wanted to release a simple first version to give 95% of the users something they can work with right now.

- Powerstrip support :)
Yeah, may come in a future version. A far away future version, probably.

[madshi]

This build fixed glitches for me too. 0.57hack and 0.56 are smooth with 8 pre-rendered frames. Although 0.57hack has glitches on 60fps videos with 4 and 6 pre-rendered frames (so does 0.56), number of those glitches is significatly low than with 0.56. Win7, 8800GT, FW 270.61 WHQL.
Thanks, that's useful feedback. Did you notice any ill effects of the "0.57hack" version? Or does it work just peachy?

[Hprd]

The filename tokens are supposed to tell madVR which framerate the movies have, not which refresh rate to change to. I've yet to see a movie with a true 48p framerate. So the proper solution is to write "24p" into the movie filename. madVR will then automatically choose a 48p display mode if there's only a 48p and no 24p mode.

Aah i see now. That works perfectly, :thanks: :)

[Mark_A_W]

Here's a special new test build which *may* help reducing presentation glitches with high refresh rates:

http://madshi.net/madVRglitchHack.rar

This test build contains a wild hack which only works properly if you set "after last render step" to "flush & wait". Without that you'll get nasty results.

Those of you with glitch problems please test this build and report back if there's any improvement.

This test build needs Vista or Windows 7. For XP this test build doesn't behave differently compared to v0.56 or v0.57.

Thanks!


So close...so very close to perfect with this build...

I have the following settings:

flush
flush and wait (sleep)
don't flush
don't flush

And 1 pre-presented frame.

I get mostly smooth playback with tiny little delays every now and again - I think they are repeated frames.

The presentation glitch counter is still going mental, jumping once every half second (30 or more each time. The other counters are solid. The little jerks/delays do NOT correspond with the increment in the presentation glitches.


If I increase the pre-presented frames, I gradually get worse and worse visible jerks/delays that DO start to correlate with the presentation glitches.

Windowed mode is still better, but this is by far the best results I've had in exclusive mode.

It's not 100% consistent, I have had a couple of instances where the pres glitches were not increasing, but playback still had little jerks every second or so.


The reclock tearing test is the only way to properly evaluate this - maybe watching credits would be ok, but not video. The tearing test is brutally revealing.


I take back my comment about the disable desktop composition option pushing my PC back to 60i - I think it's the actual act of going into exclusive that sometimes triggers it. Seems to happen more often the first time I play after a new build. It also roots Reclock, which then (incorrectly) reports 96.000hz instead of 95.906hz like madVR.

Cheers

Mark

[madshi]

So close...so very close to perfect with this build...

I have the following settings:

flush
flush and wait (sleep)
don't flush
don't flush

And 1 pre-presented frame.

I get mostly smooth playback with tiny little delays every now and again - I think they are repeated frames.

The presentation glitch counter is still going mental, jumping once every half second (30 or more each time. The other counters are solid. The little jerks/delays do NOT correspond with the increment in the presentation glitches.


If I increase the pre-presented frames, I gradually get worse and worse visible jerks/delays that DO start to correlate with the presentation glitches.

Windowed mode is still better, but this is by far the best results I've had in exclusive mode.

It's not 100% consistent, I have had a couple of instances where the pres glitches were not increasing, but playback still had little jerks every second or so.


The reclock tearing test is the only way to properly evaluate this - maybe watching credits would be ok, but not video. The tearing test is brutally revealing.


I take back my comment about the disable desktop composition option pushing my PC back to 60i - I think it's the actual act of going into exclusive that sometimes triggers it. Seems to happen more often the first time I play after a new build. It also roots Reclock, which then (incorrectly) reports 96.000hz instead of 95.906hz like madVR.
Interesting. JFMI: Is windowed mode perfect for you? Or is it not 100% perfect, either?

[Gleb Egorych]

Did you notice any ill effects of the "0.57hack" version? Or does it work just peachy?
Tested on 60p and 60i videos with ReClock, playback was very smooth with 8 pre-presented frames.

For 25 fps videos on 60Hz LCD I have 1-2 glitches per second and judder is subjectively bigger than with EVR. But as I understand your main goal is to reach smooth playback for frequencies multiple of video fps.

[fps]

Doesn't sound too good. Please try without any flushes. Does that work better?

I don't really get it. I inteded to try out different flush settings yesterday, but all of a sudden I didn't get nearly as many drops/glitches as the day before without changing anything.
First I tested with 0.56 and had 0 glitches in a 40min movie, afterwards I tested 0.57 and had 0 glitches/2 drops (they are expected, I just use reclock in bitsreaming mode) in a 90min movie (flush settings flush/flush & wait/don't flush/don't flush).
Changing all the flush settings to don't flush didn't do any harm either as far as I can tell after some short testing.

The real strange thing is that the seeking problems, where I could easily reproduce up to 5 glitches per seek, are gone now, too, no matter how high I set the pre rendered frames.

The problem with the half empty backbuffer and pre rendered frames queue, it only fills up to 6-7/16, is still existent however.
It only fills up to 14-16 if I change the display refresh rate to 60Hz (originally 23.976).
Edit: that's the way it should be, see nevcairiel's post below.

[Mark_A_W]

Interesting. JFMI: Is windowed mode perfect for you? Or is it not 100% perfect, either?

Windowed mode can be perfect.

But it's not ALWAYS perfect. Sometimes it just misbehaves - little jumps/jerks/delays. Tiny, but I notice them.

It's inconsistent with windowed mode. Usually, restarting playback (completely) results in a perfect result....it's a crapshoot.

Interestingly, I replicated the same flush settings as the exclusive ones I listed before (actually, that's how they were anyway), and with backbuffers set to one, I get very good windowed results.
I can't do anything else on the PC then, as that results in immediate dropped frames, but that's ok, I'm watching movies when I use madVR.

[nevcairiel]

The problem with the half empty backbuffer and pre rendered frames queue, it only fills up to 6-7/16, is still existent however.
It only fills up to 14-16 if I change the display refresh rate to 60Hz (originally 23.976).

Thats not a problem, thats by design.
madshi explained that earlier - if you run at your target fps, you will never see more then 8 frames in those queues, because the other queues are limited to that size. If you run at a high refresh rate, every frame gets presented multiple times (running 25p at 50Hz, exactly two times), so the present/backbuffer queues get filled with those "duplicate" frames, as madVR presents one new frame every screen refresh.

[fps]

Thanks for the clarification, missed that one :cool:.

[6233638]

Have not had a chance to do full testing yet (really needs to be done when I have the time to properly watch something rather than have it on in the background) but it looks like 25p at 50Hz MAY be smooth with the "glitch-hack" version and set to only present one frame.

Have not tried the regular 0.57 for comparison or watched closely to see if there are stutters that are not reported. It seemed like it might be OK now though.

UPDATE: Nope, having the old problem of the render queue and backbuffer gradually dropping to 0 when framerate/refresh are 1:1.

Haven't had a chance to do further testing with 25p at 50Hz or 30p at 60Hz. It seems like it may work when framerate/refresh are not 1:1 but not when they are.

[watchman]

Do you get glitches with v0.56/v0.57? In other words: Is the test build *better* than v0.5.. or is just exactly as good as v0.5..?

With 0.52 I had really choppy playback, but 0.56 and 0.57 are performing pretty good I must say and even if there are some glitches, I can't really see them and playback seems to be smooth.

But test build is performing even better I think. I can use just 6 pre-rendered frames instead of 12 to play some benchmark 1080p videos without dropped frames. And I found it a little bit smoother, but it can also be a placebo since there is always zero on glitch counter :)

[madshi]

For 25 fps videos on 60Hz LCD I have 1-2 glitches per second and judder is subjectively bigger than with EVR. But as I understand your main goal is to reach smooth playback for frequencies multiple of video fps.
Well, I do want to achieve the best possible results with odd ratios, too. Does the old exclusive mode work better for 25fps on 60Hz for you?

I don't really get it. I inteded to try out different flush settings yesterday, but all of a sudden I didn't get nearly as many drops/glitches as the day before without changing anything.
Yeah, tell me about it.

Windowed mode can be perfect.

But it's not ALWAYS perfect. Sometimes it just misbehaves - little jumps/jerks/delays. Tiny, but I notice them.

It's inconsistent with windowed mode. Usually, restarting playback (completely) results in a perfect result....it's a crapshoot.
Ok, thanks.

Have not had a chance to do full testing yet (really needs to be done when I have the time to properly watch something rather than have it on in the background) but it looks like 25p at 50Hz MAY be smooth with the "glitch-hack" version and set to only present one frame.

Have not tried the regular 0.57 for comparison or watched closely to see if there are stutters that are not reported. It seemed like it might be OK now though.

UPDATE: Nope, having the old problem of the render queue and backbuffer gradually dropping to 0 when framerate/refresh are 1:1.

Haven't had a chance to do further testing with 25p at 50Hz or 30p at 60Hz. It seems like it may work when framerate/refresh are not 1:1 but not when they are.
Something is seriously weird with your setup. Don't know what/why... :(

With 0.52 I had really choppy playback, but 0.56 and 0.57 are performing pretty good I must say and even if there are some glitches, I can't really see them and playback seems to be smooth.

But test build is performing even better I think. I can use just 6 pre-rendered frames instead of 12 to play some benchmark 1080p videos without dropped frames. And I found it a little bit smoother, but it can also be a placebo since there is always zero on glitch counter :)
Ok, good to know, thanks.

[madshi]

madVR v0.58 released

http://madshi.net/madVR.zip

* fixed: 23p/59i movie did not activate 59p display mode
* removed v0.57 win7 specific presentation path again, didn't work so well
* added glitch hack as a new render option (Vista/Win7 only)
Would be great if everybody could test the "glitch hack" and give FEEDBACK on whether it's better/worse/equal for you. FWIW, when you activate the glitch hack, madVR always does a "flush & wait" after the last render step now, even if you tell it not to, because otherwise there would be nasty artifacts.

With the glitch hack deactivated, v0.58 should behave more or less similar to v0.56 (with added display mode changing functionality, of course).

EDIT: The glitch hack also affects windowed mode, btw. (but again only in Vista / Windows 7)

[Thunderbolt8]

has the order of the refresh rates entered in that line have actually anything to say or is it arbitrary?

[madshi]

If no good match is found at all, display modes listed first are more likely to be chosen. However, as soon as a mode at least somewhat matches the requirements, the order doesn't matter, anymore.

[moophone]

Are you saying that madVR chooses 1080p23 for a 720p50 movie instead of 1080p50? If that happens, that's a bug. Can you create a log for me, please, which shows madVR choosing 1080p23 for a 720p50 movie? Also, what is the exact list of display modes you allowed madVR to switch to?

Not a bug - I had 1080p25 as a resolution which is invalid. After removing it, a 720p50 source file correctly changes to 1080p50.

Maybe it should throw up a dialog saying it can't switch to that resolution or something? If nothing else, may save some support traffic from user error ;)

[mr.duck]

Would be great if everybody could test the "glitch hack" and give FEEDBACK on whether it's better/worse/equal for you.

Works well for me with or without the glitch hack. I can't notice any difference. Radeon 5750 and 11.2 drivers if that's any help.

[Gleb Egorych]

Well, I do want to achieve the best possible results with odd ratios, too. Does the old exclusive mode work better for 25fps on 60Hz for you?

Hadn't found how to enable old path in 0.58, tested it in 0.50. Yes, old exclusive mode is better than new for 25fps on 60Hz. Judder with old is regular while with new it's jerky.

[tschi]

Hi,
Thanks for the new version.
win7, ati 5770, catalyst 11.3,
15 min of bluray 23,976 @50hz with reclock (best sync, pcm waspi)
Don't flush for all, 10 present frames.
w/o glitches hack : 0 dropped/delayed frame, 0 presentation glitche
w glitches hack : 1 dropped frames, 0 delayed frames, 5 presentation glitches
w giltches hack + 1 prepresent one frame : 0 dropped/delayed frame
0.57 doesn't work well, a lot of dropped frames and presentations glitches

[fairchild]

v.058 On my setup with the coalgirls 1080p clip

w/o glitches hack : 0 dropped/delayed frame, 0 presentation glitches
w glitches hack : 0 dropped/delayed frame, 0 presentation glitches

So no noticeable difference with glitches hack on or off. Everything in madVR at defaults aside from luma up/down changed to Bicubic75. My setup is in my sig.

[Superb]

Just tried this renderer for the first time and it works really well. Thanks madshi.
One small question... resetting stats is CTRL+R, right? Quite annoying, since this is also MPC-HC's default for reset rate. Sometimes when I press the combination, it restarts the movie. :/
So for now I've changed MPC-HC's default "Reset Rate" combination to avoid the collision.
Is it possible that you'll change your reset stats to CTRL+ALT+R? Would make it like EVR-CP and EVR-Sync.

EDIT: btw, I currently use madVR out of "c:\madVR", cuz I've noticed it creates a settings.bin file.
Since I have UAC turned on, it won't have such access if I put it in Program Files. Will it still function properly from there?
Could you provide a nicer installer for next versions (possibly based upon Inno Setup)? The current one made Windows ask me "did this software install correctly?"...

EDIT2: I noticed MPC-HC has a "D3D Fullscreen" check available in the Output page of the settings. Is it better to use this together w/ madVR's exclusive mode? any advantages in doing that? (I saw it disables madVR's own seek bar)

[oddball]

Using glitch hack 0 dropped frames (But 15 at startup). 0 delayed frames. 2 presentation glitches using default settings. Length 23:34 720p 23.976fps

[sneaker_ger]

EDIT: btw, I currently use madVR out of "c:\madVR", cuz I've noticed it creates a settings.bin file.
Since I have UAC turned on, it won't have such access if I put it in Program Files. Will it still function properly from there?

Yes, it also uses the registry to save settings.

EDIT2: I noticed MPC-HC has a "D3D Fullscreen" check available in the Output page of the settings. Is it better to use this together w/ madVR's exclusive mode? any advantages in doing that? (I saw it disables madVR's own seek bar)

It doesn't change anything for madVR, except that it will start in fullscreen. The name "D3D fullscreen" is only there from the other renderers.

[Blight]

Bug report:
I'm getting 100% CPU usage and GUI freeze (audio continues) running v0.58, playing any type of content by going from a player window on monitor #1 to fullscreen on monitor #2.
This is with the default settings, Win7 32bit, NVIDIA 450GT.

Tested with Zoom Player, with the "Advanced Options / System - Fullscreen to Monitor" set to "2" and pressing Alt+Enter several times in a row.

Here's the log, I hope it captured ok as I had to kill the task:
http://t.inmatrix.com/madVRlog3.rar

[Superb]

It doesn't change anything for madVR, except that it will start in fullscreen. The name "D3D fullscreen" is only there from the other renderers.It makes the seek bar not show at all, so I wonder what else it affects.

[sneaker_ger]

It makes the seek bar not show at all, so I wonder what else it affects.

Let me rephrase my statement: it shouldn't affect the way madVr works, except that it will start in fullscreen. Maybe you have found a bug.

[mindbomb]

can someone clarify how the display modes thing is supposed to work?

Like, i put in 1080p23 and i have to do additional stuff in the driver settings as well?

[Hypernova]

I'm not sure if disabling refresh rate changing in windowed mode makes much sense. E.g. imagine you start a movie in windowed mode with the display set to 1080p60. The movie is 24p. So you'll get non-smooth playback. Now you switch to exclusive mode. madVR switches to 1080p24. Smooth playback. Now you right click on the video to do something with the context menu. madVR goes to windowed mode, and thus switches back to 60p. Then you close the context menu. madVR goes back to exclusive mode and switches back to 1080p24.

That's not really a good idea because changing display modes takes time, and some displays take several seconds to resync to a different mode.

How about disable it in non-fullscreen mode then?

[robpdotcom]

can someone clarify how the display modes thing is supposed to work?

Like, i put in 1080p23 and i have to do additional stuff in the driver settings as well?

One thing I noticed is that you must specify more than one mode, ie, 1080p23, 1080p59, ....

My display normally stays on 1080p59, so I thought I could put 1080p23 and madVR would switch to that when needed, and just not do anything with other rates (almost everything else I watch needs 1080p59). But until I added the second mode, it would not switch.

[jdl]

New log file (http://www.megaupload.com/?d=QE7O9V40)with CRTL-J active

[Hypernova]

One thing I noticed is that you must specify more than one mode, ie, 1080p23, 1080p59, ....

My display normally stays on 1080p59, so I thought I could put 1080p23 and madVR would switch to that when needed, and just not do anything with other rates (almost everything else I watch needs 1080p59). But until I added the second mode, it would not switch.

I think that's not true. Perhaps that was the bug in 0.57?