StageCraft AI

What is StageCraft AI?

StageCraft AI is where a show is planned on paper before it is built in a venue. It checks a DMX patch for overlapping addresses and fixtures that run past channel 512, and finds the next free address for a fixture. It checks a stage plot for elements outside the stage or on top of each other, an input list for duplicate channels and reused wireless frequencies — with phantom power on a dynamic mic or DI flagged as a warning for a person — and a run of show for its total running time against curfew. Cue lists are checked for duplicate numbers and for cues that fall outside their segment. The results export as a patch sheet CSV, an input list CSV and a self-contained JSON show file for offline simulation and manual import into a console's own tools. StageCraft AI sends nothing to a lighting console, a DMX interface, an Art-Net or sACN node, QLab, Ableton or Resolume; live show control does not exist in this release, by design.

Problems it solves

• Find DMX address overlaps and fixtures past channel 512
• Check that stage plot elements fit on the stage and do not collide
• Catch duplicate input channels and reused wireless frequencies
• See whether the running order fits before curfew
• Hand a lighting programmer a patch sheet instead of a screenshot

Key capabilities

Show Planning Exports

Validate a DMX patch, input list, stage plot and run of show, and export files a production imports by hand. Nothing is sent to show equipment.

Human Approval Gates

Anything with an outside consequence — a pitch sent, a product published, a campaign sent, a booking committed — waits for a person with the named permission.

Deterministic Policy Engine

Rules, not inference, decide what is allowed to proceed — so a model can advise and never authorise.

How it is built

DMX patch validation

Exact interval arithmetic per universe, with the next free address for a fixture.

Stage plot checks

Positions in metres from downstage left; elements must sit on the stage and not overlap.

Input list checks

Unique channels, one use per wireless frequency, and phantom-power warnings for a person to review.

Run of show

Segment start and end times, total running time, and whether it fits before curfew.

Exports

Patch sheet CSV for manual import into grandMA, ChamSys MagicQ or ETC Eos; input list CSV; a JSON show file; a cue list to build QLab from.

How it works

How the work is structured, and what each step's output rests on.

1. 1

   Draw the plan

   Source

   Stage plot, input list, fixtures, cues and running order.

2. 2

   Validate

   Observed

   Exact checks on addresses, positions, channels, frequencies, cues and timing.

3. 3

   Review and approve

   Human-verified

   A person with stage-approval permission signs off the plot.

4. 4

   Export

   Observed

   Files the production imports into its own tools by hand.

Example use cases

Each example has its own page you can read and share.

Ask StageCraft AI

Illustrative examples. Results depend on your own data.

• “Does anything in universe 2 overlap?”
• “Where can a 16-channel fixture go in universe 1?”
• “Does the set fit before an 11pm curfew?”
• “Export the patch sheet for the lighting programmer.”

Questions

Can StageCraft AI run my lights or cues?

No. It does not connect to or send anything to lighting consoles, DMX, Art-Net or sACN networks, QLab, Ableton or Resolume. It plans, validates and exports; live show control is out of scope in this release by design.

Which consoles can use the exports?

The patch sheet is a CSV for manual import into grandMA, ChamSys MagicQ or ETC Eos. QLab is built by hand from the exported cue list.

Does a clean validation mean the show is safe?

No. The checks are arithmetic on the plan. Anything safety-critical — rigging, power, pyrotechnics, haze, crowd flow — needs review by a qualified technician.