On Mon, 16 Apr 2007 17:14:14 +0200
Lourens Veen <[EMAIL PROTECTED]> wrote:
> > Another way to avoid tearing is to use tripple buffers on
> > the card. One that is currently shown, one that is the next
> > one to be shown and one that is currently updated by the application.
> > It uses more memory (three buffers instead of two) and needs
> > image flip in hardware, but it simplifies programming on the
> > software side (no interrupts to take care off) and thus seems
> > to be somewhat prefered. (at least for video apps)
>
> But how do you do the timing then without an interrupt? I mean, you can
> keep rendering frames, but you don't know exactly when they will be
> displayed unless you have an interrupt to sync to. Sure, triple
> buffering will avoid tearing but it won't do anything for jitter.
The 3 buffer system does not need that. It just tells
the card which buffer should be displayed next. If you care
about timing jitters don't worry. It will be ~15ms at 60Hz
refresh rate. Very few people are able to see that (you need
to be trained to see anything below 30ms) and you'll only
experience it when the flip is around the blank time, which
makes it very unlikely.
Attila Kinali
--
Linux ist... wenn man einfache Dinge auch mit einer kryptischen
post-fix Sprache loesen kann
-- Daniel Hottinger
_______________________________________________
Open-graphics mailing list
[email protected]
http://lists.duskglow.com/mailman/listinfo/open-graphics
List service provided by Duskglow Consulting, LLC (www.duskglow.com)
