Join Date: May 2001
Location: Lake Oswego, OR, USA
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
I've got an odd issue with my TiVo Series 3, and I've seen it since the first day I plugged it in (which was last Thursday) it has frozen on me several times - hard frozen, with no response to remote control or the buttons on the box - even the clock froze up. The first couple times I was watching live and didn't have a chance to connect the dots; but the next two times I was watching a recorded program, and it occured in the same spot of that recording both times
The recording was of the 11 o'clock news on KATU-HD (via Comcast from unencrypted QAM; still don't have the cablecards why I can't just pick them up? *shrug*), and both times it occured during the weather, with the "Right Now" temperature map on the screen. It seems that, right as they're about to switch to the next map, it freezes hard and a power cycle is required; however, I can FF past it successfully.
Just now I reproduced this with a live broadcast of the 6:30 news same map, same issue. Clearly it's the process of decoding the stream - not just recording it - that causes this to happen, but that's the most peculiar happenstance; what about the bitstream could cause the TiVo to hard lock like that?
What's also peculiar is that no one else seems to be reporting this; but I wonder if maybe this is a new issue? Not in the TiVo software necessarily, as I reproduced it both with the original shipping software (8.0.x?) as well as the latest update (8.3.1); but maybe in the broadcast from KATU, since they added the blue sidebar to their 4:3 programming? Or something I haven't noticed this in any other programing - including other KATU-HD programming, though I haven't watched much more than Kyle XY - just the news.
If anyone has a TiVo Series 3 and hasn't tuned into KATU-HD for the news in awhile, mind checking it out? I'm going to record the 11 o'clock news again tonight and watch it at a later date maybe TiVo can somehow retrieve the content and debug it from their end (shyeah at 768kbps? That'd take the better part of a day).