MP1 EVR Presenter/dshowhelper community development (6 Viewers)

[zermak]

Yes, as soon as I turned back on Aero and the desktop composition the playback is perfect, thank you.
Anyway with the standard DLL (from MP 1.1.2) the tearing test shows me the two lines from the top of the TV to the bottom without problems but if I use for example the v60 DLL or the accurate vsync DLL version the lines do not appear on the entire video/image (I can see only the lines on the first, I am guessing, 100 pixels starting from top), is it the way the tearing test is made or what? Right now I am using the standard DLL since I have no issues with it.

 

[tourettes]

Anyway with the standard DLL (from MP 1.1.2) the tearing test shows me the two lines from the top of the TV to the bottom without problems but if I use for example the v60 DLL or the accurate vsync DLL version the lines do not appear on the entire video/image (I can see only the lines on the first, I am guessing, 100 pixels starting from top), is it the way the tearing test is made or what? Right now I am using the standard DLL since I have no issues with it.

Tearing test is nowadays quite pointless - since we are relying on the AERO. If AERO is on then there wont be tearing. Noe the shorter lines aren't making the stats so hard to read and they can be still used for tracking down the juddering.

 

[zermak]

So do you think it is better if I use one of those modified DLLs to get the best from my set-up?

And where can I get more info about how read the stats during playback?

Thank you.

 

[edterbak]

The dll which works best for you is (at the moment) up to you to find out. If the stock one doesnt present any glitches or problems, stick with it. You have to test.

The way how to read the shift+1 graph:
two vertical lines moving from left to right. The way I use this is to see if there is a noticable judder in the movement. Originally you could also see tearing with it. (upperhalf of the screen is different from lower part) But now with W7-AERO taking care of tearing it isnt needed anymore for that purpose.
The graph with 2/3 lines green, red and yellow. The ideal situation is if all lines are as flat as can be. This means each image is presented and drawn on time / in sync with the displays refreshrate. If they are out of sync you could see spikes or sloping lines (and up again). In general the latter isnt what you want to see.
For me the most important text is the number of frames dropped. Upon pressing play it is possible a number of frames are dropped. With my setup, I sometimes see this number go up to ~40frames. After that, it stays constant for long periods. I.E After playing 50.000 frames I drop 2-5 frames. Ideally those are gone as well.

@ Tourrets/Owlsroost: Is this correct what Im writing? Or am I leaving something out?

 

[wijnand]

Hi everyone,

I wanted to try a new dll + patch file, but how do I apply the .patch file?

Thanx!

 

[Owlsroost]

Hi everyone,

I wanted to try a new dll + patch file, but how do I apply the .patch file?

Thanx!

You just need to replace the existing dll with the new one - ignore the .patch files, they are only for people compiling the MP source code.

Tony

 

[Owlsroost]

The dll which works best for you is (at the moment) up to you to find out. If the stock one doesnt present any glitches or problems, stick with it. You have to test.

The way how to read the shift+1 graph:
two vertical lines moving from left to right. The way I use this is to see if there is a noticable judder in the movement. Originally you could also see tearing with it. (upperhalf of the screen is different from lower part) But now with W7-AERO taking care of tearing it isnt needed anymore for that purpose.
The graph with 2/3 lines green, red and yellow. The ideal situation is if all lines are as flat as can be. This means each image is presented and drawn on time / in sync with the displays refreshrate. If they are out of sync you could see spikes or sloping lines (and up again). In general the latter isnt what you want to see.
For me the most important text is the number of frames dropped. Upon pressing play it is possible a number of frames are dropped. With my setup, I sometimes see this number go up to ~40frames. After that, it stays constant for long periods. I.E After playing 50.000 frames I drop 2-5 frames. Ideally those are gone as well.

@ Tourrets/Owlsroost: Is this correct what Im writing? Or am I leaving something out?

That's correct

At the moment, I'd try v0037, v0055, v0056, v0060 - the others are probably not so good....

Tony

 

[zermak]

edterbak
Thak you, I got it. So the original DLL does not work well for me since sometimes I have spikes on the yellow line and anyway the three lines are always irregular moving from top to the bottom of the graph.
I will try the Accurate VSync DLL version with its audio renderer too then.
If it will not give me a good video playback I will start testing the ones Owlsroost said And again, thank you for your work

 

[edterbak]

Owlsroost: I tested dshowhelper v60 + patched MPaudiorenderer. So far it is working VERY well. I havent noticed any judders so far.
The stats are mostly a straight line. One instance it was jagged, but no frame drops or visual judder..

Q: Is there a difference in how the synchronisation works i.e. with MP3 audio vs DTS (digital stuff)? Sometimes I see the actual framerate fluctuating rapidly (23.97-24fps) with a HW vs system ratio not varying. Sometimes it is the other way arround. What is the desired method? Is there any difference or concequence?

Thanks for the work. Im sticking with this combo for now.

 

[Tiggel]

AW: MP1 EVR Presenter/dshowhelper community development

Hi, thanks for the great work! For me the v0056 works quite perfect for HDTV, but I have some problems with mkv Files (dropped frames ->stuttering) with v0037 mkvs are better but HDTV is stuttering..

What do I have to do with the patchfiles? I'm not quite sure how to use them.

Thanks!

Tiggel