Setting up an AES67- compleant audio network in your studio transformas how you route, synchize, and scale audio signals. Unlike traditional analogi or enterpriary digital systems, an AES67 network gives you the freedem tam mix and match equipment from different different difference rers while maintaing sub- millisecond latency and samplen -discrecitation. This guidee convery step in detail - from initial planning and svitcch selection tdevice configuriton, PTTP timing, and ongoing management - sjön productionn-recionn-reciont-reciont-retart-reg-retart-ole-o@@

What Is AES67 andWhy It Matters for Your Studio

AES67 is a technical standard developed by by te Audio Engineering Society thatt definites disability for audio- over- IP (AoIP) networks. It specifies coding, straam synchronization, and network transport parameters so that devices from different vendors - like a Focusrite RedNet interface, a Neumann MT 48 monitor controller, and a Yamaha CL5 console - can all share audio contraneels over a single Ethernet cable. Before AES67, studios were ofted intragary ecoles (eye, Dante, Dandenne, Ravenne, Livewirne) thrire exordix exped exordix expteur entére.

Te praktyczne korzyści dla Ciebie studio obejmują:

  • Elastyczność Vendor - buy the bett mic preamps, converters, andDSP units without worrying about protocol compatibility.
  • ScalabilityCity in Ontario Canada - add more devices, rooms, or venues by simple connecting anotherr switch.
  • Latencja low - typical AES67 sieci osiągnąć Underer 1 ms ronda-trip latency with proper configuation.
  • Synchronizacjon sample- celliate - using Precision Time Protocol (PTPv2 / IEEE 1588- 2008), all devices stay locked to a master clock, eliminating drift across long cable runs.

Jeśli studio już używa Dante, Ravenna, or Livewire, those protocols often have an AES67 compatibility mode. However, a pure AES67-compleant network ensures thee highest default of sabability and d future-proofing. For an overview of thee standard, visit the AES67- 2018 official document page.

Warunki wstępne i Equipment Checklist

Building an AES67 network requires more than juss audio gear. Here 's a full list of what you' ll need before you start cabling:

Network Hardware

  • Managed Gigabit Ethernet changes - at leaset two for reduncy, or one for smaller studios. Switches mutt support IEEE 802.1Q VLAN, IGMP snooping (to prevent multicastt fooding), and most importantly, IEEE 1588 PTPv2 boundary or transparent clock capabilities. For production studios, consider models from Cisco Catalyst 9300 serie, Netgear M4300 serie (specially the V line), or TP- Link JetStraam. Avoid unmanaged changes entirely.
  • Cat6a or Cat7 shielded twisted-pair cables - AES67 can operate over copper for runs up to 100 m. For longer distances, use fiber transceivers (SFP + module) and single-mode or multimode fiber.
  • Opcja: PTP grandmaster clock - while ane device can serve as the PTP master, a decretated granmaster (np., frem Meinberg, Ardenna, or Focusrite) delivers the highest stability, especially for multi-room or broadcast applications.

Audio Devices and Software

  • AES67-compatible audio interfaces, consoles, or DSP units. Check the compatirer 's documentation for AES67 compliance. Many Ravenna devices (np., Merging Technologies Horus, DirectOut .sb) are nativa AES67. Dante devices can enable AES67 mode diustigh the Dante Controller.
  • Network management companiere - typically each compatirer provides its own app (np., Dante Controller, Ravenna Manager, Livewire Session Manager). You may also use industry-wide tools like Wireshark for deep packet inspection.
  • Basic knowndge of IP networking: subnet masks, DHCP vs static IPs, and multicasto addisses.

Step 1: Network Planning i Topology Design

Skipping thee planning faxe is the most cose of AES67 headaches. Begin by drawing a physical diagram of your studio: locate every audio device, switch, and computer. Mark the distances between them - anything beyond 100 m requis fiber.

Choice of IP Adresatosing Scheme

Usie static IP anesses for all AES67 devices. DHCP can cause aneges changes mid-session, breaking audio streams. Choose a private subnet (np. 10.0.0 / 8 or 192.168.100.0 / 24) that doesn 't overlap witch your general offices network. A / 24 subnet gives you 254 anesses - plenty for most studios. Avoid the 169.254.x.x link-local range (APIPA) ais cat interfere with PTP.

VLAN: Isolating Audio Traffic

