Qobuz playlists get stuck at end of tracks (ref#3V2SGO)

Support
1

What best describes your playback issue?

· Music stops playing unexpectedly

What type of Zone is affected by this problem?

· *All of my Zones* are affected.

Does the issue affect all file formats?

· The issue affects *multiple/all* file formats.

Does the issue happen with local library music, streaming service music, or both?

· *Only streaming* music is affected.

Please select the streaming service(s) with which you're encountering playback problems.

· Qobuz

Have you tried logging out and back in again to your streaming service in Roon Settings?

· Logging out and back in had no impact, the issue remains

Do you have an approximate timestamp of when the issue last occurred?

· I've been playing music for the last 30 minutes (or trying to). So August 4th 21:00 to 21:17 *GMT)

What are the make and model of the affected audio device(s) and the connection type?

· BeoSound Theatre (I'm using GoogleCast to stream from the Nueclue to it)

Describe the issue

I have had this issue for a long time - i.e. Qobuz content (playlists especially I believe) will get stuck at the end of each track. The song timeline seems stuck at 1 second prior to the end of the track, and won't progress to the next. I can click the next track button and it will then move on, but otherwise it gets stuck. I dont seem to have this issue with local content

Describe your network setup

My Nucleus is hard wired to my router. My music endpoint (a B&O soundbar) is also hardwired to the router.

2

Hey @Sandeep_Bhatia,

Thanks for the detailed report and for sending the logs over, that made this much easier to pin down, and I’m sorry it’s been nagging you for so long.

I found the exact problem in your logs. The good news is that Roon and Qobuz are doing their part correctly: I can see the full track downloading from Qobuz and Roon handing the complete audio off to your Beosound Theatre with no errors. The music genuinely reaches the speaker.

Where it breaks is the final step. Your Beosound is playing over Google Cast, and at the end of a track the Beosound is supposed to send a “track finished” message back to Roon so the next song can start. Intermittently, that message never arrives, so Roon sits waiting at the last second of the track, which is why the timeline freezes about a second from the end and won’t move on until you press Next. When it does send that message (which it sometimes does), the next track starts on its own, exactly as it should.

So this is a hiccup in the Cast connection to the Beosound, rather than anything wrong with Qobuz itself. That also explains why local files feel more reliable; playlists just move between tracks far more often, so there are many more of these handoffs for the glitch to land on. I also noticed the Beosound briefly dropped its Cast connection to your Nucleus several times during the session, which points the same direction.

A few things to try, roughly in order, the first two are the ones most likely to sort it:

  1. Add a short crossfade to the zone. In Roon, open that zone’s settings and set Crossfade to around 2–3 seconds. This makes Roon manage the transition itself instead of waiting on the Beosound’s end-of-track signal, and it very often clears up exactly this kind of stall. Great as both a quick fix and a test.
  2. Update and restart the Beosound Theatre. Make sure it’s on the latest B&O firmware, then fully power-cycle it (and restart the Nucleus for good measure). This end-of-track behavior is handled on the Beosound’s side, so a firmware update is the most likely permanent fix.
  3. Try a quick comparison. Play the same Qobuz playlist to a different endpoint for a few tracks, anything that isn’t Google Cast. If it advances cleanly there, that confirms the Beosound’s Cast is the culprit. If your Beosound offers AirPlay or Roon Ready as an alternative to Google Cast, switching to that would avoid the issue altogether.
  4. A network note for later: Google Cast relies on multicast traffic on your network. Even though everything’s wired, it’s worth making sure the Nucleus and Beosound are on the same network/subnet and that any “IGMP snooping” setting on your router or switch is enabled. Those brief disconnects I mentioned suggest the Cast link isn’t fully stable, and tightening this up should help.

If you can start with the crossfade setting and the Beosound firmware update and let me know how it behaves, we’ll take it from there. I’m optimistic those two will make a real difference. :raising_hands: