madVR - high quality video renderer (GPU assisted)

[Thunderbolt8]

I guess the refresh rate & resolution thing is not that helpful for me, when the other resolutions switching to result in slightly different ARs? (e.g. my native res is 1680*1050, AR =1:1.6, so when switching to 1280*720 res with AR=1:1.78, my picture would be slightly distorted, right?)

[kennae]

Firstly, thanks a million for the refresrate changer, this one I have been waiting for and it seems to work just fine!
When I open 25fps file does it automaticly give you refresrate of 50 as it should? If yes, there is no improvements I can think of. Spot on!

The new handling style on win7(64b) is not as smooth as the old one. 10 minutes of 720p video gave 2 presentation glitches and two dropped frames (didn't even notice them really). So it's not so bad.

Just downloaded the newly released nvidia drivers (260.61), installing and testing if there is any difference. Used to use 260.51 beta which were really great.

Again, Big Thanks for your hard work.

[ikarad]

You can try again with v0.57, maybe it improves things, although I doubt it. Please understand that the presentation glitches reported by madVR are glitches that happen somewhere in either Direct3D or in the GPU drivers. They're not happening inside of madVR. I'm trying my best to behave so that these glitches don't appear. But in the end they're not *my* fault, as far as I currently know.

FWIW, it seems that running high refresh rates (96Hz in your case, IIRC) is kinda difficult for the new exclusive mode rendering path. I don't really know why it seems to be so difficult, I didn't expect that, but as I said, the problems seem to happen outside of madVR. All madVR can do is to try keep all queues full. If the queues are full and still glitches occur, it's probably not my fault. If you set all flush settings to "don't flush" all queues are probably full in your case, aren't they? The flushes are a hack, they shouldn't even be necessary at all. But it seems that Direct3D and/or the GPU drivers need all the help they can get...
.
Thanks.



I am going to try with 0.57 to see if it works.

Many questions:
1)How can I see if queue are full?

2) What are the differences between exclusive fullscreen mode before 0.5 and after 0.5?. Can I use the fullscreen exclusive mode path before 0.5 if the new doesn't work at me?

3) Many people buy 120hz LCD (and soon more and more people will buy these 120 Hz LCD) then your madvr risk to make problem with lots of people.

4) Fo my case, The best is to check flush or don't flush for parameters in fullscreen mode?


5) If I use windowed mode instead of fullscreen mode what are the differences?


edit: With 0.57 and all options at flush and 6 frames, for this moment only heavy movie with high bitrates make problems. I am going to test more videos.

6) Do you think that I Can increase the number of frames even under windows xp?

[Razoola]

Same here 057 is giving many presentation glitches, win7 x64.

[pirlouy]

For noobs like me who don't look at statistics, what do you call a "glitch" ? Is it something which happens when FullScreen, during movie, or something which is here only when seeking or going Full Screen/Window ?

[madshi]

It worse for me on 0.57. It drop frames, and glitch. Windows 7 64bit, HD5870, i7 920.

