Yes. tvtime is doing some major pre-processing of the data. You might try using the 'T' key while tvtime is running to try other de-interlacer methods. Mark On Tue, 2003-03-04 at 20:47, Joe Ammann wrote: > On Thu, 2003-02-27 at 18:27, Billy Biggs wrote: > > Joe Ammann (joe@xxxxxx): > > > > > However, anything besides xawtv (tried mplayer, mythtv, tvtime) does > > > not work. What interest me most at the moment is mythtv, and there I > > > get a consitently green image, with no sound. (with tvtime e.g. I get > > > sound but no picture). I can't see anything wrong in dmesg or other > > > logs. Also tried various insmod options to turn on debugging but > > > couldn't get any clue here. > > > > For the green screen problem, please use the latest tvtime, version > > 0.9.7, released yesterday. As a workaround for a driver bug, you must > > run 'v4l-conf' before running tvtime. More information here: > > > > http://tvtime.sourceforge.net/hardware.html#saa7134 > > tvtime 0.9.7 and the vl4-conf indeed fixed the problem for tvtime, > thanks! > > Unfortunately (but probably obvious :-) mplayer et.al. still show green > :-( > > One other thing I noted: tvtime (on my PIII 450, 512MB RAM, Matrox G550) > uses almost 100% CPU (to be exact, tvtime uses ~50-60% and X ~40-50%) > and sometimes the picture seems to freeze for a frame or 2. > > xawtv uses neglectable CPU. Is this expected behaviour? > > CU; Joe > > > > > -- > video4linux-list mailing list > Unsubscribe mailto:video4linux-list-request@xxxxxxxxxx?subject=unsubscribe > https://listman.redhat.com/mailman/listinfo/video4linux-list -- Mark Cooke <mpc@xxxxxxxxxxxxxxxxxx> University Of Birmingham
