Operator's manual · November 2026

EZRig™

Backing tracks, video, MIDI and lighting from one iPad, on one clock.

Written against the app as installed, 3 November 2026.
Examples use the band's own set: Main Set, Rat Star, BA Baby and The Middlenight Men Theme.
Every picture is taken by one script from a rig prepared by another, so the whole set can be retaken after a redesign in a single run.

Contents

  1. Before the first gigWhat the app is, the rules it keeps, the trial, and what you need to plug in
  2. The rigThree setups, cabling order, and what each piece does
  3. Getting songs inThe import grid, the song editor, every control
  4. SetsRunning orders, what happens between songs, backdrops
  5. Routing and the mixerBuses, outputs, levels, mute and solo
  6. Line CheckThe pre-show check: the set, the rig, and a line check per bus
  7. ShowtimeEvery pane, every control, and how a show runs
  8. VideoAttaching a screen, fades, screen latency and the Sync Check
  9. The song alignment windowLining a song's video and lighting up against its audio, with a preview, markers and an explicit Save
  10. MIDIDestinations, test notes, and starting another machine
  11. LightingCapturing DMX, watching it, sending it out
  12. Capturing DMX from the rigThe wired link, two invisible traps, and reading Test DMX Input before you commit to a take
  13. The remoteRemote mode on a phone or a second iPad, the web remote, the password, and the mix from a pocket
  14. Stands: charts and score partsScores inside the app, the read-only page for any browser, and what is not built yet
  15. NetworksWired and Wi-Fi, addresses, and keeping lights off the air
  16. Backup and moving iPadsOne file, what is in it, and restoring
  17. Sharing a show between iPadsOne Dropbox folder the band reads, what travels and what stays on your own rig
  18. Settings, area by areaEvery setting, what it does, and what it would do to a running show
  19. When something is wrongSymptoms, causes, and the log to send
  20. AppendicesWhat is on disk, developer switches, glossary
Chapter one

Before the first gig

Ten minutes of reading that will save an hour at a soundcheck.

What this app is

EZRig plays a band's backing tracks and, at the same time, the things that must stay with them: video on a screen behind you, MIDI to whatever else is on stage, and lighting. It runs from an iPad at the kit, and it is built so that the person operating it is usually also playing.

Free to try, then one purchase

EZRig is free for 28 days from the day you download it, and everything works in that time. After that, playing a show is the part that needs the full version - one purchase, no subscription, GBP 29.99 in the UK and Apple's own equivalent elsewhere, tied to your Apple Account and so covering every iPad and iPhone you sign in to.

What stops at the end of the trial is short: pressing Play, playing a song to tap a chart through, and capturing DMX, all three being a show playing with a different screen in front of you. Nothing else changes. Every song, set, alignment, mix, chart and backup stays exactly where it is, importing and editing carry on as before, and the Sync Check still plays, because setting a rig up is not performing.

A trial running out can never interrupt a show. The question is asked once, when you press Play, and never again while the show runs - so a trial that expires at half past nine during the second set takes nothing away until the next time you start something.

The Full version row is the last thing in Settings, in a group of its own, because it is a fact about the app rather than a job to do to the rig. It says how many days are left, or Bought. Restore a purchase sits on that row as well as on the buy screen, for anyone who has paid already and is setting a new iPad up - looking for it should not mean reading a sales screen first.

The 28 days run from the download, not from first opening. So an iPad bought for a tour and left in its box for a month has a shorter trial than one opened the same evening, and deleting and reinstalling buys nothing - Apple remembers the date, not this app.

One clock

Everything runs from the audio clock. Video, MIDI and lighting all read that clock; none of them can push it. This is the single most important thing about the app, and it is why a set that drifts on other rigs stays locked on this one. When you align a video or a lighting capture later in this manual, you are moving that thing against the clock — never moving the clock.

Nothing ever starts itself. Not when you open a screen, not after a crash, not after the app has been away in the background. A song starts when you press Play, when the footswitch does, or when the set says the previous song runs into it. That is the whole list.

Two modes, kept apart

Build is where you prepare: import songs, name tracks, set levels, build the running order, set the rig up. It is four doors - Songs, Mixer, Sets and Settings - and each one carries a line saying what is behind it, so how many songs are on the iPad or whether the rig wants a look is readable without going in. Showtime is the performance screen: fixed layout, big targets, nothing that rearranges itself. You reach Showtime through one door at the foot of the sidebar, and you leave it through one control in its own top corner, with a confirmation, so it cannot happen by accident.

The Build sidebar
Four doors. Songs, Mixer, Sets and Settings, each saying what is behind it right now, with the Line Check under them and the Showtime door pinned at the foot. It collapses to an icon rail when you want the width. Mixer sits above Sets because the mixer lists every song on the iPad rather than the loaded set, so it no longer waits on one.

What you need

PieceWhy
iPadThe show runs here. Everything else is optional.
Audio interfaceMore than two outputs: separate click, backing, stems. Class-compliant USB.
Powered hub or dockThe iPad charges while the interface, MIDI and Ethernet stay connected.
Screen or projectorOptional. Attach it before the show, not during.
MIDI destinationOptional. An interface with DIN, or a network session for testing.
NetworkOptional, and only for lighting and the phone remote. Wired beats Wi-Fi.
FootswitchOptional. It presses Play, so your hands can stay on sticks.

The order things happen in

  1. Plug the interface in and power it before launching the app, so the outputs are there to be found.
  2. Attach the screen if you are using one, before the show rather than between songs.
  3. Open the app. It prepares in the background; the Showtime door says READY when it is done.
  4. Load the set you are playing. With no set loaded the show plays the library in name order.
  5. Open the Line Check and walk it. It checks the set, the rig and every bus, and says what will bite before the doors open rather than after. Chapter six covers it.
  6. Check the status icons on Showtime: audio, screen, MIDI, lights and DMX.
  7. Play the first song from the Play bar or the footswitch.
The five-second rule. If the app is interrupted mid-show — a crash, a call, a cable — it is built to be back at a usable READY state within five seconds of relaunching, with the same set loaded and the same song armed. It will not start playing on its own when it gets there. That is deliberate: you decide when the room hears something.
Chapter two

The rig

What to plug in, in what order, and why each piece is there.

The smallest rig that works

An iPad and a pair of headphones. Every song plays, video appears on the tablet itself, and nothing else is needed. Useful for building a set on a train; not what you take to a gig.

The band rig

PieceWhat it doesNotes
USB audio interfaceSeparate outputs: click to in-ears, backing to front of house, stems where you want themClass-compliant. Plug it in and power it before opening the app.
Powered USB-C hubKeeps the interface, MIDI and a network adapter attached while the iPad chargesA show that runs flat is a show that stops.
Screen or projectorThe song's own video, or the backdrop when it has noneAttach before the show. The app holds a surface ready so a song starts instantly.
MIDI outStarts another machine, changes patchesDIN from the interface, or a network session over Wi-Fi.
FootswitchPresses PlaySo your hands can stay on sticks.

Adding lighting

Lighting arrives over the network as Art-Net. Two directions matter, and they are separate jobs: capturing a song's lighting from a rig that already exists, and sending a captured song back out to a node. Chapter ten covers both.

Wired beats Wi-Fi for lighting. An iPad's radio dozes between bursts, so an Art-Net stream sent over Wi-Fi arrives in clumps and reads far below its real rate. A USB-C Ethernet adapter at each end, or both ends on a switch, fixes it. Wi-Fi stays up alongside the wire and keeps carrying MIDI and the phone remote.

The order to plug things in

  1. Interface, powered, into the hub. Then the hub into the iPad.
  2. Screen. If it arrives late the app copes, but video readiness only settles once it is there.
  3. MIDI, whether by DIN from the interface or by joining a network session on the Mac.
  4. Network adapter, if you are running lights.
  5. Open the app last. It reads what is attached as it prepares.
The NETWORK card in Settings
Settings → NETWORK. Which link the iPad is actually on, and what each network-using service is bound to. It never blocks READY — a show needs no network at all.

Fixed addresses, once

If you run a wire for lighting, give both ends a fixed address rather than letting them pick their own: the lighting Mac's adapter 192.168.10.1, the iPad 192.168.10.2, mask 255.255.255.0, no router. Then nothing has to be re-pointed between gigs.

Chapter three

Getting songs in

A song is a folder of tracks, not a stereo file with things bolted on.

What the app expects

Up to sixteen audio tracks, optional MIDI, optional video, optional lighting. Every track gets its own fader, its own output and its own name. A stereo file becomes two tracks, because two sides were always two faders.

The Songs library
Songs. Everything on the iPad, with what each song carries and how much room it takes. New Song is the one big button and opens the chooser below. Import Songs... and Look for new files - which re-reads the folder, and is what you need after copying something in with the Files app - are behind the overflow beside it.

Four ways in, on one screen

