gbalaji
Well-known member
- Joined
- Dec 29, 2006
- Messages
- 655
- Reaction score
- 0
- Points
- 0
- Location
- Chennai, Tamil Nadu, India
- Website
- www.indieshd.com
Fun to watch, Red provides updates faster than users think!
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: this_feature_currently_requires_accessing_site_using_safari
No. RC 225 is a massive amount of data. Probably a ton of overkill. But will be useful when shooting 5K at 100fps.
Think data rate divided by frame rate.
Jim
So does that mean you can give us higher frame rates because the camera doesn't have to do as much work to compress the image... therefore freeing up resources for recording at the faster rates?
Or am way off base?
No. RC 225 is a massive amount of data. Probably a ton of overkill. But will be useful when shooting 5K at 100fps.
Think data rate divided by frame rate.
Jim
I'm not exactly sure what you are saying...
The amount of data that any camera can process per second divided by the frame rate tells you how large each frame can be. What I am saying is that the R1 can process just so much data. EPIC can process a whole lot more data in camera.
Jim
I didn't know that. I thought overcranked footage was supposed to be the same quality and the limit was only the fps the sensor could handle.
I wish there was a way to know when you left the sweet spot of the Red Code that was selected. That way you could know you were getting the best the camera can offer, like with film where the celluloid is the same no matter what.
You probably didn't know because it is hard to tell the difference.
Roberto... have you shot a RED ONE?
Jim
I don't understand this uncertainty about Redcode nomenclature vs. bitrate.
If it's called Redcode 80 or 225, why wouldn't it be after bitrate? Wouldn't that be pretty confusing then ? "Well it's called Redcode 250, but its actually 174.56 MB/s" ??
I don't get it.
Incessantly questioning things around here is perfectly acceptable. Keeps us on our toes.
Jim
So if the 'full pixel array' is actually 5K (4900 x 2580) then i presume theres still room for 'look around' even at 4.5K (4520 x 2540)
Because the actual bit rate varies from scene to scene. It is not fixed. That's why these are reference numbers... to give you something to hang your hat on.
Jim
Thanks. That's exactly what I was thinking. Figures to give the idea of data rise. Average & variable part is logical.
The thing causing confusion for me were the responses which suggested that the naming doesn't necessarily represent the proportional increase in bitrate, compared to current Redcode.
So I have read some numbers in this thread- but I have not heard a final answer, what will the 4.5k 2.33:1 resolution be? (4520 x 1937? Something else?)
I believe it was said earlier that the res is 4480x1880
Thanks, I saw that number as well, but I didn't think that was the official word from Red- I thought it was just speculation, as that number would be easily divisible down.