>> I still use with "at" to schedule recordings, but it has the nasty effect >> that it only works once, i.e. it hangs something and I can't get anything >> out of my 350, until I reboot (or unload all the modules.)
> I never ran it under "at" but used cron to schedule my recordings.Have you > turned on debugging output and if so, could you send me the output that it > generates? James post lead me to investigate this further and search the ivtv-devel list as this ivtv-users is not. The reason I asked about record-v4l2.pl was that I can start and stop mplayer /dev/video0 as often as I care to and the driver never hangs, but I could only run record-v4l2.pl once. If I tried to run it twice I had to reboot, as /dev/video0 remained opened by a zombie perl/record-v4l2.pl process that couldn't be killed. If I run modprobe -r ivtv immediately after record-v4l2.pl everything seemed to work fine, though. Under syslog some suspicious warning messages showed up: ivtv0 warning: ENC: EOS interrupt not received! stopping anyway. ivtv0 warning: ENC: waited 1000 ms. 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 Back to regular programming. _______________________________________________ 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
