AV Over IP Finally Has a Checkmark: What IPMX Certification Means for Your Next Room

The worst hour of any audiovisual installation is the one spent standing in a finished boardroom with two devices that refuse to acknowledge each other. The encoder is racked and powered. The fiber is terminated, tested, and labeled. Yet nothing arrives on screen, because the transmitter and the receiver came from different manufacturers who each read the same specification with a slightly different interpretation. Anyone who has built rooms for a living has lived that hour. It is the reason our trade has spent most of a decade asking for a way to verify that two boxes will cooperate before the truck ever leaves the warehouse.

This autumn, that request got a concrete answer. On September 1, the Alliance for IP Media Solutions announced that fourteen more products from eight manufacturers had passed formal IPMX certification testing, bringing the running total to sixty two certified products. The testing happened at European Broadcasting Union headquarters in Geneva during the last week of August. It was the second such event of the year. The inaugural round, held at the same Geneva facility in January and announced at ISE 2026 in Barcelona that February, had certified forty eight products from ten manufacturers. This second round matters more than the modest product count suggests, because it means the question "is this really interoperable" now has an answer you can look up instead of argue about.

What IPMX actually is

IPMX stands for Internet Protocol Media Experience. It is not a product and not a brand of switch. It is a suite of open standards and specifications for carrying professional audio and video over ordinary IP networks, assembled from pieces that already had years of service behind them. The foundation is SMPTE ST 2110, the standard suite that SMPTE describes as specifying how separate elementary essence streams are carried, synchronized, and described over IP for real time production, playout, and other professional media work. Audio leans on AES67, the AES standard for high performance streaming audio over IP interoperability, which targets latencies under ten milliseconds. Discovery and control come from the Advanced Media Workflow Association's NMOS family, principally IS 04 for discovery and registration and IS 05 for device connection management.

The glue holding those pieces together in a consistent, testable shape is the TR 10 document series published by the Video Services Forum. That series is where IPMX gets specific. TR 10 1 fixes system timing and definitions. TR 10 8, finalized this year, sets the NMOS requirements. TR 10 15 Part 1 defines how JPEG XS compressed video is carried, and TR 10 11 handles constant bit rate compressed video. Each part is public, which is what open means here.

What separates ST 2110 from the older practice of pushing HDMI around a building is that video, audio, and ancillary data travel as independent streams. SMPTE notes that the design makes it possible to route and break away ancillary data separately from the audio and video, with every stream individually timed and synchronized by PTP clocks no matter which path its packets took through the network. For a commercial installation that means the podium microphone can reach the recorder without dragging a video signal along with it, and a single camera feed can land in four rooms at once without a matrix switch in the middle.

The pieces broadcast standards left out

Broadcast engineers settled the transport question years ago. Pro AV could not simply borrow their work, because our sources are different. A corporate room has laptops, media players, and video conferencing appliances feeding it, and a great many of those sources are protected with HDCP. A broadcast facility has no reason to carry HDCP protected signals, and ST 2110 contains no part that addresses it.

IPMX does. The Video Services Forum finalized TR 10 5, the HDCP Key Exchange Protocol, this year, which gives the ecosystem a published method for moving protected content across an IP fabric. Alongside it sit TR 10 13, a finalized Privacy Encryption Protocol, and TR 10 14, a draft covering USB extension so a room's camera and touch display can reach a computer across the same network. Those are deeply practical additions, and they are the clearest signal that IPMX was designed by people who install conference rooms rather than people who broadcast football.

Compression deserves a mention as well. JPEG XS, standardized as ISO/IEC 21122, was built for exactly this job. The JPEG committee describes it as a technology with end to end delay equal to a fraction of a frame and typical compression ratios reaching about ten to one. That combination is why a 4K signal can cross a modest switch without the visible lag that makes a presenter's cursor feel broken.

What the certification mark covers

Here is the part worth reading closely if you ever sign a purchase order. Certification is not a participation ribbon. According to the published IPMX Product Qualification and Certification Requirements, a product must satisfy every Baseline Requirement, covering system timing, NMOS behavior, device behavior, and stream compatibility, and it must implement at least one Profile, such as uncompressed video, PCM digital audio, or JPEG XS. Extra features including HDCP, HDR metadata, the Privacy Encryption Protocol, and USB extension are declared capabilities layered on top, so two certified products do not automatically share every feature.

The document is equally direct about what manufacturers may claim. Products that implement IPMX technology without passing formal testing may not use the IPMX name or logo in marketing or product descriptions. That single sentence does more for buyers than any amount of trade show enthusiasm.

Testing is handled by the European Broadcasting Union against those published requirements, and the results are posted publicly in a registry at registry.ipmx.io, where each entry lists the manufacturer, the product, its functional category, its certification number, the profiles it supports, and whether it carries HDCP and privacy encryption. Sam Recine, who chairs the IPMX Pro AV Working Group at AIMS, put the reasoning plainly in the September announcement: "Interoperability claims are easy to make and hard to verify. This program gives the industry an independent answer."

How to put this in a bid

The practical move is small and powerful. Stop writing "AV over IP" into specifications and start writing "IPMX Certified," then name the profile and the capabilities the room genuinely needs. A boardroom with HDCP protected laptops and a soft codec needs the HDCP capability. A video wall running synchronized content needs the uncompressed or JPEG XS profile and a network engineered for PTP and multicast. A digital signage network pushing playlists to retail screens may need neither content protection nor uncompressed transport, which keeps the budget sensible.

Then verify. Ask the integrator for the certification number of every transmitter, receiver, and gateway in the proposal, and look each one up yourself. Checking the registry costs nothing but a few minutes. That habit alone separates a system you can extend in 2030 from a collection of boxes that only work with their own siblings.

We should be honest about the limits. Sixty two certified products is a real ecosystem but not a complete one, and certification tells you two devices conform to the same published rules, not that your network is ready to carry them. Precision timing, multicast routing, bandwidth headroom, and switch selection are still design work, and a certified endpoint on an unprepared network will disappoint you. If you want to understand that layer, AIMS launched a free online IPMX training series in June of this year, organized into Foundations, Systems, and Networks levels and available at training.ipmx.io.

Why we are enthusiastic about this

Open standards are slow and unglamorous. They also outlive vendors. We have walked into buildings where a perfectly healthy ten year old video distribution system had to be ripped out wholesale because the manufacturer discontinued the one receiver model that spoke its private dialect. Independent testing with public results is the mechanism that prevents that story from repeating, and after two certification events in a single year, it is finally real rather than promised.

If you are planning conference rooms or a signage rollout and you want the specification written so the system is still serviceable a decade from now, we would be glad to help. Reach us through our contact page or call (781) 506-6008.

Sources

AIMS: Certification of 14 additional IPMX products
AIMS: Certification of the first 48 IPMX products
IPMX: Product qualification and certification requirements
IPMX: Certified product registry
IPMX: What IPMX is built on
Video Services Forum: The TR 10 document series
SMPTE: The ST 2110 standards suite
AES: AES67 streaming audio over IP interoperability
AMWA: NMOS specifications
JPEG: JPEG XS overview
AVIXA: IPMX certification week wrap up
AIMS: Official IPMX training series