Input List & Patch Sheet Generator

Methodology

How it works

An input list describes the artist’s sources and technical needs; a patch sheet adds the venue-specific physical destination. Build one row per physical audio source and keep the channel order stable from the first advance through line check. Every row should identify the source, microphone or DI, stand, provider, phantom-power status, and any constraint that changes how the receiving team prepares. Patch values belong to a real stagebox, sub-snake, split, or console input and should be confirmed by the team that owns that system. Keep channel numbers unique and use concise source names that remain readable on console scribble strips. Stereo pairs should use exactly two adjacent channels and share a stable group name; left should precede right unless the production has documented another convention. Record 48V as yes, no, or confirm—never infer it only from a generic label such as “DI” or “vocal mic.” A provider identifies who supplies the equipment, not who operates it. Notes are for exceptions such as pads, alternate microphones, split destinations, or playback redundancy. The generator performs deterministic checks only. It flags missing sources, duplicate channels, incomplete stereo pairs, and phantom-power decisions that still need confirmation. It does not choose microphones, enable 48V, create a legal patch, or overwrite venue assignments. CSV and Markdown contain the same maintained rows, while the print view uses the current Input List or Patch Sheet view. When you continue to Techrider.live, the server validates the browser draft again before creating a Rider; channel rows are imported into the connected input list and patch-specific notes are retained with the Rider.