The next platform shift has a sunk-cost problem
Weekly insights on the technology, production and business decisions shaping media and broadcast. Free to access. Independent coverage. Unsubscribe anytime.
Broadcast technology vendors rarely describe a new platform as a replacement.
It is usually an extension, an evolution or another layer in the stack. The old system remains relevant. The new one simply handles the part of the workflow the previous architecture was not designed to address.
That is largely how MXL is being positioned alongside SMPTE ST 2110.
ST 2110 would continue moving media among physical systems and production environments. MXL would allow software applications running on shared compute infrastructure to exchange media more efficiently. One handles transport across the facility. The other handles communication among processing applications.
Technically, the distinction is reasonable.
Economically, it may not matter as much as vendors hope.
Broadcasters have spent years planning, buying and deploying ST 2110 infrastructure. Many have also absorbed the organizational cost of retraining engineers, redesigning facilities and changing how signal flow is monitored and controlled.
The industry may understand why another layer is needed. That does not mean it is eager to fund one.
“Most broadcasters believe MXL will be part of their future development, but it will take a few more years before it solves the many tricky edge case challenges of broadcast,” said James Eddershaw, managing director at Shotoku.
Eddershaw then stated the less technical reason adoption may be slow. Many broadcasters have moved to ST 2110 “at great expense,” making a rapid shift to something else unlikely.
That is the part of the MXL conversation that cannot be solved through another interoperability demonstration. The next platform shift is arriving before many organizations feel finished paying for the last one.
A migration is more than a purchase
The cost of moving to ST 2110 was never limited to switches, gateways and network interfaces.
Facilities had to rethink timing, routing, monitoring, redundancy and control. Engineers had to develop networking expertise. Vendors had to make products interoperate across standards that were still maturing in real deployments.
Even where the transition went well, it required substantial institutional attention.
That creates a different market for the next architectural proposal.
Broadcasters considering MXL are not evaluating a new technology against an untouched facility. They are evaluating it against recent investments that may still be depreciating and workflows that are only now becoming familiar.
In that environment, technical superiority is not enough.
A new platform must solve a problem that is expensive enough, immediate enough and visible enough to justify reopening architecture decisions that an organization thought it had already made.
That is a higher threshold than proving that the technology works.
It also helps explain why most vendors are careful to describe MXL as complementary to ST 2110 rather than a successor.
“ST 2110 will continue to move media between physical systems, while MXL will enable efficient media exchange between software applications running on shared compute infrastructure,” said John Mailhot, senior vice president of product management at Imagine Communications.
The layered model protects prior investment. It allows MXL to enter as an additional capability rather than as an admission that the previous migration was incomplete.
But adding a layer is still an investment.
It creates another standard to evaluate, another point of interoperability to test and another operational dependency to support. The architecture may become more efficient at the compute level while becoming more complicated at the organizational level.
The fatigue is institutional
Broadcast facilities are often described as conservative buyers, but caution is not necessarily resistance to innovation.
The industry operates live services where downtime is highly visible and failures are difficult to recover from. Replacing a working system carries risk even when the replacement promises greater flexibility.
That makes platform fatigue rational.
The ST 2110 transition asked broadcasters to move away from familiar, deterministic signal paths and into networked environments. The shift toward software-defined production now asks them to move again, this time from specialized processing hardware toward applications running on shared compute.
For vendors, these changes form a logical progression. For a broadcaster, they can look like a sequence of unfinished capital projects.
Each transition arrives with a similar promise: more flexibility, better resource utilization, less dependence on dedicated hardware and a facility that can adapt without another major rebuild.
The irony is difficult to ignore. The justification for adopting the new platform is often that it will prevent the next disruptive migration.
That pitch becomes less persuasive each time it is repeated.
The real shift may not be MXL
Olivier Suard, vice president of marketing at Nevion, framed the issue more broadly.
“The real underlying discussion to be had is to what extent software on COTS, on-prem or in the cloud, will replace dedicated hardware,” Suard said.
From that perspective, MXL and ST 2110 are not competing endpoints. They are proxies for a larger question about what a broadcast facility will be made of.
If production functions move from dedicated appliances into containerized applications running on commercial off-the-shelf servers, the economic structure of the facility changes. Processing capacity can be shared, applications can be deployed as needed and upgrades become less tied to hardware replacement cycles.
That is the sales pitch.
The skeptical version is that dedicated hardware continues to exist because it solves specific operational problems well, provides predictable performance and is already installed.
“This is anyone’s guess at this stage,” Suard said. “But as we have seen with SDI and IP, it’s likely that more traditional hardware equipment and newer COTS software solutions will coexist for many years to come.”
That may be the most realistic forecast in the MXL discussion.
Broadcast technology rarely moves from one clean architecture to another. New systems accumulate around old ones. Gateways preserve existing equipment. Software handles some functions while appliances retain others. Facilities modernize in sections because budgets, staffing and operational risk do not permit total reinvention.
The result is not a sudden transition to the dynamic media facility. It is a long period in which several generations of infrastructure must work together.
The burden of proof has changed
MXL has legitimate technical support.
Drew Martin, head of video product management at Riedel Communications, described strong interest from customers seeking to make better use of shared compute infrastructure. Michael Demb, vice president of product strategy at TAG Video Systems, argued that MXL addresses the limitations of applying ST 2110 inside software-native and cloud workflows.
Those arguments may prove correct.
But the adoption question is not simply whether operators want faster, lower-latency media exchange among applications. It is whether organizations will prioritize that capability over all the other demands competing for capital and engineering time.
The strongest early use cases are therefore likely to be additive rather than transformative.
MXL may first appear inside products, processing clusters and new software-defined facilities, largely invisible to operators. It may support new deployments without requiring broadcasters to redesign every existing ST 2110 environment.
That approach fits both the technology and the economics.
The next platform shift is more likely to succeed when it does not look like another platform shift.
For vendors, that means the argument cannot stop at performance or interoperability. They will have to show how the new architecture protects existing investment, reduces operating costs and avoids forcing teams through another extended period of retraining and integration.
Broadcasters are not necessarily skeptical of MXL.
They are skeptical of being told, once again, that the next architecture will finally make rebuilding unnecessary.




tags
Drew Martin, Imagine Communications, James Eddershaw, John Mailhot, Media Exchange Layer, Michael Demb, Nevion, Olivier Suard, Riedel, Riedel Communications, Shotoku, Shotoku Broadcast Systems
categories
AV Integration & Broadcast Systems Integration, Broadcast Engineering, Featured, IP Based Production