CBC and EBU push an open-source media exchange layer
CBC/Radio-Canada (e250 project) and EBU are collaborating to redefine live media exchange for a software-driven future, moving from SDI and dedicated hardware to IP infrastructures and containerized software. They are proposing a Dynamic Media Facility (DMF) reference architecture and developing an open-source Media Exchange Layer (MXL) SDK to enable multi-vendor interoperability and reduce latency in software-based production workflows. An industry "Tiger Team" including Grass Valley, NVIDIA, Intel, Riedel, Matrox Video, and other vendors has formed to work on a common definition and implementation of the MXL SDK.
Key Takeaways
- CBC/Radio-Canada says its e250 project is moving from SDI and dedicated hardware to IP infrastructure and containerized software at 250 Front Street in Toronto.
- The EBU Dynamic Media Facility reference architecture uses a layered model: infrastructure, host platform, container platform, applications/UI, media functions, media exchange, plus vertical layers for provisioning, control/monitoring, and security.
- The Media Exchange Layer SDK is intended as a shared library with four core functions: Create Flow, Read Flow, Update Flow, and Delete Flow.
- Phase 1 of the SDK calls for a minimum viable prototype in June 2025 with limited functionality, single-host operation, and one format support.
- A vendor Tiger Team includes Grass Valley, NVIDIA, Intel, Riedel, and Matrox Video, with AWS and Google also named among the entities involved in the discussion.
Why It Matters
CBC and the EBU are trying to standardize the hardest part of software-based live production: moving media between vendors without falling back to NDI, SRT, or clock-locked streaming paths. The immediate impact is a clearer target for broadcasters building IP and container-based facilities, especially where latency has been a blocker. The broader signal is that end users and vendors are aligning around an SDK, not a slow ratified standard, to speed interoperability. Watch for the June 2025 minimum viable prototype and whether the Tiger Team can keep vendors aligned on a single open-source reference version.
Read full article at tech.ebu.ch