New Song does not open an empty song any more. It opens the question that comes first - what are you here to do - as four tiles: build one by hand, bulk import a folder, and the two Dropbox tiles that share a library with the rest of the band (chapter seventeen's File sharing). Building one by hand is only one of the ways to add material, and the others used to be scattered across an overflow menu and a Settings pane.

There are always four, whatever this iPad has set up. A tile that cannot work yet is greyed and says why on its own second line rather than swallowing a tap - and somebody who has never shared a show can see where that ends up before it is reachable.

Picture still needed: the New Song chooser, four tiles, on an iPad with no shared show set up yet.
New Song. The question, not one of its answers.

Importing a folder of exports

Before the folder picker opens there is one more screen, and it is there because the picker on its own has no idea what it is being asked for. It sets a one-off import beside a shared show - the same folder of songs, kept in step on every iPad in the band, which is the more advanced version of the same job - as two tiles rather than a stack, because the question is which of the two you want rather than which comes first. It can be turned off once you have read it.

  1. Songs → New Song → BULK IMPORT, or Import Songs... from the overflow. Pick the folder your exports live in.
  2. The grid opens: one row per song, one column per track position.
  3. Name the tracks. Names travel with the track, so replacing a file later keeps the name.
  4. Set each track's output. Click to one, backing to another, stems wherever you want them.
  5. To move a track along its row, hold it until the fill sweeps across it (half a second), then drag. A quick drag anywhere, on a track or not, scrolls the grid. Carry a track to the left or right edge and the grid scrolls under it, faster the closer you go to the edge.
  6. Save. Each row is written as it finishes, so a long import can be watched rather than waited on. Once every song is saved the top-left button says Done; while songs are still waiting it says Cancel and asks before forgetting them.
The import grid
The import grid, opened on two folders that are not yet in the library. Nothing is written until you save.
Sample rates must agree inside a song. The first import sets the rate; anything else is converted on the way in and said out loud, rather than discovered later as a song that will not load.

There is a short, silent walkthrough on the import screen itself, showing the whole thing happening: picking the folders, what the grid does with them, and pressing Save. It loops, and it is there because the first import is the one moment where a picture beats a paragraph.

The song editor

Tap a song's row in the library to open it; the play button on the right of the row arms and plays it instead. Each section is covered below.

The top of the song editor
Name and audio. Numbered names sort into show order, and renaming a song renames it in every set it appears in. One row per track: its name, its file, which bus it goes to, and Replace and Remove, with a handle on the right to drag it up or down. Levels are not here - they are in the Mixer, where there is a fader under the number.
The video row of the song editor
Video. A real frame from the song's own video and a scrub bar. Its timing against the song is set in the alignment window (chapter nine), opened from the ALIGNMENT section, which sits directly underneath this one - it was eighth of nine sections until 2026-09-28, which put the window this app is proudest of behind four things nobody has asked about yet.
The MIDI and DMX rows
MIDI and DMX. The MIDI file sent while this song plays, and the song's own lighting - imported from a file, or captured live from the rig (chapter twelve).
The metronome card
Metronome. Off, the song's click track, a tempo you type, or the song's own MIDI tempo map — offered only when that file actually carries one.
The lead-in card
Lead-in. Whether this song waits for its video to be ready, or starts on time and clips the first frames. Per song, with the rig's own default behind it.
The bulk edit grid
Edit in Grid. Songs already on the iPad reopened in the import grid's own layout: one row per song, one column per track position, so a whole column can be renamed or pointed at a bus in one go. Nothing lands until Save, and it says how many songs will change.

Charts and score parts

Further down the editor, CHART AND SCORES holds the song's lyric-and-chord chart and any PDF score parts, for band members' own phones and tablets. They never appear on Showtime. Chapter thirteen covers them.

The chart and scores section
Chart and scores. One chart of words and chords, and any number of PDF parts. Time the chart plays the song once and you tap along; after that it scrolls itself, here and on every stand.

Folders

The Songs screen groups into collapsible folders, and a heading is always drawn with its count. New folder in the header makes one; a half-second hold on a heading renames or deletes it, and deleting a folder never deletes a song — they become ungrouped. In Bulk Edit, Move to folder… files a whole selection at once, and the sheet's first row makes a new folder and files them into it in the same step.

None of this moves anything on disk. A song is still named by its own folder under Documents, so sets, the running order and every command that names a song are untouched by filing one. A folder is a way of looking at the library, not a place a song lives.

The set editor's song picker gets the same folders as a filter, so building a set from one band's material does not mean scrolling past another's.

Deleting a song

Swipe a song's row to the left in the library and tap Delete. It always asks first: Delete this song? Everything in its folder goes, and any set that names it shows it as missing. Keep it backs out. Deleting is refused while the show plays.

Press and hold a song for more

Hold a song's row in the library for half a second and a menu opens beside it: Edit this song, Align to audio, Add to a set, Delete this song. Everything in that menu is also reachable the ordinary way - it is a shortcut, never the only route to anything. While you hold, the row fills with colour so you can see the hold registering; let go early and the fill retreats rather than opening anything. Align to audio opens the song's alignment window (chapter nine); if the show is playing it asks to stop the show first.

An entry you cannot use right now sits in the menu dimmed, with the reason underneath, rather than failing silently - Delete this song, for instance, while the show is playing. The same gesture and the same rule - stated reasons, never a dead control - turns up again in the next two chapters and in the mixer.

Chapter four

Sets

The running order, and what happens in the gaps.

Manage Sets
Manage Sets. Create, load and delete. The loaded set is marked, and loading one while a song plays asks first.
The set editor
A set. The songs in order, each row carrying how the show gets into it and, where it runs in after a gap, the stepper and its one-tap presets. The set's own backdrop, fade and first-song overrides sit along the top.

What happens between songs

This belongs to the set, not the song: the same recording waits for the singer in one set and runs straight in on another.

ChoiceMeaning
WaitThe show stops at the end of the song and waits for you.
Run inThe next song follows immediately, with no gap.
Run in afterThe next song follows after a gap you set, in half-seconds.

Beside a gap's stepper sits a row of one-tap presets: 0.5 s, 1 s, 2 s, 4 s, 6 s and 10 s. The one that matches the current gap is lit. Use the stepper for anything in between.

One row carries the song, how it starts and, for "run in after", the gap. The stepper moves in half seconds and a row of presets — 0.5, 1, 2, 4, 6 and 10 seconds — puts each one a single tap away. A song may appear twice, which is what an encore is.

Backdrops
Backdrops. What plays when a song has no video of its own — a still or a loop. One is the rig's default; a set may name its own, which wins while it is loaded.

Renaming and deleting a set

Rename sits in the set editor's header, and beside Edit and Load in Manage Sets' preview. It refuses an empty name, a name another set already has, and any rename while the show plays, and says which. Renaming the set that is loaded keeps it loaded.

Deleting a set, from its bin or its hold menu, always asks first: Delete this set? The running order goes; the songs stay on the iPad. The same goes for a backdrop's bin on the Backdrops screen.

Press and hold, here too

The same half-second hold from chapter three works on a song's row inside a running order - Edit this song, Remove from this set - and on a set's own row in Manage Sets - Load (or Unload), Edit this set, Delete this set. Nothing here is offered that a visible control could not already do; the hold just shortcuts to it.

The set preview
The preview from Manage Sets: what the set holds, read-only, with EDIT and LOAD. With no set loaded at all, the show plays the library in name order.
Chapter five

Routing and the mixer

Tracks belong to the song. Buses belong to the rig. Changing interface never means editing songs.

The idea

A track has a level into every bus. A bus says which physical output it leaves by, and how loud. Move the rig to another interface and you re-point the buses; every song is untouched.

The board shows one mix at a time. A rail of chips along the foot names the rig's buses, plus Masters for the bus faders themselves and Routing for every track against every bus at once. Pick a chip and every track strip is that track's level into that one mix. A track that is not in the mix you are looking at is still drawn, dimmed and reading -inf, because hiding it would be hiding the thing you came to change: bringing its fader up is what puts it in the mix, and taking it to silence is what takes it out. That is why there is no separate routing step any more.

One track, several levels. The click goes to the drummer's in-ears at one level and to front of house at another, and those are two numbers rather than one fader with trims hung off it. A strip's name plate says which mix you are setting and how many others that track is also heard in, so a strip can never read as the whole truth about the track.
An interface the iPad has met before gets its own routing back. Plug in an audio interface it remembers and every bus returns straight to the outputs you last gave it - no re-pointing at soundcheck. Plug in one it has never seen and it gets a sensible starting map from the show's own defaults, with a note on Settings' THIS RIG card saying so, so there is something to check rather than nothing to notice.
The mixer
The Mixer, in Bus 1's mix. The song's name and the arrows beside it move between songs - every song on the iPad, not just the loaded set, because a mix is written into the song and travels with it. Reached from the sidebar, from the song editor's Mixer button, or by tapping the song title on Showtime.

Working the faders

The mixer keeps as you go. There is no Save and no Discard. A fader you move is written to the song there and then, the way a desk remembers where you left it, and Undo steps back through what you did. The one exception is the song playing right now: a fader moved on it is heard at once and written when the show stops, never during it.

A strip reads the same either side of the board: the dB readout at the top, the fader on its printed scale with a meter beside it, then M and S, then the coloured name plate at the foot. A track strip's plate says which mix this fader is setting and how many others the track is heard in; a bus strip's says which output it leaves by. Bus levels belong to the rig, so they are the same in every song. The strips take their colour from the bus whose mix you are in, which is a colour you pick in the mixer rather than one the app assigns.

A track selected, with its detail card open
A tap on a strip only selects it: the strip lights and every bus it feeds is outlined, which is very often the whole question. A second tap on the name or the destination box opens the card over the board - the name, the level to the decibel, and where it goes.

Naming and routing

Renaming a track
Tap a track's name plate to rename it. Saving is refused while the show plays, and it says so rather than failing quietly.

Tap a bus's name plate to rename it or send it somewhere else. The outputs it offers are the ones the connected interface can actually honour, so the label and the speaker can never disagree: on a box with a routing matrix that is every output it has, and on a plain two-output interface it is left, right or both, because that is all a bus can be given there. The targets are large, because this gets used at a soundcheck with a torch in your teeth.

Hold either name plate instead of tapping it, and a menu opens with a few more shortcuts: the same rename (or rename-and-reroute for a bus), plus Reset to 0 dB, Mute and Solo - the same half-second hold as chapter three's library rows, refusing whatever the show would refuse at the time, with the reason stated rather than a dead row.

Add bus declares another. A new bus has no output until you choose one, so it can never appear in the wrong speakers. Removing one is refused while a track still feeds it.

The buses, as strips of their own
Masters, the first chip on the mix rail, is the rig's buses as strips of their own - each with its level, mute and solo, the output it leaves by, and its colour. Two of these have no output yet and say so. The chip beside the heading reads "Every song, applies at once", because a bus level belongs to the rig rather than to the song you happen to have open.
The routing view
Routing, a chip on the mix rail, shows every bus against the physical output it leaves by - one table instead of opening six bus sheets one at a time. It is not the old track-against-bus grid, which shared the word and was retired: a track feeds a bus when its level into that bus is above silence, and the board already shows you that. Linked pairs read as the left and right of one pair, and a bus with nowhere to go says so rather than going somewhere you did not expect.

Feeding more than one bus

There is nothing to add or remove. A track is in a mix when its fader in that mix is above silence, so sending the click to a second set of in-ears is one chip and one fader, and taking it out again is pulling that fader down. There is no cap on how many mixes a track can be in, and no "main" one among them.

A track can also be sent nowhere at all: take its last fader to silence and the strip reads "Not sent". That is a routing choice saved with the song, not a mute - it is why a track turned off does not come back on at the next launch, and why nothing warns you about it.

Chapter six

The Line Check

The check that runs before the doors open, so the surprises happen while there is still time to do something about them.

The Line Check sits under the four doors, beneath a BEFORE THE SHOW heading, because it is the last thing you do rather than the first: it is the one screen that looks at the whole rig at once and tells you what is wrong in plain words. The Showtime door offers it once per session when something is red, and never gets in the way a second time. It was called Tonight until 2026-09-27, when Settings' own Tonight area was removed and one name doing two jobs became one.

The Line Check screen
Three headings, and a tile each at the top. The set and whether every song has what it needs, the rig itself, and a line check that walks the buses one at a time.

The set

One row per song in the running order, saying what it carries and what it is missing. A song the set names that is not on this iPad is named here rather than discovered at the gap before it. Under a song's title it also says, without grading it, when that song sends a track somewhere this rig has no bus for — the track plays, through the front-of-house bus, and chapter five's mixer is where you would change it.

The rig

Interface, bus outputs, the audio engine, the armed song, screen, MIDI, lights, network, power, storage, your last backup, and - where one is set up - the shared show. Each line is graded: green is fine, amber is worth a look, red is something to fix. A line you can act on carries the way to fix it, and tapping it takes you to the setting rather than making you find it.

Two of them are worth knowing before you meet them. Check your buses appears when the rig declares a bus the audio graph has no mixer for, which happens when a song arriving after launch names one: its tracks play, at front of house, with their strips still naming the bus they asked for. It is red, and the fix is closing the app and opening it again - about five seconds, no network and nobody else. And the Shared show line says when this iPad is behind the band, which is never counted among the things to fix: the commonest place to be behind is a venue with no usable Wi-Fi, where taking the update is not something anybody can do.

Amber is not a fault. Off on purpose is neither working nor wrong — video output turned off on a rig with no screen is an ordinary evening, not a warning. A rig where everything is fine shows no amber anywhere, which is what makes amber worth reading.

The line check

A row per bus. Ping plays a tone down that bus alone for a couple of seconds; tap Heard it and it moves to the next. It is the fastest honest way to find out which speaker is which, and it is the only part of this screen that makes a noise. It stops on its own if the show starts.

A MIDI row after the buses sends the same test note Settings does. It is graded manually and never blocks anything, because a MIDI destination that is not answering is a normal state for a rig that does not use one.

Going on anyway

Nothing here stops you. Go on with problems? asks once and lists what is still red, and then takes you to Showtime. The check is advice from something that can see the whole rig at once, not a gate.

Under the Line Check row in the sidebar is when it was last looked at - "Checked 18 minutes ago", or, past six hours, a reminder that it no longer counts for tonight. Opening it by hand is free and changes nothing; loading a set or relaunching the app arms the door's one offer again. The switch that decides whether it is offered at all is in Settings, under Showtime screen.

Chapter seven

Showtime

One screen, fixed. Everything here is meant to be read at arm's length, mid-song.

Showtime, armed and stopped
Armed and waiting. Song two of four, stopped at the start, the waveform ready, the setlist beside it and the Play bar across the foot.

The status bar

Left to right along the top: the battery, the loaded set, the time, any warning in plain words, then an icon each for audio, the screen, MIDI, lights and DMX, and finally Settings, Debug and the way out. An icon is green when the thing it names is working, amber when it wants a look, and unlit when there is nothing to say - a rig with no screen is a valid rig, so colour on this bar always means do something.

IconGreen means
SpeakerThe engine is running and the outputs are there.
ScreenVideo output is on and a screen is attached. Amber means the two disagree in either direction - a screen with the output off, or the output on with no screen.
KeysA MIDI destination is open and can be reached.
BulbLighting output is on and the node is answering.
DMXThis song carries lighting. It brightens while the lighting is changing, and is absent when neither this song nor the rig has any.
Each icon carries its own colour, and that is the whole element. They were a coloured dot and a word until 2026-10-17, and the words kept being dropped when the bar ran out of width - so the two that were silently dropped were AUDIO and MIDI, the two that were working. An icon costs about a quarter of a dot and its word, so nothing has to be sacrificed to fit, and the battery is drawn with its percentage inside the glyph, which costs no width at all and is therefore never dropped either.
On an iPhone the battery is iOS's to draw, not ours. The phone's bar is two decks and still has less room than an iPad's one, so Showtime stops hiding the system status bar there and the battery, the charging state and the clock sit a few points above it, where every other app puts them. What that buys is the bottom of the list: before it, the 50 points the battery took were coming out of Exit Showtime, which was clipped to "EX" with no other way off the screen.

The now-playing card

Status, the song, the timers, and underneath the title what comes next and how it starts. Tapping the title opens that song's mixer; holding it opens a menu with the song editor, the alignment window and the chart.

The setlist

Each song is its own row with its own edge, so what you can press is obvious in the dark. Tap one to cue it — never to start it. READY marks what Play will start. A song the set runs into carries an amber arrow turning down into the next bar, and the word AUTO beside it; a song that waits for you carries nothing at all, which is what makes the mark readable from the kit - two grey words have to be told apart first, and a mark on some rows does not. The list scrolls itself as the show moves on, and stops fighting you if you have scrolled it by hand.

Cueing, and playing now

Showtime with a song cued
With something cued, the Play bar narrows and PLAY NOW slides in beside it. That button stops what is playing and starts the cued song at once.
Play now confirmation
With Confirm before Play now on in Settings, it asks first. Off, it goes immediately.
Showtime playing
Playing. Timers running, the playhead crossing the waveform, the video pane showing what the audience sees, bus meters moving.

Hold the video pane for half a second, when the armed song has video or DMX, and Showtime opens that song's alignment window (chapter nine), with its locator where the show is standing. If the show is playing it asks first: Stop the show and align this song? There are only two answers, Cancel and Stop and align. There is no "keep playing" choice here, because the window plays the song itself and can never run at the same time as the show.

The curfew

The banner shows the curfew, how long until it, what the rest of the set still needs, and your slack — the number that says a song is about to be cut before it is cut.

Tap the banner to change it. A venue that moves the curfew mid-show does not require leaving Showtime: the banner opens a time wheel with Cancel and Save, and Save recalculates everything without touching playback.

Leaving

Leaving Showtime no longer has to stop the show. Exit Showtime, in the status bar's top corner, always asks first and offers three ways forward:

ChoiceWhat it does
CancelStays on Showtime. Nothing changes.
Leave, keep playing (green)Drops back to Build mode with the show still running. The transport carries on under the Play bar at the foot of the sidebar.
Stop and exit (red)Stops the show first, then leaves.

The two active choices deliberately lead with different words - "Leave" against "Stop" - rather than sharing one, so which choice keeps the music going reads from the word alone, at a glance, in the dark.

Exit confirmation
Exit asks before doing anything, never after.

Solo Showtime

A second Showtime, for one performer on one iPad rather than a band with a drummer operating. Switch to it in Settings → Showtime screen; the door opens whichever you chose.

It is chart-led: the song's words and chords fill the screen, scrolling themselves if the chart has been timed, with the current line held a third of the way down. Underneath are the next song and the transport, and that is the whole screen — no faders, no video pane, no waveform, no Settings and no Debug. A drawer over the chart holds the running order; tapping a song cues it and never plays it, exactly as the band screen's setlist does.

It is the one screen built with pedals in mind first, since a solo performer's hands are on an instrument: the same pedal keys work here as everywhere, and the Play bar is sized to be found with a foot rather than a glance.

Its status strip reads the same icons as the band screen's, and for the same reason: it is the same operator on the same night, and two vocabularies for one fact is one more thing to learn at a quarter to eight. It had no battery at all until 2026-11-02 and has one now - on an iPad its own, inside the glyph, and on a phone iOS's, a few points above.

Solo Showtime
Solo Showtime. The chart fills the screen, the next song and the transport sit under it, and there is nothing else to press. The words here are placeholder, not the song's.

The Debug button's hold

Debug, beside Exit Showtime, opens on a two-second hold when no passphrase is set - a stray tap does nothing, and the button fills with colour as you hold so you can see it building rather than wondering whether you pressed it right; let go early and the fill retreats instead of opening anything. Set a passphrase (chapter eighteen's TROUBLESHOOTING card) and a plain tap opens a password prompt instead.

The buses pane

The rig's outputs with live meters, M and S, each strip carrying its name in colour at the top so what you are holding reads from across a stage. Whole strips only — it scrolls rather than resting on half a fader. Tapping the BUSES label at its foot opens the same strips large, over the rest of the screen; it never touches the transport.

Chapter eight

Video

On the same clock as the audio, with the screen's own delay accounted for.

Getting a picture

  1. Attach the screen before the show. The app keeps a surface open so a song starts instantly.
  2. Check DISPLAY is green on Showtime. Amber says no screen is attached, or video output is off in Settings.
  3. A song with no video of its own shows the backdrop — a still or a loop, set for the rig and optionally per set.

Fades

Set the rig's own fade in Settings, override it per set, and override that per song - separately for the way a song's video arrives and the way it leaves. A song with no video reveals the backdrop rather than dipping through black.

A fade happens at both kinds of boundary, and what differs is what is underneath. A song the set waits before fades out to the backdrop and the next one fades in from it; a song the set runs straight into fades out and in with no backdrop between them, because the two songs are one continuous thing to the audience. A song's two edges are asked about separately, so a set can run song two in from song one and then wait before song three, and that song hides the backdrop on the way in and reveals it on the way out.

There was a setting for this, and it never did anything. "Fade into a song that runs straight in" was read by one branch of the code that could not fire, so it was off in both positions - which is exactly how it was reported: turning it on made no difference. It is gone, and the behaviour above is what replaced it.

Two different delays

There are two numbers that decide when a picture appears, and they fix two different problems. It is worth getting straight which is which.

NumberWhat it fixesWhere it lives
Screen latencyThe screen, projector and cable are slow. Every song's picture arrives late by the same amount.Settings, SCREEN LATENCY. One number for the whole rig.
A song's own video shiftThis one video file was cut or exported a little early or late against its audio. Only this song is out.That song's alignment window (chapter nine). Saved with the song.

The two add together. Get the screen latency right first, on the real screen, with the Sync Check. Only then shift a song that still looks wrong. If every song looks late by the same amount, the fix is screen latency, not every song.

Screen latency and the Sync Check

The Video area of Settings
Settings, Video. Screen latency is the second row; its value is on the right and the steps are behind a tap on the row.

Open the row and it shows the latency in milliseconds, with its size in frames once a song with video has been armed. -10 ms, Zero and +10 ms change it, and a second row of whole-frame steps - -5 f to +5 f - appears once there is a frame rate to count in, because a screen's delay is judged by eye against a picture and a picture moves in frames. A bigger number drives the video further ahead of the audio, for a slower screen.

  1. Stop the show. The Sync Check is refused while anything plays.
  2. Tap Play Sync Check. It plays a flash and a click together through the real outputs and on the real screen, outside the running order.
  3. Watch the audience's screen, not the iPad, and step the latency until each flash and click land together.
  4. Tap Stop Sync Check. The new latency is saved then, and the song that was armed comes back where it was. It does not start playing.
The Sync Check needs its song. It plays the calibration song 99 - Sync Check from the library. Without it the button is greyed out and says so. With no external screen attached the card warns you, because the number is for the screen the audience sees.

When the armed song carries its own video shift, the card mentions it in one line, and says it is changed in that song's alignment window, not here.

Chapter nine

The song alignment window

One window per song. The audio stays still. You slide the video and the lighting until they sit right against it.

What it is for

A song's video or lighting sometimes arrives slightly early or late against its audio: a video exported with a few frames of black at the top, or lighting that came from another machine. The alignment window is where you fix that, once, for that song. The fix is saved in the song and used at every show. A capture made on this iPad with Capture DMX needs no alignment, because the iPad that started the song also heard the lights.

The song alignment window
The alignment window, Video lane selected. Top bar: Undo, Redo, Discard, Save, Close. Left: the preview and its transport. Right: the selected lane's shift and nudges. Below: the zoom bar and the lanes - Audio fixed, Video and DMX as clips, MIDI hatched out. A target ("Downbeat") and a marker ("Lips") meet, so both show a tick.

The song editor's own way in is the ALIGNMENT row, which since 2026-09-28 sits directly under VIDEO rather than near the foot of the form: it is one row for the whole song, reading "Line the video and the lights up against the song", and when it cannot open, the line underneath turns amber and says why.

Getting in

FromHow
The song editorThe ALIGNMENT section, Align to Audio. Shown when the song has video or DMX.
The Songs libraryHold the song's row, then Align to audio.
ShowtimeHold the video pane for half a second. The locator starts where the show is standing.
The Universe MatrixIts Align to Audio button. The window opens on the DMX lane.

It opens on the Video lane if the song has video, otherwise on DMX. The song editor's button is refused, with the reason underneath, for a song that has not been saved yet, for a song whose files have changed since it was saved, and while the app is still preparing.

The window and the show never play at the same time. The window plays the song itself. Open it while the show is playing and it asks first: Stop the show and align this song? The show stops where it is, then the window opens. If the show is started some other way while the window is open (from a phone remote, say), the window's preview stops at once, your edits are kept, and Save waits until the show stops.
Stop the show and align this song?
From Showtime: two choices only. There is no "keep playing" here.
The alignment window on the DMX lane
The DMX lane selected. The clip shows how much the lighting is moving rather than what colour it is, which is what you line up against a song. Suggest offers an offset from the big jumps in it; the audio lane never moves, because it is the clock.

The lanes

LaneWhat it showsCan it move?
AudioThe song's waveformNever. It is the clock everything else lines up against.
VideoA strip of the video's own framesYes. Drag it.
DMXHow busy the lighting is, moment to momentYes. Drag it.
MIDIHatched out and marked as the next stepNot yet. It needs a per-song MIDI offset first.

Drag a clip right and it plays later; drag it left and it plays earlier. The selected lane's panel (beside the preview, or on a narrow screen a sheet opened from the lane's name) shows its shift in milliseconds and, for video, in frames. It says it plainly - "Picture shifted 40 ms later (1.0 frames at 25 fps)", or "plays unshifted" at zero. It never claims the picture is in time just because of the number.

What your fingers do

GestureWhat it does
Drag a clipShifts that lane against the audio. There is no snapping.
Drag the red handle, or tap the rulerMoves the locator, the line that says where you are in the song.
Drag empty spaceScrolls the timeline. Nothing is edited.
PinchZooms. The grid gets finer as you go in: bars, beats, then halves down to sixteenths, then single video frames or milliseconds.
Double-tap a laneDrops a marker there (a target, on the audio lane).

The zoom bar above the lanes has -, a slider, +, Whole song, and a readout of the finest grid line on show. A strip beside it says in plain words what your finger is doing right now.

Nudging

For exact steps, the lane's panel has -1 fr, -10 ms, +10 ms and +1 fr (one frame at the video's own rate; 1 ms steps instead when there is no video), and Reset to 0. The DMX lane also has Suggest: it looks for the lighting's sharp hits against the song's beat and proposes a shift, with how sure it is. If there is not enough to go on it says so and changes nothing. A suggestion is one undoable step, like any other edit.

