SimpleSimon
05-09-04, 11:06 AM
Seems that talking about how well my 921 has been performing has jinxed it.
Over the last couple of days, I've had about a 90% non-fire rate on my timers. Note that I have no OTA - this is all satellite only.
I've always pushed the envelope - multiple back-to-back timers on 2 stations at once all using default padding and many times gone through conflict resolution screen to get things the way I want - I have multiple feeds, so as I browse and select a show by hitting record in the guide, it'll tell me when I'm exceeding the design limits. :) Sometimes I'll delete the new timer, sometimes an old one, sometimes do a 'skip once'. All of it has been working just fine until a couple of days ago.
Apparently, the timer database got corrupted. I lost my EPG for a while for some reason, but even after it came back, the timers were messed up. I was smelling trouble because the Menu-7 list that's supposed to be in "action order" wasn't. A whole group of timers was in the wrong place.
When seeing a misfire, I would manually tune to the channel, and hit Record and select OK to end it at the 'end of event' which was displayed correctly. However, the recording always continued beyond - no auto-stop.
It appears that the only timers that would work were some newly-created ones. I'll guess 'newly-created' means after the corruption occurred.
I did a power plug reboot and all of the above fixed itself, but my Sunday morning timers still did not fire. They also did not fire last week.
I have just deleted ALL timers and did another power plug reboot. So far, it seems to be helping. Mr. Blinky has appeared correctly. I just now thought that they weren't stopping, and manually stopped the recordings of 'current' shows, and then realized that the Record-till-end-of-event action adds in the default 3 minute padding.
Update: Seems like everything's working now. We'll know more tonight.
Over the last couple of days, I've had about a 90% non-fire rate on my timers. Note that I have no OTA - this is all satellite only.
I've always pushed the envelope - multiple back-to-back timers on 2 stations at once all using default padding and many times gone through conflict resolution screen to get things the way I want - I have multiple feeds, so as I browse and select a show by hitting record in the guide, it'll tell me when I'm exceeding the design limits. :) Sometimes I'll delete the new timer, sometimes an old one, sometimes do a 'skip once'. All of it has been working just fine until a couple of days ago.
Apparently, the timer database got corrupted. I lost my EPG for a while for some reason, but even after it came back, the timers were messed up. I was smelling trouble because the Menu-7 list that's supposed to be in "action order" wasn't. A whole group of timers was in the wrong place.
When seeing a misfire, I would manually tune to the channel, and hit Record and select OK to end it at the 'end of event' which was displayed correctly. However, the recording always continued beyond - no auto-stop.
It appears that the only timers that would work were some newly-created ones. I'll guess 'newly-created' means after the corruption occurred.
I did a power plug reboot and all of the above fixed itself, but my Sunday morning timers still did not fire. They also did not fire last week.
I have just deleted ALL timers and did another power plug reboot. So far, it seems to be helping. Mr. Blinky has appeared correctly. I just now thought that they weren't stopping, and manually stopped the recordings of 'current' shows, and then realized that the Record-till-end-of-event action adds in the default 3 minute padding.
Update: Seems like everything's working now. We'll know more tonight.