Native Meridian V3
V3 is the chosen forward path. The older V2 engine is being retired.
Brimstone Core is developing a native Meridian V3 transport to bring classic Sooloos hardware into a modern self-hosted music system.

Two days of intensive engineering transformed V3 playback reliability, with a subtle numerical defect isolated after repeated track transitions.
V3 is the chosen forward path. The older V2 engine is being retired.
Physical receiver playback is demonstrated; mixed-rate endurance and reboot recovery remain release gates.
The project does not claim a fault in Roon or any other proprietary engine without reproducible evidence.
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.
Discovery, playback ownership, packet accounting and controlled recovery are part of the Meridian transport engineering programme.
We have published a developer-friendly account of the Meridian V3 breakthrough and the remaining hardware qualification targets.
Public Meridian V3 engineering reportThe aim is long-lived hardware, trustworthy playback and recovery after network or device changes.

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