Crossfade skips every other song (20 secs) when using Spotify

Forum|Forum|3 years ago
April 20, 2023
32 replies
3515 views

Crossfade feature on Sonos when streaming Spotify works on every other song. It will play one song, crossfade correctly, then play the next song for 20 seconds and skip to the next song. That song will play in its entirety and crossfade correctly then skip the next song after about 20 seconds. I see this topic has been posted many times before with no resolution. Any help???

I use Sonos quite a bit and this feature helps the mood for events. I will need to switch to other services if this persist. Thanks!

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

Best answer by Corry P

Hi @jsimmy et al

We believe this issue to now be resolved with the most recent update (15.7). Please ensure your Sonos system is up to date.

If you still experience this issue, however, I’d encourage you get in touch with our technical support team to report as much. Thank you.

Show previous replies

J

jsimmyAuthor

Contributor I

@corryp is this a Spotify issue or a Sonos issue? And do you have any updates?

Cheers

U

User232842

Lyricist I

@corryp Do you have an update on this issue for us? It’s very annoying actual.

Corry P

Sonos Staff

Hi @User232842 & @jsimmy

No updates, I’m afraid - and there won’t be any until a fix is put in place. There never is - if we say something will be fixed by X date, and then fail to fix it by that date, it just causes more consternation.

"Common sense is the collection of prejudices acquired by age eighteen." - Albert Einstein

C

cwareham

Lyricist I

soooo…. better to bury ones head in the sand and pretend the problem doesnt exist?

I have this too, its excrutiatingly frustrating for a music system not to be able to play music in a very simple format - come on sonos, sort yourselves out, take some accountability, give your customers a date and get the problem fixed.

Airgetlam

I’m not quite sure how you reached that conclusion from @Corry P ‘s post. You may want to re-read it.

Bruce

U

Urielb92

Lyricist I

I recently bought my first Sonos product - Sonos Move - where my intentions were to create a while ecosystem of Sonos products after a lot of research.

The multiple software issues, where the crossfade skip over Spotify issue is the most prominent and serious one, as well as the route of actions taken and communication on your end over this issue is really disappointing. I would definitely consider before spending more money and vendor locking on Sonos products.

I’m a software engineer myself, I know for a fact you can and should provide better service for your customers.

Airgetlam

As a software engineer, how do you propose that Sonos engineers get access to making changes on servers owned and managed by Spotify? Since it is working on every other streaming companies service, it seem obvious that the issue is not with the API that Sonos provides to everyone, but some sort of implementation or configuration that Spotify needs to do.

I’ve never allowed external engineers code access to the servers in my company. Perhaps your experience is different.

Bruce

U

Urielb92

Lyricist I

It might be the case and probably true, and yet - there should be high interest on both sides to fix this issue, the fact that Spotify is accessible through Sonos points to some level of partnership - vague responses on Sonos end without any accountability over the end user experience is not acceptable for several months over such core functionality, that acts as a killer feature of this system is not accessible. Have them buffer and imlement crossfade on their servers if needed, just provide some sort of solution, or alternatively some ETA over permanent fix. And saying that providing ETA is not possible as it might be delayed is not a good answer.

I’m not assuming to know what’s the issue nor the solution, softwares will always have bugs, it’s how they manage or actively push towards resolution it and communicate about it, even if the root cause is in 3rd parties (and BTW, the fact that it works for all the other services other than Spotify doesn’t necessarily mean that the issue is on their end, who said that each integration is the same and exposes the same API?)