Welcome to our community

Be a part of something great, join today!

Log in
  • 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 :)

CMOS of the RedOne

J

Julien Lambert

Active member
Joined
Oct 4, 2007
Messages
35
Reaction score
0
Points
0
Website
www.julien-lambert.com
Dear all,

My name is Julien, I'm french and I'm looking for specific info on the RedOne. "Bravo" for this website, it's great!

1. Can you explain me exactly why the RedOne has 4900x2580 pixels, than we get 4520 x 2540 activ pixels? Usually, this is for the black balance. Is it true here?
In a 4K 2:1 ratio, we have 4096 x 2048 pixels, the 424 other pixels (4520-4096) are used for the DP in order to see the out-border of the frame, right? I would like to know precisely what are those pixels used for.

2. I've read the "why cmos" post (very interesting!), but i couldn't find how does the RAW converter (i mean here after the matrix) get the information about chroma whereas we have 50% of green, and 25% of Red and blue pixel. How does it get the information of the two other colors and the luma (average of the 8 pixels above?).
bayer.jpg


3. Does anyone has a good URL to introduce precisely the "RedCode Raw", to explain how it works with the wavelet compression?


Thanks a lot and sorry for my english, I've to improve it! ;)

Julien

www.julien-lambert.com
 
Andrew, i've just read the theads you gave me.
I guess you've asked the same question yourself. Thanks, it helps me a lot.

If someone has info about the point 1 (pixels arrangement) et 3 (about REDCODE through the wavelet compression), it would be nice.

Thanks, Julien
 
Red-one

Red-one

1. Yes to the look around question.

2. Andrew offered a pretty good explanation.

3. REDCODE does use Wavelets, but its optimized to the characteristics of the Mysterium sensor's RAW data, so we don't release details about that obviously.
 
Build 16

Build 16

So it´s not just a rumor that Build 16 will include Q-bert?
Click to expand...

Just working on colorizing the rear LCD display. Of course you will also need headphones.
 
Stuart English said:
Just working on colorizing the rear LCD display. Of course you will also need headphones.
Click to expand...


Damn it, so the monchrome Tetris is going to be abandoned like the RAW port was? I was really waiting for it to be released! :bleh:
Why do all these guys around want COLOR from a sensor? :wacko:

Maybe we can at least remain with the screen saver with auto-black shading...

Cheers,
Axel
 
Thank you Stoopercraft. I knew that RedCode is close to JPEG 2000, but I would like to undertand what are the differences. if someone knows that more precisely.
Ibloom, thanks a lot, your explanation about demosaicing is very interesting and It helped me a lot to understand about the interpolation of the bayer.

Ciao. Julien
 
Thank you Stoopercraft. I knew that RedCode is close to JPEG 2000, but I would like to undertand what are the differences. if someone knows that more precisely.
Click to expand...
Redcode is designed for RAW images (bayer pattern), not RGB (or grayscale) images. If Red were to use JPEG2000, debayering would have to be performed and then the resulting RGB values would get encoded. Or JPEG2000 would be applied onto the RAW image converted into a monochromatic image. That would not compress very well because non-grey areas will have lots of high frequency detail.

Or another way of thinking about it... using a RGB codec would be inefficient because you need to compress a lot of made-up information.
Using a grayscale codec would also be inefficient because of high frequency detail on non-achromatic areas.
So Redcode is optimized for RAW images to avoid those problems.

2- Redcode is 12-bit. JPEG2000 has different bit depths.

Redcode RAW compresses the RAW image without image processing. Image processing tends to add information so there is more data to compress. Or it can also throw away information.

They are also probably doing some tricks because the encoder can assume that its data came from the Mysterium sensor and it knows characteristics about that kind of image, and what the post processing is (because Red also does their own deBayering).

3- Please see Stuart's response.

3. REDCODE does use Wavelets, but its optimized to the characteristics of the Mysterium sensor's RAW data, so we don't release details about that obviously.
Click to expand...
 
Julien,
To add on...

I don't think it's very helpful to theorize about Redcode. I could come up with any number of reasons why it might be good (e.g. tailored for Red's sensor and deBayer, high degree of specialization) or bad (e.g. JPEG2000 has many experts working on it).

You'd be much better off looking at the end result.

You can download some TIFFs here showing an earlier version of Redcode versus uncompressed. (The codec has improved since then.)
http://www.cinematography.net/Red/comp-matrix.html

There is also greenscreen r3d files up on redrelay.net
 
Note also, Red is ("Real Soon Now") to release a new version of Redcode with updated firmware for the camera. My understanding is that this involves a ground-up rewrite of the codec. Details have not been released on what's changing, but if your project goes into any specifics on the Redcode design, it may soon be obsolete.
 
GlennChan said:
Redcode is designed for RAW images (bayer pattern), not RGB (or grayscale) images. If Red were to use JPEG2000, debayering would have to be performed and then the resulting RGB values would get encoded. Or JPEG2000 would be applied onto the RAW image converted into a monochromatic image. That would not compress very well because non-grey areas will have lots of high frequency detail.

Or another way of thinking about it... using a RGB codec would be inefficient because you need to compress a lot of made-up information.
Using a grayscale codec would also be inefficient because of high frequency detail on non-achromatic areas.
So Redcode is optimized for RAW images to avoid those problems.

2- Redcode is 12-bit. JPEG2000 has different bit depths.

Redcode RAW compresses the RAW image without image processing. Image processing tends to add information so there is more data to compress. Or it can also throw away information.

They are also probably doing some tricks because the encoder can assume that its data came from the Mysterium sensor and it knows characteristics about that kind of image, and what the post processing is (because Red also does their own deBayering).

3- Please see Stuart's response.
Click to expand...

Hi Glen,

JPEG 2000 can do a lot more than many end users think of. So you can store e.g. RGB+Alpha in JPEG 2000. Further it allows different bit depth, such as 8, 12 or even 16 bits per pixel. It allows to assemble large images from smaller window chunks. And so on and so on.

Lets see what Build 16 is bringing us and how the new codec will look like.

Axel
 
jbeale said:
Note also, Red is ("Real Soon Now") to release a new version of Redcode with updated firmware for the camera.
Click to expand...

Don't forget the long time ago promised Redcode encoder for Quicktime / Final Cut.
 
When you say Redcode is 12 bits deep, does this mean that the Mysterium CMOS sensor sends out 12 bits per pixel?

Thanks,
John
 
You must log in or register to reply here.
Back
Top