FCSvr FTP Connection timed out
by Zen Rosenthal
on
Jul 17, 2008 at 12:08:11 am
Hi,
We are using Final Cut Server to automate compression and uploads to our FTP site utilising a watch folder system. While most files work fine, I have noticed that some of the transfers fail with the error message:
After trying to find a consistent pattern of failures, I've narrowed it down to files over a certain length, in our case 60 secs (roughly 25MB). We are primarily a commercials post house so most of our uploads are shorter than this, which explains why most of them are fine.
Therefore, there must be something in Final Cut Server that prematurely reports an error when a file transfer takes over a certain amount of time regardless of file size. This seems rather counter productive considering that many people would be using such a feature for large file sizes, thus longer transfer times.
Does anyone run into this problem? Is it a bug or is there a setting somewhere that can be changed?
Re: FCSvr FTP Connection timed out by Francois Stark on Jul 17, 2008 at 6:25:46 pm
Zen
I've had the same problem. We are a long-form facility and all our files are quite large. Whenever I try to do a compression to ftp I get the same error. However, it is not linked to file size, it is linked to the speed of the upload. It seems the FTP server times out and aborts the transfer if FCServer uses compressor to convert a file while uploading.
I have done many copies to FTP without compressing - using Noconversion in FCServer. This works every time.
I have not done it yet, but I would think the solution is to do the conversion to a non-ftp device first, and then set up a second watch to watch this intermediate folder and do a noconversion copy to the ftp server. The second watcher could even delete the intermediate file when done uploading to ftp. I'm still battling to set up FCServer on our 8core mac pro...
Re: FCSvr FTP Connection timed out by Zen Rosenthal on Jul 17, 2008 at 11:35:33 pm
Hi Francois,
I was under the impression that FCServer compresses to a local temp cache prior to uploading to the FTP server. If you watch the progress bar it seems to run twice, one pass for compression and another pass for the upload (I'm assuming). Also, our modem only indicates upload activity on the second pass. This is the way Compressor handles the process on its own if the destination is to an FTP server. However, you might be right as I couldn't find anything in the documentation about this. When I get a chance I will try your suggestion and see if it works.
