Nodes/IAMCCS-nodes/IAMCCS ControlAudEfx
ComfyUI Node

IAMCCS ControlAudEfx

The deprecated version of IAMCCS's AudioBoard effect controller

By IAMCCS·Created 11 months ago·Updated 8 days ago· 113
IAMCCS ControlAudEfx
  • cine_linx
  • cine_linx_from_arranger
  • cine_linx
  • effect_graph_json
  • selected_clip_json
  • report
control_data{ "schema": "iamccs.control_aud_efx", "schema_version": 1, "selectedClipId": "", "view": "eq_wave_spectrum", "metering": { "fftSize": 2048, "smoothing": 0.72 } }

Straight answer up front: if you're setting up a new graph, don't use this node - the source marks it DEPRECATED = True. It's the compatibility/back-compat face of the AudioBoard effect-control system, kept around so old saved workflows keep loading. The node you actually want is IAMCCS_ControlAudEfxPanel, which is the same thing with DEPRECATED = False and a live category (IAMCCS/Cine/Audio) instead of a compatibility bucket.

So why does it exist? IAMCCS's AudioBoard is a frontend-heavy editing surface for arranging audio clips in multi-lane timelines, and ControlAudEfx is the companion that reads what you did in that UI and converts it into something the graph can act on. Think of it as the wire between the AudioBoardArranger's effect graph and the nodes downstream that need to know about it.

How it works

It takes a control_data JSON string (edited by the IAMCCS ControlAudEfx UI - it carries things like the selected clip id and metering settings) plus an optional cine_linx or cine_linx_from_arranger. It clones the linx, writes the effect graph and selected-clip info into it, and returns:

  • cine_linx - the updated bundle, with effect metadata baked in.
  • effect_graph_json - the parsed effect chain.
  • selected_clip_json - which clip the UI currently has selected.
  • report - a status string for the console/log nodes.

The default control_data schema is worth a look before you panic-edit it: {"schema": "iamccs.control_aud_efx", "view": "eq_wave_spectrum", "metering": {...}}. It's the payload contract between the frontend and the backend - you're not meant to hand-write it.

Inputs that matter

  • control_data - required, edited by the UI. The tooltip is explicit: connect cine_linx from AudioBoardArranger.
  • cine_linx / cine_linx_from_arranger - optional. If both are connected, the arranger one wins.

That's the whole surface. There are no knobs to tune because the control surface is a browser UI, not widgets.

Install

Part of IAMCCS-nodes:

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

Restart ComfyUI, or install via ComfyUI Manager (search "IAMCCS"). The heavy AudioBoard pieces need the pack's frontend assets, which ship with the repo - no pip extras.

Gotchas

Two, really. First, being marked deprecated means the author could remove it at any point in the 1.x cycle - if a shared workflow loads it, expect a future update to ask you to swap it for the Panel node. Second, like most of the pack's audio nodes, it's only meaningful inside the AudioBoard/Arranger graph; dropped into a plain image workflow it does nothing useful. Reach for IAMCCS_ControlAudEfxPanel instead.

CategoryIAMCCS/Compatibility

Inputs (3)

NameTypeDefaultDescription
control_dataSTRING{ "schema": "iamccs.control_aud_efx", "schema_version": 1, "selectedClipId": "", "view": "eq_wave_spectrum", "metering": { "fftSize": 2048, "smoothing": 0.72 } }Edited by the IAMCCS ControlAudEfx UI. Connect cine_linx from AudioBoardArranger.
cine_linxoptIAMCCS_SUPERNODE_LINX
cine_linx_from_arrangeroptIAMCCS_SUPERNODE_LINX

Outputs (4)

NameTypeDescription
cine_linxIAMCCS_SUPERNODE_LINX
effect_graph_jsonSTRING
selected_clip_jsonSTRING
reportSTRING