The new handling style on win7(64b) is not as smooth as the old one. 10 minutes of 720p video gave 2 presentation glitches and two dropped frames (didn't even notice them really).
Same here 057 is giving many presentation glitches, win7 x64.
Thanks for the feedback, guys. Seems I'll have to revert to the v0.56 logic in the next build.

I guess the refresh rate & resolution thing is not that helpful for me, when the other resolutions switching to result in slightly different ARs? (e.g. my native res is 1680*1050, AR =1:1.6, so when switching to 1280*720 res with AR=1:1.78, my picture would be slightly distorted, right?)
If your display is scaling and distorting AR then it's not a good choice. Do you get bad AR when manually switching to other resolutions/refresh rates? If so, the automatic switching won't help.

When I open 25fps file does it automaticly give you refresrate of 50 as it should?
If you have told madVR that 50Hz is one of the modes you want it to use, then yes, of course. For a 25fps file madVR will look for a 25p display mode first. Next it will look for a 50p mode. Etc...

How can I see if queue are full?
Ctrl + J.

What are the differences between exclusive fullscreen mode before 0.5 and after 0.5?
There are many differences, like in which thread the presentation is done, when the presentation is done etc...

Can I use the fullscreen exclusive mode path before 0.5 if the new doesn't work at me?
Sure. Just activate the option "present only one frame at a time". That will give you the v0.49 mode.

Many people buy 120hz LCD (and soon more and more people will buy these 120 Hz LCD) then your madvr risk to make problem with lots of people.
No, not at all. 120Hz is what these LCD displays do *inside*. That is *not* the refresh rate your GPU sends data with. The default modes for those 120Hz LCD displays will be 24Hz or 60Hz. The display will internally convert that up to 120Hz.

Fo my case, The best is to check flush or don't flush for parameters in fullscreen mode?
I don't know, you'll have to try. It seems to be different for everyone.

If I use windowed mode instead of fullscreen mode what are the differences?
You'll simply have to try what works best for you.

Do you think that I Can increase the number of frames even under windows xp?
Not sure what you mean. The max number of pre-rendered frames for XP is 3. That's a hard limitation by Direct3D. Nothing I can do to increase that.

For noobs like me who don't look at statistics, what do you call a "glitch" ? Is it something which happens when FullScreen, during movie, or something which is here only when seeking or going Full Screen/Window ?
It can happen any time. Currently madVR is only able to detect it with the new exclusive mode rendering path. It's a problem inside of Direct3D or the GPU driver. It can result in a visible judder.

[Thunderbolt8]

If your display is scaling and distorting AR then it's not a good choice. Do you get bad AR when manually switching to other resolutions/refresh rates? If so, the automatic switching won't help.Im not sure whether my display does this. Does the actual video AR stay the same when switching from 1680x1050 to 1280x720 screen res and I dont get black bars for a video with exactly 1280x720 res with both display resolutions?

[pirlouy]

Ok. Bah, I'm not bothered that much by 3:2 pulldown, you know, so it should explain why I don't see these "glitches". :D

By the way, the new refresh auto-change is just a killer function. I did not expect this before 1 year. Just unbelievable. Now that I have everything, you can quit the project, I don't need you anymore. :D

[ikarad]

Thanks for the feedback, guys. Seems I'll have to revert to the v0.56 logic in the next build.


If your display is scaling and distorting AR then it's not a good choice. Do you get bad AR when manually switching to other resolutions/refresh rates? If so, the automatic switching won't help.


If you have told madVR that 50Hz is one of the modes you want it to use, then yes, of course. For a 25fps file madVR will look for a 25p display mode first. Next it will look for a 50p mode. Etc...


Ctrl + J.


There are many differences, like in which thread the presentation is done, when the presentation is done etc...


Sure. Just activate the option "present only one frame at a time". That will give you the v0.49 mode.


No, not at all. 120Hz is what these LCD displays do *inside*. That is *not* the refresh rate your GPU sends data with. The default modes for those 120Hz LCD displays will be 24Hz or 60Hz. The display will internally convert that up to 120Hz.


I don't know, you'll have to try. It seems to be different for everyone.


You'll simply have to try what works best for you.


Not sure what you mean. The max number of pre-rendered frames for XP is 3. That's a hard limitation by Direct3D. Nothing I can do to increase that.


.

I try with vista instead of windows xp and I discover that your new exclusvie fullscreen mode crash each time and indicate "updating vertex buffer failed"

screenshot
http://img4.hostingpics.net/thumbs/mini_886449Sanstitre.jpg (http://www.hostingpics.net/viewer.php?id=886449Sanstitre.jpg)

http://img4.hostingpics.net/pics/542095Sanstitre.jpg (http://www.hostingpics.net/viewer.php?id=542095Sanstitre.jpg)

It works if I use the old path (use present only one frame at a time)

[leeperry]

Didn't work out, unfortunately. However, ... (see below)
looks good! but I need 25/29fps 4:3 content to be played in a certain resolution(in 100Hz/89.91Hz), and 23.976/24/25 16/9 in another(all in 96Hz, except 29.97@89.91Hz)...so that won't really help. I'll wait patiently. :thanks:

[robpdotcom]

First, big thanks for the refresh rate changer. There's only one thing I'd like to see done differently:


* if DScaler IVTC Mod is in the graph, madVR considers 29.970 to be 23.976

In the U.S., all broadcasts are in MPEG-2, but of course, not all is film based telecined material. So, that would mean changing preferred decoders depending on the content (atm, I just leave DScaler set to "only when IVTC flags are found" and it handles most content just fine).

We could just rename recordings with the refresh rate token, but that's not very practical either.

Could you maybe add an option so DScaler being used doesn't override what the decoder reports? Does DScaler not report 23.976 when IVTC is applied anyway?

Of course, if you want to keep it the way it is, no biggie.

[kennae]

Firstly, thanks a million for the refresrate changer, this one I have been waiting for and it seems to work just fine!
When I open 25fps file does it automaticly give you refresrate of 50 as it should? If yes, there is no improvements I can think of. Spot on!

The new handling style on win7(64b) is not as smooth as the old one. 10 minutes of 720p video gave 2 presentation glitches and two dropped frames (didn't even notice them really). So it's not so bad.

Just downloaded the newly released nvidia drivers (260.61), installing and testing if there is any difference. Used to use 260.51 beta which were really great.

Again, Big Thanks for your hard work.

Okies, some more testing with the new drivers, and good knews.
All queries full and zero drops nor glitches!

Turns out nvidia drivers had mpc-hc put into "adaptive" powersaving mode and the clocks were fiddling around, now it's locked and it's 100% smooth again.

Great job.

[Gleb Egorych]

Thanks for the feedback, guys. Seems I'll have to revert to the v0.56 logic in the next build.

0.57 is worse than 0.56 for me too, glitches appear on same settings. 8800GT on Win7.

[madshi]

Im not sure whether my display does this. Does the actual video AR stay the same when switching from 1680x1050 to 1280x720 screen res and I dont get black bars for a video with exactly 1280x720 res with both display resolutions?
Do you have a CRT or a fixed resolution display? If you have a fixed resolution display then you should always send the native resolution to the display. If you have a CRT things are more complicated. Why don't you simply try it out and see if AR is correct or not?

By the way, the new refresh auto-change is just a killer function. I did not expect this before 1 year. Just unbelievable. Now that I have everything, you can quit the project, I don't need you anymore. :D
So does it work, did you test it? Haven't got many "it works" or "it doesn't work" reports yet...

I try with vista instead of windows xp and I discover that your new exclusvie fullscreen mode crash each time and indicate "updating vertex buffer failed"
That's weird because your picture is from windowed mode, while the new exclusive rendering path only applies to exclusive mode. When did those complaints occur exactly? Already in exclusive mode? Or when switching from exclusive mode to windowed mode? Do they occur every time (or often)? Or was it a one time only problem?

looks good! but I need 25/29fps 4:3 content to be played in a certain resolution(in 100Hz/89.91Hz), and 23.976/24/25 16/9 in another(all in 96Hz, except 29.97@89.91Hz)...so that won't really help. I'll wait patiently. :thanks:
Ah, you and your special wishes... :D You know, the proper solution to your problem would be if Reclock would hook into the DirectShow video filter chain, too, and modify the video timestamps and framerate information so that madVR actually knows what Reclock is doing. Right now Reclock lets madVR think the video framerate is unchanged, which isn't really true.

First, big thanks for the refresh rate changer. There's only one thing I'd like to see done differently:

In the U.S., all broadcasts are in MPEG-2, but of course, not all is film based telecined material. So, that would mean changing preferred decoders depending on the content (atm, I just leave DScaler set to "only when IVTC flags are found" and it handles most content just fine).

We could just rename recordings with the refresh rate token, but that's not very practical either.

Could you maybe add an option so DScaler being used doesn't override what the decoder reports? Does DScaler not report 23.976 when IVTC is applied anyway?
The problem is that (at least on my PC) DScaler does *not* report 23.976 for movies, even when IVTC is applied. As a result there's no way to madVR to react properly for both video and movie content. DScaler reports both as 29.970. So madVR will switch to the incorrect refresh rate either for movies or for video, if you use DScaler for both types of content.

If you have any ideas on how to solve this, just let me know.

Okies, some more testing with the new drivers, and good knews.
All queries full and zero drops nor glitches!
Hmmmm... Earlier reported problems with v0.57 which you didn't have with v0.56. This new report of yours, is that for v0.56 or v0.57 or for both? Based on the feedback so far I was planning to revert the next build back to how the v0.56 presentation logic. If you say now that v0.57 works just fine, too, I'm not sure anymore what to do with v0.58.

[ikarad]

That's weird because your picture is from windowed mode, while the new exclusive rendering path only applies to exclusive mode. When did those complaints occur exactly? Already in exclusive mode? Or when switching from exclusive mode to windowed mode? Do they occur every time (or often)? Or was it a one time only problem?


.

Those complaints occurs only in exclusive mode.
They occur every time.

I notice that this problem isn't here when I check the option: disable desktop composition (vista and newer).
If I check also the option "only when media player is in fullscreen mode" the problem occurs. If I don't check the option: disable desktop composition (vista and newer), the problem occurs each time in fullscreen mode.


Why? I don't understand.

[madshi]

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!

[madshi]

Those complaints occurs only in exclusive mode.
They occur every time.
Ok, thanks. When exactly do these complaints appear? Directly when you enter exclusive mode? Or after some playing time in exclusive mode? Or in the moment when you switch back to windowed mode?

[sneaker_ger]

I personally didn't note any change between 0.56 and .057, my ATI has no problems on both and the Nvidia has glitches on both. Haven't done any long term tests, only short tests - a few minutes each. Both my system run Win 7.

[ikarad]

Ok, thanks. When exactly do these complaints appear? Directly when you enter exclusive mode? Or after some playing time in exclusive mode? Or in the moment when you switch back to windowed mode?

Not directly (i nfact it depends). But after some seconds, image freeze (not sound). The problem occurs when I am in fullscreen mode.
If I am in windowed mode there is no problem.

I switch back to windowed mode because the inscription "updating vertex buffer failed" is displayed only when I switch to windowed mode.

[madshi]

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?

[madshi]

Not directly (i nfact it depends). But after some seconds, image freeze (not sound). The problem occurs when I am in fullscreen mode.
If I am in windowed mode there is no problem.

I switch back to windowed mode because the inscription "updating vertex buffer failed" is displayed only when I switch to windowed mode.
Hmmmm... That's weird. You're the first to report this problem. You tested with v0.57, I guess? Does the problem also occur with v0.56? Does the problem go away of you reduce the number of pre-presented frames to e.g. 3?

[sneaker_ger]

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!

Glitches seem to be gone - will let it run some time now.

[SamuriHL]

Help...I'm having one of those stupid days. How do I use the refresh changer?? I don't see an option for it?? What am I missing?

[sneaker_ger]

Help...I'm having one of those stupid days. How do I use the refresh changer?? I don't see an option for it?? What am I missing?

devices > <yourdisplay> > display modes

@madshi
Could you open all trees in the settings by default btw.? They are so few anyways

[robpdotcom]

The problem is that (at least on my PC) DScaler does *not* report 23.976 for movies, even when IVTC is applied. As a result there's no way to madVR to react properly for both video and movie content. DScaler reports both as 29.970. So madVR will switch to the incorrect refresh rate either for movies or for video, if you use DScaler for both types of content.

If you have any ideas on how to solve this, just let me know.

I guess I just assumed it reported 23.976, since I see it in MPC-HC's statistics - if statistics are clicked under View, it shows Frame rate: 23.976 (or 29.970 for video) when you move the mouse to the bottom of the screen. Of course, that statistic seems to take a few seconds to "settle in", almost like it's really giving you an average frame rate.

Unless madVR can get the frame rate from wherever MPC-HC gets it from, I certainly have no idea how to solve it.

[ikarad]

Hmmmm... That's weird. You're the first to report this problem. You tested with v0.57, I guess? Does the problem also occur with v0.56? Does the problem go away of you reduce the number of pre-presented frames to e.g. 3?

Yes It's weird. Yes the problem occured with 0.5,0.51,0.52,0.53,0.54,0.55,0.56 and 0.57 with new exclusive fullscreen mod (It is the first time tonight that I use madvr with vista (before I used madvr with xp)).

Even, Crtl+J function didn't work and now it works (bug has disappeared at the same moment)

It's very strange because this problem doesn't appeared anymore since 5 mn. I would like to reproduce this bug and now I can't.

Finally this bug disappeared for this moment. I don't understand why I had this bug and why he diseappeared. I hope that he won't appear anew.

Other thing, When I watch interlaced bluray movies at 30fps and that I use decomb IVTC filter in avisynth with ffdshow, CRTL+J displays 29.970 fps and not 23.976 fps, is-it normal?

[kennae]

Madshi, check my last post, I edited it.

Everything is working fine now. Nvidia drivers had reverted to default values so MPC-HC was in "adaptive" powersaving mode. Changed to use steady clocks and watching 45 mins worth of material with zero dropped frames nor glitches. All the queries are full too.

Loving it now. :thanks:

[SamuriHL]

devices > <yourdisplay> > display modes

@madshi
Could you open all trees in the settings by default btw.? They are so few anyways

:thanks: I feel like an idiot now. I'll test it after my meeting is done.

[Razoola]

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 seems to fix the glitches, well I still get a couple when video starts but after that I seem to get no more during the playback.

[sneaker_ger]

Glitches seem to be gone - will let it run some time now.

Didn't get any glitches now for the 30 minutes I ran it, so they seem to be gone for good.

If I set the scaling too high for my GPU and the render queue gets empty things will get really ugly though, looks like slow playback and back and forth skipping.

Something unrelated to the new hack version:
I sometimes get the OSD messages ("exclusive") to blink two or three times. For example if I start a video in MPC-HC and then quickly press the fullscreen key so that the video starts in fullscreen immediately.

/edit:
blinking log:
https://rapidshare.com/files/458057510/osd_blinking_0.57_vanilla.7z

[jmone]

madVR v0.57 released
(1) I've added a (simple, somewhat stupid) first version of an automatic display mode changer. It works a bit different to the MPC-HC changer: You simply tell madVR which display modes you want to use and madVR will automatically pick the best one for any content you throw at it. This is not the final version of the display mode changer. There will be an improved version some time later (not too soon). This first version is stupid in that way that it only switches display modes right before the start of movie playback and never double checks whether the real movie playback actually matches the chosen display mode or not.
I'm away from my HTPC on a setup with just a 50/59/60hz dual monitor setup (ATI). All is working fine with the frequence chaning but should 23.976 material really be displayed at 50hz (over I would have through 59...)?

[/QUOTE] The display mode changer applies to both windowed and exclusive mode. The new display mode will stay active even after the media player exits. That's not a bug, but by design.[/QUOTE]
I'm not too keen on this and would prefer the HTPC be returned to the state it was it (eg the default freq), else you will get stuck in 24hz which is not a good look for the desktop / player GUI and even worse if you then have an issue with playback not using madVR (eg DVD).


Thanks very much for adding this feature and I can not wait to play with it using JRiver MC's Audio resampler and see how it all goes in comparison to Reclock!

Nathan

[leeperry]

Ah, you and your special wishes... :D You know, the proper solution to your problem would be if Reclock would hook into the DirectShow video filter chain, too, and modify the video timestamps and framerate information so that madVR actually knows what Reclock is doing. Right now Reclock lets madVR think the video framerate is unchanged, which isn't really true.
Reclock is a dirty hack, but it works damn fine. I don't think any algorithm can do what I want, and I've got batch commands in the start menu...so this is really no issue for me. Besides, I'm the only one who knows whether 25fps is genuine PAL or sped up cinema NTSC.

Talking about special wishes? :D

I wish it were possible for mVR to:
-allow on-the-fly refresh rate switches, like in <0.50. ATM, the ppl using the VBS script in Reclock are SOL.
-detect upscaled SD from ffdshow..so no more wonky 601>709 8bit conversion in the Avisynth filter of ffdshow necessary.
-support LUT compression and allow switching them on-the-fly(SMPTE-C/EBU/REC-709)

But I think you've got something going on for the last wish, using yRGB or so?

Anyway, these are the features I'm missing...but I can easily wait another year or two. Keep up the good work http://forum-images.hardware.fr/images/perso/zoubidawa.gif

[Thunderbolt8]

Do you have a CRT or a fixed resolution display? If you have a fixed resolution display then you should always send the native resolution to the display. If you have a CRT things are more complicated. Why don't you simply try it out and see if AR is correct or not?got a tft display, but after some checking I can say that the AR appears to be fine.

another thing though, arent those displays supposed to look best at the native resolution and the PQ could be a little worse with other resolutions? at least it used to be like that in the past, didnt it? if thats the case, the switch to another resolution might not help then, if the PQ is being decreased due to this.

[watchman]

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


No glitches with this test build. Everything else seems to be fine as well.

[6233638]

Madshi, thanks for the updates.

I have reset the MadVR settings, done a clean install of the new Nvidia 270.61 drivers (which is a real pain as I had a ton of custom game profiles) and it does not seem to have fixed the problems I was having.


Both 0.57 and the "glitch hack" version are still showing large numbers of presentation glitches that result in visible stuttering (but no dropped/delayed frames reported) when the refresh rate is greater than 1:1. (and I have now confirmed that my screen will not accept 25 or 30hz)

Setting "after copy to backbuffer" to flush & wait no longer results in the buffers gradually dropping to 0, but also no longer stops presentation glitches appearing as it was doing.


This is very frustrating, as playback was perfect on my old 9400 system that this replaces, and part of the reason I went with Nvidia again was because playback was perfect on it. (never and dropped/delayed frames/presentation glitches)

I wish there was something I could do to help you get to the bottom of it.

[sneaker_ger]

@6233638

Do you have "flush & wait (sleep)" set for "...after last render step"?

[ikarad]

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!

With your hack, there is no glitch anymore but I have sound problem (sound disappeared and cut off by moment) with bluray movies interlaced at 30fps (I use ffdshow + Decomb filter to make inverse telecine).
With standard video (mkv anime or BD at 24fps native), for this moment, I don't have any problem.

[6233638]

@6233638

Do you have "flush & wait (sleep)" set for "...after last render step"?Yes, that's the default.

I have also tried a number of flush combinations.

[madshi]

Could you open all trees in the settings by default btw.? They are so few anyways
Not sure about that. There will come some more in the future. Any more opinions on that?

I guess I just assumed it reported 23.976, since I see it in MPC-HC's statistics - if statistics are clicked under View, it shows Frame rate: 23.976 (or 29.970 for video) when you move the mouse to the bottom of the screen. Of course, that statistic seems to take a few seconds to "settle in", almost like it's really giving you an average frame rate.

Unless madVR can get the frame rate from wherever MPC-HC gets it from, I certainly have no idea how to solve it.
Yeah, that MPC-HC thing is counting frames per second, so it needs time to "settle in", while madVR's automatic display mode changer only changes modes *before* playback even starts. So not possible, with the current way the display mode changer works.

Other thing, When I watch interlaced bluray movies at 30fps and that I use decomb IVTC filter in avisynth with ffdshow, CRTL+J displays 29.970 fps and not 23.976 fps, is-it normal?
I guess ffdshow/avisynth don't properly update the framerate information. You may want to post this to the ffdshow thread.

This seems to fix the glitches, well I still get a couple when video starts but after that I seem to get no more during the playback.
So is this glitch-hack-version better than v0.56 and v0.57? IIRC you had found a pretty good flush combination for v0.56 for your setup, too. So which is better? v0.56 with your flush combination? Or the glitch-hack-version?

Didn't get any glitches now for the 30 minutes I ran it, so they seem to be gone for good.
And you did get glitches with all other 0x5.. versions? So is the glitch-hack version an improvement? Or is it just as good as the best official 0x5.. version?

Something unrelated to the new hack version:
I sometimes get the OSD messages ("exclusive") to blink two or three times. For example if I start a video in MPC-HC and then quickly press the fullscreen key so that the video starts in fullscreen immediately.
Filed under minor cosmetical issues, priority: ultra low.

I'm away from my HTPC on a setup with just a 50/59/60hz dual monitor setup (ATI). All is working fine with the frequence chaning but should 23.976 material really be displayed at 50hz (over I would have through 59...)?
There's no direct match, but I agree that 59 would be better than 50. Will fix that.

I'm not too keen on this and would prefer the HTPC be returned to the state it was it (eg the default freq), else you will get stuck in 24hz which is not a good look for the desktop / player GUI and even worse if you then have an issue with playback not using madVR (eg DVD).
Well, ok, I guess I could restore the mode when madVR is released. But then, if you load a new video, madVR will switch again. So if you change from one 24p movie to another 24p movie, madVR will go 24p -> 60p -> 24p. Not very nice.

-allow on-the-fly refresh rate switches, like in <0.50. ATM, the ppl using the VBS script in Reclock are SOL.
Maybe if you post a log I can see what's wrong.

another thing though, arent those displays supposed to look best at the native resolution and the PQ could be a little worse with other resolutions?
Yes, you should always use native resolution with fixed panel displays. However, if your display supports multiple refresh rates (e.g. 23.976Hz, 24.000Hz, 50.000Hz, 59.940Hz, 60.000Hz) it would make a lot of sense to let madVR switch refresh rates to match the movie file.

No glitches with this test build. Everything else seems to be fine as well.
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..?

Both 0.57 and the "glitch hack" version are still showing large numbers of presentation glitches that result in visible stuttering (but no dropped/delayed frames reported) when the refresh rate is greater than 1:1. (and I have now confirmed that my screen will not accept 25 or 30hz)

Setting "after copy to backbuffer" to flush & wait no longer results in the buffers gradually dropping to 0, but also no longer stops presentation glitches appearing as it was doing.

This is very frustrating, as playback was perfect on my old 9400 system that this replaces, and part of the reason I went with Nvidia again was because playback was perfect on it. (never and dropped/delayed frames/presentation glitches)

I wish there was something I could do to help you get to the bottom of it.
Too bad the glitch-hack doesn't help in your case. So far reports from the other users appears to be quite positive.

With your hack, there is no glitch anymore but I have sound problem (sound disappeared and cut off by moment) with bluray movies interlaced at 30fps (I use ffdshow + Decomb filter to make inverse telecine).
With standard video (mkv anime or BD at 24fps native), for this moment, I don't have any problem.
Hmmmm... What does your CPU consumption say? Is it near 100%? Not sure where sound problems are coming from. You could try different audio renderers, maybe that helps? Don't really know...

[jmone]

There's no direct match, but I agree that 59 would be better than 50. Will fix that.
:)

Well, ok, I guess I could restore the mode when madVR is released. But then, if you load a new video, madVR will switch again. So if you change from one 24p movie to another 24p movie, madVR will go 24p -> 60p -> 24p. Not very nice.

True but much of such veiwing will be movies or even TV Eps so it is not as if it is very frequent and you would normally do one freq change at the start anyway. Another option would be a check box to "Restore The Mode with madVR is Released"

[sneaker_ger]

And you did get glitches with all other 0x5.. versions?

Yes (IIRC).

So is the glitch-hack version an improvement?

Yes. So far playback has been perfect.

[ikarad]

I guess ffdshow/avisynth don't properly update the framerate information. You may want to post this to the ffdshow thread.


Hmmmm... What does your CPU consumption say? Is it near 100%? Not sure where sound problems are coming from. You could try different audio renderers, maybe that helps? Don't really know...

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.

[italospain]

The problem is that (at least on my PC) DScaler does *not* report 23.976 for movies, even when IVTC is applied. As a result there's no way to madVR to react properly for both video and movie content. DScaler reports both as 29.970. So madVR will switch to the incorrect refresh rate either for movies or for video, if you use DScaler for both types of content.

If you have any ideas on how to solve this, just let me know.


DScaler and madVR works fine for me too. (But I have to set auto for deinterlacing in the dscaler options and apply ivtc only if flag is found).

[pirlouy]

So does it work, did you test it? Haven't got many "it works" or "it doesn't work" reports yet...
Sorry, I should have been more precise. Auto-changer is working perfectly in my case.

[pankov]

:)
Well, ok, I guess I could restore the mode when madVR is released. But then, if you load a new video, madVR will switch again. So if you change from one 24p movie to another 24p movie, madVR will go 24p -> 60p -> 24p. Not very nice.

