HELP & EXPLANATIONS

Good questions.
Straight answers.

How the server and clients fit together, what each installer does and what's still being tested.

What's the difference between Core and Control?

Core is the server: it owns the catalogue, metadata, media sources and playback decisions. Control is the client you use on a Mac, phone, iPad, Apple TV or in your car to operate a Core.

Do I need a subscription?

Brimstone is designed around owned music and your own server, without making a paid streaming subscription a prerequisite for your local collection. External services, where supported, may have their own accounts or terms.

Which computer should run Debian Core?

Use Debian 13 (amd64) on a physical machine or full virtual machine. For a VM, allocate at least four vCPUs and 8 GB RAM. The QA11 ISO additionally expects a 32 GB+ boot disk and a separate music disk. LXC is not a supported Core installation target.

Should I download the ISO or the .deb?

Choose the ISO when you want the Brimstone Core OS graphical, clean-install experience. Use the .deb and 'apt install ./package.deb' on an existing Debian 13 host. The ISO can erase a selected OS disk; the package uses your existing operating system.

Can I use just one disk for the QA11 ISO?

No, not for the supported automatic media setup. The current Core OS installer expects a dedicated boot disk of at least 32 GB and at least one separate music disk. A machine with only one disk may boot and install Debian, but the media collections will not automatically be mounted and registered. See the Core OS hardware guide and real screenshots.

Does the installer erase my music drives?

The QA11 OS installation erases the specific system disk you select and confirm. The music-disk selection screen does not format the other drives. Later storage preparation or ZFS pool creation may overwrite data if you explicitly choose to do so, so make and verify a backup before any disk changes.

Does macOS Core run on both Intel and Apple Silicon?

Yes, the current 0.4.2 (42) QA archive contains a universal x86_64 and arm64 application for compatible macOS 12+ Macs. It's Developer ID-signed but not Apple-notarised.

Can I run Windows Core yet?

There is an early native Windows x64 Alpha intended for a spare test machine. It is unsigned, and clean installs, unattended startup and real endpoint playback are still being validated. Windows Control is a separate app.

What about Meridian and Sooloos?

Preserving Meridian hardware is a major design goal. Core can work with supported Sooloos discoveries and endpoints; the success of transport control and actual audio playback depends on the hardware and the specific build.

Does Core retain albums and audiobooks when I change devices?

The goal is one authoritative Core catalogue and persistent state rather than independent libraries in each client. Availability, offline downloads and resume behaviour depend on the particular Control platform and release.

Why is my browser showing an HTTPS certificate warning?

Some local Core builds and gateways use locally-issued certificates, while others use HTTP inside trusted LANs. Do not blindly bypass an unexpected certificate warning. Check the host and certificate, and place TLS in front of any remotely accessible service.

Where do I report an issue?

Use the Known Issues page or Support page, including the platform, version, endpoint model and steps to reproduce. Don't send account passwords or private access tokens.

STILL NEED A HAND?

Get help with your setup.

From first installation to a Meridian endpoint that won't play nicely.