Storage issues for Proxies using Final Cut Server

Question

Storage issues for Proxies using Final Cut Server

Hi there,

we have a fairly high amount of material that is just being put into Final Cut Server to be archived again.
I dont mind the Xserve being busy to create these proxy files, but they tie up too much space!

(Maths: 500 GB / 40 h of DVCAM footage result in more than 100 GB proxy files).
We have those 40 h running though more than once a month plus a whole LOT of material from the last 2 years - and our Xsan is only 7 TB in size.

Although we could theoretically buy another fiber raid this solution is not really future proof - it just pushes the time when we have to buy the next one a couple of months forward.. on top of that I cannot afford to have expensive, fast fiber channel storage used for proxies of files that are long archived and have only very limited use (and IF we need them, stick in the archive device and done).

Any ideas how to get rid of proxy files from archived assets?
I dont really want to take pen and paper and delete the proxies of the files by hand from the bundle.. dont think FCSvr will like this either.

thanks for any advice
tobi

Posted on Mar 10, 2009 4:36 PM

Reply

Answer 1

Best reply

Nicholas Stokes

Level 2

490 points

Mar 11, 2009 8:37 AM in response to tobiatkmtsdotinfo

So I'm not sure how your math is adding 100GB of proxy files
Are you creating VersionS and/or Edit Proxies of everything?

I ask because using the default Clip Proxy setting gives you file sizes similar to the ones below. These numbers aren't accurate because the default Transcode setting uses Variable Bit Rate (VBR) encoding for both video and audio, but assuming you had a relative constant 800kbps stream here's how large your Proxies.bundle file should be

800kbps * 30secs = 2.4mb
800kbps * 60secs = 4.8mb
800kbps * 60secs * 60min = 280.8mb per hour
280.8mb per hours * 40= 11.2GB

Also note, that deleting an asset from FCSvr doesn't delete the proxy files so you could have a lot of proxies left over from a few historical scans.

Reply

Answer 2

Mar 11, 2009 8:49 AM in response to Nicholas Stokes

Ok, that sounds a lot better. I read the figure of 3 GB per hour of material for proxies (not editing proxies).
But I think with around 280 MB I could do.. 😉

thanks
tobi

Reply