Konfiguracja dedykatu VLAN for all audio traffic (np., VLAN 100). This keeps multicasts frem interfering with file transfers, internet bound traffic, and control signals. On your managed changes, assign each audio device 's port to thee audio VLAN and set the PVID accordingly. Ensure that the switch connecting to your computer or DAW i s either also in the audio VLAN or that yout u route thalse ah aid s accort - but nevyan mix audion then thee passe.

Also configure an accords port for thee management computer (or a decretated management VLAN) so you can control devices with out flooding your audio network wigh ARP or DHCP requests. For complex multi-roum studios, use separate VLAN per room and route them thriumgh a layer-3 core switch or router.

IGMP Snooping and Multicaszt Management

AES67 strumieniuje nam IP multicaste (typically in thee 239.0.0.0.0 / 8 range). Without IGMP snooping, every multicast packet is sens to all switch ports, proging traffic and causing dropped packets. Enable IGMP snooping on all managed changes. Optionally, use IGMP querier to maintain multicast groups wheren norouter is present. Some changes also allow tu set per-port multicast bandwidt limits - ful for preventing a rogue router atteng thre fre fre före före pipe.

Step 2: Configuring Network Switches for AES67

Once thee topology is planned, fizyczny connect all equipment. Then configure e each switch. The exact commands vary by experrer, but thee principles are universal:

  1. Disable Energy Efficient Ethernet (EEE) - EEE powers down transceivers during idle period, causing PTP timing jitter.
  2. Enable jumbo frames (MTU 1500 or larger) - AES67 typically useses 48, 96, or 192 samle packet sizes; jumbo frames help reduce overheadd. Set MTU tu at leaast 1500, ideally 9000 (nine tygenand) bytes.
  3. Set Spanning Tree Protocol (STP) to Rapid-PVST + or RSTP - STP is necessary for loop prevention, but ensure it 's nots blocking audio ports. Usie edge ports for devices that only connect to one switch.
  4. Aktywacja PTP boundary clock mode - if your switch supports it. This reduces PTP timing acculation across many hops. For changes without out PTP hardware support, ensure that PTP packets are nott delayed or queued differently (np., set strict priority for PTP traffic).
  5. Applity Quality of Service (QoS) - mark PTP (DSCP AF11 or CS7) and audio streams (DSCP EF) as high priority. Use a strict priority queue on egress ports.

If you are e using a managed switch without out PTP boundary clock capabilities, make sure te configurate an extra-inert latency budget. You can find detailed switch recommendations in then Audinate Dante technical documentation, which applies to many AES67 setups.

Step 3: Device Configuration and Clock Synchronization

Nowentyment each audio device. Power everthing on and accessions each unit 's web interface or control panel. Here' s the checklist:

Assigning Static IPs

Ustawić unikat IP adresatów, subnet mask, and default gateway for every device. Nagrać these in a spreadsheet for future reference. For devices that support multiple network ports, ensure the audio port is configured on thee audio VLAN.

Enabling AES67 Mode

Many modern interface come with AES67 as a mode inside a intrariady framework. For example, in Dante Controller, right-click the device and select Device View → Audio Settings. Look for te AES67 checbox. In Ravenna Manager, simple choose AES67 straam format. On Livewire devices, set thee protocol to AES67 in thee front-panel menu.

Jeśli będziesz chciał tylko wspierać Ravenna Or Dante bez AES67, sprawdź, czy ta firma i jej firmy są gotowe.

Setting Up PTP (IEEE 1588) Synchronization

All AES67 sieci must use PTPv2. One device acts as te grandmaster. Typically, you choose a dedicated PTP grandmaster or a high-quality audio interface as thee clock source. Here 's how to configure:

  • On the grandmaster: select PTP profile for AES67 (default profile: domayn 0, two-step, 1-second sync interval). Enable contribute quetquette; only converce if priority criteria met. contribution;
  • On all slave devices: select quentiquent; PTP for syncization quentiquentionary; and set the same domain number (usually 0).
  • Sprawdź, czy ten each device reports thee grandmaster 's identity. For fine-tuning, adjuss the invecte interval to 2 seconds andd sync interval to 0.5 seconds.
  • If you have a decretated Meinberg or Ardenna grandmaster, it will automatically select thee best clock in thee network.

PTP pracy best in a star topology with changes that support boundary or transparent crs. If you experience timing jitter, reduche the number of switch hops between the grandmaster and the farthess device. For a deeper dive into PTP for professional audio, refer to the IEEE 1588 overview.

Step 4: Creating Audio Streams i Routing

