Owner, 2026-07-31: "hay que mantener el status activo, sin importar el cambio en
el backend." Gapless now survives a backend switch, ALSA included.
A deliberate divergence from BOTH references. Tauri forced it off when moving to
ALSA (`SettingsView.svelte:3409-3416`, "not compatible with ALSA Direct") and
Slint copied that (`settings.rs:1232-1237`); the two agree despite the different
wording, because in the engine's own vocabulary `using_alsa_direct` IS
`backend_type == Alsa` (qbz-player/src/player/mod.rs:725-729).
The exclusion looks broader than the hardware demands: `PlayNext` is
backend-AGNOSTIC — it appends to the live engine and refuses only on a missing
engine, a sample-rate/channel mismatch, or an active streaming source
(mod.rs:3553-3586) — and ALSA Direct does have an engine with its own writer
thread. Within one album at a constant rate there is no mechanism here that
should break. Nothing in qbz-audio or qbz-player is touched; this only stops the
frontend from forcing the user's setting off.
What this port had was worse than either reference: the guard was missing
entirely, so EVERY backend change killed gapless — including switching to
PipeWire, where it works perfectly. That is what read as "alsa breaks gapless":
the switch itself turned it off, and re-enabling it was what fixed it, not the
restart it happened to coincide with.
The `streaming-only` cascade still disables gapless and is untouched — that one
is about there being no cached file to hand the engine, not about the backend.
NEEDS REAL-HARDWARE VERIFICATION on the owner's DAC: the failure mode to watch
is a transition that renegotiates the stream mid-album (a rate change), which
the format-match guard should already refuse.
cc