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 :)

DRAGON REDCODE test (old OLPF)

Michael Tiemann

Well-known member
Joined
Oct 4, 2008
Messages
2,216
Reaction score
1
Points
38
Website
manifoldrecording.com
Dear Dragonistas,

I decided to collect some data this weekend on the behavior of REDCODE compression. I settled on the following test/evaluation theory:

1. All clips are static shots 3 seconds long. When played in a loop, one can get a really good feeling about how the noise behaves (in a static shot).
2. I used what I believe is my sharpest lens for this test: the Canon EF 24mm TS L stopped down to f5.6
3. The frame rate is 12 fps and the shutter is 360 degrees. Shooting at 12fps makes the noise more apparent than when shot at 24fps. Shooting at 1/12th of a second puts more light on the sensor, which reduces noise (generally)
4. The dark wood floor and the shadows along the sides turn out to be great generators of video noise. The high-contrast fine details in the scene don't tend to break down and show up as noise. Thus, noise typically comes from the shadows.

I shot at ratios of 2, 3, 4, 5, 6, 7, 8, 10, 12, 14, 16, 18, 20, and 22:1 (in that order). The metadata in the clips will tell you the compression rate for sure. I shot 4K at a 5:4 aspect ratio, providing enough pixels that one can evaluate noise at full-res vs. scaled-down res.

What I have observed in my cursory evaluation is that when viewed at Full/100%, even under these somewhat tortuous conditions (12fps!), REDCODE 2:1 looks better as a moving image than as a still image and whatever noise is there is very, very small and granular. As the REDCODE compression rate moves up, the relative size of the noise seems to increase, until about REDCODE 10:1, when the relative intensity of the noise (and also its prevalence across the image) also increases. At REDCODE 22:1, the noise is very easily seen coming from the entire floor and from the whole back wall.

Now, one of the reasons that DRAGON is a 6K camera is so that one can capture at a higher resolution than the delivery resolution. When these images are scaled down to Full/70%, visible noise is reduced. And when scaled down to Full/50%, it is reduced further. It is interesting to compare the noise character at REDCODE 2:1 at 100% to REDCODE 4:1 at 70% or REDCODE 8:1 at 50%. It is also interesting to stretch out the comparison a bit, so REDCODE 2:1 at 100% vs. REDCODE 5:1 at 70% vs REDCODE 12:1 at 50% vs. REDCODE 22:1 at 25% (sadly there's no 35% setting in REDCINE X).

Anyway, here's a link to the R3D files at different levels of compression, FWIW: https://www.dropbox.com/sh/bhpx7hx6xavyfae/5WjC0rCsBk
 
That Canon 24mm lens is a nice product. As is the 100mm Macro
 
Good test Michael. Would it be possible to put the files in one loop as a web exported H.264 video?
 


Hi Michael,

That 24TSE has been a lens that I have enjoyed for a long time, but careful setup still takes a lotta time, in my experience. What real world motion applications do you use it for and have you streamlined the setup process? I very frequently see building images falling over, etc. on finished material and wonder if there is an easier fix than this lens, for example. If this is too far off thread-just ignore.

Thank you very much

Fury
 
Hi Michael,

That 24TSE has been a lens that I have enjoyed for a long time, but careful setup still takes a lotta time, in my experience. What real world motion applications do you use it for and have you streamlined the setup process? I very frequently see building images falling over, etc. on finished material and wonder if there is an easier fix than this lens, for example. If this is too far off thread-just ignore.

Thank you very much

Fury

The problems with perspective distortion are quite devilish. The TS-E lenses make it possible to use more of the full-frame image with correct perspective. But the 5:4 aspect ratio of the RED camera also provides the opportunity to get halfway to perspective nirvana. A 3840x3072 image can yield a 3840x2160 slice, which gives a 21% up or down correction possible in-camera. That's about half what the TS-E lens gives (50% up/down) but it's certainly better than nothing. And the 5:4 aspect ratio means that you are not collecting the extra 7.28M pixels on the outside that are going to have to be cropped out anyways. So you are only wasting 3.5M pixels per frame. If you can shoot closer to the middle and still keep the perspective distortion under control, you can shoot and then crop 4:3, 3:2, or...wait for it...HD.
 
Im in the process of trying to understand Redcode and I really cant tell the difference in noise in these images.
 
Back
Top