On Mon, Mar 07, 2005 at 04:44:21PM +0200, Oded Shimon wrote:
Tearing happens in some vo's, most noticeably vo_fbdev or
video output drivers - "vo's" is bad grammar, it would have to be "vos"
anything that uses fb for output (ggi:fbdev, sdl:fbcon...). Tearing also
s/fb/framebuffer - try not to overuse short forms.
Best shown with an example:
Where's the verb? "This is.."
Image A is the image being shown. K is black areas. The monitor looks
s/black areas/the black area/
What happens with tearing is that halfway through this process, the image changes - a very likely event. Because of this, the monitor displays the first half the first image, and the next half it shows the new image, thinking it's all the same image. The mistake will be "corrected" in the very next refresh, as then the entire screen will be the new image - too slow. Our eye already caught the mistake. With extremely high refresh rates (150hz+), tearing is practically unnoticeable.
I'm not particularly fond of this paragraph. It could be slightly clearer. Sorry for not being more specific right now.. Diego