Q: Copy response of huge files makes all other FCS hang until finished, WHY?
Hi.
We are using FCS, in combination with telestream episode engine for transcoding.
We also have an Xsan set up for all mediafiles.
I have set up a watcher folder on a smb share (windows), and alot of HUGE .mxf files are sent there to be copied using FCS to our Xsan, and then Episode transcodes it to Apple ProRes (HQ) files.
The process works as supposed, my concern is that all other FCS watchers stops/halts during the file-copy process FCS does. This is a big problem since the files to be copied are 20+ GB, and thus filecopy via ethernet and a firewall takes quite some time!
We have set the FCS prefs to allow 15 simulantous processes, but alas this is NOT the case when it is copying these files.
Is it possible to fix this, so that this does NOT halt all other watcher responses?
Our workflow at the TV station relies alot on FCS, and we cannot afford to loose time during workhours only because of one file being copied to the system.
Is this a smb limitation? or a FCS limitation?
Are there any settings we can change to allow for other responses to be run simultaneous as filcopy responses run?
PS.latest FCS version as of 20. january 2011
thx!
-m
We are using FCS, in combination with telestream episode engine for transcoding.
We also have an Xsan set up for all mediafiles.
I have set up a watcher folder on a smb share (windows), and alot of HUGE .mxf files are sent there to be copied using FCS to our Xsan, and then Episode transcodes it to Apple ProRes (HQ) files.
The process works as supposed, my concern is that all other FCS watchers stops/halts during the file-copy process FCS does. This is a big problem since the files to be copied are 20+ GB, and thus filecopy via ethernet and a firewall takes quite some time!
We have set the FCS prefs to allow 15 simulantous processes, but alas this is NOT the case when it is copying these files.
Is it possible to fix this, so that this does NOT halt all other watcher responses?
Our workflow at the TV station relies alot on FCS, and we cannot afford to loose time during workhours only because of one file being copied to the system.
Is this a smb limitation? or a FCS limitation?
Are there any settings we can change to allow for other responses to be run simultaneous as filcopy responses run?
PS.latest FCS version as of 20. january 2011
thx!
-m
Mac OS X (10.6.5)
Posted on Jan 20, 2011 8:56 AM