Create and Route Virtual Audio Devices

Create multichannel virtual devices on supported systems and route them through Signal.

Written By 4ALL.LIVE

Last updated 1 day ago

Create a virtual audio device when a production design needs software-to-software routing, then verify every channel before making it part of a live graph.

Best for: macOS or Linux workflows that require a named multichannel software endpoint rather than an immediate physical handoff.

Support and limits

  • Virtual device creation is supported on macOS and Linux.
  • It is not supported on Windows.
  • A virtual device can be configured from 1 through 256 channels.
  • macOS uses the Signal Audio Server Plugin for the virtual-device path.

Create and use the device

  1. Stop Signal pipelines and any affected software audio path.
  2. Create or configure the virtual device with the required channel count.
  3. Apply the change during an off-air window; playback can be interrupted briefly.
  4. On macOS, confirm that the Audio Server Plugin is available to the audio service.
  5. Add the virtual device as the intended Signal source or output and map each channel explicitly.
  6. Start a test route, meter and listen to every used channel, then stop and relaunch before the show.

Driver updates or virtual-device changes can require an audio-service restart. Schedule that restart when it cannot interrupt production, then recheck device availability in both Signal and connected applications.

Recommendation: use a physical audio interface for the final transmitter handoff unless the approved production design specifically requires a virtual device.

Verify the virtual route

  • The configured channel count matches the plan.
  • The virtual device appears after the relevant audio service and Signal restart.
  • Each source channel reaches only its intended destination channel.
  • No production application changes the device rate or mapping unexpectedly.
  • An approved physical or software fallback is ready.

Troubleshoot

  • Device absent on Windows: virtual-device creation is not supported; use a supported external or physical routing design.
  • Device absent on macOS: check the Audio Server Plugin and restart the audio service during an approved window.
  • Brief silence after applying changes: allow the audio service to settle, then restart and validate the stopped pipeline.
  • Channels swapped: stop and correct the Signal and application mappings together.
  • Device disappears after an update: verify the driver or plugin update and perform the required audio-service restart.

Operational boundary

A virtual device is a local software endpoint. It is not a transmitter, an RF channel, or an attendee listening system, and it does not replace physical-output validation when hardware receives the final feed.