The short version
You may implement EDC Acoustics network control in your own product — commercial or open source — without a licence, without a fee, and without signing anything. No NDA, no developer programme, no per-unit royalty, no approval step.
That covers changing inputs, levels, mutes, EQ and processing, recalling presets, and reading status and telemetry. It is the whole third-party control surface described in the protocol reference and specified in full in the EDC Speakers Network API.
Scope
Included. Implementing the network control protocol in a control system, plug-in, module, driver, application or service. Distributing that implementation, including commercially. Writing code from our published specification.
Not included. The beam-forming algorithms themselves — the maths that turns a coverage pattern into a filter set — are ours, and this statement does not license them. Our apps compute beams; your software recalls and controls the result. See what your software can change.
What we ask in return
Not conditions of the licence — just what makes an integration good:
- Test against real hardware before you publish.
- State which firmware versions you have tested.
- Fail safely. Never leave a cabinet muted or in standby because your controller went away.
- Tell us what you have built, so we know to warn you before anything changes.
Stability
We give twelve months’ notice before any breaking change to the control interface. Build against it with that in hand.
In practice the interface has been stable since 2019, and we have never issued a firmware update in the product’s life to date. Filter discovered devices by firmware version anyway if you have only tested against one build — and tell us what you have built, so you are on the list to be told first.
Trademark
“EDC Acoustics” and the EDC mark are our trademarks. You may describe your product as compatible with EDC Acoustics loudspeakers, or say that it controls EDC Acoustics loudspeakers. Please do not use our name or mark as the name of your product, in a way that suggests we built or endorsed it, or in a logo, without asking us first.
What we do not publish
We publish no SDKs, sample applications, device simulators or control-platform modules, and we do not implement AES70. This page gives you permission to build on the protocol; it does not describe software we ship.
Documentation
The full specification is published: EDC Speakers Network API (PDF). Nothing is gated — no form, no request, no NDA. Describing the protocol in your own documentation and publishing your own source code is expected and fine.
Data
Our apps collect no data. Control traffic stays on the local network.