PDA

View Full Version : Tivo Desktop...Transfer to Tivo...Blue light on, but no show in now playing list


mike212
11-13-2009, 07:09 PM
Ok, I'm transferring video from my computer to my Tivo. Been working fine all day. Now running into a problem.

I select a file to transfer using Tivo. The blue transfer light goes on and the message on the screen indicates the transfer has started. But, the file is not showing up in the now playing list. Normally a transfer starts and the video shows up in the now playing list even before the transfer is complete. I've tried waiting twice as long as an average transfer might take (6 hours). No luck. Tried restarting Tivo and then initiating the transfer of a different video, but same problem. Any tips on what to try to get this running again?


Running Tivo Desktop Plus 2.8 (installed after running cleaner) on Vista SP2
Tivo is TivoHD

twhiting9275
11-13-2009, 07:16 PM
Does the light stay on, or is it immediately turned on then off?

This typically happens when a program is encoded in a way that tivo doesn't expect.

Try this:
go to Find programs -> todo list -> view recording history
Most likely you'll see your program in there with a "Won't Record" next to it. If you select that, you'll see why it didn't transfer

mike212
11-13-2009, 07:26 PM
The blue light stays on the whole time. I actually just restarted Tivo again and my computer and the blue light is still on. Going to shut down the Tivo server and try restarting Tivo again.

I checked the To Do List history..... The file that started all this says "Not Transferred"... when I click into it to get the reason it says.... "this program was not transferred to the DVR because of an internal error."

twhiting9275
11-13-2009, 07:27 PM
Are you running the latest desktop version (2.8)? Try upgrading if you're not.

mike212
11-13-2009, 07:39 PM
yeah running 2.8 plus.

ok this time the Tivo restart made the blue light go out. i restarted Tivo desktop and i started the transfer again. this time its showing up in the now playing list.

guess it was just a quirk in the system that required a couple restarts.