ENGINEERING UPDATE · 8 NOVEMBER 2026
Meridian V3.
A playback breakthrough.
Brimstone Core R1's native Meridian transport has taken a substantial step forward after intensive real-hardware testing.
From stutters and dropouts to working playback
Just 48 hours earlier, our experimental Meridian V3 playback engine was struggling with stuttering, premature stops, dropouts and intermittent track-transition failures. Today, native Meridian playback is working, with the major stuttering and dropout problems resolved.
Repeated forward and backward track skipping helped expose a subtle numerical issue behind apparently random failures when advancing to the next track. The floating-point-related defect has now been identified and corrected in our implementation.
It's a useful reminder that tiny numerical errors at audio transport boundaries can have disproportionately large consequences.
What's working
- Native Meridian V3 playback operational
- Major stuttering and dropout issues resolved
- Random next-track failure traced and corrected
- V3 selected as the future Meridian playback engine
What comes next
- Extended endurance and mixed-format playback tests
- Automatic endpoint rediscovery and reboot recovery
- Retirement of the older V2 engine
- Modular transport integration and 4 GB Core qualification
Keeping legacy Meridian hardware playing
Our focus includes original Meridian/Sooloos hardware such as the MS200. We are interested in hearing from other developers and owners investigating playback reliability, packet timing, buffering and track-boundary behaviour on these devices.
We have not established that other audio platforms share this particular numerical defect. The finding relates to Brimstone's own V3 implementation.
Six years in development, and still finding new ways to make old hardware sing.
Discuss this update on our Discord · Meridian integration
Brimstone Core is an independent project and is not affiliated with Meridian Audio or Roon Labs. Hardware endurance and release qualification remain in progress.
