— ROGERS

Archive
optical

200803131020.jpg While I stand in my kitchen, sipping my morning coffee, a couple of junkies outside are locked in the slowest verbal jousting I have ever heard. Each side seems to take a little nap between responses… I hope they finish before noon.

They probably wouldn’t be arguing if only they knew that details of the Canon 5D MkII have been leaked/rumoured/invented at the Digital Photography Review forums (and further comment here). Supposedly there will be an official announcement April 22.

Features (allegedly) include:

  • A new full-frame sensor with fancier noise reduction
  • Weather sealing like the 1D series
  • 15.3 MP
  • ISO 12800 (hmmm)
  • Micro lens fine adjustment
  • EOS Integrated Cleaning System
  • Live View (meh!)
  • 6/3 fps continuous shooting for up to 68 frames
  • MSRP $3499 USD, available June 2

This covers my wishlist, so much so, I am willing to believe. Anyway, it must be true, I read it on an internet chat forum. It does seem like a plausible response to the excellent Nikon D3 – what a happy day for digital SLR-ists.

I think the junkies outside must have heard. Argument finished.

Read More

I was searching for more documentation on the REDLog and PDLog LUTs* this evening, particularly so that we could get more precise input/output from our Nucoda FilmMaster for RED-to-film tests. In this case I want to convert RED Raw (R3D) footage to dpx, import that into our FilmMaster without losing any information, and then export out in a way which works for the film-out facility.

However, by the looks of this exchange, it would seem that RED is keeping that information very close to their chests (they have promised to release it to third parties in April). So for now you can only access their LUTs through REDAlert, REDCine, or SCRATCH. Even then, the conversion through the RED software is slightly nebulous, because your only choices for working with the outside world (under their workflow) is to go linear (not desirable for film) or to use the ill-defined PDLog (supposedly a R3D-to-Cineon spec). But who would know…

Not making these LUTs available as documents is like finding out your shiny new toy didn’t come with batteries on a public holiday. It’s not an insurmountable problem, but irritating. I guess we’ll have to keep rolling our own.

*Definiton: A LUT – look up table – describes how the colours and luminance of an image should actually look. Your computer uses one to show images on the screen, although maybe called something else – like ColorSync™. They are used for everything from inkjet printers, to computer monitors, to printing to 35mm film – like Ansell Adam’s zone system on steroids – and they are supposed to keep an image looking the same despite the viewing format.

UPDATE: I am quite enthusiastic about the RED, and don’t want to get down and dirty on what is, to be fair, a revolutionary camera. However, I thought this was quite interesting:

redlog_crop.jpg

This is a crop of a REDLog output from REDAlert, material was rated at 320 ISO.

PDLog_685_crop.jpg

This is a crop of a PDLog 685 output from REDAlert. It maps the peak values (like the sparkle above the eye) to 685 (of the 1023 scale). Under the Cineon spec, 685 is white. The rest of the values (to 1023) are headroom. Rolling off at 685 effectively removes any notion of headroom.

PDLog_985_crop.jpg

This is a crop of a PDLog 985 output from REDAlert. It maps the peak values to 985 (of the 1023 scale). From what I can tell, this has a closer correlation to the original REDLog file, however, it lifts the black point significantly, so I am unsure as to the application of this except that it uses more steps of the available 10-bit scale. If this was designed to cheat in more headroom, then the black point would probably not want to lift any higher than it is in the 685 version.

Stu Maschwitz has also pondered this problem (referenced previously); he uses REC709 as a consistent (non-log) reference to explain both the theory of digital negative, as well as where someone should aim with exposure on the RED. His conclusion? To get headroom something like PanaLog (Panavision Genesis format), you need to under-expose by 2.6 stops. Having tested this, I wouldn’t do it… if you are willing to ignore the noise, however, you do get more headroom! (I will post results shortly).

As I suggested previously, Stu talks in terms of REC709 (which seems to have caused a furore), where he maybe should have talked about “linearized” images. Having seen all sorts of hijinks over correct conversion of Cineon files in the visual effects industry, it is amazing to see them all over again with this camera. I guess when people “own” the technology (camera, etc), things get a bit more emotional. When people position themselves as “experts” it gets even worse.

UPDATE to the UPDATE: And now this. I guess I should stop whining. A bit of a delay, but looks like RED are on it. I’d be interested to know what the “tiered partner” thing is about, though…

As part of expanding our workflows and our partner base, we are creating a tiered partner program that will roll out in full this year. This program will be how other companies can access R3D as is appropriate for them and for us. The first step is establishing RED Lead Development Partners. Apple and ASSIMLATE are the first and currently the only companies here. We have always said we will open up R3D to other partners, and we will. But we are going to do it right.

Read More

Morning KyotoOne of the implications of moving from film capture to digital capture is that images tend to have a different “depth” or “presence”. This is probably because of the way light scatters through layers of emulsion as opposed to the way it hits a cold, hard, digital sensor.

I’m not referring to sensor crop, or any other lens aspect-based change. Rather, this is more about why digital images look “flatter” or resolve distance/light differently than their analogue equivalents. This article is more about lens design, but has little nuggets of information that apply in a this context:

The emulsion layer that holds the light sensitive silver halide grains has a certain thickness and contains up to twenty layers of grains, any one of which can be struck by photons and therefore is part of the latent image. Light rays that strike the surface of the emulsion layer at an oblique angle will travel through the depth of the gelatine layer and will be stopped by some grains in the lower layers. So the angle of incidence is no problem at all. Ideally the film plane should be plane, but film is never flat at the film gate and will bulge. But the depth of the emulsion layer and the depth of field tolerance will offset this state of affairs and optical designers can use this characteristic to compensate the problem of the curvature of field…

