· None of the above quite fits
· None of these quite match
· Track name & display mismatch; skipping tracks
· Roon Nucleus One with internal drive with Roon 2.60 (Build 1629)
Pace 5286ac router/gateway (AT&T)
Araknis AN210SWR8P 8-Port Gigabit Switch
Sonos Amp
iPhone SE with Roon V 2.67 (Build 1661)
Here are test cases with two different albums. All tests are using Sonos as the player/receiver.
[ It is to be noted that when I repeat these experiments with my iPhone as the receiver/player no such problems occur; but, then again, having the player also act as the controller may have special interactions that differ from having the controller & player as separate devices. ]
While playing the Album: Boswell Sisters: That’s How Rhythm Was Born
When it came to the 6th track : Song of Surrender, half way in, I used the end-of-track / Next track control to skip to the next track, which it did correctly.
When it reached the 10th track (“Coffee in the Morning, Kisses at Night”), it played the audio for that track, but displayed the name of track 11: “42nd Street”.
It had that mismatch between track name and audio for the entire song.
At the end of that song, it stopped playing as if at end of album, / end-of-queue - but actually had 10 more songs from that album in the queue
I should pressed play to see what happened, but instead I cleared the queue to start the experiment to attempt problem re-creation from scratch
Re-creation Attempt #1:
Played same album from beginning.
At the 3rd track : “Louisiana Hayride”, it played the correct track audio, but displayed the song name of the 4th track: Shuffle Off to Buffalo".
I attempted to pause half way through, but it kept playing the track 3 audio and displaying track 4 title to the end & then paused.
When I pressed Play icon, it started playing track 4 with correct track title.
Re-creation Attempt #1:
Played same album from beginning.
When it came to the 6th track : Song of Surrender, half way in, I used the end-of-track / Next track control to skip to the next track, which it did correctly.
When it reached the 10th track (“Coffee in the Morning, Kisses at Night”), it played the audio for that track, but displayed the name of track 13: “The Darktown Strutters’ Ball”.
It had that mismatch between track name and audio for the entire song.
I paused the song. When I tried to play it, it at first did not accept the action. A second attempt did play, but it played the track 13 audio with track 13’s title.
Note that it never played tracks 11 & 12, though they were in the queue.
It then played track track 14 (audio & title.
Next it played track 15, but displayed the title to track 16.
I tried to pause play, but it continued to the end of that track & then paused.
When I pressed Play, it played track 16 with track 16’s title.
It played & displayed correctly for the rest of the Album.
I will next try to recreate the problem with a different album (previous occurrences were with different albums than this one, but I did not log the circumstances or try to recreate with them at that time)
I definitely think it has to do with interrupting the sequence (either skipping or re-playing tracks). I suspect it has to do with interaction of Roon & Sonos.
= = = = = = = = = = = = =
A new situation.
I was listening to Soul Hits of the '70’s, vol. 1
After track1 (Grazing ion the grass), it started to play track 1 again. I quickly realized that the I had previously been listening to a single track (ambient background sound) on a repeat loop in that room.
I quickly went to the queue panel and turned off the loop setting.
Then I skipped the repeat track 1 to play track 2.
It then was correctly playing the tracks until after track 3, it began playing track 4 BUT it started several seconds into the track. I quickly looked at the display that showed the track progress bar stating that it was near the end of the track.
When the progress bar reached the end, track 4 music continued playing (it was nowhere near the end of the song) but the display now was showing track 5 as playing.
I then paused the play to type these notes. When I resumed the play (even though the music from track 4 had not ended), it began playing track 5 so that the song display and the music being played were back in sync.
But when it reached track 7 it was playing track 7 while the display showed the track 8 name.
When that song ended, it started playing track 8 - but displayed the song name for track 9. When the track progress bar reach the end of track 9, the display hung for a bit and then started tracking track 10, while still playing track 8!
While displaying the progress as the middle of track 10, it started playing the beginning of the track 9 music.
I paused it while it was display the track 11 name while playing track 9.
When I resumed, it again was sync’d back up - playing the music from track 11 while displaying the correct song name and track progress.
At that point I quit that experiment.
I once again, after having played a different album’s track on repeat, replayed the Soul Hits of the '70’s, vol. 1.
Again, I waited until it started to repeat track 1 before I disabled “repeat track” and then manually jumped it to track 2.
having correctly played the first 5 tracks, when it reached track 6, it displayed the track 6 name but was actually playing track 7.
I paused to type these notes. When resumed, it was sync’ed back up, playing track 7 while displaying track 7. At end of track 7, it the correct played & displayed track 8, in sync.
It continue normal play, until track 10. Soon after starting track 10, the display showed track progress as being near the end of track 10. When the progress bar reached “the end”, it displayed track 11 as the current track but continued to play track 10.
Sync’ing back up by doing a pause & play does not prevent problems later in the album play.
At that point I quit that experiment.
I don’t really think the problem is related to the repeat track function & that it just related to manual changes to play order that causes an odd interaction between Sonos & Roon; but I thought it best to recreated the exact condition leading up to the behavior.
Hi @Michael_Arones,
Thank you so much for taking the time to provide such incredibly detailed test notes. Having step-by-step reproduction steps is usually exactly what we need to track down a bug!
I went ahead and searched your Roon Server diagnostic logs for the exact tracks you mentioned (like “Song of Surrender” and “Louisiana Hayride”) to see exactly what state the Sonos Amp was reporting back to Roon during those skips. However, I wasn’t able to locate those specific playback events in your recent logs- it is possible the log files rolled over before the diagnostic report was generated.
Could we ask you to do two things to help us move forward?
1. Reproduce and provide a timestamp Could you please reproduce this issue one more time? When the track name and audio fall out of sync, please note down the exact local date and time (e.g., June 22 at 4:15 PM) and the name of the track. Reply here with that exact timestamp so we can immediately pull a fresh diagnostic report and zoom in on that precise moment.
2. Report this to Sonos Your isolation test was perfect: because this only happens when streaming to the Sonos Amp and works flawlessly on your iPhone, this points heavily toward how the Sonos API is handling queue interruptions (skips, pauses, repeats) and reporting its buffer status back to Roon. Because this is isolated to the Sonos ecosystem, we highly recommend reporting this behavior directly to Sonos support. If a recent Sonos firmware update altered how their devices report playback state to third-party controllers, they will need to investigate this on their end as well.
Thank you again for your patience and for helping us track this down! Looking forward to your timestamp.
Hi @Michael_Arones,
We actually have a ticket in the pipeline tracking position offset issues that particularly affect early generation (Sonos S1 firmware) Sonos Amp models.
We’ll give you a ping here when we expect this work to be released in Early Access so you can test it out.
Thank you again for the report.
Wow! Glad to hear that.
I will be eagerly awaiting the possible fix.
Sonos and Roon aren’t official partners, and we sometimes need to implement patches and one-off fixes for the native Sonos protocol to work with Roon on older Sonos models or in cross-generational setups (mixed Sonos S1 and S2).
This work can take a little time but it’s resolved issues in the past. We’ll reach out here as soon as we have more information available from development.
You shouldn’t have any issues with Airplay2 on the same devices in the meantime, as those rely on a separate playback position sync mechanism.
The connection from Roon to the particular Sonos Amp (apparently not “Roon Tested”), which drives the speakers in the bedroom where I have been testing this situation, uses Airplay2. Thus your last statement confuses me .
My entire Sonos system has a mixer of Sonos 1 & Sonos 2 generation devices,thus I am using Sonos 1 to manage them.
Hey @Michael_Arones,
Thanks for the followup! We took another pass through your Roon Server logs and have some clarifying news.
It turns out the Bedroom zone isn’t actually running AirPlay 2, it’s using the native Sonos protocol. All of its playback goes through our Sonos zoneplayer engine, with Roon serving the audio over its own HTTP stream, and driving the Amp via Sonos transport commands.
There’s no AirPlay activity for that zone anywhere in the logs.
The good news is that this places you squarely within the ticket we already have open, rather than outside it:
Your Bedroom device reports as Model “AMP,” and our autodetect logs a “No Match” for it, so it falls back to generic Sonos handling.
Your Sonos units are all on S1 (SWGen 1, software 57.23-74170) exactly the early-generation S1 Amp profile that ticket is tracking.
On what’s happening: the desync clusters at track boundaries and right after manual skips or pauses, which matches your description. Roon queues the next track, but the Amp keeps reporting its status against the previous stream, and Roon ends up discarding those updates (“stale av status event ignored”). That position drift is what surfaces as the track name and audio falling out of sync.
Two things that would help from here:
If you can reproduce the mismatch once more and jot down the exact local time and track, we can pull a fresh diagnostic on that precise moment to add to the ticket.
As an interim workaround, your Amp does support AirPlay, so you could set that zone up as a true AirPlay 2 output. AirPlay uses a separate position-sync path, so it should sidestep this particular issue while the fix is in development.
We’ll ping you here as soon as this work is ready to test in Early Access. Thanks again for the detailed reports, they’ve been genuinely useful.
I truly appreciate your help. Excuse my being a bit thickheaded …
As an interim workaround, your Amp does support AirPlay, so you could set that zone up as a true AirPlay 2 output.
As the previous image shows, Roon describes the enabled Sonos Amp as using Airplay2. That same unit is displayed a second time in that Roon device listing as “via Sonos Streaming”, but that instance is disabled.
How do I change the Roon configuration from “via Airplay2” to being setup as a “true Airplay2”?
I feel like I am missing some essential knowledge here …
Hey @Michael_Arones,
Good question, and sorry for the confusing wording, let me clear this up.
The “AirPlay2” tag you’re seeing next to the enabled Bedroom entry is just indicating that the Amp supports AirPlay2 as a protocol - it doesn’t mean Roon is actually sending audio to it that way. Based on our log review, that enabled entry is running through Roon’s native Sonos zoneplayer engine (the same engine tracked in the ticket), which is why you’re seeing the position drift.
To get a true AirPlay 2 output, you’ll want to look for a second, separate device entry for that same Amp - one that isn’t grouped under the Sonos section at all. It typically shows up under Settings > Audio as a standalone AirPlay device (often just the device’s network name, without any Sonos branding or icon next to it).
A couple of things to try:
Go to Settings > Audio and see if the airplay option is available for you
If you still can’t find a distinct entry, go ahead and send us a fresh screenshot of your full Audio setup page - that will let us confirm exactly what’s showing up on your system and point you to the right one.
Once you do find it, yes, enable that AirPlay entry and disable the current Sonos zoneplayer entry for the same Amp, so you don’t end up with two competing zones for one speaker.
Thanks for your patience while we sort this out!