Video has no Suggest, on purpose. A music-video edit rarely cuts on the beat, so a beat matcher would confidently line up the wrong thing. Video is lined up by hand, by watching the singer's mouth against the vocal.

Instead, the Video lane shows Lip sync to vocal track, tagged Soon. It is a placeholder. Tap it and it explains what it will do one day - find the singer's mouth in the picture, line it up against the song's own vocal track and suggest a shift for you to check - and changes nothing at all.

Markers

Markers are there to help your eyes, nothing else. Drop a target on the audio at a clear moment - a word, a hit - and a marker on the video or lighting at the matching moment, then drag the clip until they meet. When a marker sits on a target, both are drawn in green with a tick and the word "Aligned".

Markers never move anything. They are never used in any calculation. The window does not snap to them, and Suggest does not look at them. Only your drag or your nudge changes a shift.

The MARKERS list shows every marker with its time. Tap a name to rename it; tap the cross to remove it. Marker at locator and Target on audio drop one where the locator is. Markers are saved with the song. If a video or lighting file is later replaced, its old markers are dropped, and the window says how many.

The preview

The preview plays the song itself - its audio through your outputs, at the song's own levels, and its picture in the window, with your unsaved shift already applied. The projector is left alone, and no lighting or MIDI is sent.

ControlWhat it does
Back to startPuts the locator at the top of the song.
Frame back / forwardOne video frame (40 ms with no video). The arrow keys do the same on a keyboard.
Play (green) / Pause (red)Runs the preview from the locator. Space does the same.
Beat lampFlashes on each beat in the corner of the picture.
Follow locatorKeeps the timeline scrolled to the locator while it plays.

