View source for Networked Audio Library

= Setting Up Audio on a Networked Client Machine =

This page describes how to configure audio input and output on a networked client machine in a broadcast or automation environment. It is intended for client workstations that connect to a central server and rely on networked services for audio playout, monitoring, or live assist operation.

== Overview ==

In a networked audio system, client machines typically:
* Authenticate to a central server
* Access shared audio content over the network
* Use local or network‑attached audio interfaces for playback and recording

Correct audio configuration is essential to ensure low latency, reliable playback, and proper signal routing.

== Prerequisites ==

Before configuring audio on a client machine, ensure the following:

* The operating system is installed and up to date
* Network connectivity to the server is functional
* Required user accounts and permissions are configured
* Audio hardware is physically installed or available on the network
* Any required audio daemons or services are installed

== Supported Audio Architectures ==

Client machines may use one or more of the following audio architectures:

=== Local Audio Interfaces ===

Local audio interfaces are physically installed in the client machine and may include:
* PCIe or PCI audio cards
* External USB audio interfaces
* Built‑in sound devices (for non‑production monitoring)

These interfaces provide the lowest latency and are typically preferred for on‑air or production use.

=== Network Audio Interfaces ===

In some environments, audio is transported over the network using:
* IP‑based audio interfaces
* Network‑attached sound devices
* Centralized audio engines accessed remotely

Network audio setups require careful clocking and bandwidth management to avoid dropouts.

== Selecting the Audio Backend ==

Most Linux‑based client systems use one of the following audio backends:

* '''ALSA''' – Low‑level audio system, often used directly by broadcast software
* '''JACK''' – Low‑latency audio server designed for professional audio workflows
* '''PulseAudio''' – Desktop‑oriented audio system (generally avoided for on‑air systems)

For professional broadcast clients, ALSA or JACK is strongly recommended.

== Configuring ALSA Audio ==

=== Identifying Audio Devices ===

List available audio devices:
<code>
aplay -l
arecord -l
</code>

Verify that the expected input and output devices are present.

=== Setting the Default Device ===

You may define a default ALSA device by creating or editing:
<code>
~/.asoundrc
</code>
or
<code>
/etc/asound.conf
</code>

Example:
<code>
pcm.!default {
  type hw
  card 0
}

ctl.!default {
  type hw
  card 0
}
</code>

== Configuring JACK Audio (Optional) ==

JACK is recommended when low‑latency routing, signal monitoring, or advanced patching is required.

Steps:
# Install JACK and related utilities
# Set real‑time privileges for the audio user
# Configure sample rate and buffer size
# Start the JACK server before launching client applications

Common sample rate settings are 44100 Hz or 48000 Hz, depending on the broadcast standard.

== Mapping Audio Channels ==

Client applications often allow explicit assignment of:
* Playback output channels
* Recording input channels
* Monitoring outputs

Ensure each client machine uses a unique and correctly mapped set of channels to avoid conflicts.

== Testing Audio Operation ==

After configuration, perform the following tests:

* Play a known audio file and verify output
* Record a short audio clip and validate input levels
* Monitor latency and synchronization
* Confirm audio is routed to the correct physical or network outputs

Testing should be done before the client is placed into production use.

== Common Issues and Troubleshooting ==

=== No Audio Output ===
* Verify the correct audio device is selected
* Check mixer levels and mute states
* Ensure no other process is blocking the device

=== High Latency or Dropouts ===
* Reduce buffer sizes
* Disable non‑essential background services
* Verify network stability for networked audio

=== Device Busy Errors ===
* Ensure only one audio backend is accessing the device
* Stop desktop audio services if necessary

== Best Practices ==

* Use identical audio hardware models across client machines when possible
* Keep sample rates consistent across the system
* Label physical audio connections clearly
* Document each client’s audio channel assignments