Create, Save, Duplicate, Import, and Export a Signal Pipeline

Build reusable audio graphs and manage local pipeline configurations safely.

Written By 4ALL.LIVE

Last updated 1 day ago

Create a reusable Signal pipeline that makes every audio source, processing stage, and destination visible before the graph is used on air.

Best for: operators building a new route, preparing a repeatable show configuration, or moving an approved graph between workstations.

Create and connect a pipeline

  1. Create a new pipeline and give it a name that identifies the event, room or program, and intended output.
  2. Add the required input node.
  3. Add any approved processing or monitoring nodes.
  4. Add an output node or a monitor destination.
  5. Connect the input through the intended processing chain to the output or monitor.
  6. Check channel mapping, device availability, and sample-rate expectations before starting.
  7. Save the pipeline locally, start it off air, confirm metering and output, then stop it cleanly.

Save and name safely

Use names that distinguish production, rehearsal, room, language, and revision where those details matter. Save after a verified change, and do not overwrite the only known-good configuration with an untested structural edit.

Duplicate, import, and export

  • Duplicate: make a separate pipeline before adapting a known-good graph for another room, language, or rehearsal.
  • Export: save a transportable copy of an approved local configuration for controlled transfer or backup.
  • Import: load the configuration, inspect every node and connection, and remap unavailable devices or channels before starting.

Important: stop the pipeline before adding, removing, reconnecting, importing, or otherwise making structural production changes.

Verify the pipeline

  • The saved name identifies the intended use.
  • Every source and output resolves to an available device, event, peer, or file.
  • Channel mappings match the planned physical or virtual path.
  • Source and output meters respond without clipping.
  • The pipeline stops, restarts, and survives a Signal relaunch while off air.

Troubleshoot

  • If an imported device is missing, keep the graph stopped and select the correct available device and channels.
  • If an edge cannot be created, check port and channel compatibility and confirm that the connection would not create a cycle.
  • If the wrong output carries audio, stop the pipeline and inspect channel mapping rather than changing downstream equipment blindly.
  • If the duplicate behaves differently, compare its source, device, channel, and processing selections with the known-good graph.

Operational and security notes

Pipeline files describe local routing; they do not grant event access, license a workstation, provide LL-TTS entitlement, or validate downstream hardware. Transfer configurations only through the production team's approved process and inspect them before use.