Hi all,
I'm not officially an owner (yet) but I'm the DIT on a feature with two RED One's. Here's my estimate of the data footprint for the project.
This is for the A-camera only. Could you check my assumptions and math?
Thanks.
Michael
|
|
Hi all,
I'm not officially an owner (yet) but I'm the DIT on a feature with two RED One's. Here's my estimate of the data footprint for the project.
This is for the A-camera only. Could you check my assumptions and math?
Thanks.
Michael
14 to 1 ratio!
will you be overcranking anything?
Dave
Wow!
I had a producer ask me the same question and I said 5TB for 23 days including redundancies. I'm using a Caldigit 3.7TB drive for all our "data loading"
so much data I love it!
This is a feature starring a Hollywood B player. It's an ensemble piece with six friends often in the scene together hence the high shooting ratio. It is intended for theatrical release. This doesn't take into account any over/under cranking or the B camera.
So, no one answered the question. :shifty: Is the math correct?
M
My math isn't going to help you - but I do want to remind you that collecting data is step one but at some point - when you're finishing - you're going to need more drives to which you convert your footage.
quote:
mccarthy tech
Basically it is all a big math equation. I hear that 4K at 24fps in Redcode is supposed to be 27.5MB/s. That is 1.6GB/min, and 100GB/hr. 20 to 30 hours will require 2 to 3TB of storage space for the source footage.
Then you will have to select an offline format, unless you plan to use the Quicktime reference files, which doesn't seem like the best plan yet. I don't recommend using DV or HDV, but I will use those numbers for the same of estimates. 20 to 30 hours of footage would require 250-360GB at HDV. DVCPro-HD would require four times that much space, 1-1.5TB. ProRes or Cineform would be bit more than that. 1080p doesn't make much sense as an offline for a 2K conform since it is very close. 720p might give you a bit of a performance boost, and SD will work if you already have the tools available. I definitely recommend editing in a native 24p environment, instead of adding and removing 30 frame pullldown. Regardless, budgeting 2TB for the offline gives you the flexibilityto do whatever you need.
Once you have an offline, you will likely want to export uncompressed 2K versions of the shots you used. Uncompressed 2K 10bit RGB at 1.85 aspect ratio is 200MB/s (DPX or Blackmagic 2K) , which is 12GB/min, and 720GB/hr. For a two hour movie, with short handles, you are looking at 2TB. From there, ideally your color system can take those files directly, and export directly to DPX for filmout, which is another 1.5TB. If you need uncompressed versions of a texted and textless, that will be one more set of uncompressed files requiring 1.5TB.
That is 3-5TB for the source and online, and 5TB for the finishing at uncompressed 2K. Note not all of these files need exist at the same time, especially if you have LTO-3 backups. Using a compressed finishing codec for finishing would lower the requirements as well. A 14 disk array with 1TB spindles, split into two 6TB Raid-5 arrays, would give you 12TB. 10TB that we discussed, plus 20% to minimize fragmentation etc. You want to avoid filling any drive to more than 90% of capacity, unless you are just using it to transport data. Working on that data with no free space will cause excessive fragmentation.
The lowere end solution would be a single array of 8 1TB disks, 7TB usable after Raid redundancy. Delete your offline source after you move to 2K, delete your (BACKED UP) source footage after your 2K conform is done, before rendering colored versions.
I make a lot of assumptions, and this is only one of many ways to look at it, but I hope this helps, and gives you a few ideas.
__________________
For more information on PC based Post-Production, check out my tech website at www.hd4pc.com
| « Previous Thread | Next Thread » |