IAMCCS BusOut
Pull the master bus and up to five stems out of your AudioBoard mix
- cine_linx
- cine_linx
- master_out
- track_1
- track_2
- track_3
- track_4
- track_5
- bus_manifest
- report
The IAMCCS pack's AudioBoard is a full mixing surface - tracks, stems, a master bus - all living inside the pack's cine_linx connector object. But a mix that stays trapped inside a JSON blob is useless; at some point you need the audio out. IAMCCS_BusOut is that extraction point. Its docstring says it plainly: it exposes the AudioBoardArranger master bus and up to five stem tracks from cine_linx.
Feed it a cine_linx (from an AudioBoard arranger or a Shotboard stage) and pick a mode:
from_arranger_bus(default) - pull whatever the arranger's current bus mode says should go out.master_plus_stems_max_5- force the master plus up to five stem tracks.all_lanes_force- dump every lane, no pruning.
Outputs are exactly what you'd hope: master_out plus track_1 through track_5 (each a path/asset reference to a stem), the original cine_linx passed through for further chaining, a bus_manifest (a JSON describing what's in the bus - segments, track settings, bus mode), and a report. Note that the track outputs are strings (asset references), not raw AUDIO tensors - you connect them to the pack's media loading or export side, or read them for external tools. If you're not in a full IAMCCS AudioBoard workflow, that's the thing to know before you go looking for an audio waveform on master_out.
Why it exists: this is the output stage of the pack's multi-lane audio system - dialogue lanes, foley, music, effects get arranged in the AudioBoard, and BusOut is how a downstream video-combine or export stage gets the finished mix. It's also the answer to the "the AudioBoard has no output" confusion: the board is a routing/editing surface, and this node is the tap.
Installing: part of IAMCCS/IAMCCS-nodes - ComfyUI Manager → search "IAMCCS", or cd ComfyUI/custom_nodes && git clone https://github.com/IAMCCS/IAMCCS-nodes.git, restart. No models, no extra deps.
Honest take: standalone, this node does nothing - it has no required inputs beyond a mode string and reads everything from cine_linx. It only earns its keep at the end of an AudioBoard/Shotboard graph, and the README even points at a dedicated AUDIOBOARD_BUSOUT_GUIDE.md for exactly this. If you just want to splice a couple of audio clips, use the AudioTimelineAssembler instead; BusOut is for when you've built a real mix and need to get it out of the system intact. When things come out empty, the report and bus_manifest are where you check first - a from_arranger_bus mode with no arranger upstream is a "no bus found" situation, not a bug.
Inputs (2)
| Name | Type | Default | Description |
|---|---|---|---|
| mode | COMBO | from_arranger_bus | 3 options: from_arranger_bus, master_plus_stems_max_5, all_lanes_force |
| cine_linxopt | IAMCCS_SUPERNODE_LINX | — |
Outputs (9)
| Name | Type | Description |
|---|---|---|
| cine_linx | IAMCCS_SUPERNODE_LINX | — |
| master_out | STRING | — |
| track_1 | STRING | — |
| track_2 | STRING | — |
| track_3 | STRING | — |
| track_4 | STRING | — |
| track_5 | STRING | — |
| bus_manifest | STRING | — |
| report | STRING | — |