What Do AES3, AES67, and BS.1770 Mean on a Spec Sheet?
Why standards names appear on gear
Audio equipment from different manufacturers interoperates because standards bodies define, in exact technical terms, how signals are formatted and exchanged. A spec sheet citing a standard is making a compact promise: this device speaks that defined language. The names below are the ones most often encountered.
AES3
AES3 is the Audio Engineering Society's standard for carrying two channels of digital audio over a single connection — the professional digital audio interface, typically run over balanced cable with XLR connectors. When a mixer or converter lists "AES3" (or "AES/EBU," reflecting its joint heritage with the European Broadcasting Union) it means the device exchanges digital audio in this format, with clocking and channel data as the standard defines. The consumer-side relative, S/PDIF, carries similar data over unbalanced RCA or optical connections. The AES standards catalog is the primary reference for the current documents.
AES67
AES67 addresses a newer problem: sending many channels of audio over ordinary IP networks. Several proprietary audio-over-IP systems developed independently, each with its own transport details; AES67 defines an interoperability mode so that equipment from different ecosystems can exchange streams over the same network. A device listing AES67 compliance is stating that it can participate in such mixed networks. Details and related documents live in the AES standards program.
Other AES numbers
The AES maintains standards well beyond interfaces — covering measurement methods, file interchange, and device testing (AES75, for instance, concerns loudspeaker measurement). The pattern to remember: an "AES-number" on a spec sheet is a checkable claim, and the standard's scope page at the AES tells you exactly what was promised.
ITU-R BS.1770
On broadcast equipment, loudness meters, and delivery specifications you will see a different body cited: ITU-R BS.1770, the International Telecommunication Union recommendation defining how program loudness (LUFS/LKFS) and true-peak level are measured. A meter described as "BS.1770-compliant" measures loudness by that algorithm, which is what makes readings comparable across meters and facilities. Delivery documents phrase their requirements as targets "measured per BS.1770" for the same reason. The measurement itself is unpacked in LUFS vs. dBFS.
Reading a spec line critically
Three habits make standards citations useful rather than decorative:
- Note the exact designation. Standards are revised; a citation may include a revision year, and behavior can differ between revisions.
- Distinguish compliance from compatibility. "Works with" is a manufacturer's claim; "complies with AES67" refers to a published, testable specification.
- Check scope. A standard may cover only part of what a feature involves — AES67 covers stream interoperability, for example, not every aspect of network configuration.
For the sample-rate and bit-depth figures that travel across these interfaces, see what 44.1 kHz and 16-bit mean.