Convert to H.264 never completes for one show

Discussion in 'TiVo Home Media Features & TiVoToGo' started by WeKnSmith, Oct 17, 2007.

  1. WeKnSmith

    WeKnSmith New Member

    233
    0
    Jun 24, 2002
    Noblesville, IN
    I've got one show that I transferred off of my Humax DRT-400 that for some reason will not ever completely finish being converted to H-264. I originally pulled it off of the TiVo last week (Fall update had been installed on the TiVo, TiVo desktop was 2.3a, and used TiVo Converter Wrapper 1.1.0.2) The TiVo desktop software got stuck at 99%.

    The interesting thing is that I can actually play the converted file via Quicktime and it is completed. If I view the file via windows explorer the file looks as if it is not complete, "ghosted" or "opaque", which means that windows still has the "hidden" flag set on the file. The PC CPU is still running at 100%. To fix the CPU issue I rebooted the computer. The next issue was that even after the reboot TiVo desktop would decide to spike to 100% at random times, and would get stuck there. Also after the reboot the converted H.264 file still looked as if it was "opaque" in windows explorer.

    The next thing I tried was to delete the converted file (didn't fix the random CPU spikes.) I deleted the source .TiVo file off of my PC (still didn't fix CPU issue.)

    Next I upgraded to TiVo desktop to 2.5 (no need to reenter the desktop plus key, it remembered it.) The issue seemed to be resolved, until I redownloaded the .TiVo file & attempted to convert it again (did not user TiVo Converter Wrapper this time.) Once again the CPU is stuck at 100% and the file is "opaque" in windows explorer.


    Has anyone seen this? Any idea how to fix the issue?


    Thanks,

    Bill
     
  2. bighurt1b35

    bighurt1b35 New Member

    2
    0
    Oct 14, 2007
    This same exact thing happened to me. I did all of the same steps as you did. I already started a thread for this problem in this fourm.

    Its not a transfer to the PC problem, it just seems to be a conversion problem. Hopefully it gets fixed soon!
     

Share This Page