Hi! What’s not quite right with Roon?
· None of the above quite fits
None of the above quite fits
· None of these quite match
Tell us what's going on
· Human Diagnosed! ** AI summarised ** Playback failure at fixed timestamp (Qobuz) causing RAAT zone lock-up – reproducible across endpoints
**System:**
* Roon Core: ROCK (latest build, updated recently)
* Source: Qobuz streaming only (no local files)
* Playback modes tested:
* Roon → HQPlayer → NAA (Innuos Pulsar)
* Roon → RAAT endpoint (Innuos)
* Roon → RAAT endpoint (Windows PC)
* Network: stable, no packet loss, issue reproducible across different endpoints
---
**Issue Summary:**
A specific track "Spanish Castles In Space" from The Orb's Adventures Beyond the Ultraworld* (Qobuz) consistently fails at **exactly 6:20**. There is only 1 Qobuz version of this album. I do not use any local storage.
* Playback stops abruptly at the same timestamp every time
* Roon reports “lost control of audio device” (in some cases)
* The affected zone becomes **unusable** afterwards:
* No tracks will play
* Queue cannot be advanced
* Requires zone disable/re-enable or Core restart to recover
This
---
**Critical Observations:**
1. **100% reproducible** at exactly 6:20 on every attempt
2. Occurs across multiple endpoints:
* Innuos (RAAT)
* Windows PC (RAAT)
* HQPlayer path also affected
3. Does **NOT occur** when playing the same track via Innuos Sense (direct Qobuz integration) or Qobuz app via the PC on same network.
4. Other tracks/albums generally play normally
5. Issue appeared **recently** – this track has been used as a reference for ~2 years with no prior problems
---
**Additional Behaviour:**
* If another zone is playing a different album simultaneously, that zone continues normally
* Only the affected zone locks up
* Suggests a **per-zone pipeline failure**, not a global Core crash
---
**Assessment:**
This appears to be:
* A **deterministic decode or stream-handling failure** at a specific point in the Qobuz stream
* Followed by a **RAAT session not being properly torn down or recovered**, leaving the zone in a deadlocked state
Given that:
* The same track plays correctly outside Roon
* The failure is timestamp-specific and reproducible
* The issue began after a recent update
This strongly suggests a **regression in Roon’s Qobuz streaming and/or decode pipeline**, possibly triggered by a specific FLAC frame or stream boundary condition.
---
**Request:**
* Can you reproduce this internally with the Qobuz version of this album?
* Is there any known issue with fixed-timestamp playback failures or RAAT zone lock-ups?
* Are there logging steps I can provide to help isolate the failure?
Happy to supply logs or run specific tests.
---
**Note:**
This is not a network or endpoint issue – behaviour is identical across multiple endpoints and isolated to Roon playback only.
---
Thanks — this is fully reproducible and should be straightforward to isolate.
Tell us about your home network
· This is not network related, since any non-Roon route to playback on the same devices all works fine, using exclusively Qobuz.