DirectFB - Home of the pragmatist Roadmap


[directfb-dev] Re: Seeing "tearing" using mplayer dfbmga
Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[directfb-dev] Re: Seeing "tearing" using mplayer dfbmga



On Sun, Dec 08, 2002 at 08:47:27AM +0500, Antonino Daplas wrote:
> On Sun, 2002-12-08 at 04:16, Ville Syrjälä wrote:
> > But perhaps the blit hasn't completed when we flip the buffers... Ok, I
> > admit to being an idiot. When I added the vsync stuff I copied it straight
> > out of the fbdev stuff without thinking. The gfxcard_sync(); is totally
> > misplaced. Obviosly it should be before programming the registers not
> > after. I attached a patch to fix this.
> > 
> 
> This depends on the hardware though.

Talking about Matrox CRTC2 here.

> In some hardware, flips are
> automatically done during vblank, thus you can actually program the
> registers then wait for vsync (or not wait at all).  This one is perfect
> for mplayer since it already regulates the frame rate via time stamps,
> and flips are automatically done during vblanks without additional CPU
> penalty. 
> 
> In others, flips are independent of vblank/vsync (async flips).  In this
> case you have to wait for vsync, then touch the registers to avoid
> tearing effects. Yours is most probably this case.

??

> This is precisely the reason I asked for further differentiation of the
> wait_for_vsync flags in a message I sent some time ago.

I don't think I've seen that message. And didn't find anything in the
archives either.

-- 
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/


-- 
Info:  To unsubscribe send a mail to listar@directfb.org with 
"unsubscribe directfb-dev" as subject.



Home | Main Index | Thread Index


directfb.org / Development / Old Archives