>> In the devel list reasons for this run from bad VIA >> chipsets to bad encoder firmware. I have ATrpms ivtv >> stuff and thus I've been loading the 0x02040024 >> encoder version that Axel supplies and generates the >> "firmware can be buggy" warning. >> I thus downloaded the latest firmware version >> 0x02050032, and my problem went away. The only >> syslog warning now reads: >> ivtv0 warning: ENC: EOS took 196 ms to occur > This is an important finding. After a recent discussion > on this list it was decided to remove the "firmware can > be buggy" warning from the code, as the firmware > deployed with ATrpms was thought to be reliable. Based > on your experience it seems it would be better to leave > the warning in place and to upgrade the ATrpms package > to include the latest firmware. What do you think? It seems that the "buggy" firmware did indeed interfere with record-v4l2.pl, thus if there are no flaws with the way James is using the ivtv calls that firmware may be indeed buggy. Your call. By now I'm up to FC5/ivtv-0.6.1 and record-v4l2.pl doesn't work at all under ivtv-0.6.1 (things changed in the standards and tuner settings) and either firmware seems to work with mplayer and plain cat /dev/video0. _______________________________________________ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
