Midiable

What it is

Midiable is the bridge between the Performance Percussion suite and Ableton Live. It exports your Rundown setlist as standard MIDI clips or a full Ableton Live Set, and it hosts a two-way live mirror with Live so you can see and control Live's transport and scenes from Midiable.

Requirements

• macOS
• Ableton Live 12.4.3 for the .als Live Set export (that version is what the exporter targets)
• An IAC (virtual MIDI) bus for the RundownLive mirror and clip export
• A show file from Rundown (.ppshow.json) to export from

Install & first run

1. Download Midiable from the Mac App Store.
2. Open Midiable. By default it watches ~/Documents/Performance Percussion/Shows/ for show files; use File → Open… to load one from elsewhere.
3. To export MIDI clips or an .als Live Set, open a show and use the export action in the UI.
4. To link with Ableton Live, install the RundownLink Remote Script and set up an IAC bus — see the in-app Ableton link setup guide for the exact steps (installing the script into Live's User Library, creating the IAC port, and enabling it as a Control Surface in Live's MIDI preferences).
5. In Midiable's Settings, set the IAC port name to match what you set up in Live (default name: "IAC Driver — Ableton").

Common questions

What does the MIDI clip export give me?

One folder per setlist song, with a .mid file inside for each MIDI action (Program Change, CC, or Note) in that song — plain Standard MIDI Files that work in any DAW, not just Ableton.

What does the Live Set (.als) export give me?

A full Ableton Live Set built offline from your show: one scene per song, one track per app that appears in your bindings, and MIDI clips that fire the right recall — all pre-routed to your IAC bus. No Ableton plugin or Max patch required.

Will exporting a Live Set overwrite my changes if I've already been editing it in Live?

No — if Midiable detects the target .als was edited in Live since it was last generated, it writes a new file with a "regenerated" suffix instead of overwriting your work.

Can Midiable control Ableton Live's playback?

Yes, through the RundownLink control surface over your IAC bus — Midiable can see Live's transport and track list, and can launch scenes and control transport from its side.

Do CC (Control Change) events show up in the Live Set export?

Not in v1 — CC automation in the Live Set export is planned but not available yet. The .mid clip export does include CC events if you need them now.

Troubleshooting

RundownLink doesn't show up as a Control Surface option in Live. Confirm the Remote Script folder is directly inside Live's Remote Scripts folder and contains its required files, then restart Live.

No mirror data appears in Midiable. Check that the Control Surface's Output is set to your IAC port in Live, and that Midiable's IAC port setting matches exactly.

Sending commands from Midiable does nothing in Live. Check that the Control Surface's Input is set to your IAC port in Live, and that "Remote" is enabled for that port in the MIDI Ports list.

Export warns about missing MIDI for a binding. If a trigger only has an OSC address and no Program Change, note, or CC value, Midiable can't represent it as a MIDI clip — that slot exports empty. Check the export report for the full list of warnings.

Known limitations

• Control Change (CC) automation in the .als Live Set export is not yet available — use the .mid clip export if you need CC data today.
• OSC-only trigger bindings (no MIDI equivalent) can't be represented in the Live Set export and will show as an empty clip slot.
• The Live Set export is verified structurally and against a reference file, but round-tripping it in Ableton Live itself (opening, saving, and confirming no drift) is a manual check — do this yourself before relying on a generated set for a show.

Still stuck?

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