The corner readout says SHIFTED, UNSHIFTED or LINED UP (the last only when a marker actually sits on a target). If the audio output changes while the preview plays, it stops; press Play to carry on.

Undo, Save, Discard

Every finished drag, nudge, reset, suggestion or marker change is one step. Undo and Redo sit in the top bar, greyed out when there is nothing to undo or redo (Command-Z and Shift-Command-Z on a keyboard).

Nothing is kept until you tap Save. Save writes the song's video shift, DMX shift and markers in one go, and the next show uses them. Discard throws every change away. Closing with anything unsaved asks Discard changes?, says what each lane goes back to, and offers Keep editing. A swipe cannot close the window past that question.
Discard changes?
Discard changes? It names what each lane goes back to before anything is thrown away.

Save is greyed out while the show is playing, and when there is nothing new to save. Save from a window opened in the song editor and the editor picks up the same values, so its own Save or Cancel neither overwrites nor undoes them.

Lighting from elsewhere gets a head start. For a DMX file with no shift of its own that did not come from this iPad's capture, the window starts from this rig's last measured lighting delay, as a first undoable step, and says so. Nothing is kept unless you save.
Chapter ten

MIDI

What starts the other machine, and how to prove it before the first song does.

MIDI destination card
Settings → MIDI DESTINATION. Choose where MIDI goes, fire a test note, and see whether anything is actually listening.

Two ways out

Joining a network session

  1. On the Mac: Audio MIDI Setup → Window → Show MIDI Studio → double-click Network.
  2. Under My Sessions, add a session and tick it to enable.
  3. In Directory, select the iPad and click Connect. It moves up into Participants.
  4. Set Live routings to that session.
  5. In your DAW, enable Track and Remote for that input.
  6. On the iPad, choose that session as the destination and press Test.
Choosing a MIDI destination
Choosing a destination. It says whether it can actually reach what is named, not only which name is selected — a session that has gone away looks identical otherwise.
The cable is the simple way. Your interface's own MIDI out needs no pairing, no session and no Wi-Fi. Wireless is the fallback for when that port is spoken for, and Settings → MIDI carries a short walkthrough of the pairing — which happens entirely on the Mac, in Audio MIDI Setup, and is the part that reliably catches people out the first time.
What a song sends. Whatever its own MIDI file contains, in time with the song, from the same clock. Typically a note at the very first tick — the one that starts the other machine — and program changes through the song. If one song starts your DAW and another does not, compare the note each sends; they are rarely the same.
Chapter eleven

Lighting

DMX means anything on that wire — lamps, hazers, motors. The app records it, plays it back on the show's own clock, and sends it out.

There is a walkthrough for the network part. Settings → Lighting carries a short silent video covering both shapes a rig takes — everything through a travel router, or one cable from the iPad straight to the node — and what "on the same network" actually means. It is there because this is the step people expect to be hard, and it is one rule rather than a subject.

Three jobs, kept apart

JobWhere
Capture a song's lighting from the rig you already haveSong editor → DMX → Capture DMX
Align it against the song, if it came from somewhere elseThe song's alignment window: Align to Audio, from the song editor's ALIGNMENT section or the Universe panel
Send it out to a node during a showSettings → DMX OUTPUT

Before you capture

  1. Get the iPad and the lighting machine onto the same network — a wire if you can, Wi-Fi if you must.
  2. Point the lighting software at the iPad. Sending to its own machine (127.0.0.1) reaches nothing.
  3. Open Test DMX Input from the song's DMX row. It lists every address the iPad has, and says what is arriving.

Chapter eleven walks the wired setup and Test DMX Input's own log in full, plus the two faults that look exactly like a broken network and are not.

If nothing arrives, in order of likelihood: the lighting software is sending to loopback or to a network the iPad is not on; iOS has not been given Local Network permission for the app; the iPad is on a different Wi-Fi band; a VPN on the sending machine is swallowing local traffic.

