Meridian Unplugged - Powered by MrTechGuy.co.uk Forums Discussion Meridian - Streaming Brimstone core update

BRIMSTONE CORE AUDIO – DECEMBER 2026 PREVIEW
Your music. Your memories. Your Meridian.

After months of testing, we're aiming for a December release that brings easier installation, better recovery and much more than an ordinary music library. We're keeping older hi-fi useful, not telling everyone to replace it. Here's what's coming; anything still in development is described as a target, not a finished feature.

A simpler, safer Core

For December we're developing a new Debian installer with a clear choice of normal system, backup system or recovery tools. A protected, largely immutable operating system and an A/B-style recovery design aim to make updates easier to roll back if something goes wrong. Two or more drives are recommended so music and personal data can remain separate from the operating system. These are release targets, not a reason to stop making backups.

Your own music — and concert films

Core brings your owned albums, bootlegs, radio, podcasts, audiobooks and concert media into one organised library. It is designed for high-resolution stereo and multichannel playback, with continuing support for Meridian/Sooloos and compatible audio endpoints. Supported import workflows include audio CDs, DVD-Audio, Blu-ray Audio and suitable DVD/Blu-ray concert recordings, subject to the disc, equipment, format and applicable rights. Concert video playback on iPad and Apple TV is part of the December release plan.

Control wherever you listen

Control runs across macOS, iPhone, iPad and Apple TV, with its own layout for each screen. CarPlay is integrated: music can be streamed from your Core or downloaded to the iPhone to play offline. Your own collection remains the centre of the experience, whether at your desk, in the living room or in the car.

A look at the running beta software
macOS Control · 15 October beta


iPhone Control · October beta


iPad Control · October beta


Gig Guide: keep the memories, not just the tickets

The Gig Guide is a personal, interactive record of concerts you've attended. Add your photographs, scanned tickets, notes, memories, sound and video to each gig; browse and enjoy the digital version on your own computer.

For December we are targeting an optional professionally printed hardback. The proposed standard sizes are UK A4 and US Letter, with a target book price of £15 including Brimstone's 50p contribution; postage is additional. The printer, page allowance and final price still need confirming. Where practical, printed QR codes can point back to your media, whether privately hosted or deliberately shared online. We hope to offer direct ordering from within the system.

More ways to enjoy and preserve music

Eligible material from the Addams, Jacob and other Internet Archive collections will become easier to browse and download through updates over the following months. That includes freely available audiobooks and historical recordings where downloading and reuse are permitted.

We also plan optional ordering of CDs, vinyl records and cassettes at a later date, with a proposed 50p contribution to Brimstone per order. Manufacturing prices, postage, availability and rights requirements will be confirmed before that service launches.

Which computers will run Core?

Debian remains the main dedicated Core platform. Native macOS Core editions for Intel x64 and Apple Silicon M-series computers are the other focus, including compatible older hardware. Standalone Windows Core development is not continuing; we're concentrating testing and support on the platforms we can maintain properly.

What's next?

December 2026 is our Core and Control release target, with the revamped installation and recovery work, concert media and interactive Gig Guide. By March 2027 we aim to provide both remote streaming of your own Core library and integrations with supported third-party streaming services. From May 2027, the Gig Guide is planned to help you find upcoming gigs near you. All dates are targets and depend on testing and partner availability.

A note for beta testers

Please back up your music, Gig Guide memories, settings and downloads before any future beta upgrade. The move to protected operating-system layouts and a multi-drive recovery design may involve storage migration. Do not treat an unfinished beta as a substitute for a verified backup.

More information and current test downloads: https://core-audio.uk/downloads.html
Full preview with screenshots: https://core-audio.uk/december-2026.html

Thanks to everyone testing and reporting problems. Your music belongs to you; your equipment deserves to keep playing.

**BRIMSTONE CORE — R1 DEVELOPMENT UPDATE**
**A New Operating System, Built-In Recovery and Onboard Diagnostics**

A little update on where Brimstone Core is heading as we work towards our planned 1 December 2026 R1 release.

Over the past few months, Brimstone has grown considerably beyond the original idea of a simple replacement for ageing music-server hardware. We've now reached the point where it makes sense to rethink the operating system underneath it, rather than continually adapting a general-purpose Linux distribution.

**Moving from Debian to Buildroot**

