Can you please reproduce this issue, and let us know the exact local time + date + track that was playing when you experienced this issue? I can enable diagnostics mode afterwards for your account, thanks!
I just noticed it: May 8th 13:49 CET.
Unfortunately it may have started occurring anywhere from ~10:30.
I will try to narrow things down in subsequent attempts.
Song that Roon says is playing (zone Office):
/data/music/hi-res/Metallica_-Metallica(Deluxe_Box_Set)/0507-metallica-the_thing_that_should_not_be_(live_at_maimarktgelaende_mannheim_germany_may_22nd_1993)-3ee209ba.flac
Song that is really playing (I think):
/data/music/hi-res/Metallica_-Metallica(Deluxe_Box_Set)/0506-metallica-wherever_i_may_roam_(live_at_maimarktgelaende_mannheim_germany_may_22nd_1993)-bd1945e9.flac
Roon says this file is playing:
/data/music/hi-res/Metallica_-Metallica(Deluxe_Box_Set)/0504-metallica-welcome_home_(sanitarium)_(live_at_maimarktgelaende_mannheim_germany_may_22nd_1993)-7f1153cc.flac
Actually this file is playing:
/data/music/hi-res/Metallica_-Metallica(Deluxe_Box_Set)/0503-metallica-harvester_of_sorrow_(live_at_maimarktgelaende_mannheim_germany_may_22nd_1993)-2e6238d1.flac
The play session consisted of the following files (take base path from above):
Roon plays /data/music/albums/iron_maiden_-best_of_the_beast/208_track08.flac
and switches to /data/music/albums/iron_maiden-_best_of_the_beast/209_track09.flac
This 2nd track doesn’t start at the beginning.
Because I heard the skip I immediately switched to see what Roon was doing.
The progress bar was correctly indicating track 209 Hallowed Be Thy Name but the progress bar was moving forward at a pace of at least 10s per 1s of realtime (audible playback was normal speed).
Another related side-effect I sometimes have is the following:
When playing an album/playlist, due to the Roon playlist skipping ahead of what’s actually playing;
Roon indicates nothing playing anymore at 1 or 2 tracks before the end.
At this point you also can’t stop anything.
Are you still seeing this issue on the latest Roon release? We spoke to the team regarding this and they have noted that this may be a network-related issue. We heavily rely on Sonos to tell us where the position it is in the track, and if there are any network issues, Roon can end up missing some of these “this is where I am in the track” messages.
This appears to be a Managed switch with QoS abilities. We have sometimes found that managed switches can be the cause of similar issues, are you able to temporarily bypass the switch and see if the issue remains?
How, specifically, have you hardwired the Play:5 and the Sonos Five? Are they on separate ethernet ports on the Juniper, daisy-chained inline together, or in configuration with other hardware of some kind?
SonosNet effectively builds a second Sonos-only network on top of whatever LAN is already available, but will occasionally “short-circuit,” so to speak, in finding the closest path to a linked Sonos device. In certain situations, this can interfere with traffic passing between other Sonos devices in Roon. Knowing the particular configuration of your Sonos network may illuminate what’s wrong.
Please see my colleague’s questions above as well. Thank you!
QoS is disabled on the switch so it should essentially work like an unmanaged switch with a single shared buffer.
Bypassing the switch should be possible.
Currently Roon Core runs as a VM on Synology (QEMU I think) and is wired via a fiber trunk.
Connect a new unmanaged switch to the Juniper switch
Connect Sonos to unmanaged switch
Connect VM to a new virtual bridge network on a copper port which is also wired to the unmanaged switch
Other network issue / “We heavily rely on Sonos to tell us where the position it is in the track”
Here I suppose we can try to correlate what Sonos sends with what Roon Core receives.
I can look into packet capturing what the Sonos sends
I can look into packet capturing what the Roon Core receives from the Sonos
Is it possible to have Roon Core log the track position info it receives from Sonos?
Play:5 and Sonos Five are wired to separate ports on the Juniper. Would it have any effect to disconnect all but 1 Sonos?
Thank you for the precise reports. The team is investigating with development - Roon receives playbar position from Sonos, and we can confirm in logs that Sonos is miscommunicating the position here immediately after a drop in bandwidth. The buffer within Roon is also hanging.
Fortunately, yes. This is available in logging and was our mechanism for determining the above information.
This is absolutely worth trying as it would reduce a large number of variables. SonosNET will forward traffic between these devices and there’s a possibility of loops, reflection, etc.
We’ll follow up shortly with what we learn with development. Thank you for your patience.
We’ve enabled a setting for your account that should provide more precise diagnostic logging with Sonos devices. Please restart your Roon Server machine two times to make sure this setting has taken effect, and attempt to play to your affected Sonos devices at your convenience. We’ll see any relevant events in logs. Thank you!
We’ve identified some potential inroads from logs and are syncing with development. Please allow us another few days and we’ll have next steps. Thank you!
We’ve continued to review diagnostics and logs with development and have a few follow-up questions and steps:
Are you able to reproduce this issue at will? If you’re in a position to try, please attempt to switch your Roon Server to your Macbook to see if the problem also occurs when connecting to that machine - we want to rule out the VM as a variable here.
When you next encounter a skipped track, incorrect track, or incorrect position timer, rather than pausing/playing the stream, remove and then re-enable the affected Sonos Zone within Roon. Note this will not be as effective or efficient with grouped Sonos Zones, as disabling Zones requires recreating the group.
We have identified a mechanism for a potential mismatch in the position timer handoff between Sonos and Roon and created a ticket to address the issue with development. Please allow us a few weeks to track the ticket and merge the fix. In the meantime, we’ll continue to assess logs and keep this thread open. This issue is under active investigation.
Having Sonos Five as only speaker had no effect → issue remained.
Disabling SonosNet (as far as I can be sure) had no effect → issue remained.
Detailed post to follow on SonosNet.
Feedback on your points:
Currently I have installed another Roon Server on a Windows PC (macbook is used for work w/ vpn connections - didn’t want to throw that into the mix).
I suppose it doesn’t matter if the goal is to eliminate the VM as a variable.
Installed RoonServer on a Windows 10 PC.
Problem remains.
When encountering the skipping; I disabled the Sonos Five in Settings/Audio.
This stopped the audio playing.
Next, I re-enabled it.
The queue was remembered and I resumed playback from where it left off.s
I let the remainder of the queue play to the end, and then started playing a new album.
The timeline skipping was again there.