Capturing

  1. Stop the show. Capture is refused while anything plays, while the app is still preparing, and with no network.
  2. Song editor → DMX → Capture DMX.
  3. It arms and plays that song; your MIDI starts the rig exactly as it does in a show.
  4. Watch the log and the small universe beside it. Channels light as they arrive.
  5. Stop when you have what you need, or let the song finish.
  6. Read the summary, use Sanity Check to see the activity under the waveform, then Save or Discard.
Capture summary
The summary. Captured length against the song's length, universes, channels, how long the rig took to answer, and a warning if it came over Wi-Fi. Nothing is written until you choose.
A capture needs no alignment. The same device started the song and heard the answer, so the timing is known rather than guessed. Only lighting that arrived some other way needs the alignment window.

Watching it

The universe matrix
The Universe Matrix, opened from Showtime's DMX light: 512 cells, brightness by value, tap a cell to read its channel and value.
The fader view
The same moment as faders — one per channel the song actually uses, labelled and moving live. The switch at the top remembers which you prefer.

Aligning lighting that came from elsewhere

Lighting imported from a file rather than captured here may sit a little early or late. Open the song's alignment window (chapter nine) - from Align to Audio in the song editor's ALIGNMENT section, or from the Universe panel - and work on the DMX lane: drag it, nudge it, or try Suggest. Drag right to make the lighting later. Nothing reaches the song until you tap Save.

The old lighting-only alignment view, and the live nudging of the lights from Showtime while a song played, are gone. A lighting shift is now changed only with the show stopped, in the window, and takes effect as soon as it is saved.

Sending it out

DMX output card
Settings → DMX OUTPUT. On or off, the node's address and port, the send rate, a latency offset, and which link it may use.
The status line counts what is actually leaving. It reads "Sending 43.8 a second to 10.0.0.50" - frames measured on the wire - and mentions the rate you asked for only when the two genuinely differ. That is not a nicety. A gig was lost on 2026-10-23 to four separate faults that all read identically from a stage, because every lighting readout the operator could see was derived from the settings and so could only ever agree with itself. Four of the states it can be in are now named apart: off, no address, nothing to send (an ordinary song with no lighting in it), and holding until the first Play - which used to say the bare words "not sending" and was read, correctly enough, as a fault.
Chapter twelve

Capturing DMX from the rig

The wired link that makes a capture reliable, and the two faults that look exactly like a broken network and are not.

What Capture DMX actually does

It plays the song on the iPad. The song's own MIDI triggers your lighting software, exactly as it will on the night, and the iPad records the Art-Net the rig sends back — aligned to the song's own clock as it arrives, because the same device that started the song also heard the answer. The result is saved as song-lighting.dmx in the song's own folder.

Wiring the two machines together

  1. A USB-C Ethernet adapter on the lighting Mac, and one on the iPad. One cable straight between them.
  2. Give both ends a fixed address rather than letting them negotiate one, so nothing needs re-pointing next time.
  3. From the Mac, ping the iPad's address. A live wired link answers every time, at around a millisecond.
EndAddressSubnet maskRouter
Lighting Mac's adapter192.168.10.1255.255.255.0leave empty
iPad's adapter192.168.10.2255.255.255.0leave empty
Same network, different addresses. Both ends share the first three numbers, 192.168.10 — that is what makes them one network. Each end still needs its own last number: the Mac is .1, the iPad is .2. Give both ends the same address and the link will not work at all, even with the cable plugged in and everything else right. No router or gateway is needed for a straight cable between two machines.

Mac: System Settings → Network → the USB LAN adapter → Details → TCP/IP → Configure IPv4 Manually. iPad: Settings → Ethernet → the adapter → Configure IP → Manual.

LinkPacket lossLatency
Wired (adapters, direct cable)0 of 100 pings1 ms, steady
Wi-Fi4 of 100 pingsspiking as high as 941 ms

Measured on the rig. Wi-Fi is fine for the phone remote, which only polls once a second — it is not fine for lighting, and the gap above is why a wire is worth running.

Pointing the lighting software at the iPad

Send Art-Net to 192.168.10.255 — the wired link's own broadcast address — or straight to the iPad at 192.168.10.2.

If the software will only send to 127.0.0.1, it is talking to itself, not the iPad. Run Scripts/artnet-relay.swift on that Mac instead: it listens on port 6454 and forwards every Art-Net packet onto the network unchanged. Run it in the foreground, from a Terminal window on that Mac — never with nohup, and never backgrounded. macOS 15 strips Local Network permission from a process detached from its own session, so a backgrounded relay has every send to a LAN address refused with "No route to host" — while a ping to that same address is flawless, which reads exactly like a network fault and is not one. Approve the Local Network permission prompt the first time it appears.

The one thing that costs an evening: App Nap

Keep the lighting application frontmost for the whole capture. Some lighting software stops sending properly the moment it is not the frontmost application on the Mac — macOS quietly throttling its background timers, App Nap. On this rig it collapsed Art-Net output from 44 frames a second to roughly one frame every six seconds. Nothing reports an error. Nothing looks wrong. It reads exactly like a dead network, and it cost a whole evening to find because every other part of the setup was correct. Before a show: quit the lighting application, select it in Finder, press ⌘I, tick Prevent App Nap, then reopen it — and do not switch away from it on the Mac while a capture is running.

A second symptom worth naming

"It works for about eight seconds, then stops" is not a bad cable — it is the Art-Net node timeout. A controller polls the network every few seconds and drops any device that misses three replies in a row. The app now answers every poll and announces itself every four seconds, so this should not come up again — but if traffic dies after roughly nine seconds, this is what it is. Rescanning for devices in the lighting software brings it straight back.

Check the link before you commit to a take

Test DMX Input, reached from the song's DMX row, plays nothing and saves nothing. It exists purely to answer one question — is anything arriving, and from where.

ColumnWhat it shows
TIMEWhen this line was logged.
RATEFrames a second actually arriving, right now.
UNIVWhich Art-Net universe the frame belongs to.
LITHow many of the 512 channels in that frame are non-zero.
ART-NETValid Art-Net packets read, running total.
DATAGRAMSPackets of any kind that have arrived on the port, valid Art-Net or not.

A healthy link settles around 40–44 frames a second, with ART-NET and DATAGRAMS climbing together. A dead one is exactly that: no new lines, RATE stuck at 0. Each line names the address the frame arrived from, so wired traffic can be told apart from Wi-Fi at a glance. If DATAGRAMS keeps climbing while ART-NET stays flat, something is arriving on the port that is not Art-Net — worth chasing down before assuming the lighting rig itself is at fault.

Doing the capture

  1. Wire up, point the lighting software at the iPad, and check the rate on Test DMX Input first. A take is only worth taking once the rate looks right.
  2. Song editor → DMX → Capture DMX, then wait through Getting the rig's attention — the iPad announces itself for a moment before the song starts. Starting the song first, before that finishes, loses the opening seconds of lighting: nothing was listening for it yet.
  3. Let the iPad trigger your lighting software itself, over MIDI, exactly as it will on the night — do not start it by hand.
  4. Let the song run to its own end and stop cleanly, or stop it yourself once you have what you need.
  5. Read the summary, use Sanity Check to see the recorded activity under the song's own waveform, then Save.
Saving makes the capture the lighting that plays. A song that already had a lighting file imported under its own name used to keep playing the old one - the capture landed, the screen said Saved, and the lights were somebody else's. Saving now points the song at what you just recorded, and if it cannot, it says so rather than reading as success.

When a capture will not behave

What you seeLikely causeFix
Nothing arrives at allSoftware sending to loopback, or the two machines are not really on one networkPoint it at 192.168.10.255 or .2 directly; confirm with a ping from the Mac first
"No route to host" from the relay, but ping works fineRelay was started with nohup or left in the background; macOS pulled its Local Network permissionRun it in the foreground, in its own Terminal window; approve the permission prompt
Rate collapses to about one frame every six secondsApp Nap throttling the lighting application in the backgroundKeep it frontmost; tick Prevent App Nap in Finder's Get Info before opening it
Traffic dies after about eight or nine secondsArt-Net node timeout — the controller dropped the iPad after missed pollsRescan for devices in the lighting software
DATAGRAMS keeps climbing, ART-NET stays flatSomething that is not Art-Net is arriving on the portCheck what else on the network is sending to port 6454
Capture is missing its opening secondsSong was started before the iPad finished announcing itselfWait for "Getting the rig's attention" to finish before the song starts
Chapter thirteen

The remote

The band sees the set on their own phones. Whoever holds the password can run the show, and the mix, from there too.

There are two of these, and it is worth knowing which you want. Remote mode is this same app on another device, driving the show running on the iPad: it finds the tablet by itself, so there is nothing to type. The web remote is a page the iPad serves, opened in any phone's browser — no app to install, so anyone in the band can use it. Both are served by the iPad and both work with no internet at all.

Remote mode

Under the Showtime door, on a phone and - since 2026-11-02 - on an iPad too. Nothing technical ever stopped the second one; the door simply sat inside the phone's own shell, and a spare iPad is exactly what a band already has at the other end of a stage. On a large screen the column is held to a readable width in the middle rather than stretched, so every control stays the size a thumb was given and the set can be read from across a room.

It lists the tablets it can see, each row saying which set that one has loaded, which is the fact worth knowing from across a room. A tablet is named as its owner named it - "Nicks iPad" rather than "Show Sequencer Remote" - and will not offer you the device you are standing on, which matters more than it sounds: a remote driving its own tablet would appear to work perfectly and would go unnoticed until a second device was expected and never turned up. Tap one and you get the now-playing card, the setlist and the Play bar, drawn the same way Showtime draws them — no video and no waveform, since the phone does not have the files and streaming them is the one thing here that could cost the show something.

It asks for the password at the first command that needs one, not at the door, and remembers it for that tablet. If the link drops it says so plainly, and says whether the show was playing when it went — that sentence is the most important one in the mode, so it is only ever shown when it is true. It locks itself after a minute untouched, because a phone in a pocket presses things.

The web remote