Our current development systems are based on Debian Linux, which has served us well. However, Debian is designed to do thousands of different jobs, whereas Brimstone has one principal purpose: playing music reliably and at the best possible quality.

For R1, we're developing a dedicated operating system using Buildroot and the Linux 6.18 LTS kernel.

Buildroot isn't another Debian derivative. It allows us to assemble a Linux system specifically for Brimstone, including only the components we actually need.

The advantages are straightforward:

- Fewer unnecessary background services.
- Less software to maintain and fewer potential security vulnerabilities.
- A cleaner, more predictable operating environment.
- No conventional package-management updates interrupting normal use.
- Better control over hardware drivers and audio services.
- A stable operating-system foundation that doesn't need constantly changing.

We're not chasing the latest kernel or rewriting perfectly good software for the sake of it. If something works reliably, the intention is to keep it working.

The existing Brimstone music engine is being preserved. The new operating system is designed to run it, not replace it.

**Three Operating-System Slots — A, B and C**

One of the most significant changes is our new multi-slot boot and recovery architecture.

Rather than relying on a single operating-system installation, Brimstone will have three separate system environments.

**Slot A — Primary Operating System**

This is the normal working system, running Brimstone Core.

**Slot B — Secondary Operating System**

A separate operating-system image, used for updates and rollback.

When an update is installed, it can be written to the inactive slot while preserving the known-good installation.

If the updated system fails its startup checks, the machine can return to the previous working version.

**Slot C — Dedicated Recovery and Maintenance**

This is a separate recovery environment with its own operating system and tools.

It is designed to remain available even if both normal operating-system installations become unusable.

Slot C provides:

- Operating-system repair and restoration.
- Installation of verified OS updates.
- Boot-slot selection and rollback.
- Storage and filesystem diagnostics.
- Network diagnostics.
- System health reporting.
- Diagnostic log export.
- Recovery from USB media.

The recovery interface is deliberately text-menu based, so it does not depend on a working graphical desktop.

**Why does this matter?**

Because a music server should not become unusable simply because an update failed or a system file became damaged.

The intention is to provide recovery facilities built into the appliance itself, rather than requiring the owner to reinstall Linux from scratch.

**An Operating System That Cannot Easily Be Altered**

Another important change is that the normal operating-system images will be immutable.

In simple terms, the operating-system files are read-only during normal operation.

This helps protect against accidental system modifications, inappropriate software installations and other changes that can destabilise an otherwise working machine.

Music, playlists, metadata, databases and user settings remain separately stored and writable.

The system software is protected without making the customer's music collection read-only.

**Independent Brimstone Core Updates**

We're also separating operating-system updates from Brimstone application updates.

A correction to the music library, streaming services or playback interface should not require replacing the entire operating system.

Core will have its own signed application packages and a separate rollback mechanism.

The intention is for OS updates to be comparatively infrequent, with Core improvements delivered independently.

**Single-Disk and Multiple-Disk Installation**

Not everyone has a machine with several drives.

The new installer is being designed to support both single-disk and multi-disk computers.

Where multiple drives are available, the operating system and music storage can be separated.

The installer will also identify existing disks and provide clear choices before making changes. Existing music collections must not be inadvertently erased during installation.

**Audio Hardware**

Brimstone Core remains an audio-focused system.

Our planned output support includes HDMI multichannel PCM, external USB DACs, USB-to-SPDIF interfaces and compatible network audio endpoints.

This is particularly relevant to Meridian users, including those using the HD621 HDMI audio processor and digital loudspeaker systems.

Video playback and its associated audio remain functions of the iPad and Apple TV Control applications, rather than adding an unnecessary video playback system to Core itself.

**Where Are We Now?**

The new Buildroot appliance is already undergoing development and testing in an isolated virtual machine.

Initial tests have included successful booting, multi-slot recovery, failed-update rollback, USB recovery and operation of an unchanged Brimstone Core runtime in the new environment.

However, there is still work to complete, particularly with physical hardware, audio interfaces, installation and full system integration.

Our current Debian development installations are being retained while the new platform proves itself.

Nothing will replace the working system simply because the new one boots successfully in a virtual machine.

**The Aim for R1**

Ultimately, Brimstone should behave like a dedicated piece of hi-fi equipment.

Switch it on, select an album and enjoy the music.

The operating system, recovery facilities, diagnostics and updates should quietly take care of themselves without the owner needing to become a Linux administrator.

