Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Problem: Spotify Disconnect Issue in 9.1.2
#1
I just updated from 9.1.0 to 9.1.2 and am no longer able to play Spotify: I can connect to my RPi3 (seemingly much quicker compared with previous releases), but then the RPi3 would immediately disconnect the moment I hit the play button.
Reply
#2
Reboot and then post the contents of the startup log.

The log can be viewed via the SSH command moodeutl -l or downloaded via the Logs section in System Config, or via Menu, System info from any of the Config screens. The startup log will be at the end of System info output.
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#3
(10-06-2024, 10:05 PM)lyramax Wrote: I just updated from 9.1.0 to 9.1.2 and am no longer able to play Spotify: I can connect to my RPi3 (seemingly much quicker compared with previous releases), but then the RPi3 would immediately disconnect the moment I hit the play button.

I can repro this on a moOde player when I haven't selected a legitimate audio output device first.  The moode.log file shows


Code:
20241006 185804 watchdog: Spotify Connect crashed and was restarted


In this case, the selected audio output device was HDMI but no audio device is connected to the HDMI port. Had I tried to play a local file or a radio station, I'd get an Alert popup saying the same thing.


Solution (in my case, at least) - select a working audo output device before you connect to the Spotify renderer.

Regards,
Kent
Reply
#4
(10-06-2024, 11:09 PM)TheOldPresbyope Wrote: I can repro this on a moOde player when I haven't selected a legitimate audio output device first.
...
In this case, the selected audio output device was HDMI but no audio device is connected to the HDMI port. Had I tried to play a local file or a radio station, I'd get an Alert popup saying the same thing.
...
Solution (in my case, at least) - select a working audio output device before you connect to the Spotify renderer.

Regards,
Kent
Thank you, I also just found having a non-existent audio output device was the culprit.

I had not thought of checking the audio player selection since I had been under the assumption that my DAC which was the sole active device when moOde booted would be automatically detected and selected.
Reply


Forum Jump: