IAMCCS ControlAudEfx Panel

If you've ever wanted to adjust an EQ, watch a waveform, and have the changes flow into your video-generation graph - this is the node. ControlAudEfxPanel is the current, non-deprecated face of IAMCCS's audio effect-control system, and its whole job is to turn edits made in a browser UI into metadata that the rest of the AudioBoard graph can act on. It's the tool you reach for when you're doing actual sound-design work on a timeline inside ComfyUI, not just bolting audio onto a video after the fact.

How it works

The panel is a frontend-plus-backend pair. The UI writes a JSON control_data string describing the current state - which clip is selected, which view you're in (eq_wave_spectrum by default), and the metering configuration. The backend takes that string, merges it into the cine_linx it's given (the shared data bundle that travels through all the IAMCCS cine/audio nodes), and hands the result forward.

Outputs:

• cine_linx - updated bundle carrying the effect state.
• effect_graph_json - the parsed effect chain from the UI.
• selected_clip_json - what the UI currently has selected.
• report - status text for logging.

It's a state pass-through with a structured contract, which means it's deterministic: same control_data, same linx in, same graph out. No randomness, no surprises.

Inputs that matter

• control_data - required, and you're not meant to edit this by hand. The tooltip says it plainly: "Edited by the IAMCCS ControlAudEfx UI. Connect cine_linx from AudioBoardArranger."
• cine_linx and cine_linx_from_arranger - optional. If you connect both, the arranger version takes priority. Wire at least one, or the panel has nothing to attach its edits to.

That's genuinely the whole interface - the tuning happens in the panel's UI, not in node widgets.

Install

Ships inside IAMCCS-nodes; install the pack, get the node:

cd ComfyUI/custom_nodes
git clone https://github.com/IAMCCS/IAMCCS-nodes.git

Or ComfyUI Manager → search "IAMCCS" → install → restart. The frontend lives in the pack's web/ directory, which ComfyUI serves automatically, so there's nothing extra to fetch. Note this is a node that only makes sense with a recent ComfyUI build - the pack requires ComfyUI 0.3.0+, Python 3.12+, Torch 2.8+.

Gotchas

The biggest trap is expecting it to do audio processing itself. It doesn't - it's the control surface. The actual effect computation happens in the AudioBoard/Arranger nodes further down the graph. If you drop the panel in and see nothing happen, that's correct behavior; connect it into a full AudioBoard path first. And like all of IAMCCS's audio tooling, it's part of a fast-moving solo-dev pack, so if your saved workflow predates an update, re-verify the control_data schema still matches.