Remote control card
Settings → REMOTE CONTROL. Serve the page, see the address to type, and set the password that grants control.
  1. Turn Serve the phone remote on. The card shows an address.
  2. Open that address in any phone's browser, on the same network. Nothing to install, and it works with no internet.
  3. Watching needs no password: the setlist, what is armed, what is playing, time left.
  4. Set a remote password to allow control - at least six characters. A phone types it once and remembers it.
  5. Changing the password revokes every phone that knew the old one.

The remote can Play, Stop and cue a song, exactly as before. It now has a second screen too - a SHOW/MIXER switch at the top of the page - carrying the same faders, mute and solo as the iPad's own mixer, and the same bus-first board: a rail of chips picks the mix, and a fader sets that track's level into that one mix rather than everywhere at once. Touch a fader on a phone and the same fader moves on the iPad at once; watch the strip and you will see it happen, or catch it afterwards as a line in the Debug screen's system event log naming which control a remote last changed and when. It still cannot jump straight to another song while one is playing (Play Now), rename or reroute a bus, add or remove one, or change anything under Settings.

Five wrong passwords from one phone in thirty seconds gets that phone refused for a minute. No lockout to clear from this end - it lifts on its own once the minute is up.

The remote password cannot be the same as the stand password (chapter fourteen). The stand address is a separate page for the rest of the band: it shows charts and score parts and can control nothing.

Chapter fourteen

Stands: charts and score parts

Band members' own phones and tablets can show the current song's lyric-and-chord chart, or their own page of the score. Read only. Nothing on a stand can touch the show.

A score can scroll itself. The app reads a part's own bar numbers out of the PDF - a Sibelius export writes them as text, not as a picture - and ties them to the song's click, so the music moves under the reader while it plays. Nothing is set up: every part of a song is read in one pass the next time the show is stopped. A part with no bar numbers printed on it, such as a scan, is the exception, and its page turns can be tapped in once instead. Auto-scroll needs the song's metronome to have been analysed, because that is what turns a bar into a moment.

Scores: the stand inside the app

A band member with EZRig on their own iPad or phone does not have to type an address at all. Scores sits under Remote on the door list: it finds the tablets serving stands, asks which instrument you are tonight, and then shows nothing but music.

The questions come in the order they are actually asked - which tablet, which part, then the page - and that order is what lets the last screen be bare. Everything needing a menu has already been answered by the time the music is up.

The instrument picker
Which instrument are you tonight. Every part anywhere in the set, not only in the song that is armed, with the chart at the top of the same list. The stand remembers what you picked.
A score part on a stand
A part, upright and whole. The bars sit over the page rather than beside it, so they cost the music no height, and a tap in the middle takes them away altogether.
A chart on a stand
The chart. The same screen with words and chords instead of a page. A chart that has been timed scrolls itself; this one has not, so it is read by hand.
Four screens are the iPad's alone - the import grid, the bulk edit grid, Capture DMX and the Universe Matrix. A phone says which screen it is, what it does, and what this phone can do instead, rather than offering a squashed version that looks like the feature and behaves like a trap. Debug was nearly the fifth and is not: it draws a single column on a phone - the session log, the ready checklist, and the export and report buttons - and says in one line which panels it left out.

Two addresses, two jobs

AddressForCan it control the show?
Remote Control (chapter thirteen)Whoever runs the show or the mix from a phoneYes, with the remote password.
StandEveryone else in the band, in a browser or through ScoresNever. It has no play, stop, cue or mix at all.

Hand the stand address round freely. It never asks for the Remote Control password, so giving it out never gives out the mixer.

Adding a chart and parts to a song

Open the song editor. The CHART AND SCORES section appears once the song has been saved at least once. Changes here are written straight into the song folder, not held for the editor's Save, and they are refused while the show plays.

Charts and parts are part of the song folder, so a rig backup carries them. The prepared page images are left out of a backup and rebuilt when needed.

The chart and scores section
CHART AND SCORES in the song editor, on a song that has neither yet. Import takes one chart; Add a Score Part (PDF) takes as many parts as the band has.

Turning stands on

  1. Settings, Remote and stands, Stands: turn on Serve charts and scores to stands. It is off until you do. iOS may ask for local network permission the first time.
  2. The card shows an address like http://192.168.1.23:51828/. Open it in any browser on a stand, on the same network. Nothing to install, and no internet needed.
  3. Optional: set a stand password, at least six characters. A stand types it once. It must be different from the Remote Control password; the card refuses one that is the same. Changing it sends every stand back to the password prompt and leaves Remote Control phones alone. With no stand password, anyone on the network can read the charts, and nobody can control anything.
  4. The link choice on this card is shared with Remote Control: changing it on one changes it for both.
Picture still needed: the Stands row in Settings' Remote and stands area, turned on, showing the stand address and the password line.
Settings, Remote and stands -> Stands.
Picture still needed: the stand page itself on a phone and on a tablet, showing a chart and a two-page score spread. It needs real devices on the rig's network.
The stand page.

On the stand

Turn auto-lock off on each stand device. A web page on the local network cannot keep a phone or tablet awake by itself, so a stand left alone will go dark mid-song unless its own screen lock is set to never.
Chapter fifteen

Networks

Only lighting and the remote need one. Audio, video and MIDI over DIN do not.

Reading the link

Settings -> Network says whether you are on a wired link, Wi-Fi or nothing, and what each service is bound to. Debug -> NETWORK lists every interface by name and address - the quickest way to tell whether an adapter is really there.

Pinning a service to a link

Each of the three network users - DMX output, DMX capture, the remote - can be set to any link, wired only or Wi-Fi only, each in its own area: the first two in Lighting, the third in Remote and stands. Pinning lighting to wired means it will not quietly fall back to Wi-Fi and stutter; a service pinned to a link that is not present says so rather than pretending.

The Network area of Settings
Settings, Network. Nothing to set here: the network is what you plug in. Each service picks its own link in its own area - a capture's choice sits in Lighting, beside the output's, since both are about the same wire.

A wire for lights, Wi-Fi for everything else

  1. A USB-C Ethernet adapter at each end, one cable between them, or both on a switch.
  2. Fixed addresses: lighting machine 192.168.10.1, iPad 192.168.10.2, mask 255.255.255.0, no router.
  3. Restart the lighting software after the link is up — most only offer destinations whose interface existed when they started.
  4. Leave Wi-Fi on. It carries MIDI and the phone remote at the same time.
Why not just Wi-Fi? An iPad's radio sleeps between bursts. A stream sent at forty frames a second arrives in clumps and reads far lower, which shows up as lighting that lags and then catches up. On a wire it simply arrives.
Chapter sixteen

Backup, and moving iPads

One file. Everything that matters. Nowhere near the internet.

This is not the shared show. A backup is one file taken against disaster and restored whole; a shared show (chapter seventeen) is a folder the band keeps in step song by song, and it must never replace a library wholesale. They were neighbours in Settings until 2026-10-17 and are two areas now, for that reason.
Backup card
Settings → BACKUP. When you last backed up, a button to do it now, and a button to restore.

What is in it

Every song folder whole — audio, MIDI, video, lighting, names, levels, waveforms — every set, every backdrop, every design you dropped in, and the rig's own profile. Left out: where the show last stopped, developer recordings and exported logs.

Backing up

  1. Back Up Now. It checks there is room first.
  2. Choose where it goes in the Files app — a USB stick, a cloud folder, anywhere you like.
  3. It is refused while anything is playing.

Restoring

  1. Restore… and pick the file.
  2. It shows what it would replace and what it would add before doing anything.
  3. Rig settings come back only if you tick the box — another iPad's outputs and MIDI destination may not suit this one.
  4. Nothing is moved into place until every part has been read, so a half-copied file leaves your library untouched.
Chapter seventeen

Sharing a show between iPads

One Dropbox folder, several iPads, and nobody wondering whether their copy is the current one.

What it is

A shared show is one folder in Dropbox that holds the band's songs, and several devices that keep themselves level with it. Somebody re-bounces a stem on a Mac and drops it in. Somebody fixes an alignment on the night. Everybody else's iPad notices, says which song, and takes it when they ask it to.

It is not a new place to keep your music. It is the folder you almost certainly already have, with the app taught to read it.

Why your iPad still keeps its own copy

The honest answer to "can we have one copy of the truth": the folder is the truth, and your iPad keeps a copy of it anyway. That is deliberate, and it is the oldest rule in this app - a prepared show runs with no internet at all. A venue's Wi-Fi is not something a set should depend on, and a backing track streamed out of a cloud folder mid-song is exactly the failure this app exists to prevent.

So the folder is where the band exchanges work, and the iPad is where the show plays from. What disappears is not the second copy. It is the guessing.

Without oneWith a shared show
Getting a new bounce inDownload the folder, bulk import, re-do the namesThe iPad says a song changed; you tap Take
Knowing something changedSomebody says so in a messageThe iPad says so, by song
Alignments and namesLive on one iPad onlyTravel with the song

Dropbox, and only Dropbox

The app talks to Dropbox itself rather than through the Files app, and that is not a preference. It was built the other way first - one folder picked in Files, which would have reached Drive, OneDrive, iCloud and a USB stick too - and two devices disproved it in an evening: the same file, in the same shared folder, read through each device's own Files provider, came back as different bytes with different dates and no error on either side. A bandmate's published change could sit unnoticed until somebody opened the file by hand.

Dropbox answers the question properly. It computes a hash of every file and reports it in the listing, so the app can tell which copies differ without downloading anything - a check moves no media at all, however big the show is.

The other two were tried and will not do it. Google Drive was built and then measured: the free permission an app can ask for covers what it created and what you picked, and picking a folder conveys nothing about what is in it - a folder with one file in it listed as empty, with no error. A stem your guitarist drops in from a Mac is invisible by that same rule, which is the whole job. The engine behind it is written and costs nothing, in case Google ever ships a scope that can read a folder. iCloud has no interface of this kind at all.

Using a folder you already have

This is the ordinary case, not a special one. You already have a folder per song with the stems in it. Point the app at it.

The app looks at what is in the folder and decides which of three things is happening. There is no mode to pick and get wrong.

What is in the folderWhat happens
NothingCreate. This iPad publishes its songs into it.
Songs, and it is already a shared showJoin. This iPad takes what is there.
Songs, but no shared show yetUse it as it is. The app adopts the folder: the songs in it become the show.
Adopting a folder never changes what is already in it. Nothing is renamed, moved, reorganised or deleted. The app adds one small hidden file saying "this is a shared show", and later, when you first name a track or save an alignment, a tracks.json in that song's folder. Your Cymatic already does exactly this - song.set sits beside the stems for the same reason - and the two ignore each other.

