HTP vs LTP Priorities in Lighting Control: The Rules That Decide Your Look

HTP and LTP are priority rules that decide which value wins when multiple cues fight over the same channel. HTP sends the highest level to the rig, while LTP obeys the latest change so you can layer looks without surprise blackouts, glitches, or color chaos.

Picture this: the room is suspended in a silky blue wash, your movers are creeping into position, and as you bring in a new cue for a slow build, the front light on the headliner suddenly snaps down before it fades up again. Vibe: broken, crowd: distracted, you: angry at the desk. Once your priorities are set right, you can run a steady base look, slam in color hits, ride movement chases, and still keep key faces, crowd haze, and safety light locked in. This guide breaks down what HTP and LTP really do on real consoles, how they show up in DMX land, and how to plot your priorities for smooth, high-impact parties and shows.

The Battle For Each Channel: HTP vs LTP Basics

Every DMX-based system is constantly throwing numbers at your fixtures. In a typical DMX512 universe, the controller sends out 512 channel values around 33 times per second, each between 0 and 255. Your rig reads those values as intensity, color, position, and so on. The twist is that modern shows rarely run a single “master cue”; you have multiple playbacks, executors, and faders all trying to command the same channel at once.

HTP, or Highest Takes Precedence, is an intensity-merging rule. A common explanation goes like this: if two playbacks hit the same dimmer channel at 50% and 75%, the fixture will output at 75%, not an average. If the 75% playback fades out, the fixture smoothly settles back to 50% instead of dropping to zero, because that lower level is still coming from another active cue.

LTP, or Latest Takes Precedence, is a “last word wins” rule. For LTP channels, the desk looks at which cue most recently changed that parameter and sends that value, ignoring other sources. Industry guidance highlights that LTP is the standard for non-intensity attributes such as color, gobos, and pan/tilt: the last cue to touch color sets the color, regardless of what earlier cues requested.

In other words, HTP mixes intensities like multiple dimmer hands on the same fader, while LTP behaves more like a switch for your look-defining attributes.

Many professional console manuals describe exactly this split: dimmer and intensity channels are treated as HTP, while color, position, and other attributes are LTP, so you can safely layer brightness while still getting crisp scene changes.

HTP Priorities: Building a Safe, Punchy Base Layer

For intensity, HTP is your safety net and your secret sauce. When dimmer channels use HTP, multiple playbacks can share the same fixture without stepping on each other in dangerous ways. For example, if one playback keeps a fixture at 30% as a security or house level and another playback bumps it to 100% for a hit, the fixture never drops below 30% until every relevant playback is down.

From a show-design point of view, this lets you build a firm “floor” of light. You might park the DJ and audience wash at 40% on one executor, then use other faders for strobe, crowd sweeps, or accent beams. Because those intensities merge using HTP, you can ride the energy up and down without losing faces or sightlines.

Some consoles go even further with an “HTP always active” option. When that mode is enabled, HTP channels respond purely to fader level and ignore release commands: as long as the fader is above zero, the intensity contribution from that playback is in the mix. This is perfect for a global “room brightness” master or a permanent safety wash, but it also means you must be intentional about which playbacks get this treatment so you do not accidentally leave a ghost layer of light in the rig.

Energy and comfort come along for the ride. Industry research shows that dimming and high-end trim (task tuning) are foundational for energy-efficient, comfortable spaces. Guidance from networked lighting control providers notes that running LEDs at about 80% of their maximum output can yield notable savings with little visible loss. If your base looks live on HTP intensity playbacks, you can set that base around 70–80%, then stack effects on top without blowing past your desired maximum, because no cue can push a dimmer above its programmed highest active level.

The downside of HTP is that it can make intent murky when you want a cue to truly “own” intensity. If you forget that an older playback is still contributing light, you may see fixtures refusing to go fully dark even when the new cue says 0%. That is usually a sign that another HTP source is still shouting, not that the fixture is misbehaving.

LTP Priorities: Owning Color, Position, and Drama

LTP, the Latest Takes Precedence rule, gives you crisp control over how the stage actually looks. For color, gobos, and pan/tilt, you almost always want the last cue or playback to be in charge rather than blending values.

Consider color: one cue has your fixtures deep blue, another cue hits them with saturated red. In an LTP world, if you fire the red cue after the blue, the stage turns red and stays red until something else changes color. That clarity is why major consoles treat color channels as LTP by default.

LED color mixing is where it gets spicy. Training materials often point out that each RGB channel is technically just an intensity. If you treat red, green, and blue as HTP, you can do creative tricks such as running a “red scene” and a “blue scene” on separate faders; when both are up, the fixture outputs magenta-style mixes because the highest value for each color channel is active. It is fun and flexible, but it can also create strange intermediate colors during manual crossfades.

If you map those same color channels as LTP, fixtures obey the last cue that touched each color channel. Crossfades between looks are cleaner and more predictable, but you lose some of that additive layering magic. There is no universal “right” answer for LEDs; the choice depends on whether you prioritize blended color layers or sharply defined looks.

There is a comparable nuance with intensity itself. Historically, as one forum discussion recounts, intensity channels migrated from primitive “last handle moved” behavior to HTP with electronic dimmers to avoid dips in crossfades. But that same discussion demonstrates that treating certain dimmer channels as LTP can be powerful in complex cueing, because each channel can carry its own background fade independently, letting you run many overlapping timed cues without the classic HTP tug-of-war.

The trade-off is simple: HTP gives you safe, shared ownership of brightness; LTP gives one cue at a time clear authority over a parameter. Use LTP wherever you want the rig to snap to a statement.

