PDA

View Full Version : BIG problem with V-Sync/tearing using VMR7/9


takeshimiyagawa
27th June 2004, 22:18
Hi!

Well, here is a problem I've noticed for a long time, but now has become important because I use MPC for fansubbed proyections with a lot of people.

The V-Sync in VMR7/9/windowed/renderless seems to not work at all, and it's most noticeable in flashing scenes or camera movings.

Here are the test scenarios:

MPC 6.4.8.2:
VMR7/windowed V-Sync don't works but it's very little noticeable
VMR9/renderless V-Sync don't works but it's little noticeable
VMR7/windowed V-Sync don't works
VMR9/renderless V-Sync don't works and it's the worst
Overlay Mixer V-Sync works always (error: some flying pixels are white, and the resize quality it's lower than VMR)

Zoom Player 3 and 4:
VMR9 Same as MPC
Overlay Mixer Same as MPC

Microsoft Windows Media Player 8 (XPSP1):
Supposed VMR7 V-Sync doesn't works too

mPlayer 1.0pre4 in Linux Slackware 9.1:
Using almost all renders Works perfect (equal to Overlay Mixer in windows, but without errors, and better resize quality than Overlay Mixer. Seems to be the best at video playback)

This has been tested with a lot of videos, with this specs, and the results were always the same:
-Athlon XP geForce 2 Ti Samsung Monitor 955DF trying almost all the detonators till today. Has been tested too with the latest unofficial Omega Detonators which allows setting ON/OFF the DirectX V-Sync from Display Properties, being worst when it's ON!
-Pentium 4 Radeon 9200 with a 17'' Monitor, and too with 2 different proyectors (and the errors are most noticeable because the size)
-Athlon XP geForce 4 AOC 19'' monitor, latest detonators too. The same results here.
-Tested with other random computers and configs too.

Tried too with the colorspaces in ffdshow without luck, but noticed less tearing only using YUY2 and/or UYVY colorspaces. Anyhow, the problem is still here.

I remember that in games, DirectX have some errors of V-Sync too, so I'm thinking that this is not limited to video playback. In games using OpenGL the V-Sync is perfect.

So I'm thinking that the problem resides in DirectX and/or VMR, and maybe a workaround or patch to this problem could be implemented.
What do you think guys?

Regards!
Takeshi Miya

kilg0r3
29th June 2004, 09:08
I can only tell you that I do also have tearing with VMR9 and 7 (renderless). The problems seems to be complex though. I.e., it might be a software bug, yet, it might also be an issue due to hardware limitation, specificly system memory bandwidth.

You could try installing SP2 though.

And, please, if you find a solution, post back ... :)

Soulhunter
29th June 2004, 21:38
Maybe changing the DirectDraw-refresh stuff @ the last page of dxdiag helps... :confused:


Bye

kilg0r3
1st July 2004, 09:37
@ Soulhunter

Where is this supposed to be?

Winxp and DX 9.0b here. DirectX Diag only has the following pages

System | DirectxFiles | Display | Sound | Music | Input Devices | Network | Advanced Help |

Can't find any option to change direct draw behavior on these.

BTW what's your system's FSB?

niamh
1st July 2004, 12:09
Where is this supposed to be?
"more help" "override" button :)

http://forum.doom9.org/showthread.php?s=&threadid=76516

http://forum.doom9.org/showthread.php?s=&threadid=75173

http://forum.doom9.org/showthread.php?s=&threadid=71029

kilg0r3
1st July 2004, 14:30
The strange thing is that I have the vague feeling that the problem has arisen only recently on my system. Yet, of course, I am not really sure.

Soulhunter
1st July 2004, 18:45
Originally posted by kilg0r3
BTW what's your system's FSB?
Atm @ 190MHz (Core @ 2185MHz = XP 3000+) !!!


Bye

Soulhunter
6th July 2004, 21:39
@ kilg0r3

Would be nice to know if the DirectDraw trick helped... ;)


Bye

kilg0r3
7th July 2004, 12:56
nope, sorry.

Yet, I am not quite sure what it is that one should enter in the box. I filled in the frame rate I was using at the time.

Rash
18th July 2004, 18:32
Originally posted by Soulhunter
@ kilg0r3

Would be nice to know if the DirectDraw trick helped... ;)


Bye
No it didn't work. :( Not even trying other output methods like Offscreen Surface, 2D texture or 3D texture.