Why do mobile camera apps offer only discrete shutter speeds instead of any exact exposure time?
Asked 12/6/2016
6 views
2 answers
0
Many iOS and Android camera APIs let developers request a specific exposure duration, sometimes with very fine granularity. But in practice, many manual camera apps show only a list of preset shutter speeds such as 1/2, 1/4, 1/8, 1/12, 1/16, etc. Why do apps usually present discrete shutter-speed steps instead of a continuous value? Is this mainly for photographic convention and usability, or is it also limited by the sensor or camera hardware?
Originally by Photography Stack Exchange contributor. Source · Licensed CC BY-SA 4.0
Photography Stack Exchange contributor
9y ago
2 Answers
3
Now, my question is why most camera apps use a limited set of shutter speed values instead of a continuous value.
Using discrete values rather than a continuous range makes it easier for photographers to select the right value, predict the result, and reproduce any given setting. The usual range of speeds provides enough granularity to achieve any exposure level the photographer is likely to want, so there's little benefit to being able to choose an arbitrary value along a continuous scale. The scale is (approximately) exponential, with the difference between any two full stops being a factor of 2, and that corresponds to the scales for aperture, sensitivity (ISO), and flash power, so it's easy to understand how to compensate for a change in one of the parameters. Read up on the exposure triangle if you're unfamiliar with that concept.
or due to some other factors, e.g., the support of underlying CMOS sensor?
The range of shutter speeds in use today is about the same as what you'll find on a camera that dates back 75 years or more.
I notice that the iOS API provides a function that takes a continuous exposure duration as input.
Tiny cameras like the ones in iPhones have fixed apertures, so the only parameters available for controlling exposure are shutter speed, ISO, and the LED "flash". Also, the exposure parameters are mostly controlled by the computer rather than by the photographer, so there's no reason to use a set of discrete values. That's a very different situation from what you have with a dedicated camera that's meant to be controlled by the photographer.
Originally by user4262. Source · Licensed CC BY-SA 4.0
user4262
9y ago
0
Generated from our catalog & community — verify before relying on it.
Mostly it’s a usability and photography-convention choice, not just an API limitation. Photographers are used to shutter speeds being presented in standard steps because they’re easier to choose, remember, compare, and repeat. Those steps also line up with the exposure system: shutter speed, aperture, ISO, and flash power are commonly adjusted in stops or fractions of a stop, making exposure changes predictable.
A truly continuous control would be awkward to operate and usually offers little practical benefit, since the standard increments already provide enough precision for most exposure decisions.
The APIs can accept very fine time values, but that doesn’t guarantee the camera hardware can deliver every exact value. As Android’s documentation notes, if the sensor can’t do the requested duration exactly, it may use the nearest supported shorter value instead. So the real exposure time may still be quantized by the hardware.
In short: apps use discrete shutter speeds mainly because it’s clearer and more useful for users, while hardware may also support only certain actual timings.
Recommended products
UniqueBot
AI9y ago
Your Answer
Related Questions
Is there an iPhone location-scouting app that can read GPS EXIF from photos in my library?
Why is flash sync speed slower than flash duration?
Why do cameras only offer certain shutter speeds and aperture settings?
Why does an equivalent exposure table differ from the Sunny 16 rule?
Why don't cameras simulate shutter speed by combining many ultra-fast sensor reads?