Build a stage plot. Input-bearing elements and manual inputs create a sorted, numbered list; visual-only elements stay visual.
Free tier with watermark · Pro: $99 one-time
Three steps. One shared source.
Place instruments and microphones on the stage. Input-bearing elements create channels; amps, risers, furniture, and annotations remain visual unless you add an input manually.
Channel numbers, names, mic/DI types, phantom notes, and stereo pairs follow your authored input data, with a practical editable K·S·H default order.
Export supported console files and PDF/PNG documents from the same plot. The preview states the limits of each workflow.
Practical crew fields, generated where source data exists and editable before export.
Start free. Upgrade when you need clean exports.
Core planning tools, no credit card
One-time purchase. Clean exports and supported Pro workflows.
One-time purchase · No subscription · No recurring charge
Not sure? Start free. Upgrade when you need clean exports or unlimited plots.
Everything you need to know about input lists.
An input list is channel-by-channel documentation of every audio source on stage. It lists channel number, source name, mic/DI type, stand type, phantom power requirements, and notes. Engineers use it to prep the console and communicate with the stage crew before soundcheck.
K·S·H means Kick, Snare, Hi-hat. load·in uses a practical, editable default order that begins there and groups related inputs. It is not a universal rule; rename or reorder any channel for your workflow.
Build a stage plot in load·in and the input list follows source elements that define audio inputs. Instruments, microphones, DIs, and playback rigs can create channels; amps, furniture, infrastructure, and annotations stay visual unless you add a channel manually.
A useful input list includes channel number, source name, mic/DI type, stand type, phantom requirement, stereo, color, and notes. load·in derives fields where the plot or input data supplies them, and every field remains editable before export.
Yes. Native X32/M32 scene export is free; Pro adds the currently supported paid console workflows. Each export carries only the fields named in its preview, and console files should be verified in the official editor or target desk.
An input list documents what enters each channel. A patch list documents physical connections. load·in can record both, but native routing is written only where the selected console preview explicitly says so; it is not a blanket promise across desks.
Build a stage plot. The input list generates automatically.
Try load·in Free →No signup required. Works in your browser.