Max number of tracks in a Spotify playlist

Maybe this thread contains an answer for you: 

Thank you for your response @106rallye . I had seen that but it talks about size of playlist not number of tracks:

Upon further checking on this, Sonos has playlist limitations.

• General 10k track limit (total for all playlists)
• Spotify: 6.75k (+/- depending on metadata)

Based on that information, I broke up all of my original Spotify playlists into 4k or lower track segments but I still get the “Unable to add songs to Queue” error message. That thread is a year old and locked. So I opened this new one.

Which includes time outs due to interference between your speakers and your speakers and the router. 

Thanks @ratty and @Airgetlam,

Understood, and I also realize there are multiple factors that could contribute to that kind of latency:

WiFi strength: Could be part of the issue on my iPhone, but my PC where I am running the Sonos desktop app is connected via ethernet cable.

Issues with my router and/or the cable company’s modem: I just went to speedtest.net on that same PC and I am getting:

• Ping: 3 ms
• Down: 304.98 Mbps
• Up: 344.44 Mbps
• That seems pretty robust in my opinion

Latency issues caused by Spotify’s response time:

I don’t have any good way to measure that but:

• The Spotify desktop app on the same computer can build a queue based on one of the playlists with 4k songs in under 2 seconds even after deleting the Spotify client cache using the instructions at https://community.spotify.com/t5/Desktop-Windows/cache/td-p/4722569.
• I realize that may not be an apples to apples comparison though because the Spotify app seems use a method that builds the queue in a rolling fashion; 100 tracks at a time.
• Based on some experimentation, the Sonos desktop app seems to build the entire queue all at once.
• Based on the same experimentation, the Sonos app threw the “Unable to add songs to Queue” error at 2,045 songs but was able to load at 2,044 songs.
• Based on other things I have read in this community forum, I suspect that the exact number varies based on amount of metadata.
• Interestingly, the Sonos app threw the “Unable to add songs to Queue” error in less than 10 seconds after I right clicked on the playlist and choose “Add to queue”.
• I was also able to play that same playlist from the Sonos app on my iPhone which probably rules out WiFi bandwidth issues.
• However, I believe I also read somewhere in this forum that playlists get cached on the speaker itself. So, maybe that was why I was able to start the playlist from my phone after I had already run it from my desktop app. But maybe not.

I guess my bottom-line questions now are:

1. In general, should I expect to only be able to use Spotify playlists that are around 2k in the Sonos desktop app?
2. Should I expect similar thresholds in the Sonos mobile app?

Well, I can say that 2) shouldn’t make any difference. The controller is merely a remote that is talking to the app that’s running on your speakers, so whether it’s a PC/iOS/Android/Mac controller shouldn’t make a difference. 

What can make a difference is which device/speaker is running the operation. In general, you want it to be a wired device, and newer (more memory, better CPU) than an older device. Wired reduces interference possibilities, although doesn’t obviate duplicate IP bouncing, but many people incuding myself, have no issues with larger playlists on wireless connections. I happen to use SonosNet, but the BOOST isn’t capable (I think!) of running this kind of operation, it requires a “player”. 

But then again I’m not sure how to force it from one processing device/speaker to the next. I suspect @ratty knows that, though. 

I’m unsure of the question. If it’s about the location of the GC (group coordinator) node it’s in the first room of the group. Juggle the group to suit.

If the first room is a home theatre setup the GC is the master player; if the first room is a pair then the GC is usually the left unit, but it depends how the pair was assembled (check for the top one in Settings/System/{pair_room}/Products).

The former was the answer I was unsure of.

Under the assumption that it’s the group coordinator that does the processing of the library files from the service, which makes sense.

Thank you most kindly. 

Yes the GC owns the queue.

When I go to Settings/System the first device listed is my Sonos One named “Basement”. “Basement” is connected to my router via an ethernet cable. It was the first device that I set up (at least a year ago). If I am following the discussion correctly, this would be the GC, correct?

The devices in my system are:

• The Sonos One named “Basement” described above
• 2 additional Sonos One (i.e. 3 total)
• 1 Move
• 1 Play: 5

None of these speakers are configured as a pair nor is my system set up as a home theater.