Why LED Stage Lights Flicker on Camera—and How to Test Them Before a Show

An LED can appear steady to an observer even when its driver is switching output rapidly. A camera does not simply report the average that a person perceives. It records light during each frame, and many sensors expose or read different rows at slightly different times. If the fixture changes output during that interval, the recorded result may contain horizontal bands, a rolling bar, alternating frame brightness or color shifts.

Sony’s official camera flicker guidance explains that banding can occur because bright and dark moments are captured at different sensor positions. It also shows why matching shutter timing to the light cycle can reduce the artifact. This is a timing interaction, not proof that either the camera or fixture is defective.

At high output, an LED may remain on for most of each PWM cycle. At low output, the on-time becomes shorter. The eye can integrate those pulses into an apparently smooth dim level, but a camera exposure may sample unequal portions of successive cycles. The resulting image depends on PWM frequency, pulse shape, dimming algorithm, exposure duration and sensor readout.

The official ETC camera-flicker support note gives a product-specific example: a camera can reveal a rolling bar when fixture PWM aligns poorly with shutter timing, and that fixture family offers a higher-frequency operating mode. The useful lesson is the relationship between timings. Its numeric settings must not be transferred to another product as a universal answer.

Some drivers also combine PWM with current regulation, curve processing or resolution changes across the dimmer range. Two fixtures with the same published frequency can therefore produce different camera results. Likewise, a higher number does not guarantee clean images at every shutter, color, intensity or high-frame-rate setting.

PWM frequency

The number of output-switching cycles per second. It is one important test input, but it does not describe the entire dimming waveform or its interaction with a particular sensor.

Camera mode or high-frequency mode

A fixture setting intended to change dimming or output timing for camera use. Its availability and behavior are model- and firmware-specific, so the selected setting belongs in the test record.

A camera running at 25 fps does not automatically expose for 1/25 second. It may use 1/50, 1/100 or another shutter value. A cinema camera may express the same relationship as shutter angle. High-frame-rate capture usually shortens the available exposure, which can make modulation easier to see because fewer output cycles are averaged within each sampled interval.

With rolling shutter, sensor rows are not read at exactly the same instant. If LED output changes while the readout moves across the sensor, one part of the frame may be brighter or differently colored than another. The direction and speed of a rolling bar can change when shutter timing changes even though the fixture setting remains constant.

Sony lists 1/50 or 1/100 second as useful starting points in 50 Hz regions and 1/60 or 1/120 second in 60 Hz regions, while also noting that the effective value varies by camera and situation. Use those as initial test points, not as a guarantee. For cinema workflows, consult the camera maker’s manual—such as the ARRI ALEXA LF user manual—for the exact shutter controls available on the production body.

Low intensity shortens the active part of a PWM cycle

At a low DMX level, the emitted pulse may occupy a smaller portion of each cycle. That can increase the difference between camera samples and make brightness steps or bands more apparent. Test 1%, 5%, 10%, 25%, 50% and full output rather than jumping directly from blackout to 100%.

Slow fades reveal transitions, not just endpoints

A ten-second fade can expose coarse dimming steps, curve changes or a brief unstable region that a static level misses. Record the whole fade in both directions. Include fades that cross the bottom of the dimmer range, because a visually acceptable steady 5% state may still show a jump while entering or leaving it.

Color mixing activates different driver channels

White, red, green, blue, lime or mixed pastel cues can use different channel combinations and duty cycles. Test the actual palette instead of assuming full white represents every color. Keep color-system selection separate; the RGBL versus RGBW guide covers color architecture, while this procedure deals only with camera timing and dimming behavior.

Phones frequently change shutter, frame rate, exposure, gain, tone processing and anti-banding behavior automatically. Different lenses or recording applications on the same phone may use different sensor crops and readout modes. A clean phone clip therefore describes only that phone state, while a bad phone clip may disappear on the production camera.

Use a phone for receiving inspection or a fast comparison between units, then repeat the decision test with the actual camera body, recording format, frame rate, shutter, lens, exposure level and monitoring path. If multiple camera types will be used, each creates a separate acceptance row.

• Disable automatic exposure, frame-rate switching and anti-banding controls where the phone allows it.
• Record the phone model, application, resolution, frame rate and shutter if exposed by the application.
• Treat the result as a screening observation, never as a fleet-wide camera-performance certificate.
• Repeat slow-motion and live-stream modes separately because their readout timing may differ.

Pre-production camera acceptance checklist

• Identify every camera body, recording mode, frame rate, shutter and high-speed requirement in the project.
• Use a production sample with the intended firmware, DMX personality, dimming curve and fixture menu settings.
• Test static levels, show-critical colors, slow fades, strobe-off states and the lowest levels used on air.
• Fill the frame with the illuminated surface and also test the normal shot distance and exposure.
• Watch a calibrated production monitor and inspect recorded files frame by frame; do not rely on the camera preview alone.
• Name clips with fixture, serial or batch, firmware, camera, frame rate, shutter, intensity, color and mode.
• Repeat a passing setup after power cycle, reset and DMX reconnection.
• Define acceptance language around the tested matrix, not an unqualified “Flicker Free” phrase.

For a wider product shortlist, start with the current Aolait product range and then apply the same matrix to every sample. Pixel-heavy fixtures also require a known channel map; the Bee Eye and pixel-effects guide explains how control depth can change between personalities.

1. Lock the camera frame rate, shutter, exposure and anti-banding controls. Save the recording mode.
2. Confirm the fixture model, firmware, DMX personality, dimming curve and any documented frequency or camera mode.
3. Reproduce the symptom at one fixed intensity and color; remove automatic programs, sound modes and unintended strobe channels.
4. Adjust shutter in controlled steps while keeping the fixture state unchanged.
5. Test each documented fixture dimming or frequency mode, power-cycling only when the manual requires it.
6. Repeat at low intensities, critical colors, slow fades and the actual high-frame-rate condition.
7. Compare another unit with the same configuration to separate a system interaction from an individual-unit difference.
8. Send the manufacturer clips, settings, DMX values, firmware, serial or batch data and the passing or failing matrix.

Contact the manufacturer when the manual does not state PWM or camera-mode behavior, units differ under identical settings, a documented control is missing, or no usable camera combination passes the required matrix. Ask for current model- and firmware-specific data, supported menu settings and a repeatable factory test condition.

If electrical load or fixture configuration is still being selected, keep that work separate from the camera test. The LED wattage configuration guide helps frame output and system choices, while camera acceptance remains a timed capture test.