Server Version#: 1.24.0.4930
Player Version#: Plexamp 3.5.0, Plex Web 4.63.0, Plex for Windows 1.33.0.2444-a220eae4
After replacing a few Chromecast Audio with Sonos devices (1 x Sonos Port + 2 x Sonos Connect on Sonos S1) in order to have gapless playback through the (AV) receivers around the house I have experienced the following undesirable behaviour from the Plex queue:
-
After pausing playback for a time, resuming playback causes the queue to restart from the first track in the queue rather than the current point in the queue.
-
After moving playback to “This Device” on Plexamp for Android (3.5.0), leaving the house and continuing playback of the queue on device and/or in the car via Bluetooth, upon returning home and moving playback back to the Sonos devices often causes the queue to restart either from the first track in the queue or from where the queue was up to when playback was moved to Plexamp for Android.
-
After pausing playback, playing something other than Plex on the Sonos devices (such as a radio station via TuneIn), stoppping playback on the something other, resuming playback from Plexamp (or Plex for Web, Plex for Windows) causes the something other to resume rather than the Plex queue resume.
1 and 2 seem to exhibit dependant on duration of the pause - 30 minutes plus at a guess - and seemingly more often after the queue has progressed into implicit territory.
I am more than happy to provide logs as required, but expect this will be a lengthy process. At least the turntable will be happy, having something to do during all the pausing of Plex.
Note: The undesirable behaviour is not a deal breaker as gapless playback trumps the queue issues and the ability to have multiple controller apps connected the receiver app is very useful.
Aside: It would be great if Plex for Sonos would include the calculated replaygain in the Sonos API payload as Sonos only repects the track gain tag. I’m currently working around this with a modified beets replaygain plugin to write album gain to the the track gain tag. This likely warrants a separate post and a support request to Sonos.
