IAMCCS AudioBoard Arranger

The audio arrangement stage of the Shotboard pipeline

The IAMCCS pack's Shotboard system is a full multi-timeline video production path - shot boards, takes, master audio, and generated video lanes. Somewhere between planning and render, someone has to decide what audio sits on which lane, where clips land on the timeline, and how the master bus is set. That's this node: a DAW-style audio lane arranger that runs as a UI surface inside ComfyUI and writes its decisions back into the pipeline through the cine_linx contract object.

What it actually is

The arranger_data input is a JSON document with the whole arrangement state - audioSegments, audioTrackCount (5 by default), masterAudioGain, masterAudioNormalize, masterMono, a masterBus section (limiter, ceiling, compressor, width, reverb and delay sends), plus audioSyncMode and duration_seconds. The tooltip is the honest summary: "Edited by the IAMCCS AudioBoardArranger UI. Uses Shotboard V3 audioSegments schema." So the node is the backend half of a frontend editor - you mostly interact with it through the visual audio-board panel, and this node is where that state lands and gets committed.

Its real input is frame_rate (the timeline's), sync_policy, and an optional cine_linx. The sync_policy decides whether the arranged audio lanes drive the pipeline's custom audio (audio_lanes_drive_custom_audio, the default) or just produce a metadata-only report.

Outputs

• cine_linx - the updated contract, with the arrangement written into it, ready for the next stage.
• audio_timeline_json - the arrangement as a serializable timeline document.
• report - confirmation of what was applied.

When you'd use it

This is squarely a Shotboard-pipeline node. If you're building cinematic multi-lane video with the IAMCCS Shotboard/Video Editor system, this is where audio gets placed and mixed at the arrangement level - think of it as the timeline view for audio, alongside the video editor's lanes. If you're not running the Shotboard system, the node is inert: it needs cine_linx from a Shotboard planner to have anything to write into, and its outputs are consumed by the Shotboard render stages.

Install is the pack install (Manager: "IAMCCS", or clone IAMCCS/IAMCCS-nodes into custom_nodes, restart). The guide the pack links - the AudioBoard + BusOut guide - is worth reading before you fight it: this node's power (master bus, limiter, sends) only becomes visible once you understand how the board maps onto the Shotboard's master-audio flow. The honest expectation: it's a power tool for a specific production pipeline, not a general-purpose audio mixer.