MLVC: Multi-platform Learned Video Codec for Real-World Deployment
Tanel Pärnamaa, Martin Lumiste, Ardi Loot, Evgenii Indenbom, Andrei Znobishchev, Ando Saabas
ECCV 2026
eess.IV, cs.AI, cs.CV, cs.LG
2026-06-26
MLVC encodes scale parameters into the bitstream so decoding stops breaking across devices, hitting ~100 FPS on commodity NPUs and beating hardware HEVC by 70%+ in subjective quality.
Neural video codecs swap HEVC-style hand-tuned modules for neural networks and now beat classical codecs on compression. But they have never been deployable, for two reasons: heavy compute, and a more fundamental cross-platform problem.
Applications like video conferencing run the encoder and decoder on different devices, often chips from different vendors. The paper's opening failure says it plainly: encode a clip on an Apple M3 NPU, decode it on an Intel NPU, and the strongest existing neural codec, DCVC-RT, produces completely corrupted frames.
The root cause sits in entropy coding. The codec needs a scale parameter describing the latent distribution to run entropy decoding. Each side computes it on its own floating-point hardware, and the tiny differences accumulate over the prediction chain until decoding blows up. The obvious fix, quantizing to INT8, does not work either. Apple's Neural Engine simulates INT8 in FP16, and every vendor's compiler makes different choices, so bit-exact parity is off the table.
MLVC's central move is to stop computing the scale and send it instead. The scale parameters are compressed 128x through structured parameter sharing, packed into the hyperprior, and transmitted in the bitstream. Both sides read the scale from the same stream, so entropy decoding agrees without bit-exact arithmetic. The cost is a higher bitrate.
Four changes claw the efficiency back:
Benchmarked on the VCD video conferencing set against hardware HEVC-QSV, the strongest deployable classical baseline:
| Setting | Metric | Result |
| DCVC-RT same-platform | PSNR BD-rate | -69.6% |
| DCVC-RT cross-platform | PSNR BD-rate | inf (decoding fails) |
| MLVC cross-platform | PSNR BD-rate | -58.7% |
| MLVC subjective (MOS, 360p) | BD-rate | -75.5% |
| MLVC bitrate-ladder combined | MOS BD-rate | -71.8% |
| DCVC-RT subjective (same-platform) | MOS BD-rate | -81.9% |
DCVC-RT is genuinely stronger same-platform, but it collapses cross-platform and is therefore undeployable. MLVC sits about 18 percentage points behind DCVC-RT same-platform, the direct price of the cross-platform constraints. Among neural codecs that actually decode across platforms, MLVC leads by a wide margin: -45.2% versus +15.0% for the prior fixed-prior approach on HEVC B.
On speed, both encode and decode average over 100 FPS across the three NPUs: Apple M3 Pro does 129.5 encode / 122.9 decode at 360p, Intel Lunar Lake 98/98, Qualcomm Snapdragon X 80/77.5. In the cross-platform matrix, most encoder-decoder pairings land within 2 BD-rate points. The larger MLVC-S model reaches 1080p at 30 FPS while keeping -37% BD-rate.
This is the first neural video codec that is cross-platform robust, real-time on commodity NPUs, and competitive on compression at the same time. For end-to-end, cross-vendor workloads like video conferencing, neural codecs have until now been theoretical. Microsoft open-sourced it (github.com/microsoft/mlvc) and tuned it explicitly for commodity NPUs rather than high-end GPUs, which signals a deployment-first intent. The PSNR gap versus DCVC-RT same-platform is real, but it buys a codec that actually runs, and that trade is the right one for shipping product.
The authors name their own: power consumption becomes the next frontier once real-time is solved; simultaneous encode and decode at high resolution (1080p and above) on a single device is still hard for symmetric architectures; the unified I/P-frame model trades BD-rate for deployment simplicity; and the regular I-frames that cross-platform operation requires are overhead that single-platform setups would not need. One more caveat: the subjective-quality comparison is anchored almost entirely on HEVC-QSV. Stronger classical codecs like VTM and ECM were omitted because they lack commodity hardware implementations, so the "strongest deployable baseline" framing should be read with that scope in mind.