💡

After installing your Raspberry Pi 5 OS, it's time to install the SOUND4 application. Please follow these steps and recommendations.

AoIP .CL

Connect BIG VOICE .Cl, IMPACT .CL & x1 .CL in an AoIP architecture

Audio over IP (AoIP) is the distribution of digital audio across an IP network. Our commitment to versatility and interoperability is reflected in our support for multiple AoIP protocols. We've implemented AES67, a crucial standard that facilitates interoperability between various IP-based audio networking technologies. We also offer compatibility with Livewire. For discovery protocols and for AES67, we've implemented both Ravenna and SAP (Session Announcement Protocol). A key advantage of SAP is that it enables communication with AES67 Dante devices, allowing us to connect to Dante, but only in AES67 mode. Of course, discovery protocol is also available for Livewire.

The AoIP version supports all available processing engines:

BIG VOICE .CL
IMPACT .CL
x1 .CL

Additionally, SOUND4 streaming and SOUND4 Kantar Media watermarking features can be integrated into AoIP versions.

OS Compatibility: ONLY compatible Debian and derivatives

The main challenge for the AoIP version is achieving low latency for live applications. This requirement necessitates using the Linux operating system, there are no Windows-compatible versions.

⚠️

We increasingly recommend using Debian versions without a graphical environment to maximize low-latency performance.

💡

See also “Raspberry Pi5 best practice” for installing your OS

Hardware compatibility: AMD64 or ARM64

Results depend on the hardware being used. While streams with longer latency will work in most cases, achieving low latency is more challenging. At SOUND4, we have fully qualified test results on Raspberry Pi 5. This hardware is capable of running 8 to 10 BIG VOICE instances with low-latency profiles.

Of course, it can work on conventional PCs or servers running Debian. However, for low-latency applications, we recommend conducting tests first since performance may vary depending on PC components.

SOUND4 AoIP installation: Debian packages…

Only two steps are necessary for installing SOUND4 AoIP:

Configure SOUND4SOFT repository

wget https://deb.sound4soft.com/sound4soft-archive-keyring.deb
sudo dpkg -i ./sound4soft-archive-keyring.deb
sudo apt update

Installing SOUND4 AoIP.CL

sudo apt --install-recommends install sound4.aoip.cl

‣

Choosing installed packages (only if needed)

‣

Customizing configuration

First connection to SOUND4 application

The AoIP .CL system is fully managed through a web interface. Simply access the Raspberry Pi's IP address from any computer on the same network to open the user-friendly interface.

💡

By default, there is no login or password activated. You will be able to set it up later.

Physical Ethernet Ports

The Raspberry Pi has only one Ethernet port, which by default for AoIP version handles both admin HTML pages and AoIP streams.

If you like to separate admin and AoIP network traffic, you can install a USB Ethernet port. The Raspberry Pi will detect it automatically after rebooting. In this case, we recommend using the Pi's Ethernet port for AoIP and the USB Ethernet port for administration (HTML).

Default opened port for SOUND4 applications

By default, SOUND4 HTML pages are accessible on port 80 for non-secure access and port 443 for HTTPS access.

Ports can be edited directly through HTML pages or by fixing them in the /etc/default/sound4.aoip.cl file.

Viewing logs

This is a standard systemd service, so you can see the logs with :

journalctl -u sound4.aoip.cl

If you want a real-time updating log, use :

journalctl -u sound4.aoip.cl -f

To save logs to a file, just redirect its output like :

journalctl -u sound4.aoip.cl > aoip.logs

SOUND4 AoIP .CL detailed installation procedure