TTCB Size Limit?

[PeteTV]

Is there a size limit for files uploaded to a TiVo?

I have an S3 and I'm trying to upload a 30Gb mpg file from a Linux system using pyTivo. The file is in a format natively supported by the TiVo, so it does not require any transcoding and ffmpeg is not even started.

The file is approx 10 hours long and the TiVo transfers fine until it gets almost 6 hours into the transfer (5:42 according to the info "Duration", 5:49 according the green progress bar), then it stops. I can play the same portion of the video via VLC and it's fine, so I don't think it's something odd about the video.

If I skip to the end of the already downloaded portion, I get a message saying the transfer was temporarily interrupted and implies there's a network problem. But the TiVo, Linux system and network are fine and have been during the entire upload.

The message also says the transfer will resume automatically once the network is available, but it never does.

I've tried the upload twice and it stopped at the same point. There's no errors displayed via pyTivo even with debugging turned on.

[greg_burns]

Why not split it with VideoRedo or something?

[dlfl]

Ideas:
Your TiVo HD is too full.
A timeout either in the TiVo or pyTivo/Linux, i.e., based on assumption no single network session could ever take that long.
And as you suspect, a size limit at one end or the other.

[PeteTV]

Why not split it with VideoRedo or something?

I could... just trying to figure out if size IS the problem. I haven't received any indication it is, but given it's a pretty big file, I'm just guessing it might be related to the size. I've previously downloaded a 30Gb file from the TiVo, so it seems like I should be able to do the reverse (not the same file).

[PeteTV]

Ideas:
Your TiVo HD is too full.

Nope... at least I'm 95% sure it's not. Before I started the upload there were over 40 hours of files in the Suggestions folder and over 10 hours in another folder. The TiVo removed all those before it started the upload.

Also... if it were a space problem I assume (I hope) the TiVo would say something about space.

A timeout either in the TiVo or pyTivo/Linux, i.e., based on assumption no single network session could ever take that long.

I don't think it's a network issue on either the TiVo or Linux, because the entire time during the transfer I've been connected from my Mac via iTerm to the Linux system. I haven't received any network interruptions between the Mac and Linux systems.

Also, assuming it was a network issue on the TiVo... and that's ALL it was... the TiVo should have continued the transfer as soon as the network was available... at least according to the warning message. I know the network is working on the TiVo when the transfer is stuck because I can go to the pyTivo shares and see the files I have.

If the problem really is because of a temporary network issue, then there's a bug in the TiVo (or possibly pyTiVo) in resuming an upload.

And as you suspect, a size limit at one end or the other.

I'm quite sure there's no size limit on the Linux system itself (at least anything related to this transfer), but I guess there could be a bug in the TiVo or pyTivo.

PS. I also tried to reboot the TiVo after the first time it hung. Hoping that if it were some kind of memory or network issue that might clean it up and it would resume the upload. After the TiVo restarted, the transfer did start up again, but it started from the very beginning and wiped out everything uploaded so far.

[greg_burns]

Pretty sure when you run out of space you get some bogus error. But nothing indicating what the real problem was.

Didn't know Tivo transfers supported resume?

[PeteTV]

Pretty sure when you run out of space you get some bogus error. But nothing indicating what the real problem was.

Didn't know Tivo transfers supported resume?

I don't know that it does for sure... I'm only going by what the warning message implies. Here's the exact message I get when I skip to the end of the video after the transfer has "hung":


The transfer has been temporarily interrupted. The DVR or the XXXX DVR
may have been unplugged or restarted, or there may be a problem with the
network. To resume the transfer, make sure that both DVRs are plugged in
and connected to the network using the correct settings. Also, confirm that
the network is up and running. The transfer will then resume automatically
after a few minutes.


To me... that implies the transfer should continue from where it left off (ie resume) if it was a temporary problem like a network issue or even if the DVR or computer were rebooted.

Certainly doesn't SEEM to be the case though.