# AES70 / OCA mapping note

> Where EDC sits against the open control standard consultants ask for — and the honest answer that OSC and REST are the developer-adoption path while AES70 is the specification-compliance path.
>
> Status: draft-spec. Canonical: https://www.edcacoustics.com/developers/aes70/

> **Status: roadmap note.** AES70 is not implemented today. Nothing here should be read as a compliance claim.

AES70 — the Open Control Architecture — is the AES standard for control, monitoring and connection management of networked audio devices. It is open and licence-free; d&b audiotechnik ships it on amplifiers and the DS100 with plug-ins for Q-SYS, MediaMatrix, Crestron, AMX and Beckhoff, and states that third parties are free to implement it.

## Proposed mapping

| EDC function | AES70 class |
|---|---|
| Input gain / mute | `OcaGain`, `OcaMute` |
| Input EQ bands | `OcaFilterParametric` |
| Input compressor | `OcaDynamics` |
| Beam delay | `OcaDelay` |
| Beam aim / shape (pan, tilt, width, skew) | Manufacturer extension worker, e.g. `EdcBeamShaper`, registered through the OCA Alliance extension-class mechanism |
| Device health, temperature, faults | `OcaDeviceManager`, `OcaSensor` subclasses |
| Transport | OCP.1 over TCP |

## Why not first

Few show-control tools speak OCP.1 natively; QLab users ask for AES70 and get no easy answer. OSC and REST reach developers today. AES70 answers the consultant's "open standard?" question in a tender, and belongs in the third horizon of the roadmap, verified with the OCA Alliance compliance test tool before any claim is made.