Priority Games on Real Consoles

Layered Intensity, LTP Attributes, and Priority Playbacks

A classic hybrid model on many consoles uses HTP for dimmer and intensity channels and LTP for all other attributes. The fader position scales HTP outputs, so moving the fader to 50% brings every intensity in that cue to half its programmed values. LTP attributes, such as colors or positions, trigger as soon as the fader rises above zero and either follow programmed fades or snap, depending on the cue’s mode.

In practice, this lets you stack multiple cues: a slow movement look, a color theme, and a key-light playback all at once. Some systems also expose high-priority playbacks so that critical fixtures, such as the star performer’s key light, do not get overridden by other playbacks using the same fixtures. That is HTP and LTP plus another layer of priority, used to guarantee that the most important look wins when there is a conflict.

HTP Always Active and Fader-Controlled Release

Some consoles introduce an “HTP always active” setting for cue stacks, separating activation from output. With that option, HTP channels in the playback output whenever the fader is above the activation threshold and are released only when the fader returns to zero. Release buttons do not affect those HTP channels; the fader is the only off switch.

This is tailor-made for atmospherics like haze or room brightness in party environments. You can keep haze at a subtle level with the fader, layer show cues on top, and know that no release action or other playback will suddenly kill the haze level, because its HTP contribution is locked to the fader rather than to cue activation state.

When Priorities Go Wrong: The Snap-to-Zero Problem

A lighting control forum thread shows exactly what happens when priorities are not doing what the operator expects. One scene parks a fixture at 50% intensity. Another scene is programmed as a two-step fade from 0% to 100%. When the second scene is brought in with the current LTP-style behavior, the fixture first snaps down to 0% and then fades up to 100%, ignoring the existing 50% level from the first scene.

The operator’s request in that example is for per-channel HTP/LTP selection so that the second scene’s fade would start from the live 50% intensity already on stage, creating a continuous climb instead of a jarring drop then rise. That single example captures the core creative risk of a rigid LTP model on intensities: if new cues always start from their own stored value, you can accidentally cut light before rebuilding it, which feels wrong in a live show.

LTP Intensities for Complex Cue Stacks

Other forum explanations show the opposite extreme, where LTP on intensities is leveraged as a feature. In that model, each LTP channel tracks foreground and background fades; a cue is considered “running in the background” until all its channels finish fading. This allows dozens or even hundreds of cues to overlap, each with its own timing, without intensity values fighting under HTP.

For high-end theatrical or deeply scripted shows, that kind of per-channel LTP behavior on dimmers can deliver precise transitions. The price is that you must be very intentional about cue programming and understand exactly how your console resolves competing levels, or you will get unexpected results.

Designing Your HTP/LTP Map for High-Energy Shows

Start by deciding which parts of your rig are non-negotiable. Front key on performers, minimal house and egress lighting, and any safety-critical fixtures should live on HTP dimmer channels and often on dedicated, high-priority playbacks. That way, even if you stack aggressive effect cues, the highest of those safe levels will always hold.

Then, define your base vibe. Use HTP for your core wash and room fill, and program those cues with tuned maximums rather than full blast. Research on high-end trim and guidance on running LEDs below 100% both support the idea that you should cap output for comfort and energy savings. If your “100%” fader actually corresponds to 70–80% output in the fixtures, you can push the room bright when the music peaks without overlighting faces or wasting power.

Next, be deliberate about where you want LTP. Colors, gobos, and positions for movers should almost always be LTP so that the last cue you fire defines the look. When you want a crisp change from icy blue beams to hot magenta sweeps, LTP keeps the transition clean. Save HTP on color channels for intentional tricks, such as layering a slow red “heat” look with a blue “cool” chase on RGB fixtures when you actually want intermediate mixes.

Finally, tune your transitions. If you are seeing snaps to black when bringing in new cues, revisit how those channels are prioritized. The snap-to-zero examples from forum discussions are a reminder that an LTP-only mindset for intensities can undercut smooth fades. Conversely, if your tightly scripted sequence never quite lands the intended blackouts or quiet moments, check whether an unseen HTP source is still contributing light and whether selective LTP on certain dimmer channels would give you the precision you need.

When all of this is aligned with the broader control system—dimming, high-end trim, scheduling, and occupancy sensing from networked controls, as recommended by industry organizations and national energy agencies such as the U.S. Department of Energy—you end up with a rig that not only looks electric but also runs efficiently and comfortably every night.

Dial in HTP and LTP like this and your rig stops being a collection of fixtures and becomes a playable instrument. Your base looks stay rock solid, your hits land exactly on the beat, and your fades feel like music, not accidents. Get the priorities right, and every push of a fader becomes a confident move, not a gamble.

References

1. https://www.energy.gov/energysaver/lighting-controls
2. https://lightingcontrolsacademy.org/best-practices-for-lighting-control-narratives/
3. http://www.qlcplus.org/forum/viewtopic.php?t=7803
4. https://designlights.org/news-events/news/lighting-control-strategies/
5. https://facilityexecutive.com/lighting-controls-in-the-workplace-from-dim-to-dynamic
6. http://forum.thelightingcontroller.com/viewtopic.php?t=6727
7. https://support.actentertainment.com/knowledgeBase/7853431
8. https://www.eliteelectrical.co.uk/optimising-lighting-control-systems-a-guide-to-efficiency/
9. https://www.csemag.com/your-questions-answered-lighting-and-lighting-controls-best-practices/
10. https://hereandafter.com/energy-optimisation-of-current-lighting/