…The main characteristics [of a] sensor are the fact that the sensor is flat (plane), constructed as a discrete matrix of pixels and not transparent (has no depth). The flatness of the sensor is bad for the curved nature of the image created by the lens. The opaque nature of the sensor cells implies that the oblique angle of incidence of the light rays striking the sensor surface must be limited. Otherwise only a few photons will be captured. [link]

So to paraphrase: film scatters the light in a gooey, flawed (but nice), analogue sort of way, whereas a sensor is a bit more “clinical”… yes, wild, over-simplification…

An interesting footnote is the Foveon X3 sensor, which is built more like film – red, green and blue all layered on top of each other (other sensors are usually one layer, arranged like a checkerboard). Sigma markets a series of cameras which use this sensor. Supposedly, it gives a more “film-like” look, as well as less noise and a higher dynamic range than other sensors. I can’t tell, from what I have seen online.

Read More

The top stepThere seems to be a lot of concern about the footage coming from the RED One being soft. Discarding focal issues, this is pretty much the same complaint that used to come from photographers of digital RAW stills. The solution is that there doesn’t need to be solution. It is not that the images are soft, it is more that they haven’t been sharpened (digitally, in the camera). It is better that RAW footage is not sharpened before post-processing. Film has grain, which increases perceived sharpness. As digital images are usually low in grain/noise, they don’t carry this “advantage”.

Filters such as unsharp mask are used as a matter of course by stills photographers. And even though there are modern day digital equivalents, the technique originated as an optical process with the Germans in the 1930′s. Basically what they did was to use a negative combined with a soft (contact printed) positive as a mask, which was then used to increase the contrast of edges and details. The advantage was that it did not change the flatter parts of the image. This works well optically for our eyes, which is something Ernst Mach had a lot to say about.

Scanned film also looks soft, especially when you zoom in to 100%. With the proliferation of DI systems, techniques like Super 2k have become a popular way of getting better looking scans from 35mm film. Many scanning houses now offer this service. They scan at 4k, and then downsize to 2k, using a sharpening algorithm along the way (probably using filters such as sinc which tends to sharpen when scaling down). The images look punchier and the file size is relatively small. In addition to the sharpening, the perceived resolution is higher because all the extra detail of the pixels in the 4k image are blended into the pixels of the 2k image (see: sub-pixels). For transfers to video, manufacturers of telecine chains usually refer to sharpening in some sort of euphemistic jargon. It is all the same, of course.

The only problem is that while the sharpening process looks good, it’s absolutely horrible to work with from a visual effects point of view. Sharp spikes and artefacts appear in the grain structure, which are not visible on the run, but make it very hard to get a key or pull RGB channels apart. In these cases there are kinder ways to scale without the sharpening, such as lanczos or guassian. Sharpening has ramifications in post-processing and manipulation.

RAW footage ideally has the least done to it as possible, so you can do what you want with it later. RED Cine offers sharpening as one of the output functions, but basically you will be wanting to do the final sharpening when you are doing the final grade. There are lot of different sharpening functions, so the final “look” should be a consideration when deciding how much and what kind to wind in.

More reading on filters (pdf).

Read More

200803070933.jpg

POSTSCRIPT (to the last post): I have since tried to re-create this “look” in Apple Aperture (v2.0) but found I couldn’t “overwork” the dials as much as you can in Lightroom. Aperture seems to have very safe limits, even when you ignore the sliders and type numbers up to their highest value. I do think Aperture has a more “pure” approach to image processing… and the new RAW 2.0 conversions are very nice. But I think Lightroom handles shadows more delicately (it won’t crunch them as suddenly); plus it has curves. The tint wheels are too small in Aperture, I wish they were bigger as you can’t be very precise on such a tiny scale! The other thing that bugs me in Aperture is that you cannot reorder the modules, so that the processing happens in a different sequence. Lightroom also has this limitation, but it seems to be somehow less apparent, or maybe I need to get used to the tools…

camparison.jpg

If I wanted to go the full monty on rescuing highlights, for example, I would prefer that it did this before it went through the Levels adjustment (which is pretty much your last chance to change the shadows and highlights, contrast, etc).

I have read online that Aperture works in float, although the user manual seems to have no reference to this. If true, a float pipeline would mean you couldn’t end up clipping an image in the whites or blacks – information would be preserved module to module, so if you did two contradictory adjustments (say, brighten in one module and darken in the next), the detail in the image would not be adversely affected. In most Apple products, this means 32-bit float, and they have it implemented (and documented) in Core Image, Motion, and Shake.

The trouble with Aperture is that you don’t get far into the processing chain to see that it is not working in float, at least module to module. If you crank the contrast up in the Enhance module, but try to pull the highlights down using the quarter tone controls in the Levels module, you will see that your image has been clipped. In fact, I would say that one would be best off not to touch a lot of the controls in the Exposure and Enhance modules, and try and get it all done in Levels, so that you are not losing too much detail in your image.

Maybe I don’t know enough about the Aperture processing chain, but it would seem to be a little better if you could “optimise” the order the modules worked. Because working in float can have ramifications on speed, it would be nice if you could define the bit-depth that you want to process at, switching say, from fast 8bit to create a rough “thumbnail” look, to a more refined float-based render for your final image. It means a bit of a coffee break, but at least you would have the option. This is a similar way to how you would use Shake, but for some reason Aperture doesn’t get the stable-mate’s bit-depth goodness.

Of course, Aperture does a lot of other stuff quite well. The difference between Lightroom and Aperture (or C1, Bibble, et al.) is becoming the modern equivalent of shooting Kodak or Fuji.

I like both.

REVIEW

Read More