Program a laser show as a controlled chain: document the exact projector and class, applicable jurisdiction and authorization conditions, venue envelope, audience and worker access, responsible operator, control route, and stop plan. Then version the profile, zones, masks, patterns, parameter states, colors, sync sources, cues, fallbacks, rehearsal results, release file, and change log.
This guide teaches that general workflow. It does not authorize a show, calculate exposure, teach audience scanning, or establish site-specific safety, scan-fail behavior, compatibility, installation, or venue approval. Creative output begins only after the applicable preflight fields are resolved for the real show and recorded.
Complete the authorization and operating preflight
Create one gate before opening a cue editor or enabling projector output.
| Field | Record | Owner | Status |
|---|---|---|---|
| Jurisdiction and authorization | Applicable location, current conditions, approval path, and supporting record | Responsible show or authority contact | Resolved or stop |
| Projector and class | Exact model, variant, asset ID, label, class, and current documentation | Equipment owner | Resolved or stop |
| Venue envelope | Current drawings, intended effects, direct and reflected paths, targets, terminations, and uncontrolled areas | Venue and responsible technical owner | Resolved or stop |
| Access and operation | Audience and worker access, operator, surveillance, communications, and accessible stop controls | Named responsible parties | Resolved or stop |
| Outdoor boundary | Indoor, enclosed, outdoor, or open-sky status and applicable review | Show owner | Resolved or stop |
These unknowns are nonblocking verification boundaries for publishing a general article. For any real show, however, every unresolved item that applies is an operational stop condition before projector output.
Within United States federal scope, use the current FDA laser light-show page, FDA EPRC variance application process, and 21 CFR 1040.11 for their exact roles. They do not create an approval for the reader's show. For a United States outdoor or open-sky operation that may affect navigable airspace, apply the separate FAA AC 70-1B boundary.
How this guide selects a laser programming system
This is a SHEHDS-owned guide using first-party commercial pages for candidates and authoritative sources for operating boundaries. It is not an independent authorization, exposure, scan-fail, compatibility, reliability, or venue test.
| Step | Rule |
| Include | Require exact identity, class and authorization fit, documented profile and interface, venue envelope, operator, stop and fallback plan, qualified tests, records, and change control. |
| Exclude | Remove candidates with unresolved identity, authorization, access, zones, masks, scan-fail evidence, interface or software fit, safeguards, or outdoor review when applicable. |
| Verify | Map every candidate to the exact show boundary, controller route, cue needs, evidence, owner, test, stop condition, and release status. |
The candidate universe is current SHEHDS laser-light entries, including the exact examples below. Evaluation weights are 30% jurisdiction and authorization fit; 20% audience, worker, path, termination, and control envelope; 15% exact profile and interface fit; 15% setup, test, stop, fallback, and change control; 10% venue and effect fit; 5% service and records; and 5% market and budget fit. Evidence is current through August 18, 2026. Verify price, stock, shipping, warranty, accessories, licensing, firmware, and regional availability at purchase time. Browse laser lights only after these rules are applied.
Build the device identity, profile, and route register
The show file must travel with an exact-system record: model, variant, asset ID, manufacturer-listed class, label and report references, firmware, profile source, channel mode, interface, connector, protocol, software build, controller, output route, owner, file version, source date, and verification status.
| Documentation example | First-party fields captured August 18, 2026 | Still verify before use |
| Constellaser 3W laser light | Page lists Class IV and stated DMX, PowerCon, app, sound, auto, ILDA, and software-support fields | Exact variant, current manual and reports, authorization fit, profile, interfaces, firmware, venue envelope, safeguards, tests, and commerce |
| Constellaser 6W laser light | Page lists Class IV, up to 25 KPPS, pattern-animation, DMX/RJ45, PowerCon, ILDA, and software-support fields | Exact variant, scan angle and method, current records, profile, authorization, scan-fail evidence, venue, tests, and commerce |
| 3000mW moving-head laser variants | Page lists variant-specific DMX channel modes plus DMX/menu, sound, and auto modes | Selected variant, manual, firmware, profile, route, compatibility, classification records, operating boundary, and tests |
These are documentation examples, not approvals or rankings. Keep every field attached to its exact page and variant.
Define zones, masks, targets, terminations, and no-go areas
Represent the actual venue envelope in the programming package. A zone describes an intended output area. A mask or blanking control limits programmed output. A target or termination records where the effect is intended to land or stop. A no-go area records a prohibited programmed path. None of these labels is a portable coordinate or safety conclusion.
| Projector | Zone | Mask | Target or termination | Access state and path | Owner | Test and approval | Version |
| Exact asset and route | Drawing or geometry source | Exact control and state | Intended surface or volume | Audience, worker, uncontrolled, direct, reflected, or camera view | Named role | Evidence, result, approver, and status | File and date |
The FDA Form 3640 is used here only for its United States reporting fields concerning show descriptions, paths, people, targets, safeguards, controls, tests, records, and changes. HSE laser display guidance is limited to United Kingdom workplace planning and handover scope. This article does not complete either process or validate a site-specific zone, mask, exposure control, scan-fail response, installation, or approval.
Build a pattern library by visual job
Name patterns by the job they perform instead of filling one page with untracked thumbnails.
| Pattern ID | Source | Visual job | Exact profile | Zone | Allowed modifiers | Color | Trigger | Fallback | Status |
| Versioned ID | Factory, software, or authored source | Beam, graphic, text, logo, mapping, or animation when supported | Projector and software version | Accepted destination | Only documented transforms | Palette ID | Cue or manual source | Known replacement or stop state | Creative test and release state |
Pattern names, counts, formats, editing features, and transformations remain exact-product and exact-software questions. Movement, point count, visual smoothness, or a smaller pattern does not establish audience safety or authorization.
Record speed and point-density fields without a safety formula
Treat every speed-related field as a versioned parameter, not a universal physical measure.
| Field | Version | Value or state | Method | Pattern and zone | Owner | Creative test | Safety evidence | Status |
| Exact software or profile label | Build and profile | Recorded setting or state | Unit, scale, scan angle, or test method when documented | IDs from the approved records | Named programmer | Visual and cue result | Separate qualified record or unresolved | Release or stop |
The Constellaser 6W page's listed up to 25 KPPS field lacks an accepted scan angle and independent test method. Do not extrapolate scan-fail behavior, exposure, fidelity, audience-effect suitability, or a safe setting from it. The same boundary applies to scan speed, animation rate, point density, pattern choice, zone size, power, and software presets.
Build the color system and verify the sync handoff
Create named palettes with exact projector route, software or profile version, pattern role, transition rule, surface and camera test, owner, and fallback. Do not promise color accuracy or matching across projectors.
For synchronization, record the source, interface, route, version, owner, timing test, loss behavior, manual override, and fallback. Manual cueing, sound mode, BPM, MIDI, timecode, console, app, or network triggering enters the plan only when the exact system documents and onsite test support it.
| Sync source | Interface and route | Version | Timing test | Loss behavior | Operator | Fallback |
| Exact music or cue source | Supported connection and destination | Hardware, profile, software, and show file | Marker, latency or drift observation, and result | Expected response when the source is missing | Named owner and override | Known cue, hold, or stop state |
Compare DMX controllers only after these fields are defined. Clean timing, a supported channel mode, or deliberate color design does not prove compatibility, authorization, exposure control, or safe operation.
Build the cue-state matrix
Turn every look into a reproducible configuration object. Version the cue ID, projector and profile, route, zone and mask, pattern source, speed or point-related state, size and position, color, trigger, transition, access state, responsible operator, fallback or stop action, test date, approver, and restore result.
| Cue | Creative state | Operating boundary | Release status |
| Static test | Exact pattern, color, intensity state, size, and position | Projector, route, zone, mask, access state, owner, and stop action | Controlled test only |
| Build or peak | Versioned pattern, parameters, palette, sync source, and transition | Same accepted show-specific records plus atmosphere and viewpoint when relevant | Release only after approved tests |
| Transition | Source and destination cues, timing, and operator action | No unapproved route, zone, mask, or access change | Pass, revise, or block |
| Blackout or stop-output cue | Exact programmed response | Accessible stop-control and responsible action remain separate verified records | Test result and owner |
| Fallback and restore | Known reduced state, isolation, rollback, and recovery | Applicable unresolved item remains a stop condition | Restore result and new version |
A cue record organizes creative state; it does not create authorization, exposure control, scan-fail performance, compatibility, or venue approval.
Program fallback, stop-output, and restore states
Do not wait for a fault to invent an operator response.
| Trigger | Detected by | Expected output | Operator action | Stop control | Fallback | Restore test | Owner and record |
| Wrong route or unexpected path | Operator or surveillance | Show-specific documented response | Use the approved stop and communication plan | Exact verified control | Output isolated or accepted fallback | Confirm identity, path, and boundary before restore | Named person, time, fault, and version |
| Signal, software, interface, sync, scanner, or projector fault | Exact monitoring method | Product- and system-specific response | Follow current approved procedure | Verified accessible control | Known state or isolation | Fault corrected, tests repeated, approval recorded | Technical owner and change log |
| Invalid file or operator error | Version check or operator | No projector output until the accepted version is confirmed | Load rollback or stop | Verified control | Approved rollback | Full cue and restore check | File owner and approver |
A generic blackout value, mask, software command, interlock label, or scanner-speed field is not proof of a safe state. The exact safeguards, procedures, authorization conditions, and qualified tests govern.
Rehearse and release the show file
Use a controlled release gate between creative programming and operation:
- Review the identity, profiles, routes, zones, masks, cue versions, and responsibility records offline where useful.
- Confirm the exact equipment and routes during a controlled no-audience onsite setup.
- Validate zones, masks, targets, terminations, direct and reflected paths, cues, transitions, communications, surveillance, and accessible stop controls under the approved process.
- Run the approved fault, stop, fallback, and restore drills.
- Record the evidence, owner, pass or block result, approver, release version, backup, and rollback copy.
Testing does not replace required measurements, qualified analysis, authorization, installation review, or venue approval. Audience-scanning evaluation remains outside this article. If a show-specific item is unresolved, do not release projector output.
Run the pre-open laser show check
Before every show, confirm the exact asset and release version, output route, zones and masks, targets and terminations, access state, communications, surveillance, stop controls, cues, sync, fallback, restore, faults, authorization or venue changes, named operator, and stop condition.
Record each item as pass or stop, with its owner, expected record, fallback, and change status. This runbook releases only the accepted show-specific configuration. It is not a universal legal, exposure, engineering, compatibility, scan-fail, safety, or venue approval.
Maintain the change log and reopen review when needed
Record every issue, evidence source, owner, modification, affected projector, profile, interface, route, zone, mask, pattern, cue, venue, access boundary, stop behavior, maintenance action, approval, retest, release version, and rollback copy.
Reopen review after a relevant equipment, firmware, software, profile, interface, route, venue, access, zone, mask, safeguard, authorization, or operator change. In United States scope, use the current regulator process to determine whether a change affects reporting or authorization. General guidance cannot decide that question for a particular show.
Build your SHEHDS laser programming comparison brief
Record the jurisdiction and authorization conditions, projector and class, venue map and access controls, operator, stop and safeguard plan, profiles and interfaces, zones and masks, pattern and cue needs, sync source, fallback, test records, change process, market, and budget. SHEHDS can use the brief to narrow current documented options and identify the evidence and tests that remain open.
Frequently Asked Questions
What information must I verify before programming a laser show?
Verify the exact projector and class, jurisdiction, authorization conditions, venue envelope, access state, operator, control route, safeguards, stop plan, profiles, interfaces, and current records. Any applicable unresolved item stops real-show projector output.
Is DMX enough to program patterns, speed, and color?
Only when the exact projector, variant, profile, mode, channel map, controller, route, firmware, and supported behaviors have been verified. DMX control alone does not establish authorization, exposure control, scan-fail performance, or compatibility.
What is the difference between a laser zone and a mask?
A zone records an intended output area; a mask or blanking control limits programmed output. Both belong to the actual venue file and require show-specific evidence, tests, ownership, and approval.
Does a faster-moving pattern make audience scanning safe?
No universal speed or pattern rule supports that conclusion. Audience scanning requires separate qualified analysis, applicable authorization and safeguards, exact equipment evidence, controlled tests, and responsible approval; this tutorial does not teach it.
How should I sync laser cues to music?
Choose a supported manual, timeline, sound, BPM, MIDI, timecode, console, app, or network handoff. Record the exact route and versions, test timing and loss behavior, assign an operator override, and program a fallback.
What should the operator test before the show starts?
Check the released asset and file versions, routes, zones, masks, targets, access state, communications, surveillance, stop controls, cues, sync, fallback, restore, faults, changes, and named stop condition before enabling output.
Program the file, preserve the operating boundary
A repeatable show links exact identity to zones, patterns, parameters, color, sync, cues, failure states, release records, and change control. Complete the comparison brief so SHEHDS can help narrow documented options and list the remaining evidence and tests.
