MP1 EVR Presenter/dshowhelper community development (2 Viewers)

[doveman]

I'm having problems even on single-screen now (with 1.2 Final).

I'd been playing a game (The Witcher) and closed that and started MP.

The first time I tried to start LiveTV I got "unknown error occured" even though I'd left it on the EPG for a good 30 seconds. When I tried again it worked. The picture wasn't terrible, but I was noticing what may have been tearing around the centre of the screen, basically a line twitching, which I haven't seen before.

Unfortunately this screenshot doesn't show what I see in the stats, which is a jagged bit coming out of the left of the bottom of the dips in the red line. The first two digits of the Act FPS are also constantly flipping.



I then switched back to the default dshowhelper and this flipping of the digits stopped (it's not completely steady and every few seconds changes from 50 to 49 briefly, but with the DWM .dll it's doing this constantly). However, I had major stuttering for 10 seconds before it settled down (the first two screenshots below are from two different starts of MP). Again, it's not captured in the third screenshot, but after it settles down the red line is disjointed, this time near the top of the downward slope.

 

[doveman]

After rebooting, I'm not seeing the breaks in the red line with the default dshowhelper (haven't tested the DWM one yet), but it's still stuttering like mad when it starts, so I'll report that as a MP bug.

EDIT: Further testing has shown that the stuttering only happens if I bring up the stats and it doesn't matter when I do this.

 

[Owlsroost]

Owlsroost
First of all, thank for a great work you are doing for us!

Have a question - what version of dshowhelper is used in MP 1.2.0?
And a kind of feature request - is it possible to add to statistics screen the information about whether DXVA is used or not?

It's basically v0055f (without the MP Audio Renderer support)

Tony

 

[Owlsroost]

After rebooting, I'm not seeing the breaks in the red line with the default dshowhelper (haven't tested the DWM one yet), but it's still stuttering like mad when it starts, so I'll report that as a MP bug.

EDIT: Further testing has shown that the stuttering only happens if I bring up the stats and it doesn't matter when I do this.

You have relatively long render times (8ms or more) for a powerful GPU/CPU, so there's some sort of performance (or multi-monitor related) issue somewhere - the render stats display increases the rendering load, hence the increase in stuttering.

What happens if you disconnect the second monitor completely i.e. just have the TV connected ?

As this isn't a dshowhelper development issue, can you keep the posts about this in your other thread please

Tony

 

[tourettes]

After rebooting, I'm not seeing the breaks in the red line with the default dshowhelper (haven't tested the DWM one yet), but it's still stuttering like mad when it starts, so I'll report that as a MP bug.

You have relatively long render times (8ms or more) for a powerful GPU/CPU, so there's some sort of performance (or multi-monitor related) issue somewhere - the render stats display increases the rendering load, hence the increase in stuttering.

AERO is most likely stalling the EVR presenter Present() call as long as it finds a correct v-sync to match the both display devices. This is one reason why display devices should always share a common refresh rate (or whole number multiplier like 50 Hz and 100 Hz would have).

Having two display devices connected with separate refresh rates (which both are even non-mathing to the played content) isn't nothing more than a doomed atempt when it comes to media playback.

 

[doveman]

After rebooting, I'm not seeing the breaks in the red line with the default dshowhelper (haven't tested the DWM one yet), but it's still stuttering like mad when it starts, so I'll report that as a MP bug.

EDIT: Further testing has shown that the stuttering only happens if I bring up the stats and it doesn't matter when I do this.

You have relatively long render times (8ms or more) for a powerful GPU/CPU, so there's some sort of performance (or multi-monitor related) issue somewhere - the render stats display increases the rendering load, hence the increase in stuttering.

What happens if you disconnect the second monitor completely i.e. just have the TV connected ?

As this isn't a dshowhelper development issue, can you keep the posts about this in your other thread please

Tony

Thanks for the tip about the render times. I don't really know what most of these stats mean, so it's useful to know what to be looking for

I just found out that I actually had RadeonPro set to disable Aero for MP, so the fact that I'd enabled it in Windows wouldn't have made any difference Strange that when I did before it seemed to make the DWM dshowhelper work better, but I guess that was just a co-incidence. Now that I've re-enabled it, render times even with dual-screen and the default dshowhelper are around 2.3ms. Still stutters when I enable the stats display the first time. If I then disable it and re-enable it, it doesn't seem to. I'll see if the DWM dshowhelper makes any difference.

I can't imagine that disconnecting the monitor will make much difference compared to running in single-screen mode, as the second output is effectively disabled anyway but I'll give it a go, and yes of course I'll put any further non-related posts in my other thread

After rebooting, I'm not seeing the breaks in the red line with the default dshowhelper (haven't tested the DWM one yet), but it's still stuttering like mad when it starts, so I'll report that as a MP bug.

You have relatively long render times (8ms or more) for a powerful GPU/CPU, so there's some sort of performance (or multi-monitor related) issue somewhere - the render stats display increases the rendering load, hence the increase in stuttering.

AERO is most likely stalling the EVR presenter Present() call as long as it finds a correct v-sync to match the both display devices. This is one reason why display devices should always share a common refresh rate (or whole number multiplier like 50 Hz and 100 Hz would have).

Having two display devices connected with separate refresh rates (which both are even non-mathing to the played content) isn't nothing more than a doomed atempt when it comes to media playback.

I found out that I had RadeonPro set to disable Aero for MP.

I've tested now with Aero enabled and I still get major stuttering when enabling the stats display (at least the first time, it doesn't seem to happen if I then disable and re-enable the display).

This happens with both the default and the DWM dshowhelper and only happens in dual-screen mode, not with a single display. If I don't enable the stats, TV playback is fine so it only appears to affect the stats display, which is no big deal.

 

[Owlsroost]

If I don't enable the stats, TV playback is fine so it only appears to affect the stats display, which is no big deal.

OK - good

(and 2ms - 4ms render time is about normal with Aero running, if Present() is not being blocked as Tourettes describes)

Tony

 

[tourettes]

I've tested now with Aero enabled and I still get major stuttering when enabling the stats display (at least the first time, it doesn't seem to happen if I then disable and re-enable the display).

When enabling stats for the first time there is some extra DirectX stuff going on (font etc. is created). That is causing some stutter since the presentation time window might not be enough for all the stuff to be done. Resources aren't created on video startup since those usually aren't needed in normal use and it is better to save some resources. If someone would really want to fix that stutter then introducing a new thread that creates the needed resources could be a good way to solve it.

 

[chrik]

tourettes-> Can´t find out how to enable stats? Could someone tell me? and are there a guide that tells what the stats mean?

 

[peque]

shift + 1. You can find this info in the MP wiki.