[SOLVED] Spotify connect stopped playing audio

[the_bertrum]

With no changes to anything, now everything works again as it should. Spotify did something ...

Yup, working for me again too with my original (non-google) dns settings.  Folks in Spotify Forums are also saying all is well.

Gotta love dev-ops.  Screw up more stuff, faster.

[TheOldPresbyope]

To paraphrase badly, those who live by the cloud die by the cloud.

Regards,
Kent

[Tim Curtis]

Version 0.5.0-dev also appears to work perfectly however it uses the event string "session_connected" instead of "started" as is used by v0.4.2 to indicate a session between client and server has been started.

This means that the current event script /var/local/www/commandw/spotevent.sh won't be able to detect that 050 has started the session and thus ALSA volume won't be set to 0dB and no renderer overlay will appear.

I'll update the script so it handles both event strings. That way when the librespot team publishes the 050 release and we bump to that release in moode it will be supported by the event script.

[the_bertrum]

To paraphrase badly, those who live by the cloud die by the cloud.

Regards,
Kent

I've a load of customers who have "heard of dev ops and we want to use it so we can have features faster".  Now I can ward them off by the single word "CrowdStrike".

[Falco]

With no changes to anything, now everything works again as it should. Spotify did something ...

Yup, working for me again too with my original (non-google) dns settings.  Folks in Spotify Forums are also saying all is well.

Gotta love dev-ops.  Screw up more stuff, faster.

Very weird, just tested here as well, all is good again!

[the_bertrum]

Version 0.5.0-dev also appears to work perfectly however it uses the event string "session_connected" instead of "started" as is used by v0.4.2 to indicate a session between client and server has been started.

This means that the current event script /var/local/www/commandw/spotevent.sh won't be able to detect that 050 has started the session and thus ALSA volume won't be set to 0dB and no renderer overlay will appear.

I'll update the script so it handles both event strings. That way when the librespot team publishes the 050 release and we bump to that release in moode it will be supported by the event script.

Well at least something useful resulted from all this

[Tim Curtis]

Version 0.5.0-dev also appears to work perfectly however it uses the event string "session_connected" instead of "started" as is used by v0.4.2 to indicate a session between client and server has been started.

This means that the current event script /var/local/www/commandw/spotevent.sh won't be able to detect that 050 has started the session and thus ALSA volume won't be set to 0dB and no renderer overlay will appear.

I'll update the script so it handles both event strings. That way when the librespot team publishes the 050 release and we bump to that release in moode it will be supported by the event script.

Well at least something useful resulted from all this

For sure. 

There also appears to be a bug in version 5 whereby the setting --initial-volume 0 results in super loud volume (prolly 100%) even though the slider on the client app is at 0. Once the slider is bumped volume is set correctly.

Warning for anyone thats testing or using version 5 dev. If in moode Spotify Settings the initial volume is set to 0 be very careful and make sure to set downstream volume to a low level.

I have to do more testing but if my results are repeatable I'll file a bug report with the librespot project.

ETA: Here's the bug report
https://github.com/librespot-org/librespot/issues/1325

[Tim Curtis]

I marked "Spotify not working" as SOLVED.

For version 5 dev testing I'll start a new thread when there is some new info in the Git issue.

[ovizii]

Thanks everyone for chiming in and confirming it wasn't me messing up somehow ;-)
Thanks for marking the thread solved, it started working again for me too but I was travelling for a few days so I didn't notice all the responses to my thread.