THE #1 AV NEWS PUBLICATION. PERIOD.

Matrox Video Integrates Matrox ORIGIN with NVIDIA Holoscan for Media

Matrox Origin Integration with NVIDIAMatrox Video has announced an integration between Matrox ORIGIN and NVIDIA Holoscan for Media that allows Matrox ORIGIN media services to be provisioned, configured and deployed within NVIDIA Holoscan for Media using Kubernetes.

The integration will be demonstrated at IBC 2026 as part of the European Broadcasting Union’s Dynamic Media Facility (DMF) showcase.

According to Matrox Video, a Kubernetes-native operator developed by the company extends the Kubernetes control plane to manage Matrox ORIGIN resources. The operator automatically deploys the required pods when new resources are added and supports the provisioning, configuration and placement of media functions with resource limits and isolation.

The integration combines the Kubernetes-native deployment capabilities of NVIDIA Holoscan for Media with Matrox ORIGIN. Matrox said the ORIGIN SDK provides a framework for building media functions, allowing developers to focus on their core competencies while developing software-defined live media applications.

“Developers shouldn’t have to solve the underlying complexities of live media processing every time they build a new application,” said Daniel Robinson, product manager at Matrox Video. 

“Matrox ORIGIN provides the media foundation so they can focus on what differentiates their applications. Bringing those capabilities into NVIDIA Holoscan for Media extends that developer experience into a Kubernetes-based environment for software-defined production.”

NVIDIA Holoscan for Media is an open reference architecture and developer toolkit for developing AI-powered media applications for software-defined live production on NVIDIA-accelerated infrastructure.

The integration being demonstrated at IBC includes Matrox ORIGIN media processing services such as color correction, media playback, audio shuffling and Ograf graphics.

These services connect to the wider DMF deployment through the Media eXchange Layer (MXL). The integration also supports NMOS BCP-007-03, allowing MXL I/O services to register using IS-04 and receivers to be switched using IS-05.

Top