However, I do use some quite large queues (currently playing over 3,000 songs) and haven’t found large queue sizes to cause a problem. What happens when you do the same thing to just one device? (i.e. not part of a group)
Formats are mainly a mix of WMA and MP3
Today’s experiment
- done on PC to eliminate phone from the equation
- again group speakers based on strength of wifi connection.
- Clear the queue and SHUFFLE over the 2,000+ songs on the PC -- that worked w/o error
- Now DON’T SKIP just let it play for like over an hour -- again worked without any errors at all
So as I’ve noted before, the act of skipping songs seems to initiate the problem, i suspect because SONOS starts buffering based on initial queue construction, then when you skip (maybe several songs) you get ahead of what it has buffered and it scrambles to catch up.
Just tried the same thing with a queue of 3.2k tracks, then skipped multiple tracks many times - worked without a hitch. Then grouped it with the other two devices and it continued to work without a hitch. It therefore seems unlikely to be a Sonos bug.
If you’re sure that nothing is spinning down or otherwise becoming unavailable, then network issues seem to be the most likely candidate. And before you say that everything else works OK, then yes - it does - but Sonos has greater requirements of the network than most systems.
