News for hackers. Stuff that matters.
Re:A method for improving Milky Way exposures in light pollu... by vanderZwan on Tuesday September 12, 2017 @10:16AM (#15227419)
What article doesn't explain is the physics behind why ETTR captures more light data: our perception of light scales logarithmically, while a CCD captures it linearly. Each stop is a doubling (or halving) of the amount of light captured. CCDs work by increased voltage based on captured photons.

Imagine back to when digital photography just started, when we were stuck with 10-bit RAW images (before processing them to 8 bit JPGs). That's 1024 different values per channel, not a whole lot of room to begin with. Because we're converting a linear signal to a logarithmic one, that means that highest stop in the image takes up 512 of those values.

EDIT: As rightfully pointed out in a reply, 8-bit JPGs are not in linear colour space any more - so this logic does not apply there (however, JPG compression is more harsh on shadow details, since it's lossy, and it tries to move that loss of information to the parts of the image where you're less likely to notice, like the shadows, but we're digressing)

By that logic, the low light data should have a lot more banding than the highly exposed data. Try it with level tools on a RAW file and see for yourself.

So you can imagine that when the dynamic range of (part of) the scene that you want to capture is less than the dynamic range of your sensor, you want to be on the right edge of the histogram (all else being equal - if this causes motion blur due to long exposure it's pretty useless)

Caveat: this is potentially outdated knowledge, perhaps the analog/digital converter in modern cameras actually converts the voltage of a CCD to a (pseudo)logarithmic scale for the digital output, which might partially circumvent this issue (although the sensor is still linear). And nowadays many of the better cameras have 14-bit A/D converters - the usefulness of which also largely depends on the quality of the sensor - so there's a lot more detail in the shadows than before.

Re:A method for improving Milky Way exposures in light pollu... by planteen on Tuesday September 12, 2017 @10:48AM (#15227686)
While the color depth of a JPG is 8-bits, it is not a linear 8 bits. The sRGB color space is gamma corrected (non-linear) and is roughly equivalent to taking the square root of a linear pixel value.

The same thing holds true for a processed RAW image as well.

Re:A method for improving Milky Way exposures in light pollu... by jxcl on Tuesday September 12, 2017 @12:38PM (#15228785)
I'm going to be pedantic and air a pet-peeve of mine. "Raw" isn't an acronym. It's just shorthand for raw image data. It's not even the file extension of most (any?) camera raws. Why does everyone insist on writing it in capital letters?
Re:A method for improving Milky Way exposures in light pollu... by dwringer on Tuesday September 12, 2017 @03:56PM (#15231694)
Another possible reason not outlined the other replies you received to this comment - If I were to say "copy the raw file" someone less experienced may think "okay, take the fresh jpeg file and copy it", interpreting "raw" in a more conventional, non-technical sense. Capitalizing it emphasizes that it refers to the file format, even if not the actual file extension. Sure, I could say "copy the NEF file" or "copy the CRW/CR2 file", but that means I'd have to know whether the user was using Nikon or Canon. "RAW" lets the speaker eliminate ambiguity in non-technical contexts without needing to be so specific as naming the actual extension.
Re:A method for improving Milky Way exposures in light pollu... by vanderZwan on Tuesday September 12, 2017 @02:14PM (#15229813)
Never really thought about that. I think I subconsciously interpret RAW as only meaning "file of unprocessed image data from a camera", whereas raw has more possible meanings. I know this shouldn't matter, because it's never confusing in context what one would mean.

I guess there's also the visual "symmetry" with JPG or JPEG.

Re:A method for improving Milky Way exposures in light pollu... by jpk on Tuesday September 12, 2017 @02:41PM (#15230233)
Probably because it's cased that way in camera menus (correctness notwithstanding).
Re:A method for improving Milky Way exposures in light pollu... by vanderZwan on Tuesday September 12, 2017 @11:30AM (#15228090)
Thanks for the reminder about JPGs, edited in!

When you say processed RAW, you mean after importing to image editing software, right? Which implies you wouldn't see much of a difference in posterisation in the high and low exposure areas

Re:A method for improving Milky Way exposures in light pollu... by planteen on Tuesday September 12, 2017 @11:53AM (#15228306)
Right, after importing to image editing software.
Re:A method for improving Milky Way exposures in light pollu... by vanderZwan on Tuesday September 12, 2017 @12:01PM (#15228386)
Still, for a very long time the RAW file itself used to be linear in storing the signal. Perhaps not any more though.
Re:A method for improving Milky Way exposures in light pollu... by planteen on Tuesday September 12, 2017 @12:16PM (#15228544)
It is still linear as far as I know. And the linearity is quite good, within a few percent. There is a community of astrophotographers interested in making photometric measurements with DSLRs (American Association of Variable Star Observers). I think the harder part of the problem is getting a standard candle for calibration of your DSLR DN values to actual SI quantities.

https://www.aavso.org/dslr-observing-manual

Re:A method for improving Milky Way exposures in light pollu... by vanderZwan on Tuesday September 12, 2017 @12:25PM (#15228637)
Huh, that sounds like a very interesting (but different) problem to tackle, given the vast differences between models.
Re:A method for improving Milky Way exposures in light pollu... by sosuke on Tuesday September 12, 2017 @10:36AM (#15227584)
You should write an article on the subject. Seems there are a lot of interested people in the process and you've got some domain specific knowledge to lay it out nicely.
Re:A method for improving Milky Way exposures in light pollu... by vanderZwan on Tuesday September 12, 2017 @11:58AM (#15228360)
Thanks for the compliment, but I doubt I'll do better than the Wikipedia summary[0] or the original article suggesting the method from 2003, which is still really good[1]. The 2011 followup is also worth a read[2].

If you want a good website in general for explaining photography techniques plus the physics behind it, I highly recommend Cambridge in Colour[3].

By the way, per the example of the second linked essay: if we try to capture 10 stops in 12 bit channels, the darkest stop only has 32 discrete available in the RAW file.

However, this might be somewhat less of an issue these days because most cameras have a really high resolution, and most images are resized for screen displays. So we can average out some banding (and image noise, for that matter).

Example: I have a 20 megapixel camera. A 1080p screens is just 2.1 megapixels. So even for a full-screen export, that's roughly ten "source pixels" per "output pixel". Which would mean that the output pixel, being an, could have 300 different values. The distribution won't be like that of course, but it still should help.

[0] https://en.wikipedia.org/wiki/Exposing_to_the_right

[1] https://web.archive.org/web/20150209012804/http://www.lumino...

[2] https://web.archive.org/web/20150213002736/http://www.lumino...

[3] http://www.cambridgeincolour.com

Re:A method for improving Milky Way exposures in light pollu... by daviesgeek on Tuesday September 12, 2017 @11:06AM (#15227861)
I agree. I’d love to read an article about this!