I dont fully understand whats happening because i think everyone should suffer this tearing. Basically the x driver splits large updates into 2 calls to prep_frame. Each call to prep_frame in the driver waits for a vsync to occur so we should allways see tearing. You could easily modify the xdriver to make one call instead of 2 or if you like i could post you a modified pre-built version to try.
John --- Alex Harford <[EMAIL PROTECTED]> wrote: > On Fri, 04 Feb 2005 11:03:02 -0700, Warren Roberts > <[EMAIL PROTECTED]> wrote: > > Ya I have to use the X11 driver as well. The > /dev/video16 device works > > great for about 5 or 10 min then hangs. Soooo I > have to use the cpu to > > decode in realtime which uses up my 3.2 ghx P4. > The X11 driver is > > reliable but really consumes the cpu. > > Yup. Do you have a smooth display? I'm wondering > if my 2.4GHz > Celeron is just below the requirements for > acceptable X11 output, > because I get a lot of tearing right in the middle > of the display. > > Alex > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IntelliVIEW -- > Interactive Reporting > Tool for open source databases. Create drag-&-drop > reports. Save time > by over 75%! Publish reports on the web. Export to > DOC, XLS, RTF, etc. > Download a FREE copy at > http://www.intelliview.com/go/osdn_nl > _______________________________________________ > ivtv-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ivtv-devel > ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