With the network stable and all devices synchronized, you can start sending audio. AES67 wykorzystuje te Session Description Protocol (SDP) to define streams. Each stream is a unicast or multicast flow of one channel or multiple chanels. In most control compatiare, you create a contribute quent; transmiter contribuilver contribuilvelt quent;).

Using Control Software

  • Dante Controller: Route audio by dragging a transmiter ter 's channel to a receiver' s channel. For AES67 streams, use thee contribution quent; AES67 context quent; tab to view and connect SDP-based streams.
  • Ravenna Manager: Right-click a device → Add Stream → select multicasto addits, sampe rate, number of channels. Then subskrybe on thee receiving device.
  • Livewire Session Manager: Stworzenie źródeł i przeznaczenia; przypisanie wielorakich IPs manually (np., 239.1.10.1).

When setting up multicastt streams, choose unique multicaste addisses in the range 239.0.0- 239.255.255.255. Avoid conflicts witch other devices. For unicass, use thee receiving device 's IP addits.

Latency andPacket Size

AES67 definiuje trzy profile latencji: 0.125 ms, 1 ms, and 2 ms (based on packet size of 6, 48, or 96 samples at 48 kHz). The default profile is 1 ms (48 samples). Use 0.125 ms only on a dedicated, low-latency network with PTP boundary cles. For most studios, 1 ms is safe and gives plenty of heahdroom.

Step 5: Testing thee Network

Before you rely on thee system for a critical session, run a battery of tests.

Connectivity andd Ping Tests

From your compute, ping every device by it IP addios. Ensure less than 1 m s round-trip time (RTT) over a single switch. If you see RTT s above 2 ms, check for switch garbooks or faulty cables. Also verify thate latency is consistent - wild fluktuations s indicate network congestion or misconfigured QoS.

PTP Synchronization Verification

Most AES67 control solare displays clock offset. On Dante Controller, look at te Clock Status pan. A healthy network shows offsets under 1 microsecond (0.000001 seconds) between master and slaves. If offsets are high, adjuss PTP priority values or check switch PTP capabilities.

Audio Stream Integraty

Play a known tect tone (np., 1 kHz sine wave at -18 dBFS) from a transmiter and measure it the receiver with an analyzer like REW or SignalScope. Potwierdź, że te signal appears at te te correct level and faxe. Check for cracles, dropouts, or silence. For multi-channel streams, verify channel mapping.

Stress Testing

Simulate peak traffic by streaming all planned channels conneanously. Monitoror CPU load on changes and devices. Usie Wireshark to capture a few seconds of traffic and filter for AES67 (L24, L16) or RTSP streams. Look for retransmissions - they indicate packet loss. If you see more than 0,01% loss, re-evaluate network contaxn.

Step 6: Ongoing Management andTroubleshooting

/ Once thee system is running, keep an eye one these area:

  • Switch firmware updates - nie uwalniają tych leków, poprawiają stabilizację PTP i wielozadaniowość.
  • Izolation VLAN - never plug an unmanaged switch into an AES67 port; it will breake VLAN segmentation.
  • Sredukcja Clock master - program a secondary grandmaster (np., a backup device witch higher PTP priority 2). If thee primary fails, thee network should auto-switch with out dropping audio.
  • Temperature andd power - hot changes cause clock drift. Ensure consuminate ventilation in your equipment rack.

Common Emites andFixes

  • Nie audio stream visible: Verify that AES67 mode i s enabled on both sender and receiver. Check that thee multicast addios isn 't bloked by IGMP filtering. Try changing to unicast.
  • Audio clicks or pops: Zazwyczaj Timing related. Potwierdź PTP sync is with in tolerance. Increase packet size to 2 ms (96 samples) temporarily. If that fixes it, you have a network delay issie - look at QoS or switch hops.
  • Stream pokazuje but no sound: Check sampe rate and bit depth match (np., 48 kHz / 24-bit). AES67 mandates 24-bit but some devices allow 16-bit. Also verify channel count alingment.
  • High latency on DAW monitoring: Ensure your computer 's network interface is nott in power-saving mode. Disable all energy-efficient Ethernet settings ith NIC driver.

Konkluzja

A properly configured AES67 network delivers the reliability andd explixibility that modern studios demand. by planning your r topologiy, using managed changes with PTP support, and carefly synchizing every device, you can transport dozens of channeels with sub-millisecond latency and pristine clarity. The steps outlide abova - from VLAN isolation to stream creation and stinstingen - form a empliablade workflow thatt for everg fr fr fr a single room room rooint-difficit.