For those familiar with older Meridian and Sooloos equipment, that philosophy should sound familiar.

The technology underneath may be considerably more modern, but the objective remains the same: a reliable music system that concentrates on music rather than computer maintenance.

We're still targeting 1 December 2026 for R1, subject to completing the necessary testing.

More updates as development progresses.

**Chris**
**Brimstone Core**
https://core-audio.uk

Brimstone — heading towards the December release 🎶


As we approach the planned December release, I want to say a proper thank-you to everyone who has helped test Brimstone. Your time, patience, suggestions and bug reports have made a real difference — especially when something that worked yesterday decided otherwise today!

It has grown considerably from where we started, and we’re now bringing the pieces together.
Two Core options
There will be two Core editions: a Debian-based version with an immutable operating system and three boot slots, providing separate system and recovery environments, and a new, purpose-built Core platform developed from the ground up.

The Intel x64 and Apple Silicon Core builds are now finished, with both audio and video playback working. Attention is now on bringing Control through the remaining development and testing.
More ways to enjoy your music
Apple Music integration is native, Spotify playlists play directly through Meridian outputs, and Bandcamp Radio is working.

TIDAL is the remaining service awaiting partner go-live, so that part is still pending rather than something I’m announcing as available today.

The aim remains the same: bring your collection and supported services together, without making listening to music feel like an IT project.
Live music, concert archives and a little something for Christmas
Brimstone also brings together three online archives of live concerts and authorised bootleg recordings, with downloads available where the recording’s permissions allow.

And it isn’t just about listening. You can rip supported concert discs to Core for video playback, where copying is permitted — so those concerts on the shelf can become part of the library you actually use.

Core also supports compatible videos recorded on Apple and Android devices. That means the footage you took at a gig, the family recordings and those slightly shaky but irreplaceable moments can have a home in your own library, rather than being forgotten on an old phone. Do keep a separate backup of anything irreplaceable.

Your albums, your playlists, your concerts and your memories — brought together to enjoy.

There is still testing to finish before December, and I’ll keep sharing progress as we get closer. To everyone who has helped get Brimstone this far: thank you. This is a small independent project, and your support genuinely matters.

Chris

Thanks for this awesome project!

When will there be an update for Windows?
The current version, is unable to install for me on 2 Windows 11 PC's, getting install errors.

So far I'm also unable to find the core using control software.

Windows was and alpha and won't be carried on, instead we have built a Debian installer that installs a fresh OS on the machine:

https://core-audio.uk/downloads/core/Brimstone-Core-R1-Debian-Rev29-20261021-amd64.iso

This needs ideally 250 GB boot drive and a second drive for media but can be installed on a single large drive.

https://core-audio.uk/features.html

The new controls will be released later in the week that also provides concert playback.

Thanks for your fast response.

I've tried downloading the Debian Core R1 · Revision 29 ISO multiple times, but it always fails.
Using Firefox/Chrome as browser here, tried on multiple PC's.

Download always fails when it reaches around 1GB.

Windows control is not being deprecated I hope?

Try a download manager for the ISO and the new control has had 2000k lines of code changed to make the interface work on anything, if having issues PM me ad I can send you a Dropbox link.

Thanks, I've just send you a PM.

Brimstone Core / Control R1 – patches and improvements this week


A busy week of using the system, finding the niggles and fixing them. The main focus has been making everyday listening and ripping easier, while keeping existing Meridian / Sooloos equipment useful.

