Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Sensor chart

nice chart work. but actually scarlet's 2/3" sensor size is 10.1mm *5.35mm. so its actual capable resolution is 3060 *1621 according 3.3 microns per mm not 3072*1728, so it gives 4,961,844 pixels only, that is 93.4% of 3k resolution. in debayer pattern we can get 80% of resolution from sensor for processing and usable only, then 4,961,844*(0.8) = 3,969,475 pixels. that is 74.7% of 3k and 1.6 times more of 2k resolution. am i calculating the correct way or not? but red team are saying it captures 3k resolution how it could be possible where as actually capturing at 93.4% of 3k? please provide me some more information on this, seniors.thanks in advance. good views about charts and sensors also you guys.
with best regards
nageswara rao surapaneni
 
Some of the details on the chart here are not quite right. Either based on old info or numbers rounded off incorrectly -- they're close for generalized reference. You are correct that the photosite/pixel size on the 2/3" MX sensor 3.3 microns (as far as what I've seen from RED and based on how the math works out). The sensor's recordable area is 3072 pixels wide by 1620 high. It seems you're applying the 3.3 micron dimension to the incorrect (assumed) dimensions that were posted on the old chart.

80% resolution is a blanket assumption often used in the industry. RED has shown they are getting close to 88% nominal (almost 3.6K measured from 4096 pixels recorded) or more from the MX sensor on the RED One. Much of this depends on the OLPF design and the algorithms used to process the Bayer data. Scarlet 2/3" records 3K and it has been said repeatedly over and over, it will make superior 2K and 1080p images and deliver nominal / measured resolution close to 2.8K. The sensor's recordable area is 3072x1620 (2880x1620 when recording 16:9) and there is an additional active look-around area. Recordable area dimensions should be 10.138mm x 5.346mm.

Of course, all specs subject to change... It's not official until we can buy it.
 
where'd the chart go? I can't see it.
 
cant find this chart on red.com

Uhm.... probably because it contains info that is no longer accurate or wasn't entirely accurate to begin with. And it was not made by RED.
 
Yes please sir, we want some more chart.
 
Thanks to Brook for giving us a new Relevant Format template for the new sensors, thought I would share...


1_chartx.jpg

Is the link dead?
 
Well that's a healthy two year bump. Though this is a sticky and this information should be up to date and relevant.

I happen to have a copy of Brook's old chart, which is mostly accurate to the formats that existed back in 2008 and projected Red formats at the time:




However, a lot has changed over the last *gasp* six years. Here's a chart I have made in an overlaying style with valid Dragon formats and a couple other notable formats:





If Brook and Jarred don't mind I'll update the first post of this thread so we have both valid image links and up to date info.
 
Or add some due to Advanced Dragon Debayer?

Or this has nothing to do with either?

Sensor size does not change with debayer, advanced or otherwise. If the implication is you both are incorrectly referring to resolution even then ADD will not add resolution. How could it?
 
Or this has nothing to do with either?

Sensor size does not change with debayer, advanced or otherwise. If the implication is you both are incorrectly referring to resolution even then ADD will not add resolution. How could it?

Uprezzzzzzzzzzz! '-)

EDIT: To clarify, ADD does not add resolution, but it reveals resolution that is already there but not debayered to its optimal level.
 
Last edited:
Back
Top