On Sunday 14 Aug 2005 00:18, Jason Tackaberry wrote: > On Sun, 2005-08-14 at 00:41 +0200, Lucas Meijer wrote: > > great. I used to have this subtle "tearing-like" thing going on. Now, I > > cannot tell the difference anymore between watching mpeg2 trough the > > hardware decoder, or watching it softwaredecoded and sent trough xv. > > I haven't played with tv-out on my PVR-350 for a while, so this > statement piqued my curiosity. What player are you using? Does > interlaced video really look correct using Xv on the PVR-350? At least > with MPlayer, I remain skeptical, since it seems to me there will > definitely be vsync issues.
At present anything up to 511 pixels high must be de-interlaced for correct playback, but de-interlacing is not required once you go beyond that. The vsync code has been written so that it can change between two modes of operation. It can either sync on every field, or every frame. The current driver has this mode switch hard-coded. Sync on every field gives the highest framerate (50/60), but the field order can become messed up when playing interlaced material. Sync on every frame gives a lower framerate (25/30), but it ensures the field order is correct. It depends on what you're doing as to which mode is best. If you try to use time-stretch in MythTV, then sync on every field gives the best results but you need to de-interlace first. If you simply want the best quality image, then sync on every frame is best because there is no need to de-interlace the source. -- Ian ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
