Understand Signal Nodes, Ports, Channels, Sample Rates, and Routing

Understand Signal's graph model before building multichannel production paths.

Written By 4ALL.LIVE

Last updated About 23 hours ago

Use Signal's graph model to understand where audio enters, how it is processed, and where each channel leaves the workstation.

Best for: designers and operators planning a multichannel route before connecting production devices.

Node roles

  • Source nodes introduce audio from microphones, the system, an application, a file, a TTS stream, or a network peer.
  • Effect nodes change or measure audio, such as gain, dynamics, delay, suppression, EQ, reverb, or meters.
  • Output nodes hand audio to a speaker, physical interface, virtual device, network peer, or recording destination.

Ports, edges, and channels

Ports define compatible connection points. An edge carries one or more audio channels between ports. A mono source can feed a mono path, while multichannel edges preserve or map multiple channels according to the connected nodes.

  • Fan-out: one source can feed more than one downstream branch, such as an output and a meter.
  • Mixing: more than one compatible path can arrive at an output. Control levels and headroom deliberately.
  • Channel mapping: map graph channels to the intended device channels; do not assume the first visible channel is the production destination.
  • Cycle rejection: Signal rejects connections that would create a graph cycle. Redesign the route instead of trying to force a feedback loop.

Sample rates and clocks

Plan a consistent graph output rate and understand where devices or processing stages depend on a particular rate. Mismatched sample rates or unsynchronized device clocks can cause distortion, drift, clicks, or dropouts. Validate the audio interface and clocking plan before the show.

Important: a missing-device state means the saved graph cannot currently resolve that endpoint. Do not start a production route until the intended device and channels are available or an approved fallback has been selected.

Verify a route

  1. Identify the source node and its channel count.
  2. Follow every edge through processing and metering.
  3. Confirm any fan-out or mix is intentional.
  4. Check the final output device and channel mapping.
  5. Start off air and verify source, intermediate, and output meters.

Troubleshoot

  • No edge: confirm compatible ports and channel counts.
  • Unexpected mix: trace every path feeding the output and reduce or disconnect the unintended branch while stopped.
  • Feedback: remove the return path that routes an output back into its own source chain.
  • Clicks or drift: inspect sample-rate selection, buffering, and the external clock arrangement.
  • Silence after loading: resolve the missing device or saved source before starting.

Operational boundary

The graph represents Signal's workstation routing. It does not configure an external transmitter, RF channel, receiver, headset, or venue mixer.