A powerful standard for live audio and video
Audio Video Bridging (AVB) is a suite of IEEE standards that brings deterministic, low-latency, time-synchronized transport to standard Ethernet networks. It was purpose-built for the demands of live audio and video — where timing, reliability, and lossless delivery are non-negotiable. AVB gives manufacturers and integrators a rock-solid foundation for professional A/V systems.
Profiles make interoperability possible
AVB defines the networking layer, but interoperability between devices from different manufacturers requires more. Without agreed-upon application profiles, two AVB-capable devices may speak the same network language but still fail to work together. Profiles define the specific capabilities, formats, and behaviors that devices must support, making seamless plug-and-play interoperability achievable across the ecosystem.
Open standards deserve open profiles
AVB is an open IEEE standard — freely available and not owned by any single vendor. The profiles that build on top of it should reflect the same principle. Open profiles lower the barrier for manufacturers, encourage broader adoption, and ensure that no single party controls the direction of the ecosystem. Keeping profiles open is essential to maintaining the collaborative spirit that makes AVB valuable.
Community-driven, backwards-compatible evolution
Profiles should not be static. Real-world deployment surfaces edge cases, new use cases emerge, and technology evolves. The community — manufacturers, integrators, and end users — is best placed to identify what needs improving. Profile specifications are maintained on GitHub, and the process for evolving them is straightforward: submit an issue to propose a change, discuss it openly, and merge improvements that preserve backwards compatibility so existing deployments are never broken by a new version.
Open source tools for developers
To help developers validate their implementations, open source testing tools are available on GitHub. These tools allow manufacturers and developers to verify interoperability against the published profiles, catch compliance issues early, and build confidence before devices reach the market. By keeping the tooling open source, the community can contribute improvements and ensure the tools evolve alongside the profiles themselves.