NATIVE MERIDIAN PLAYBACK

Keep Meridian playing.

Brimstone Core is developing a native Meridian V3 transport to bring classic Sooloos hardware into a modern self-hosted music system.

Brimstone Core connected to Meridian MS200 receiver
THE PLATFORM

A breakthrough for original hardware.

Two days of intensive engineering transformed V3 playback reliability, with a subtle numerical defect isolated after repeated track transitions.

Native Meridian V3

V3 is the chosen forward path. The older V2 engine is being retired.

MS200 testing

Physical receiver playback is demonstrated; mixed-rate endurance and reboot recovery remain release gates.

No false equivalence

The project does not claim a fault in Roon or any other proprietary engine without reproducible evidence.

NOVEMBER 2026 · ENGINEERING UPDATE

From stuttering to working native playback.

The V3 engine has moved from stutters, stops and dropouts to native MS200 playback. Intensive next/previous testing exposed a small floating-point-related error responsible for random track-change failures; the defect was corrected in our implementation.

Built for the original equipment

Discovery, playback ownership, packet accounting and controlled recovery are part of the Meridian transport engineering programme.

Read the public findings

We have published a developer-friendly account of the Meridian V3 breakthrough and the remaining hardware qualification targets.

Public Meridian V3 engineering report
THE PLATFORM

Original engineering, practical compatibility.

The aim is long-lived hardware, trustworthy playback and recovery after network or device changes.

Brimstone Core MS200 playback and queue
THE FUTURE

One native engine, with clean boundaries.

Transport modules are being separated from catalogue, metadata and discovery systems so improvements are less likely to break each other.

Read the V3 update