Pro LED Lighting: DMX Pixel Chase Setup Guide
Table of Contents
- Why Pro LED Lighting Demands a Real DMX Workflow
- Choosing Professional LED Lights for Film: Specs That Decide the Rig
- DMX Lighting Control: Profiles, Modes, and Channel Maps
- Step-by-Step: Programming a Pixel Chase on LED Tube Lights for Film
- Killing LED Light Flicker on Camera Before It Reaches the Sensor
- 2026 Compatibility: Software Versions and Multi-Tube Synchronization
- Conclusion
- Frequently Asked Questions
Last Updated: October 12, 2026
Why Pro LED Lighting Demands a Real DMX Workflow
Pro LED lighting is professional-grade LED equipment built for film, broadcast, and studio work, and it lives or dies by its control layer.
At Walter Lighting & Grip, we supply lighting and grip gear to film and television crews across the country, and we see the same pattern: the hardware is rarely the problem. The setup is. This guide walks through the full pixel chase workflow, from specs to patching, programming, and troubleshooting.
Choosing Professional LED Lights for Film: Specs That Decide the Rig
Professional LED lights for film are chosen on four specs: color accuracy, CCT range, control protocol, and pixel count. Get those right and the rig behaves. Get them wrong and no amount of programming rescues it.
Here is what actually decides a purchase:
- Color accuracy: Look for high CRI and TLCI ratings. The NANLUX Evoke 5000B, for example, carries CRI/TLCI ratings of 97/98.
- CCT range: A 2700K to 6500K span covers daylight through tungsten without gels.
- Control protocol: DMX, Art-Net, CRMX, and app control should all be present.
- Pixel count: More pixels mean finer chases, but more channels to patch.
The NANLUX Evoke 900C adds RGBLAC color mixing with a 1,800K to 20,000K range, which matters when a chase needs saturated color rather than white light.
DMX Lighting Control: Profiles, Modes, and Channel Maps
DMX lighting control is the protocol that tells each fixture what to do, and the profile is the map that tells your console how to speak to it.
Every fixture ships with a DMX profile, sometimes called a personality file, defining how many channels it uses and what each controls: dimmer, color, pixel zones, effects. It is the contract between console and fixture.
1-Pixel vs 4-, 8-, and 16-Pixel Modes
Pixel count decides how much control you get per tube. The trade-off is always channels.
| Mode | Channels Used | Best For | Trade-off |
|---|---|---|---|
| 1-pixel | Fewest | Simple color washes | No chase detail |
| 4-pixel | Low | Basic chases, small rigs | Coarse movement |
| 8-pixel | Medium | Standard chase effects | Moderate channel use |
| 16-pixel | Highest | Fine, smooth chases | Eats universes fast |
A useful rule of thumb: each pixel zone typically needs its own color and intensity channels, so doubling pixel count roughly doubles the channel block, which is why 16-pixel mode can consume four times the channels of 4-pixel mode on the same fixture.
Worked Patch Example: 16-Pixel Tube on a Console
Say you patch one tube in 16-pixel mode with RGB CCT DIM IND control. Each pixel needs its own color and intensity channels, so a single tube can consume a large block of a 512-channel universe.
The fix is planning, not luck. Map your universes before you hang anything.
Here is a worked example you can adapt. Assume a fixture in 16-pixel mode where each pixel uses four channels (red, green, blue, intensity) plus a small global block for master dimmer, CCT, and control, roughly 64 pixel channels plus a handful of global channels, call it a 70-channel block.
| Fixture | Universe | Start Address | Channels Used |
|---|---|---|---|
| Tube 1 | 1 | 1 | 70 |
| Tube 2 | 1 | 71 | 70 |
| Tube 3 | 1 | 141 | 70 |
| Tube 4 | 1 | 211 | 70 |
| Tube 5 | 1 | 281 | 70 |
| Tube 6 | 1 | 351 | 70 |
| Tube 7 | 1 | 421 | 70 |
| Tube 8 | 2 | 1 | 70 |
Reading a Channel Map
A channel map is the fixture's profile laid out as a list. A typical 16-pixel map looks like this:
- Channels 1-4: Pixel 1 (R, G, B, intensity)
- Channels 5-8: Pixel 2 (R, G, B, intensity)
- … and so on through Pixel 16
- Final channels: master dimmer, CCT, and a control or effect channel
When you patch, confirm the console's profile matches that order. If your console shows dimmer first and the fixture expects dimmer last, your chase will run backward or not at all. Most lighting software lets you inspect the channel map before you patch, use that view. Properly aligned channel maps serve as the foundational step for integrating lighting shows across complex pixel arrays and dynamic dance floor surfaces.
Choosing a Mode for the Rig
Match the mode to the effect, not the fixture's maximum. A 16-pixel mode on a tube that only washes a wall wastes universes and console processing; a 1-pixel mode on a chasing tube looks coarse no matter how good the programming is. Most practitioners default to 8-pixel mode for chase work and reserve 16-pixel for hero tubes.
Step-by-Step: Programming a Pixel Chase on LED Tube Lights for Film
Programming a pixel chase on LED tube lights for film takes five steps: set the pixel mode, patch the fixtures, assign the profile, build the chase effect, and sync the timing.
- Set the pixel mode. Choose 1, 4, 8, or 16 pixels on the fixture itself or in its app.
- Set the DMX address. Give each tube a unique start address that matches your patch.
- Patch the fixtures. Add each tube in your lighting software or on the console.
- Assign the profile. Load the matching DMX profile so channels line up.
- Build the chase. Set direction, speed, width, and fade in the effect engine.
- Sync and test. Run the chase across all tubes before the shoot.
Use the fixture's app, like the NANLINK App on NANLUX units, to set pixel count and DMX address without climbing a ladder. Pair over Bluetooth, then confirm the DMX configurator shows the mode you want.
The Chase Parameters That Actually Shape the Effect
Most consoles and media servers expose the same handful of controls. Understanding them is the difference between a chase that reads as motion and one that reads as flicker.
NANLUX Evoke 5000B LED Bi-color Spot Light with Flight Case →
- Speed: How fast the chase steps from pixel to pixel. Too fast and the camera sees a strobe; too slow and it reads as a static gradient.
- Direction: Forward, reverse, or ping-pong. Ping-pong hides the reset seam that a one-way chase shows when it loops.
- Width: How many pixels are lit at once. A width of one is a hard dot; a width of four is a soft band.
- Fade: The ramp between pixels. A short fade looks digital; a long fade looks like a traveling glow.
Previewing Before You Commit
Run the chase in your software's visualizer or on a small test rig before the full hang. A preview catches address collisions, profile mismatches, and universe overflows while they are cheap to fix. If your console supports a 3D preview, use it to check the chase reads correctly from the camera's angle, not just the front.
Scaling the Chase Across Multiple Tubes
A single-tube chase is a demo. A multi-tube chase is the shot. The rule is one source, one profile per fixture type, and a deliberate fixture order.
- Arrange fixture order in the patch to match physical order. If tube 1 is stage left and tube 8 is stage right, patch them in that sequence so the chase travels the way the camera sees it.
- Use phase offset to extend the wave. Instead of running the same chase on every tube, offset each tube's start time slightly so the effect travels across the rig rather than repeating per tube.
- Split universes cleanly. Keep a fixture's channels inside one universe where possible. A fixture split across two universes is harder to troubleshoot and can stutter if the two universes are not refreshed together.
- Test the loop seam. A chase that looks perfect for ten seconds can show a visible jump when it restarts. Ping-pong or a crossfade at the loop point hides it.
A Quick Pre-Shoot Checklist
- Pixel mode matches the intended effect on every tube.
- Every fixture has a unique start address.
- Console profile version matches fixture firmware.
- Universes are mapped and no fixture is split unnecessarily.
- Chase direction matches physical fixture order.
Wireless, Wired, and Network Troubleshooting
Most chase failures come down to a wrong address, a wrong profile, or a dropped signal. Check the address first, then the profile, then the link.
- Wireless: Confirm pairing and check for interference from other transmitters.
- Wired: Inspect terminations and cable runs; a bad end kills the whole chain.
- Network: Verify Art-Net or sACN universes match between console and fixtures.
Killing LED Light Flicker on Camera Before It Reaches the Sensor
LED light flicker on camera comes from a mismatch between the fixture's dimming frequency and your shutter. Fix the frequency and the banding disappears.
Most professional fixtures offer flicker-free or high-speed modes built for camera work.
Cheaper dimming curves cause visible stepping. Look for smooth dimming across the full range, like the 0.1% increments on the Evoke 2400B, which also carries an IP55 rating for tough outdoor conditions.
2026 Compatibility: Software Versions and Multi-Tube Synchronization
Compatibility in 2026 comes down to three things: current firmware, matching protocol support, and a media server or console that speaks the same language.
For multi-tube synchronization, run every tube from one source.
The Creamsource Vortex8 offers a 2,000K to 10,000K range with an IP65 rating, which helps when a chase rig has to survive weather on location.
Pairing and software setup follow the same rule every time: one source, one profile per fixture type, and a test run before the crew arrives.
Conclusion
A pixel chase looks effortless on screen and takes real prep behind it. The crews that get it right plan their universes, match their profiles, and test before the shoot day, not during it.
That is where Walter Lighting & Grip comes in.
Get started with Walter Lighting & Grip and build a rig that runs clean from the first frame.
Frequently Asked Questions
What should you look for in professional LED lights for film?
Prioritize color accuracy and control, not just brightness. Look for CRI/TLCI ratings of 96 or higher, a CCT range wide enough for your work (2700K-6500K covers most daylight and tungsten matching), and flicker-free dimming down to low levels. DMX, CRMX, and Art-Net support matter if the fixture will live on a console. The NANLUX Evoke 2400B, for example, offers 2700K-6500K, CRI 96/TLCI 97, and 0-100% dimming in 0.1% increments.
How do you control LED lights with DMX?
Set the fixture to a DMX profile and mode in its menu or app, give it a start address, then patch that address on your console or software. Each mode uses a different channel count: a 16-pixel tube needs far more channels than a 1-pixel fixture because each pixel occupies its own RGB block. Match the profile on the light to the profile in your software, or the chase will run on the wrong channels.
How do you avoid flicker when filming with LED lights?
Match your shutter angle and frame rate to the fixture's dimming behavior, and avoid running LEDs at very low dim levels where PWM artifacts are most visible. Use high-speed or flicker-free modes if the fixture offers them, and test at your actual camera settings before the shoot day. If flicker persists, raise the dim level and cut light with diffusion or ND instead of dimming further.
How do you set up LED tube lights for a film scene?
Mount the tubes, set each to the correct DMX profile and pixel mode, then patch them in your console or software with sequential addresses. Build the chase by assigning a color and timing to each pixel step, then test the run at camera speed. For multi-tube rigs, sync them over Art-Net or CRMX so every tube follows the same timeline rather than drifting apart.