DEVELOPMENT UPDATE · 13 NOVEMBER 2026

RC26 testing. The next step for Brimstone.

A cumulative Core build, continued native Meridian V3 work and clearer Control connections. Here is what you can download and where each app stands.

CORE · RC26 C08

The cumulative Core testing build is online.

Choose the fresh-install ISO for a spare Intel/AMD machine or disposable VM, or the separately signed application update for a compatible installed Core. Checksums, the exact build record and installation notes are available beside the downloads.

Playback and your library

The cumulative source includes Meridian V3 handoff and output planning, queue and podcast fixes, clearer source-quality reporting, streaming and AirPlay fixes, LAN discovery, trusted local access, metadata references and missing-artwork recovery.

Installation checks

Normal installation and cold boots passed on an isolated VM. The same user session and profile survived the tested boot-slot transitions. The VM remained headless; these results do not establish physical display, mouse or automatic-login acceptance.

Engineering test candidate. C08 is still being qualified. Fresh installation erases the selected system disk. Use spare hardware or a disposable VM, and read the installation notes. Existing Core updates must pass the trusted updater’s compatibility checks; host-specific maintenance patches are not automatically covered.
ORIGINAL MERIDIAN EQUIPMENT

Native V3 playback, tested on an MS200.

Listening tests on original MS200 hardware have given encouraging results following corrections for stuttering, dropouts and a fault when moving to the next track. Work with Sooloos equipment continues alongside receiver recovery and longer playback runs.

The native MS200 network route is stereo. Multichannel playback uses a separate Core-host HDMI path and compatible equipment. Compatibility is assessed per device; Brimstone is an independent project, not a Meridian or Roon certification.

Meridian engineering background
CONTROL · BETA DISTRIBUTION

Choose the right build for your device.

These are the latest recorded distribution checks from 12 November. Apple processing, review and tester eligibility can change what your account is offered. Core’s RC26 download does not itself update the Control apps.

iPhone and iPad

2.5.0 (81) · TestFlight testing. The existing external group reached Testing. Use the build offered to your eligible TestFlight account; CarPlay remains available in the compatible app.

Open the existing TestFlight programme

Apple TV

2.5.0 (36) · TestFlight testing. Both existing groups reached Testing. Automated and remote-interface checks passed; physical Apple TV HDMI, remote and listening acceptance still needs separate testing.

Open the existing TestFlight programme

Mac

2.5.1 (77) · Uploaded to Apple. This update improves recovery from rejected saved credentials and adds Recheck Core connection after certificate changes. Upload succeeded; processing and tester availability have not yet been verified.

Build 76 was verified in internal TestFlight. Its last external-group check was waiting for review. Install only the build TestFlight offers to your account.

In build 77, open Settings → Connect to Core → Recheck Core connection, review the Core address and any certificate confirmation, then use Open Core for a configured local single-user Core. Control does not supply a default administrator password.

Android

2.6.0-rc.4 (2533) · Internal-test draft. The signed build is validated, but rollout is awaiting tester setup. It is not yet an available public release.

The earlier Android APK on Downloads is a separate beta and does not contain all RC26 work.

Windows

2.0.4 (2014) · Unsigned testing build. RC26 source and testing packages are prepared. This is not a new public customer installer.

The published Windows download remains 2.0.3 (2013), clearly identified on the Downloads page.

NEXT CHECKS

Real machines, real listening.

Physical HP EliteDesk display, mouse and automatic login checks, wider audio hardware coverage and longer playback runs remain part of acceptance. Please include your Core and Control versions, output model, source format and the steps that reproduce a problem when reporting a test result.