• Meridian / Sooloos control: improved discovery and speaker selection, with a speaker selector on Core's Home screen. Mac-local playback now follows the correct queue and lyrics as well.
• Simpler music browsing: Albums, Bootlegs, Playlists and Radio Recordings have their own shelves in the current Core, Mac and iOS listening updates. Bootlegs and radio recordings stay off the normal Home album shelf. Album actions are centred on Play and Add to Queue; normal Mac/iOS playback selects the best complete available edition.
• Compilations and Various Artists: repaired albums that had split into multiple entries or individual tracks, including guest-performer releases. Original performer credits are retained. Original Album Series discs can be identified as the actual artist and album rather than retaining the box-set title.
• Artwork: improved cover lookup and preview before ripping. Core's album grid now handles artwork properly when filtering, refreshing or redrawing the page, with working retry controls for missing images. Existing artwork choices are preserved; a few unmatched releases still need a suitable provider match.
• The new Rip workspace: Audio Rip, Video Rip, MiniDisc Rip, Import and Burn are grouped clearly, with Recording Studio kept separate. Improvements cover USB optical access, disc-change detection, stale metadata from the previous disc, and metadata correction before ripping. Support still depends on the drive, disc and format.
• Background ripping and imports: completed rips can upload and publish while the next disc is prepared. A finished import triggers a library update. Large transfers and albums containing one long track are supported. Concert imports prepare one verified Apple-compatible playback file.
• Radio: Mac and iOS use Core's station directory, with search and personal lists kept separate. Available station and playing metadata is displayed. Eligible non-commercial streams can be recorded through Core; paid subscription services are excluded. Saved recordings have their own shelf and a simple Delete → Yes action.
• Podcasts and audiobooks: selecting a programme queues its episodes or chapters and starts at the chosen item, then opens Playing. Podcasts play on the device being used. Audiobook preparation, resume and available metadata have also received fixes.
• Bootleg downloads: Core owns the durable queue, prevents duplicate selections, shows queued/downloading/downloaded status, and restores work after a crash or restart.
• Video playback: concert videos are grouped by band, with available artwork and metadata. Streaming, startup buffering, seeking and format handling have received updates on Mac and supported iPad video. Apple TV uses HDMI audio only for R1 to keep sound and picture together; alternative network audio outputs remain R2 work.
• Layouts and controls: simpler navigation, Radio within Streaming, Podcasts and Audiobooks within Spoken Word, a smaller Playing layout for an 11-inch iPad in landscape, adaptive Duo layouts and CarPlay album browsing. TV Playing controls are smaller too.
• Core maintenance: repaired Clear All Queues and added Start/Restart controls for supported Core services. Library management belongs in Core; Control stays focused on listening and the local media devices it needs.

Current builds

Debian Core R1 revision 40 is available as an update patch. iPhone/iPad Control 31 and Apple TV Control 31 are testing in TestFlight. Mac Control 40 and Mac Core 51 are going through the remaining Apple release checks. Further TV parity and the newest Windows/Android listening updates are follow-up work.

Full weekly update: https://core-audio.uk/r1-weekly-2026-10-24.html
Downloads, build status and checksums: https://core-audio.uk/downloads.html

Thanks to everyone testing and reporting problems. If something misbehaves, the app/build, device, selected output and album or programme involved are the most useful details.

Hi all,

A fairly substantial Brimstone update: Core R1 beta QA106 is now available, both as a fresh Debian installer and a cumulative patch for existing Rev29/Rev48 systems.

We’ve been working through the listening, library and usability niggles. The main improvements include:
- Albums and artwork: further fixes for split compilations and Various Artists albums, missing covers and source availability. Where an album exists locally and remotely, Core’s own copy takes priority.
- Album and artist information: richer history, credits, photographs and available booklet artwork in the current Mac Control and iPad builds, with manual matching and scanned-booklet import.
- Meridian and USB playback: configurable DAC output limits and fixed PCM formats for compatible setups, plus improved output discovery and naming in Control.
- Squeezebox and Lyrion: players can be selected as speakers, with supported albums and radio integrated into the existing library.
- Streaming: tidier browsing, album searches, playlists and complete album queues. Audius and Jamendo routes are included, and Bandcamp Radio refreshes daily.
- iPhone listening: improved Wi-Fi/Tailscale handover, background playback, caching and reuse of downloaded tracks & full working CarPlay.
- Ripping and maintenance: better disc metadata/artwork refresh, library updates after completed rips, persistent bootleg download queues and clearer Settings.
Apple Music uses official MusicKit. TIDAL currently retains its official web/native handoff. Account permissions and subscriptions still apply.

Fresh installation and the complete signed update process—including reboot and confirmation—have been tested. Existing users should use the patch rather than reinstalling. Older Rev29/Rev48 systems need the initial console step described in the instructions.

Downloads and checksums:
Downloads

Full changes and installation instructions:
QA106 relase notes

Updated Mac and iPhone/iPad Control builds have also been uploaded for TestFlight. Android will follow once production signing and device checks are finished.

Thanks to everyone testing and reporting the awkward bits—it’s helping us get R1 into much better shape.

