bfdhe
01-23-2009, 01:45 PM
I apologize if this is an old known issue, but i searched the forum and nothing came up similar.
About 4 weeks ago, my 3 TiVo's (2 HD and 1 S3) started loosing one cable card when a scheduled recording occurs.
Example: Watching channel 906. Second tuner has a recording scheduled and changes to channel 302. Channel being watched stays tuned and viewable. Channel being recorded goes black and nothing records. Recording indicator sits at 0:00.
Stopping the recording does not bring back a viewable channel. Changing the channel does not bring back a viewable channel on the affected card.
Switching tuners - the unaffected card works OK.
The only way to fix is a restart. After restart, everything works fine until the same situation happens again.
At first, I thought the issue was only happening on my son's HD TiVo and it was always the same channel, so I blamed the channel. However, it has happened twice on my bedroom HD TiVo and has caused missed (blank) recordings. It happened last night on my S3.
I find it hard to blame the cable company for this issue and wanted to see if any others had run into this issue.
About 4 weeks ago, my 3 TiVo's (2 HD and 1 S3) started loosing one cable card when a scheduled recording occurs.
Example: Watching channel 906. Second tuner has a recording scheduled and changes to channel 302. Channel being watched stays tuned and viewable. Channel being recorded goes black and nothing records. Recording indicator sits at 0:00.
Stopping the recording does not bring back a viewable channel. Changing the channel does not bring back a viewable channel on the affected card.
Switching tuners - the unaffected card works OK.
The only way to fix is a restart. After restart, everything works fine until the same situation happens again.
At first, I thought the issue was only happening on my son's HD TiVo and it was always the same channel, so I blamed the channel. However, it has happened twice on my bedroom HD TiVo and has caused missed (blank) recordings. It happened last night on my S3.
I find it hard to blame the cable company for this issue and wanted to see if any others had run into this issue.