A very interesting question popped up on Flickr: Is there any technical advantage of specifying AdobeRGB or sRGB in a Camera RAW file?
Almost all digital cameras obtains color by placing a color filter in front of identically constructed photodiodes. The RAW file just stores digitization of those monochromatic values. Color profile information on a RAW file is stored in the metadata, not applied to the file itself. So there is no technical difference between the two profiles besides hinting to your image processing applications your preferred color space.
There is a slight theoretical exception here: the RAW format isn’t a standard so there is no reason why a camera manufacturer couldn’t record different raw data based on the intended color space. This might be advantageous in a camera like the Nikon D200, which does color processing in analog space before digitization. The intended color space could theoretically provide hints to the camera so as to minimize interpolation to the resulting color space.
Of course, this doesn’t happen. If Nikon did such a thing, Adobe would probably have a conniption and call it “encryption.” Sometimes I wonder if Nikon’s White Balance code page in the D200 was intended to give Nikon engineers the flexibility to take advantage of this camera trait—I know of no other camera that uses white balance information to modify digitization—in a future firmware release…and corresponding Capture NX update.
Now we’ll never know.
[Adobe Camera RAW and color profiling after the jump]Continue reading