Hello @Mel_Martin,
Thank you for your patience. We’ve taken another close look at the logs around the timestamp you provided (Dec 10, ~08:35–08:45 local time), including an expanded window on both sides of the reported event.
What we see in the logs
At the time the album page was opened, the server logs show only local database activity, for example:
12/10 15:39:14 [Local 12/10 08:39:14] Info: [library/albumdetails] found 1 ingroup alternates, 0 other alternates
12/10 15:39:14 [Local 12/10 08:39:14] Info: [library/albumdetails] Created album details screen for LibraryAlbum[2170671, London Symphony Orchestra/Antal Doráti - The Mercury Masters: Antal Dorati in London – Volume 2 - Bartók: Music for Strings, Percussion & Celesta / Sonata for 2 Pianos & Percussion]
12/10 15:39:14 [Local 12/10 08:39:14] Info: [library/albumdetails]
12/10 15:39:14 [Local 12/10 08:39:14] Warn: null SortEnv language. Defaulting to current culture.
12/10 15:39:14 [Local 12/10 08:39:14] Trace: [music/query] performing album query
12/10 15:39:14 [Local 12/10 08:39:14] Trace: [music/query] query returned 2 Sooloos.Broker.Api.AlbumLite(s)
12/10 15:39:14 [Local 12/10 08:39:14] Trace: [music/query] performing album query
12/10 15:39:14 [Local 12/10 08:39:14] Trace: [music/query] query returned 0 Sooloos.Broker.Api.AlbumLite(s)
These entries indicate that RoonServer successfully:
- resolved the album object from the local library
- queried the local database for album metadata and alternates
- constructed the Album Details view
Importantly:
- these are local DB queries, not cloud metadata or streaming-service requests
- they complete immediately in the logs (no retries, no long-running queries, no timeouts)
- this code path is not one where we would normally expect minute-long delays
In other words, from the server’s perspective, the album page was created promptly and without error.
What we do not see
In the same time window, we do not see:
- long-running or stalled metadata requests
- repeated retries to Roon cloud services
- blocking calls to TIDAL/Qobuz
- database locks, I/O stalls, or memory pressure
- errors that would explain a 30–60 second delay opening an album page
Because of this, there is no clear indication in the logs of a server-side condition that would account for the behavior you’re experiencing.
Why this makes the issue difficult to isolate
RoonServer relies heavily on exact correlation between:
- a specific album
- a precise timestamp
- and the corresponding log activity
Without that correlation, we’re left reviewing large volumes of normal background activity (analysis, indexing, networking) that don’t clearly map to the symptom you’re seeing.
At the moment, the logs around the reported time simply don’t show anything abnormal that we can act on.
How we can move this forward
We absolutely understand how frustrating this is, especially given how long you’ve been dealing with it. To make further progress, we’ll need your help with one of the following:
- A precise album name and a precise timestamp (to the minute) when the delay occurs
- Or a short screen recording showing the delay, with the system clock visible
- Or confirmation that the issue still occurs immediately after a fresh RoonServer restart (before background analysis resumes)
Without one of these, it’s extremely difficult to distinguish a client-side rendering delay, a transient network condition, or a background task overlap from a true server-side fault.
We’re not seeing anything in the logs that suggests a persistent defect in RoonServer itself, but we’re very willing to continue investigating once we can reliably line up the symptom with the diagnostics.
We understand that this issue has been reported before and that you’ve shared timestamps, album names, and even recordings in earlier cases. Unfortunately, logs from that time are no longer available. To correlate the behavior with the diagnostics we currently have access to, we need this information again for a recent occurrence where the issue can be matched directly to the available logs.
Thank you for your continued patience and cooperation — we’ll keep working with you to get to the bottom of this.
