Cue editor

The cue editor is the main workspace for creating, modifying, and organizing individual cues in a script. Arthoff provides a set of built-in cue types and can support custom types through plugins or future integrations.

Editor interface

📋 Cue and section list

The left side shows the section and cue tree. Use it for navigation, drag and drop, and understanding the script structure.

✏️ Editing panel

The center panel contains the properties of the selected cue, including shared fields such as name, description, and section, plus type-specific fields such as dialogue text, DMX channels, or effect parameters.

👁️ Preview and actions

The right side previews how the cue behaves in live-oriented views. Depending on the cue type, this can include dialogue presentation, DMX values, or audio information. Action buttons include cancel, save, duplicate, and delete.

Adding a new cue

Editing an existing cue

Inline editing

For selected cue types such as Dialogue and Comment, the main content can be edited directly in the list. Double-click the cue text, make the change, then press Enter to confirm or Escape to cancel.

Cue types and fields

Dialogue

• Icon: speech bubble
• Color: --cue-dialogue
• Fields:
  • Text – the spoken line, required.
  • Character – character name or description.
  • Director note – visible only in presenter-oriented views.
  • Start delay – seconds after the previous cue before activation.
  • Display mode – caption, left bubble, right bubble, or center bubble.

Audio

• Icon: speaker
• Color: --cue-audio
• Fields:
  • Audio source – MP3/WAV file or stream URL.
  • Volume – 0–100%.
  • Pan – left/right from −100 to +100.
  • Fade in/out – duration in seconds.
  • Playback mode – once, loop, or until the next cue.
  • Trigger – automatic, space bar, or MIDI/OSC signal.

Lighting

• Icon: spotlight
• Color: --cue-lighting
• Fields:
  • DMX channels – channels and values from 0–255, including ranges.
  • Groups – previously defined lighting groups.
  • Preset – a saved lighting preset when a console integration supports it.
  • Fade time – transition duration from the previous state.
  • Mode – Snapshot or Fade.

Camera

• Icon: camera
• Color: --cue-camera
• Fields:
  • camera number or preset name,
  • focus, zoom, and aperture when supported by the control protocol,
  • transition: Cut, Fade, or Wipe,
  • transition duration.

Stage Move

• Icon: performer or moving-object symbol
• Color: --cue-stage-move
• Fields:
  • object or performer,
  • target X/Y position or named stage point,
  • speed,
  • path: straight line or waypoints,
  • start delay.

Comment

• Icon: comment
• Color: --cue-comment
• Fields:
  • comment text for the team,
  • background color,
  • optional target person or department.

Timer

• Icon: clock
• Color: --cue-timer
• Fields:
  • duration in seconds,
  • countdown or stopwatch mode,
  • optional end sound,
  • optional presenter notification when finished.

OSC Placeholder

This type is described as a future integration placeholder.

• OSC address, for example /light/1/intensity.
• Value, such as a number or array.
• Data type: float, int, string, or blob.
• Destination port, with 8000 shown as the default example.

Custom

Custom cue fields are defined by the plugin that provides the cue type.

Special views

Presenter preview

The preview action can show how a cue will appear or behave in a presenter-oriented view, including dialogue styling, DMX value simulation, audio level/waveform information, and camera preview when an appropriate feed is available.

Connections and dependencies

Some cues can be triggered by other cues or external signals. Open Advanced → Trigger to configure behavior such as:

• activation after a delay,
• manual keyboard activation,
• MIDI or OSC signal,
• activation after a preceding Timer or another cue completes.

Cue comments and discussion

Cue version history

Exporting a single cue

Open … → Export cue as JSON. The file contains the cue fields and metadata such as its ID, section, author, and creation time.

Common cue-editor workflows

Scenario 1: Director writes dialogue

Create a Dialogue cue, enter the text and character, optionally set a short delay, add a direction note, and coordinate the next technical cue with the team.

Scenario 2: Lighting operator builds a look

Create a Lighting cue, enter channel values, configure a 2-second fade, duplicate it for the next look, adjust values, and choose the appropriate trigger.

Scenario 3: Sound operator plays music

Create an Audio cue, select the source, configure fades and volume, choose the playback mode, and optionally trigger it from MIDI.

Scenario 4: Camera operator changes shot

Create a Camera cue, select the camera or preset, configure zoom/framing and a transition such as a 1-second Fade, then choose automatic or manual triggering.

Scenario 5: Actor follows their lines

Actors use /show to see the Dialogue cues assigned to their character. In the documented workflow they can mark progress without editing the cue content itself.

Frequently asked questions

Can I change the default fade time for new lighting cues?

The source documentation points to project lighting settings for default fade values and default channel configuration.

Can I preview DMX values without a connected console?

Yes. The documented presenter preview can simulate channel values from 0–255 so lighting cues can be inspected without a live console.

How do I add a custom cue type?

The source material describes this as a plugin/development task and mentions a future no-code Cue Builder as a planned direction rather than an existing feature.

Is there a hard cue limit per script?

The source document does not define a hard technical limit. It recommends splitting very large productions into multiple scripts for easier operation.