Brimstone Core R1 update – native Meridian playback, the full Store installer and simpler downloads
4 November 2026

Hi everyone,

A proper update for those following Brimstone, and a thank-you to everyone who has been testing it and sending feedback.
/
The main news is that Core is now at R1 release candidate 1.0.0-rc.2, direct native MS200 /ID41 /MD600 / Twinstore playback is working, and Brimstone Store now has a complete Debian installer rather than a collection of files to assemble yourself. The website has also had a much-needed clear-out.

The aim remains the same: keep good Meridian equipment useful, keep ownership of your music collection, and improve the software around it rather than require everyone to replace their system.

Native Meridian playback

The important distinction is that the tested MS200 route sends audio directly from Brimstone Core to the receiver over Ethernet. It does not require the old Sooloos library broker to act as the audio intermediary. This is native Meridian receiver communication, not an AirPlay or DLNA route with a different label.

Local-library playback has completed real track transitions through the normal Core playback path. Play, pause, resume, seek and stop have also been exercised on the physical MS200. The latest work adds podcast playback to that native route, with smooth listening confirmed on the attached receiver.

Meridian settings now identify and retain individual devices, their names and enabled preferences. Two boxes are not treated as the same unit simply because they share a model name. Discovery handling has also been corrected so an older discovery announcement does not, by itself, make an otherwise reachable saved receiver disappear from the available outputs.

ID40, ID41 and MS600 are included in the shared receiver-protocol implementation and software tests, but they still need their own physical acceptance tests. The MS200 is the hardware reference actually tested so far. That is not a claim that every model, firmware revision, sample rate or multiroom arrangement has been qualified. Native volume and mute are also separate from the transport controls already exercised.

There is another distinction worth making: sending audio to Meridian equipment is not the same as making an original Control 15 or Sooloos application browse Brimstone as though it were a Sooloos server. That discovery, catalogue and controller-compatibility work remains a separate development task. I am not presenting the current release as a complete drop-in replacement for every original Sooloos component.

Current release notes

Library, metadata and everyday listening

A fair amount of the recent work has been on the less glamorous things that make the system nicer to live with.

Core now prefers a suitable copy in its own library before consulting a remote library. That avoids waiting for an old or unavailable Sooloos broker when Core already has the selected music. Edition choices and explicit version selection are still respected; the intention is not to substitute a different release just because it is easier to reach.

The release retains the artwork, compilation and enhanced-metadata work, alongside manual corrections and the album/artist reading features on supported clients. Metadata availability still depends on the material and configured sources; a cover image is not being passed off as a complete booklet.

Recent fixes also address large-catalogue publication memory pressure, playback-position reporting and lyric timing. Longer-running background-scan and endurance testing remain part of qualification; I am not claiming that one successful listening session proves every workload is finished.

Podcasts have had particular attention. Missing or zero timings in feeds previously prevented some programmes from playing properly. The DruidCast test kept the complete 234-episode programme available while the selected episode played through the MS200. That is a retained queue, not a claim that all 234 episodes have been listened through as a test.

Radio, podcasts, audiobooks and owned live recordings remain part of the wider library alongside albums. Support for a particular source and output still matters; a screen appearing in the interface does not imply that every possible combination has been tested.

Feature overview

Core, Store and Control

There are three roles, rather than three competing music systems.

Core maintains the main catalogue, metadata, queues and playback.

Store provides dedicated storage when you need it.

Control is the family of interfaces used to browse and operate the system.

A separate Store is optional. Core can still use its own storage or suitable network shares. The point of Store is to let storage grow separately, not to force everyone to buy or run another machine.

Store now has a full Debian installer

Store Beta 1, build 1.0.1-debian.1, is now available as a bootable x86-64 ISO of approximately 1.11 GB. It installs Debian and Store together on a dedicated computer NOT a virtual machine.

This is ordinary writable Debian. There is no immutable operating-system root, no A/B/C slot layout and no recovery-slot switching for Store. Normal Debian administration and package management remain available. This is deliberately different from Core's protected appliance/update design.

You boot the ISO, follow Debian's installer, create the machine account, select and confirm the system disk, and restart into the installed system. First-boot setup loads the included Store services. There is no Git checkout, no separate Debian installation to do beforehand and no manual service build.

Internet access is required during installation for Debian packages. The Store runtime is included in the ISO. A unique Store web-administrator password is generated rather than shipping the same factory password to everyone.