It also recognises the two folders that are not a show: one holding loose audio, which is a single song's own folder (it says so, and says to try the folder that one is in), and one with nothing shaped like a song in it at all, which almost always means the wrong folder was picked. Nothing is written in either case.

What a song folder has to look like

Less than you would expect. The folder's name is the song's name - yours already are. Any .wav, .aiff, .caf, .m4a or .mp3 in it is a track, in name order, keeping whatever it is called. MIDI and video keep their names too: a song's Black Parade.mid or Helena Live.mov is found as it stands.

The one case the app will not guess at is two MIDI files, or two videos, in one song folder. It takes neither rather than picking, because a video picked wrong is on a screen an audience is watching and a MIDI file picked wrong is a program change on somebody else's rig that nobody can see. Name the one you meant and it is used. Everything else - song.set, Ableton's .asd files, notes, artwork - is left alone and travels with the song.

A Logic or GarageBand project in a song's folder stays where it is and travels to nobody else: it is a folder of hundreds of files wearing one name, and carrying it would put all of them in every listing and every check.

What is checked before you adopt. An import converts every track to one sample rate, because a song's tracks are scheduled against a single clock and have to agree, and taking a song from a folder copies the bytes as they are - so a song bounced across two sessions at two rates would be refused when it is armed, at the kit, with an audience in. Those songs are named at adoption instead, along with any holding two MIDI files or two videos. You can carry on and fix them later; they are simply the ones that would otherwise fail at a soundcheck.

Setting one up

Two ways to the same sheet: New Song on the Songs screen has a Dropbox tile, and Settings has a File sharing area of its own. It is its own area rather than part of Backup on purpose - a backup is one file taken against disaster and restored whole, a shared show is a folder a band keeps in step song by song, and somebody looking for one and finding the other is being offered the opposite of what they came for.

  1. Connect Dropbox. Once, on this device. Nothing leaves the iPad at this point.
  2. Choose a folder, one level at a time, in the app. You are choosing the folder that holds the song folders - Middlenight Men, not one song inside it and not Band above it. You can make a new folder here too, so there is no trip to Dropbox and back.
  3. Read what it found. It says which of the three above is about to happen, and how many songs, before anything is written.
  4. Say where the songs should be filed - a library folder on this iPad, offered with the shared folder's own name. That is how your Songs screen is organised and changes nothing in Dropbox.
  5. Let it run. A thirty-song set is several gigabytes and is bounded by your broadband, not by the app. Do it at home the night before, not at the venue. It is safe to leave: nothing reaches your Songs screen until a song is complete and checked, so an interrupted download leaves you with fewer songs rather than broken ones.
A blank iPad is the easy case, and the one to start with. Joining on an iPad that already has its own copies of the same songs is the awkward one: the app cannot know whether your Helena or the folder's is the newer, so it asks you song by song. If you have an iPad with old copies on it, it is usually less work to delete those songs first and join clean.

Publishing rather than joining - a set you built on this iPad and no shared folder yet - is the same sheet with an empty folder. One step comes first and nobody guesses it: put the set's songs in one library folder (Songs, Bulk Edit, select them, Move to folder), because a shared show covers a library folder and the app needs to know which songs you mean. A set only travels when every song in it is in that folder, since a set half in and half out would leave everybody else with a running order naming songs they will never have.

What travels, and what stays here

TravelsStays on your own iPad
Songs - stems, video, MIDI, lightingWhich output each bus comes out of
Track names and orderYour bus names
Levels, mute, and each track's level into each busScreen latency and the lighting node's address
Video and lighting alignmentRemembered interfaces
Charts and score partsTheme
Sets, where every song in them is sharedHow your library is filed into folders

The right-hand column is the rig, and it is why a shared show is safe between iPads with different hardware: a four-output interface and a phone with two outputs can hold the same songs and each send them where they need to go. If the rig travelled, the first sync would hand somebody a routing map for an interface they have never owned.

Bus names are compared, never copied. A track remembers that it goes to output 3. What output 3 is called, and what is plugged into it, belongs to each iPad. If your bus 3 is the click and somebody else's is a guitar, the songs are right on both and the sound is wrong on one - so the app compares the names, says the two rigs disagree, and points you at the Line Check. It never quietly applies another rig's names to yours.

Waveforms, meter envelopes and video filmstrips do not travel either, and that is a fix rather than an omission. They are rebuilt from the media on each device anyway, so sharing them bought nothing - and because each one records the date of the file it describes, and Dropbox rewrites dates on upload, every device rebuilt them on arrival and published a change back. Two devices can keep that going for ever. Excluding them stopped it.

A week in the life

  1. Tuesday, on the Mac. You re-bounce the bass for a song and drop the file into its folder in Dropbox, over the old one. Nothing else to do.
  2. Wednesday, on your iPad. The File sharing row says that song has changed. You tap it, and the new bass lands. Your alignment and your track names are untouched: only the file that moved is replaced.
  3. Thursday, at a rehearsal. The deputy spots that a video is a frame or two late and fixes it in the alignment window. His iPad says he has something to publish. He publishes.
  4. Friday, before the gig. Your Line Check says you are behind the band. You take the update, and nothing of yours is lost.

Each of those is one tap, and none of them is "download the folder again". Every publish after the first sends only what actually changed, which is usually one stem.

Being behind the band is a note, never a blocker. The Line Check says so, because an iPad a revision behind may play an older alignment than everybody expects. It is not counted among the things to fix before you play: the commonest place to be behind is a venue with no usable Wi-Fi, where taking the update is not something anybody can do.

When things disappear

A shared folder has a particular way of going wrong: a folder that has not finished syncing down looks exactly like one somebody has emptied. The app will not act on that.

Two devices, one song, both edited

If you and somebody else change the same song between checks, that song is a conflict and nothing is decided for you. The details sheet lists them and you answer each one: keep mine, or take theirs. Changes to different songs never conflict, and two devices making the same edit is not a conflict either.

A song somebody has put in the folder that is not part of the show yet is offered, never taken automatically: the details sheet names it and you say whether it belongs. Deriving membership from whatever is in the folder would turn one person's tidy-up into a deletion on four iPads.

Two bands

A shared show covers one of your library folders, so two bands are two shared shows with two folders and nothing in common. A song can only be in one. Tidying your library on a Tuesday cannot remove anything from anybody's show - what a show contains is the folder's own statement, not a guess from how you have filed things.

Quick answers

QuestionAnswer
Can I use the Dropbox folder we already share?Yes - that is the ordinary way in. Point the app at it and nothing in it changes.
Do I have to rename my stems?No. Audio, MIDI and video all keep the names they have. The only thing to tidy is a song folder holding two MIDI files or two videos, where the app will not guess which you meant.
Will it play straight from Dropbox?No, and deliberately. The show plays from the iPad so it runs with no internet.
Does it still need a bulk import?No. That is the step this replaces.
Will my routing be overwritten by somebody else's?No. The rig never travels, in either direction.
Does a check cost data?No. Dropbox reports each file's hash in the listing, so nothing is downloaded to find out whether anything changed.
What if I am signed out?It says so and offers to sign in, rather than reporting itself as offline - those are different problems with different answers.
Chapter eighteen

Settings, area by area

These describe the rig and stay on this device. A list of areas down the left, the settings themselves on the right, and every one of them says what it does, when you would change it, and what it would do to a running show.

The Settings screen
Areas, not one long page, in three groups: the rig, how it looks, and looking after it. A row carries its current value on the right, so reading what something is set to costs nothing; the explanation and the control itself are behind a tap on the row, because that is where the question gets asked. The Tonight area in this picture no longer exists.

The two marks on a row

They answer different questions and it is worth keeping them apart. The effect mark says what changing this would do to a show that is playing right now:

MarkMeans
LiveReaches the stage the moment you change it, mid-song included.
Next songTakes effect at the next song boundary, not before.
Locked while playingWaits until the show stops. The row says so and states why, rather than going grey.
This screen onlyChanges nothing the audience can hear or see.

The dot beside the title says whether the thing itself is working: green when it is plugged in and answering, amber when it wants a look, and absent when there is nothing to say.

A rig where everything is fine has no amber anywhere. That is the point of the dot, and the reason "off on purpose" counts as neither working nor wrong. Before it, a healthy rig still read as a page of warnings, because nothing on the screen was ever allowed to say it was fine.

A few settings stage rather than apply: screen latency and the lighting delay collect their steps and write them on Save, with Revert beside it, because nudging a number ten times should not be ten writes to the rig. And four changes ask once before landing mid-show — turning off video output, turning off lighting output, turning off the phone remote, and switching the MIDI destination — since each one takes something away from a stage that is currently using it.

Twelve areas, in four groups

THE RIG holds Audio, Video, Lighting, MIDI, Remote and stands and Network. HOW IT LOOKS holds Showtime screen and Theme. LOOKING AFTER IT holds File sharing, Backup and Troubleshooting. THE APP holds Full version, on its own and last, because it is a fact about the app rather than a job to do to the rig (chapter one).

There was a twelfth, called Tonight, and it went on 2026-09-27. The sidebar already had a check by that name, and one word naming two different screens is one word doing two jobs. Its five settings moved to the areas they belong to: rig status and Find your outputs to Audio, screen latency to Video, the test note to MIDI, and the curfew to Showtime screen, where it already was.

Audio

SettingWhat it decides
Rig statusWhat interface is connected, how many outputs it has, whether a screen is attached, and what routing this device remembers (chapter five).
Reclaim the audio outputTakes the outputs back when another app has them.
Find your outputsPlays a tone down one output at a time, so you know which is which. Refused while the show plays.
Lead-inWhether a song waits for its video or starts on time and clips it.
MetersWhether a meter reads before the fader or after it. After it by default; before it is what a desk calls PFL, and it ignores mute and solo, so a channel pulled down still shows signal arriving.
If the interface failsOff by default. Where each bus lands on the iPad's own speaker if the interface goes - left, right, both or nowhere - so a dead interface is a smaller disaster than silence.
The Audio area of Settings
Audio. Buses, levels and which output a bus leaves by are in the Mixer, not here, because they are part of the mix.

Video

