Rundown support — Performance Percussion

What it is

Rundown is the show spine for your setlist. Build songs with a title, BPM, and key; attach up to five MIDI actions per song (Play 1–4 and Click); and run the gig from a full-screen Perform mode a sub could run cold. When you change songs, Rundown fires recall out to the other Performance Percussion apps and devices on your list.

Requirements

macOS (uses CoreMIDI for MIDI input/output)
A wired USB MIDI connection for show use (Bluetooth is not used for shows)

Install & first run

Download Rundown from the Mac App Store.
Open Rundown.
Create an artist project, then a show, then a setlist, then add songs.
Set each song's MIDI actions (Play 1–4, Click) and try MIDI learn to map them from a real controller.
Switch to full-screen Perform mode to run the set.

Common questions

What file format does Rundown save?

Shows save as .rundown files (JSON). If you have older .setline files from before the rename, Rundown opens them and re-saves in place — it never silently renames them for you. There's a one-click "UPDATE FILE TO .RUNDOWN" action in the editor if you want to convert a file, but it only happens with your explicit OK.

How is a show organized?

Artist projects contain shows, shows contain multiple setlists, and setlists contain songs. Reordering a setlist just reorders which songs play in what order — the songs themselves live at the show level.

Can Rundown control my other Performance Percussion apps?

Yes. When you change songs in Rundown, it can fire OSC and Program Change recall messages at sibling apps (like Pit, Breakbeat, or Cycle) so they follow along automatically, as long as they're on the same network.

Does Rundown work with Ableton Live?

Yes, through a two-way mirror over a virtual MIDI (IAC) bus using the RundownLink control surface, so you can see Live's state and control it from Rundown.

Troubleshooting

Rundown won't open a legacy .setline file. Make sure the file isn't open in another app or read-only. Rundown reads .setline files directly and re-saves them in the same format unless you explicitly convert with "UPDATE FILE TO .RUNDOWN."

MIDI learn isn't picking up my controller. Confirm the controller is connected over wired USB MIDI (not Bluetooth) and shows up in your Mac's Audio MIDI Setup before trying MIDI learn again.

Sibling apps aren't following song changes. Check that all apps are on the same local network and that Bonjour/network discovery isn't blocked by a firewall.

The Ableton mirror shows nothing. Confirm the RundownLink control surface is installed and routed to your IAC bus in Live's MIDI preferences.

Known limitations

MIDI-clip export to Ableton (exporting each setlist song as a .mid file) is a feature still awaiting final testing and merge — it is not yet available in the shipped app.
A per-song pad-matrix helper for the LioBox² stage controller is designed but not yet built.
Loop editing in the show editor is not yet wired up.

Still stuck?

Email [email protected] with "Rundown" and your app version in the subject line.