RED Storage Calculator

[aboerger]

I have written a very basic RED Storage Calculator:

http://red.glanzunion.de
there is also an "on set explaining things to the DOP sheet" on the site

have fun!

Alex

EDIT:
Widget: http://glanzunion.de/?p=18
Info Sheet: http://red.glanzunion.de/red_alexboerger_b15_v11.pdf
http://www.hackermovies.com/cmsfiles/attachments/9958_cd723905822648b72f80d959a7620330.jpg

[Paul Hazlett]

thats damn handy, thanks!!

[Deanan]

Nice Chart Alexander.

BTW, the chip sizes are a bit off.
For example, to calculate the sizes for a format on RED One:
4096 = 4096 * 5.4u = 22.118mm
2048 = 2048 * 5.4u = 11.059mm

Jon Farhat also posted a size diagram which should be

[aboerger]

hi Deanan

i will fix it in the next version,

thanks
alex

[Filipo]

Is it possible to make a Widget for Mac OS X ?

That would be great !

[Brandon Fraley]

Is it possible to make a Widget for Mac OS X ?

That would be great !

ditto

[Corrado Silveri]

Thanks!
Very useful. A vector pdf version of the chart will be perfect...

[BASSAM MSSALATIE]

Yes it is perfect .good design

[Corrado Silveri]

Thanks!
Very useful. A vector pdf version of the chart will be perfect...

Just noticed the link (to the pdf file) at the bottom of the calculator page.
Thanks again.

[aboerger]

Is it possible to make a Widget for Mac OS X ?

That would be great !

yes, thats possible and easy, but i have no photoshop here so you have to wait a day

alex

[Shawn Booth]

Aboerger you rock!!
Thank you.

[aboerger]

ok, cant resist:

here is the widget, but i think i will build a smaller version

http://glanzunion.de/?p=18

alex

[Neil W. Smith]

Great widget, Aboerger .... very nicely done.

Quick question .... don't know why but I assumed that a 2:1 extraction would be bigger than 16:9 but according to your cool tool, 16:9 extraction is larger than 2:1 ... could you explain the math behind the calculation.

Thanks,
Neil


ok, cant resist:

here is the widget, but i think i will build a smaller version

http://glanzunion.de/?p=18

alex

[Conrad Hunziker]

Quick question .... don't know why but I assumed that a 2:1 extraction would be bigger than 16:9 but according to your cool tool, 16:9 extraction is larger than 2:1 ... could you explain the math behind the calculation.


4k 2:1 recorded image size is 4096 x 2048
4k 16:9 recorded image size is 4096 x 2304

But if you do a 16:9 extraction from a 2:1 recorded image you'll get 3640 x 2048, which may be where the confusion comes in.

[Snow R. Shai]

Thank you Alex for this useful software and chart.

[Brandon Fraley]

awesome :) thanks for the widget

[Adam Levins]

Nice Job dude.... Thanks

[Mike Prevette]

very nice!

[Rocco Schult]

slick work. Congrats.

[MikeCurtis]

Just found this thread, very useful, thanks. BTW, the codec is variable bitrate, so I don't know what numbers he worked from.

Curious about how MUCH it varied, I did a little test shortly after I got my camera - I went and found a scene with the most high frequency detail I could - in the park by my house, with trees, gravel, leaves, etc.. Shot it as sharp as I could get it, then totally defocused, then with the lens cap on.

Here's how they varied:
http://www.reduser.net/forum/uploaded/107_1216839387.png

....so you can see from the second to last column that they varied a LOT, as much as 35%.

I shot this with the Red 18-50 lens, so with, say, a Cooke S4, you could probably get even more detail, and hence possibly higher data rates, from the same scene.

This was all build 15 I think, I'm planning on reshooting a similar test with build 16 soon.

Also interesting to note was that the purportedly "all black" frames (with lens cap on) pretty much matched the high frequency scene - perhaps the codec was scrambling in the dark for any detail it could latch onto, like a tweaker sifting through carpet for that one...lost....pill?

Anyway, interesting stuff (to me).

Codec tweaker that I am.

-mike

EDIT - checking the release date of the builds, this was probably with a beta of build 15

[Ed Watkins]

Here are some updated data rates for build 16.
They are an average of three tests: out of focus, sharp focus, lens cap on
Each test was approx 60 secs, @24fps
(I used the frame count from Red alert for the data rate calculation)
The average file size shown is in GB for 60 secs.

These are estimates (which I am using in my iPhone app), bear in mind the codec varies allot.

edit:
sorry my bad, last attachment was build 15 results, build 16 now attached

[Trevor Meier]

Is there an update for the widget that uses these data rates?

[MOSES]

Thanks for the PDF file & calculator website!

[Julien Lambert]

Hi,

I would like to understand how to calculate the storage needed for the Red.
I would like to know precisely how you calculate it from the different variables:

- format (2/3/4K)
- Ratio (16/9, 2:1)
- RedCode (18/36MB/s
- frame rate

For me,
Storage (Go) = 28 (or 36) x SECONDS
exemple: 28 x 3600 = 100 Go / hour

I simply do that, but i would like to be more precise (with the ratio and the three formats). Can you help me?
Thank you.
Julien

[Julien Lambert]

Can you correct me if it is wrong?

4K, 16/9:

>4096 x 2048 x 12 = 100Mbits = 12MB

At 25fps:
12MB x 25fps = 314MB/s
This is for uncompressed 4K.

REDCODE 28MB/s means a 12:1 compressed and 36MB/s means 9:1 compressed, is that true?

Thanks.