TiVo Community Forum banner

Shows not recorded, channel changing

825 Views 1 Reply 1 Participant Last post by  Null Register
Ok, I've done a lot of searching and only found this on the web in a UK usenet thread. There was no solution posted there...

I have no cable box, a Series 2 DT, and TiVo is connected via the TV's video connection (not the tuner). I'm getting a lot of the following:
This program was not recorded because someone in your household did not allow the TiVo DVR to change channels to begin the recording.
Here's the weird thing: the last time I saw this happen the TiVo remote was not being used. Two shows were set to record at the same time. Someone wanted to watch a 3rd show live so the (a) TiVo remote was put aside and (b) the TV was flipped to the tuner via the TV remote. Prior to doing this, I checked the To Do list to make sure the 2 shows were on track to record. Even more annoying is that the higher ranked Season Pass was the show that was dropped (identical start times).

As a precaution, I've restarted the TiVo unit. A double recording worked earlier tonight but I had set TiVo's live TV channel to one of them as a precaution. I've set up a double recording for later tonight with the live TV channel set to a 3rd station as a test.

We do have an IR repeater in the room and I have had the TiVo do a 30-sec skip ahead when the repeater was hit with RF noise from something nearby. This only occurred for one 15 minute period. Also, I've never noticed any interaction between the TV remote and the TiVo box.

Any other ideas?

Ideally, there would be a way to set the "Ok to change channels" to default to "yes" every time or "yes" after a brief wait.
1 - 2 of 2 Posts
As a precaution, I've restarted the TiVo unit. A double recording worked earlier tonight but I had set TiVo's live TV channel to one of them as a precaution. I've set up a double recording for later tonight with the live TV channel set to a 3rd station as a test.
Quick update, the double recording when starting on a 3rd live channel worked twice since this post. I'm starting to suspect this was either (a) something the restart cleared up or (b) the IR repeater waiting to strike again.

If anyone has seen this sort of behavior before, I'd appreciate hearing about the scenario. I'm hoping for (a) but it would be good to know if there is a (c) out there...
1 - 2 of 2 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top