SettingWhat it decides
Video outputWhether video is sent to the external screen at all. On by default.
Screen latencyHow late the audience's screen shows a picture, with the Sync Check beside it. One number for the rig; a song's own shift lives in its alignment window.
Video fadeThe rig's own fade, which sets and songs may each override.
BackdropsWhat plays when a song has no video of its own.

Lighting

SettingWhat it decides
Send lightingArt-Net out or not. Turning it on is what asks iOS for permission to reach the local network.
Node address and portWhere to send it. Committed when you leave the field, not per keystroke.
Find nodesAsks the network who is out there and sets the address from the one you tap.
Send a test signalReplays a real song's lighting at the node for a few seconds, so you can prove the chain at a soundcheck without starting a song. The armed song's if it has any, otherwise the first in the running order that does, and the exact frames a Play would send - it sent an invented blackout until 2026-10-31 and failed twice on the rig, where the difference between this button and the Play that worked was never in the sending. A rig with no DMX anywhere gets a sweep instead, every channel fading up and down, because there is nothing to be faithful to.
RateMatch the recording, or a fixed 44 a second.
Short lighting framesOff by default. Sends only the channels a song uses instead of all 512. Whether it helps is a question about your node, not about the app - on the rig it measured as no gain at all, because the node padded the frame back out.
Lighting delayThis output's own hardware delay, staged and saved.

MIDI

SettingWhat it decides
MIDI destinationWhere MIDI goes. It says whether it can actually reach what is named, rather than only which name is selected.
Test noteProves the chain before a song does. The result is shown under the button, so a press that could not send looks different from one that worked.
Pedals and triggersWhich keys a footswitch sends and what they do; MIDI notes learned from the gear itself; and the guard window that ignores a second press too soon after the first.

Remote and stands

SettingWhat it decides
Remote controlServe the phone page, its address, and the remote password that grants control of the show and the mix.
StandsServe charts and score parts to the band's own devices, the stand address, and an optional stand password. Shares its link choice with Remote control (chapter fourteen).

The ready board - the shared page for band, FOH and monitors, which signals people and controls nothing - sits in the Network area rather than this one.

Network

SettingWhat it decides
NetworkWired, Wi-Fi or nothing, in plain words, and every interface actually present. No network is a valid rig, so this is never a fault.
Link per serviceLighting, a DMX capture and the remote can each be pinned to wired only or Wi-Fi only. A pinned service refuses the other link rather than quietly falling back.

Showtime screen

SettingWhat it decides
Showtime styleBand or Solo. Solo is a chart-led screen for one performer; chapter seven covers both.
Turn upright with the iPadWhether the app follows the iPad's orientation. Off by default, and app-wide rather than per screen, because iPadOS turns every screen or none.
CurfewWhether to warn against one, and the time. Also editable from Showtime by tapping the banner.
Confirm before Play nowWhether the Play now button asks first.
During a showKeep the screen awake, the wall clock, time left in the set.
Beat flashAround the whole screen or only the video pane, and how bright and how wide. Never shown on the external display.
AnimationHow long the app's own transitions take, or off.
Start hereWhether the chooser opens with the app. It never appears after an interruption, whatever this says.
Line CheckWhether the pre-show check is offered on the way to Showtime.
The Showtime screen area
The beat flash takes a strength and a size as well as a placement, so it can be read across a stage or kept to a hint.
The Theme area
Themes differ in shape, depth and density, not only colour. A design dropped into Files appears here with no rebuild.
The File sharing area
File sharing is one row, and that is the point of it. A shared show is a folder the whole band reads, so an alignment fixed on one iPad reaches the others; it earned an area of its own because a backup and a shared show are not neighbours - one is a single file taken against disaster, the other is a library kept in step song by song.

Theme, File sharing, Backup, Troubleshooting and Full version

SettingWhat it decides
ThemeThe nine built in, plus any design dropped into Files. Look for new designs picks those up; Export this design writes the current one out as a starting template.
File sharingA folder on Dropbox that the whole band reads, so an alignment fixed on one iPad reaches the others. Its own area since 2026-10-17: a backup is one file against disaster, a shared show is a library kept in step song by song, and they are not neighbours.
BackupBack up now, restore, and when you last did (chapter sixteen).
Send a reportGathers the device, the rig and what went wrong into one message with the session log attached, and shows it to you before anything is sent.
Show me the tour againPlays the short tour the app opens with on a new install.
Debug passphraseWith none set, Debug opens on a two-second hold. Set one for gigs where somebody else can reach the iPad.
Share anonymous diagnosticsWhether this device sends reliability figures, and whether it is marked as a test rig so its data is kept apart.
Start the rig settings againTwo ways out of a rig state you cannot undo, narrower first: forget the remembered interfaces, or reset every rig setting. Neither touches your songs or sets, and each says what goes and what stays before doing it.
Full versionDays left in the trial, or Bought, with the buy and restore buttons behind it (chapter one). Last, on its own, because it is a fact about the app rather than a job to do to the rig - and never locked while playing, since refusing somebody Apple's own sheet mid-show would be this app interrupting a show over licensing.
The Troubleshooting area
Troubleshooting. Send a report first, because it is the one that gets used in anger; the resets last, because they are the ones you want to have read about before pressing.
Chapter nineteen

When something is wrong

What it means, and what to send afterwards.

What you seeWhat it means
A file you copied in isn't thereLook for new files, in the overflow on Songs. Files added behind the app's back are not noticed until something looks again.
DMX light greyThis song has no lighting. The light stays in place so "none here" never looks like "gone".
Capture says "nothing yet"Packets are not reaching the iPad. Use Test DMX Input to separate the network from the capture.
Capture DMX greyed outSomething is playing, the app is still preparing, or there is no link — the reason is printed beside it.
Lighting slightly outOpen the song's alignment window and drag the DMX lane. Right is later. Save when it looks right.
Every song's video late by the same amountThat is screen latency, not the songs. Run the Sync Check in Settings (chapter eight).
One song's video outOpen that song's alignment window and drag the Video lane against the singer's mouth.
Save greyed out in the alignment windowNothing new to save, or the show is playing. Stop the show; your edits are kept.
"Video will not be presented"No screen attached, or video output is off in Settings.
MIDI arrives but nothing startsCheck which note the song sends and what the receiving machine is armed for. They are rarely the same across songs.
A track plays but no bus fader moves itThat track is sent somewhere this rig has no bus for, so it goes to the front-of-house bus. The mixer names which tracks, and ticking a bus on the track fixes it.
Lighting never sendsIt holds until the first Play after launch, on purpose, and the status line says so in those words rather than reading as a fault. To prove the chain before a soundcheck, use Send a test signal in Settings - that line then leads with the frames a second actually leaving, measured, rather than the rate you asked for.
The node cannot be foundBoth ends have to be on one network, and a node fresh out of the box usually is not. Find nodes in Settings asks who is out there.
A bus is silentA bus with no output chosen makes no sound anywhere — that is deliberate, so it can never appear in the wrong speakers. Tap its name plate in the mixer and give it one.
The rig is in a state you cannot undoSettings → Troubleshooting has Forget the remembered interfaces and Start the rig settings again. Neither touches your songs or sets, and each says what goes and what stays before doing it.
Debug will not openHold it for two seconds. That is deliberate.
Play is refused and says the trial has ended28 days are up, and playing a show is the part that needs the full version (chapter one). Everything you have built is still here, and the sheet it raises has the buy and restore buttons on it. If you have paid already - on another device, or before reinstalling - restore rather than buying again.
The debug screen
Debug. A dark, diagnostic screen: transport, setlist, buses, faults, readiness, the video preview and the session log. It follows its own look rather than your theme, on purpose.

Two panels on it are worth knowing about. The system event log carries MIDI, transport and faults, filterable by kind and kept for the whole session rather than cleared at each stop. Diagnostics carries the numbers behind the plain-words warnings — routing, meter health, dropouts, timing.

After a bad gig, export the session log from Debug and send it. It is saved at every stop, never during playback, and the last five sessions are kept.
Chapter twenty

Appendices

A · What is on disk

Everything the app writes is plain, versioned and yours. A song folder holds its audio, its MIDI file, its video and its song-lighting.dmx - the MIDI file and the video may be called anything, since a song assembled by copying files in is a supported way to build one - plus tracks.json (names, order, levels, buses, offsets), waveform.json and levels.json, and video-filmstrip.bin (the stills the alignment window shows, rebuilt whenever needed). tracks.json also holds the song's alignment: its video shift, DMX shift and markers. A song may also hold a chart file and PDF score parts, with their prepared pages in a hidden .score-pages folder that a backup leaves out. Sets live in Playlists/, backdrops in Backdrops/, designs in Designs/, and the rig's own settings in profile.json.

B · The themes

Nine ship, and each one answers a different working condition rather than a different taste in colour. They differ in shape, depth, density and type as well - a theme is not a repaint, and no two of them are allowed to differ in colour alone.

ThemeThe condition it answers
PosterThe default, and the one every other picture in this manual uses.
DaylightAn afternoon set outdoors: a near-white page with heavy strokes, because in sun a shadow carries nothing and stroke weight buys more than point size.
ConsoleA desk: dark graphite, rounded, with depth.
RackHardware: brushed metal and engraved labels.
Aurora, Ember, Tide, OpalThe glowing set - cool, warm, long-evening and a light one with depth rather than hairlines.
NeonA sign: bright edges on near-black.
Console theme
Console: dark graphite, rounded, with depth - a desk.
Studio and Blackout have been retired, along with Chalk, Avionics and the old System theme. A rig still set to one of them keeps working and says, in the Theme area, which theme is standing in for it and why. The picture above of the Studio theme is kept because it is what that rig would have looked like; it is not a theme you can choose today.
Studio theme
Studio, retired: light, square and flat, for a lit room.

Any design dropped into Files appears beside them with no rebuild.

C · The collapsed sidebar

Collapsed sidebar
The sidebar narrows to an icon rail when you want the width, and the Showtime door stays at its foot.

D · Developer harnesses

One screen exists for building the app rather than running a show, reached by launch argument in a development build. The design gallery that used to sit beside it is gone: the two halves an operator actually wanted from it — looking for new designs, and exporting the current one as a template — are rows in Settings' Theme area instead.

Recording viewer
The recording viewer: Showtime drawn from a recorded state, so a screen can be checked at a desk with no rig at all.

E · The rules, once more