The Priority Hierarchy
Everything in Blackout follows a strict priority hierarchy. From highest to lowest priority:
1. Park (Coming Soon)
Highest Priority
When completed, this feature will allow you to "park" fixture values
Parked values cannot be overridden by any other control source, including the master fader
Use for critical safety lighting or fixtures that must remain at specific settings
Parking a Fixture, parameter, or output address at a certain value Universe 4 Address 510: 4/510 @ 255 is the topmost priority. Nothing, not even the Master Fader can modify this value. Parked values cannot be recorded into Looks.
This is usually done to park values so that one cannot easily change them. This is often used in a similar way to FREEZE or during a live event where you don’t want anything you do in the console to affect a certain group of lights such as background lights uplighting a banner. Park is much harder to release values from on purpose whereas FREEZE can easily be unfrozen quickly. Parked Fixtures/parameters will have a tree icon next to them.
2. Master Fader
Controls overall intensity output
Can affect all fixtures below it in the hierarchy
Cannot override parked values (when park feature is implemented)
The Master Fader is used for inhibiting Fixture intensities globally throughout the app no matter what state or Fader has control, except for parked values.
3. Inhibitive Faders
Purpose: Limit maximum values that fixtures can reach
How it works: Sets a ceiling that other controls cannot exceed
Example: Set an inhibitive fader to 50% intensity - no other fader or command can make that fixture go above 50%
Even super priority faders and the command line cannot override inhibitive limits
Useful for safety restrictions or venue limitations
This priority state is used for overriding levels. Inhibitive Faders can be used to lower the intensity, regardless of what is set in other priority levels.
4. Effects
Positioned below inhibitive faders, so they can be limited by inhibitive controls
Cannot be overwritten by anything below them in the hierarchy, including super priority faders
Run independently once started, making them reliable for consistent automated lighting
5. Super Priority Faders
Special behavior: Starts as additive, becomes non-additive when reaching maximum
Default settings: Auto stop is turned OFF by default
Use case: Perfect for live adjustments during critical cues
Cannot override effects or inhibitive faders
Command line cannot override super priority faders
Ideal for "throw that light on a fader for this cue" scenarios
This is the highest level of priority for a Fader. This priority is typically reserved for very critical objects that must always take precedence in your lighting setup, regardless of any other settings or changes happening on lower priority levels. By default, Super Faders are Exclude from Record which means the values they are affecting will not be recorded into any Looks you create.
6. Freeze
Will convert command line values into a frozen/super priority state
Allows you to play looks while maintaining manual adjustments
Manual values remain unchanged until unfrozen
FREEZEis a way for users to temporarily FREEZE Fixtures so that the user can still play through Looks without those Fixtures changing.This is most often used while programming a live show. A Lighting Designer is very quick to call out changes and often wants to see a temporary change they are making carry through a transition. The lighting programmer, FREEZES those changes, then is able to press
Goand play the next Look. Those values are still frozen and do not adhere to the next move/change in the played Look. At this point, the programmer usually UNFREEZES a selection, updates their Look and discards the rest of the frozen Fixtures values or records them elsewhere.FREEZEcan be easily turned on/off as it is a workflow tool vs PARK (see above Priority #1).
7. Command Line/Manual Values
Can overwrite any fader below super priority
Important change: If you dump a fader and bring it back up, it will retake control from manual values
Cannot override super priority faders, effects, or inhibitive faders
The command line allows the user the ability to give precise values to targets in batches. This priority level is the same as changing a Fixture via the Fixture Controls Sidebar as those are still manual changes.
Note that only LTP, HIGH, and HTP (and frozen fixtures) can be overwritten by the commandline/manual changes.
8. HTP (Highest Takes Precedence) Faders
Uses intensity values for comparison to determine output level
Mixed behavior: Other parameters (color, position) use LTP since there's no "higher" value for different colors or positions
Good for traditional intensity control where multiple sources might control the same fixtures
In this mode, for intensity parameters only, the highest value from any control source is used. This is typical for controlling the brightness of lights, where you might have multiple Faders or inputs affecting the same light, and you want the highest intensity value to be the one that is output.
9. High Priority Faders
One step above default LTP
Cannot be overwritten by standard LTP faders
Useful when you need one control to take precedence over standard playback
This priority is a step above the normal LTP. It means that any command given at this priority level will override commands in the standard LTP priority. This is useful when you have a particular control or effect that you always want to take precedence over others set in the normal LTP mode.
10. LTP (Latest Takes Precedence) Faders
Default priority level
Most recent adjustment takes control
Fundamental concept: Whatever you touch last controls the fixture
Applies to both faders and command line operations
This is the standard mode for handling conflicting control inputs. In this state, if there are multiple commands for the same control channel, the most recent command takes precedence over the others.
Key Priority Concepts
LTP vs HTP
LTP (Latest Takes Precedence): The most recently adjusted control takes over - essential concept for lighting control
HTP (Highest Takes Precedence): The highest intensity value wins, but other parameters still use LTP logic
Additive vs Non-Additive Faders
Additive (default): Adds to existing fixture values for smooth transitions
Non-additive: Jumps directly to fader level, taking immediate control
Super priority faders have special behavior: additive until maximum, then non-additive
Auto Start/Stop Settings
Auto Start: Fader activates when moved up from zero
Auto Stop: Fader deactivates when returned to zero
Super priority faders default to auto stop OFF for maintained control
Overwritten Setting
When ON (recommended): Higher priority faders will turn off lower priority faders controlling the same parameters
When OFF: Lower priority faders remain active and will resume control when higher priority faders are turned off
Practical Applications
Live Performance Scenario
Use super priority faders for critical live adjustments that must not be overridden by other playback.
Safety Applications
Use inhibitive faders to set maximum safe levels for fixtures in venues with power or heat restrictions.
Layered Control
Think of faders like Photoshop layers - each fader adds a "layer" of control that can be shown or hidden without destroying the layers below.
Temporary Adjustments
Use high priority faders when you need temporary control that shouldn't be overridden by standard playback sequences.
Tips for Success
Start with LTP: Most faders should use LTP priority unless you have a specific need
Use inhibitive sparingly: Only when you need absolute limits
Super priority for live work: Reserve for hands-on adjustments during shows
Understand the stack: Like Photoshop layers, each priority level adds to or modifies the output
Keep overwritten ON: Helps maintain clear control hierarchy
View States
Use the top navigation bar to help visualize what's controlling each parameter, showing whether control comes from faders, sequences, effects, or other sources.
Understanding priorities is like learning a new language - take time to practice and experiment with different scenarios to build confidence with the system.