Who Decides How Much Light

The Decision at the Very Front

Last time I said that the same word, "tuning," names different work depending on which seat you sit in. One seat holds the ISP as its asset and makes that algorithm behave consistently across many inputs. The other holds a specific module as its asset and makes it deliver the required image on top of a given ISP. This installment looks at the first block, AE, through that frame.

AE, or auto exposure, is the job of deciding how much light the camera takes in from a scene. As the decision at the very front, where the image begins, it earns its place as the series' first block. Every block that follows sees only the light AE let through. Getting white right, moving color: all of it starts on top of the brightness AE has already set. Take in too little and there isn't enough signal to even discuss color. Take in too much and information is gone, beyond the reach of any correction downstream.

What AE Decides

AE deals with two things in the end. How much light to take in from the scene, and how to produce that amount.

"How much" comes from measuring the scene: how to divide the frame and where to put the weight when measuring brightness (metering), and what brightness to bring that measurement to (the reference brightness). In backlight, do you save the subject or the background? How far does "the subject" extend? That judgment decides the "how much."

"How" comes from splitting that amount between exposure time and gain. In a mobile module the aperture is usually fixed, so there are effectively only two roads to the same brightness: expose the sensor longer, or amplify the signal more. And finally, how quickly and smoothly should these values follow when the scene changes (convergence). Metering → reference brightness → allocation → convergence. That is the skeleton of the AE block.

The Core Is a Decision About Splitting a Budget

Within that skeleton, what most reveals AE's character is the "how": splitting the amount of light between exposure time and gain.

If you see the amount of light as a budget, AE is the job of allocating that budget across two line items. Fill the same brightness with exposure time and hand shake and subject motion smear. Fill it with gain and noise rises. Neither is free. So at the heart of AE tuning sits a rule that decides "at this brightness, how far do I allow time, and from where do I start raising gain?" It's commonly called the program line: a curve joining (exposure time, gain) pairs across brightness.

In the Two Seats, This Decision Diverges

The two seats grip this rule from different ends.

In the ISP seat, the asset is the AE algorithm itself. The metering engine that measures the scene, the convergence control that carries values through scene changes without shaking, and the shape of the program line. These are the handles this seat moves. But this seat does not choose which sensor or module its algorithm will be paired with. Each sensor's gain-versus-noise behavior and each module's response are given inputs, which is why an AE engine must hold up not on one sensor but across many. In this seat, the sensor's characteristics are not a handle you can move but a wall you cannot cross.

In the module seat, that handle and that wall swap places. The AE algorithm is now a given: it arrives with the ISP this module will run on. And the module, already designed and in production with its sensor, lens, and actuator, is fixed. What can be moved are the values the algorithm leaves open. You seat the program line against this sensor's actual noise and motion-blur behavior, and you adjust metering weights and reference brightness to the brightness and subject priority the client wants.

So "It Went Well" Means Different Things

Both seats share the goal of passing spec. What diverges is what each protects beyond it.

What the ISP seat protects is breadth. An AE engine converging well on one module isn't enough. It has to converge consistently, without hunting, across many sensors and many customers, and it has to expose a parameter surface that the integrating side can adjust to its own module. Only then does that engine get chosen again on the next project. In this seat, AE "going well" is closer to a generality that gets reused.

What the module seat protects is repeatability. This one module passing the client's AE spec (brightness accuracy under defined conditions, convergence speed, no flicker banding) isn't the end. That pass has to hold across the sensor variation that shifts from unit to unit in production. Fit the allocation too tightly to one unit and it falls apart on the next line. In this seat, AE "going well" is closer to a specificity that repeats on this module.

After the Amount of Light Is Set

Once AE sets the operating point, the next question opens on top of it. Does the light taken in land evenly across the frame? Even light whose amount is settled falls off at the edges, and sometimes changes color there.

Having passed through both seats, I've watched up close which handle and which wall these decisions get made between. Next time I move the frame to that unevenness: lens shading.