Store includes NFSv4, encrypted SMB 3.1.1, HTTPS WebDAV and DLNA/UPnP services. Pairing with Core uses an Add Store code; NFS access remains closed before valid pairing.

The fresh BIOS installation test passed with a writable system, all four Store services healthy, working administrator login and the ZFS module loaded. A separate disposable test disk was left unchanged. The Store source regression suite passed 250 tests, with two warnings. Full UEFI installation, physical storage hardware and populated-library commissioning remain separate checks.

Please keep valuable media disks separate from the installation target. The installer does not automatically adopt your existing collection, and a tested installer is not a substitute for a backup.

Store installer and installation guide

Installing or updating Core

Existing Core installations should use the current signed R1 1.0.0-rc.2 update, rather than reinstalling the operating system. The application update is approximately 6.87 MB and is intended to retain the existing library, accounts and manual metadata.

On a Core already equipped with the trusted slot-C updater, the normal update screen queues the update, backs up state, boots maintenance C, updates the inactive system slot and returns to Core. Earlier installations follow the route supported by their installed updater. An ordinary application update does not silently add the newer privileged recovery worker.

For a fresh Core, the published route is still the tested QA106 ISO followed by the current RC2 update. The newer all-in-one RC2 Core ISO is built but has not completed its fresh-install qualification, so it is not being offered as the tested installer. No intermediate historical patches are required for the documented fresh-install route.

For Core, the current recommendation is a dedicated 128 GB or larger system drive and 8 GB RAM, with media kept separately. Do not reinstall merely to update an existing system.

Fresh Core installation

Updating an existing Core

Streaming services

Spotify retains its beta Connect and personal-library integration.

Apple Music uses official MusicKit playback and the user's own authorisation; normal users no longer need to supply their own Apple developer key. The protected playback still belongs to the authorised Apple playback route, not a new headless Apple Music decoder running on Debian.

TIDAL retains catalogue/library integration and the official playback handoff. General native full-track playback through Core is not being claimed while provider authorisation and qualification remain outstanding.

Radio, Audius, Bandcamp and Jamendo retain their documented supported routes. Accounts, subscriptions, permissions and output capabilities still determine what can play where. Direct MS200 support does not automatically mean that every streaming service can be sent to it through the same path.

Roon/RAAT receiving, OAAT integration and a replacement Sooloos catalogue server are not new features of this Store release. They are separate interoperability work, not something silently enabled by installing the storage software.

Streaming services and provider status

Control apps

Apple Control access remains through the existing TestFlight invitation for iPhone, iPad and Mac. The invitation shows what Apple currently makes available to your account; a development build or successful upload is not automatically a public beta release. CarPlay remains part of the iPhone Control work.

The public downloads also retain the Windows Control installer and signed Android beta. Windows Control is currently an unsigned review build, so Windows may show an unknown-publisher warning. The Android download is the available signed public beta, not a newer development build relabelled as released.

Standalone macOS Core and Windows Core development are paused, and their older previews are no longer promoted as current downloads. Mac Control is separate from Mac Core and remains part of the active controller work. tvOS development remains paused; there is no new Apple TV release being announced here.

Control downloads and Apple TestFlight access

A simpler website

The downloads page now separates Core, Store and Control, with a clear distinction between a fresh installer and an update.

Superseded packages, old previews, duplicate installation choices and the source-deployment route have been removed from public download access. Older material has been retained privately for rollback rather than left there to confuse new users. Current installation guides, update instructions and checksums remain available.

The goal is less time deciding which of fifteen similarly named files to install, and more time actually listening.

Current downloads

Where things stand

Core is a release candidate, not the final 1.0.0 release. The current target for 1.0.0 is 14 November 2026, subject to the remaining qualification work. Store is a beta with its own installer and its own testing requirements.

The immediate priorities are broader Meridian hardware testing, reliable storage commissioning, longer-running playback/library tests and the remaining installer checks. Keeping original Sooloos controls useful is still an important objective, but it will be described as working when that end-to-end controller path has actually been demonstrated.

Thanks again to everyone testing and reporting the awkward cases. Reports from ID40, ID41 and MS600 owners are especially useful: please include the model, firmware, Core build and whether the source is local music, a podcast or a streaming service.

Brimstone is an independent project, not an official Meridian or Roon product.

Chris