[other] Problems with dropping frames with EVR (2 Viewers)

[disaster123]

AW: Problems with dropping frames with EVR

thanks for you wonderful explanations - for me my last version of dshowhelper is running smooth and fine - so i'll simply use it and i'm happy again (latest SVN dshowhelper was not working for me even on X2 2300BE + ATI 3200). If i can help with something - please ask - but i'm not able to implement new dshow things.

 

[gemx]

I would recommend "...accept that 1:2 fps/Hz ratio stutters (was always the case with the EVR code) and reverse some changes..." since more and more users are going to use some lower end machines (Atom, ION ....) as they are very silent and don't use much power.

Also the more CPU the renderer needs MP is getting more and more useless.
On my current machine which is (overclocked though) a 2.0 GHz Atom dual core + an ION GPU i can only watch 1080i absolutely smooth when i disable nearly every plugin.
So more and more people may say
"Hey, wait - MP with only the Tv plugin and pictures and videos and nothing else do have full HD? Are you crazy? I will stick with 1.0.2 stable and wait for MP II"

What i wanted to say is that over all improvements MP 1.1.0 brings, we can't tell the user that you can only use it with full HD content if you have a > 3 GHz dual core + > GeForce 220 system

 

[disaster123]

AW: Problems with dropping frames with EVR

is there really no way to remove the extra copy step MP is using at the moment? (tourettes mentioned something like this)

 

[Sebastiii]

Hi for me i have dropframe and i can see it in screen.
I have i7Core and 5770 ATI, so i use version from 24892 source) and it's smooth, so i take it for now.
Thx,
Cheers,
Sebastiii

 

[Scythe42]

There's one more thing you guys can try. As said I rarely have dropped frames and therefore can't really reproduce the issues here. But I just had an idea:

In CheckForScheduledSample() don't reschedule current samples at all.

I mean exchange the

if (*pNextSampleTime > (m_rtTimePerFrame/4))

to

if (*pNextSampleTime > m_rtTimePerFrame)

and leave everything as it is in SVN for now.

Then it would break and reschedule a sample if the delta of the presentation time is larger than the duration of a frame which means it is one of the frames in the queue. Maybe this could help and this is where the actual problem lies...

If this helps a bit, then try use *3/4 or *2/3 in scheduler.cpp depending on how early a sample needs to be presented on a machine to be there in time.

@tourette:
Can you try this and check if it breaks 1:2 fps/Hz? In theory you could remove the stuff you added to the scheduler.cpp when m_rtTimePerFrame is correct for 25p material at 50Hz.

disaster123
Can you give this a try, too?

 

[tourettes]

What i wanted to say is that over all improvements MP 1.1.0 brings, we can't tell the user that you can only use it with full HD content if you have a > 3 GHz dual core + > GeForce 220 system

And in the same time MP 1.1.0 wont be able to play the standard definition DVDs with the same system specs. There are progressive DVDs out there... In my opinion that is not a good route to go. The first DVD I tested those new dshowhelper.dll changes happened to be 25 fps progressive one (maybe coincidence). Also every one who is using beamers with 48/72hz are doomed (no matter what HW is used, there will be horrible stuttering when most of the time frames are scheduled on 1 to 3 v-sync intervals).

 

[OnkelChris]

AW: Re: Problems with dropping frames with EVR

...

I mean exchange the

if (*pNextSampleTime > (m_rtTimePerFrame/4))

to

if (*pNextSampleTime > m_rtTimePerFrame)

and leave everything as it is in SVN for now.
...

Did this... see attached dshowhelper. Perhaps some "low-end-system" users will also test

 

[tourettes]

Re: AW: Problems with dropping frames with EVR

is there really no way to remove the extra copy step MP is using at the moment? (tourettes mentioned something like this)

yes and no:

1) ATI starts to flicker
2) reducing the 2nd step would make Windows 7 dependency

so, not possible in 1.1.0. For MPII I wouldn't even care if we had to drop ATI support if we need to get rid from the extra texture copy... (please, start a new thread ot discuss if you dont like the proposal... or ask ATI to fix their drivers...).

 

[jameson_uk]

What i wanted to say is that over all improvements MP 1.1.0 brings, we can't tell the user that you can only use it with full HD content if you have a > 3 GHz dual core + > GeForce 220 system

The theory of all this makes sense but a few of the technicalities are over my head

Can Atom users not select to use VMR9 under Vista / Win7 ?? I am running XP and full HD is not problematic with a 2.2Ghz dual core processor and same graphics chip as the Atom setup (9400 based IGP)

 

[disaster123]

AW: Problems with dropping frames with EVR

What are the disadvantage of my changes? It seems to help a lot on ION systems and normal systems are also running fine and i don't break anything with 1:2 hz/fps and so on

tourettes
i thought ati flickers in MP in general? or have you changed something and that is why i don't see any flickering anymore? OK something like if Win 7 use X and other use Y in the dll isn't possible?