True but much of such veiwing will be movies or even TV Eps so it is not as if it is very frequent and you would normally do one freq change at the start anyway. Another option would be a check box to "Restore The Mode with madVR is Released"
I'm just about to test the new display mode changer, but I decided to read the tread first and I think I'm with madshi on this subject.
Exactly watching TV Episodes is the reason I think restoring the previous refresh rate is a bad idea, because this means a lot of switching/flashing between episodes. madVR can't know that there will be a new episode/file with the same frame rate starting just after the previous one.
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.

[pirlouy]

Personally, I prefer to keep the refresh rate of latest video, just like right now. But I think a setting is inevitable, a vote would result in 50/50.

[yesgrey]

Not sure about that. There will come some more in the future. Any more opinions on that?
IMHO the best option would be to memorize the state when it was closed. I only change some of the settings, so see all or none is always a pain for me, because I would still need to close or open some. I prefer the settings dialog to show like it was when closed.

[pirlouy]

+1, like the regedit...

[SamuriHL]

Is it supposed to go back to the original res when the video stops? Cause it's not in my case. Other than that minor annoyance it's rocking nicely. A few minutes of my wife's Glee discs were in sync which is great on that machine. This is awesome!

[SamuriHL]

Yea, I could go with that myself. Remember what was open/closed last time the dialog was closed.