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.

Have you brought in a new cue and seen the front light dip to black before fading up? That is usually a merge-priority problem. This guide explains what HTP and LTP do on a lighting console and how to set them so your base looks stay stable while you add color and movement.

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 up to about 44 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. For example, 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. 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.

Most consoles use 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 Base Layer

For intensity, HTP is your safety net. 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.

HTP also makes brightness easy to manage. If you program your base wash at around 70–80% and keep effect cues at similar maximums, stacking them never pushes faces past that level, because HTP outputs the highest active level rather than adding levels together.

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 adds a twist. 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. 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. HTP on dimmers avoids dips in crossfades, but 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

Here is what happens when priorities do not do 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.

What the operator needs here is 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

Some consoles take the opposite approach and use LTP on intensities 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 complex 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 look. Use HTP for your core wash and room fill, and program those cues with tuned maximums rather than full blast. Capping output also keeps LEDs cooler and extends their life. 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 example above is 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.

Rule of thumb: keep intensity on HTP, keep color, gobo, and position on LTP, and put safety or key light on a high-priority playback. If a fade snaps to black or a light will not go dark, check the merge rule first.