The problem cropped up suddenly, without me having made any changes to my system that I can recall.
Some programs record without any issues, but once a recording has aborted the backend doesn't do anything more until I restart it.
The log doesn't indicate any errors of any kind.
I've tried updating my ivtv drivers with no change.
For the last couple of days I've actually sat and watched the logs as recordings start (with "tail -f") to see if I could figure anything out and I've noticed something that may be pertinent:
I get:
2005-01-14 11:00:02 Started recording "Blue's Clues" on channel: 1120 on cardid: 1, sourceid 1
2005-01-14 11:00:03 Changing from None to RecordingOnly
2005-01-14 11:00:04 Found changes in the todo list.
120
(the "120" is output from my channel changing perl script)
The recording startsm abd a few seconds later I get: 2005-01-14 11:00:28 Scheduled 516 items in 23.0635 seconds.
and at that instant the recording stops.
Mythweb still reports it as recording, and the backend does report 30 minutes later:
2005-01-14 11:30:00 Finished recording Blue's Clues on channel: 1120
2005-01-14 11:30:00 Changing from RecordingOnly to None
2005-01-14 11:30:00 Found changes in the todo list.
2005-01-14 11:30:22 Scheduled 516 items in 21.8944 seconds.
but the file itself is only 15-20 seconds long.
So it appears that something is happening when the scheduling routine runs (but only sometimes -- it works 60-70% of the time) that makes the recording stop.
Any ideas?
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.6.11 - Release Date: 1/12/2005
_______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
