Spotify went crazy!!

[Tim Curtis]

Reboot and post the moOde startup log and I'll have a look.

What audio device ar you using?

Code:

moodeutl -l

Keep in mind that Spotify volume is controlled entirely at the client via the Spotify app.

[oasis1701]

Reboot and post the moOde startup log and I'll have a look.

What audio device ar you using?

Code:

moodeutl -l

Keep in mind that Spotify volume is controlled entirely at the client via the Spotify app.

Hi there, thanks for your help
Here's the log:
https://pastebin.pl/view/36036c13
-I'm connecting moode with hdmi to my sony tv
-spotify clients see moode as a speaker, but today they just won't connect to it no matter what i tried.
-spotify clients windows and phone can play properly from the same network.
-yesterday moode spotify connect kept buffering and disconnecting after a minute, today  it just won't connect at all.
-I installed a fresh installation of moode this morning just in case and applied the workarounds to /etc/hosts

[oasis1701]

Sorry for double posting
I have removed 0.0.0.0        apresolve.spotify.com from /etc/hosts and added 104.199.65.124 ap-gew4.spotify.com
then i cleared the spotify credentials and restarted the renderer

Now spotify windows client can connect to moode and moode is playing my song without buffering, however; after a minute, my spotify on windows disconnects and pauses the song, while moode keeps playing my song and at the end won't be able to continue my playlist because spotify is no longer connected.
Very confusing stuff

[oasis1701]

Sorry for double posting
I have removed 0.0.0.0        apresolve.spotify.com from /etc/hosts and added 104.199.65.124 ap-gew4.spotify.com
then i cleared the spotify credentials and restarted the renderer

Now spotify windows client  can connect to moode and moode is playing my song without  buffering, however; after a minute, my spotify on windows disconnects and pauses the song, while moode keeps playing my song and at the end won't be able to continue my playlist because spotify is no longer connected.
Very confusing stuff

Tried all sorts of things by googling and searching the forum, nothing works.
Still spotify connect disconnects, moode plays the rest of the song and then stops.

IS it possible that this is caused by me running moode audio from a usb stick and not an sd card?
I'm running it on a raspberry pi 3b+ and i am using a usb device to run the OS on.

[Tim Curtis]

Debugging can be tedious but you could try the procedure below to begin finding out what error messages are being dumped by librespot.

1. Turn on debug logging in System Config
2. Restart Spotify renderer in Audio Config

Post the moOde startup log and I'll have a look at the librespot launch string.

Code:

moodeutl -l

[oasis1701]

Debugging can be tedious but you could try the procedure below to begin finding out what error messages are being dumped by librespot.

1. Turn on debug logging in System Config
2. Restart Spotify renderer in Audio Config

Post the moOde startup log and I'll have a look at the librespot launch string.

Code:

moodeutl -l

Here is the log with debugging on
https://pastebin.com/3DD4cZGT

[Tim Curtis]

Here is the launch string from the log

Code:

sudo librespot --name "Moode Spotify" --bitrate 160 --format S16 --mixer softvol --initial-volume 0 --volume-ctrl log --volume-range 60 --cache /var/local/www/spotify_cache --disable-audio-cache --backend alsa --device "_audioout" --onevent /var/local/www/commandw/spotevent.sh

1. Turn off Debug log in System Config
2. Turn off Spotify renderer in Audio Config
3. Paste the launch string at the SSH command prompt 

Look for errors in the output

[oasis1701]

Here is the launch string

Code:

sudo librespot --name "Moode Spotify" --bitrate 160 --format S16 --mixer softvol --initial-volume 0 --volume-ctrl log --volume-range 60 --cache /var/local/www/spotify_cache --disable-audio-cache --backend alsa --device "_audioout" --onevent /var/local/www/commandw/spotevent.sh

1. Turn off Debug log in System Config
2. Turn off Spotify renderer in Audio Config
3. Paste the launch string at the SSH command prompt 

Look for errors in the output

uh oh, i think i found the error
[2022-08-30T13:19:22Z WARN  librespot_core::cache] Cannot save credentials to cache: Permission denied (os error 13)

edit: Here's the error it showed me when moode disconnected from my spotify, and my song stopped after 2 minutes or so
[2022-08-30T13:27:19Z INFO  librespot_playback::player] <kaos2 - instrumental> (241400 ms) loaded
[2022-08-30T13:27:19Z INFO  librespot::player_event_handler] Running ["/var/local/www/commandw/spotevent.sh"] with environment variables {"PLAYER_EVENT": "playing", "POSITION_MS": "0", "TRACK_ID": "3uqNvGBK9HgfIZO8R1kchX", "DURATION_MS": "241400"}
[2022-08-30T13:30:50Z ERROR librespot_playback::player] Unable to load audio item: MercuryError
[2022-08-30T13:30:50Z ERROR librespot_core:ession] Connection reset by peer (os error 104)
[2022-08-30T13:30:50Z ERROR librespot_connect:pirc] subscription terminated
[2022-08-30T13:30:50Z WARN  librespot] Spirc shut down unexpectedly
[2022-08-30T13:30:51Z INFO  librespot_core:ession] Connecting to AP "ap-gew4.spotify.com:4070"
[2022-08-30T13:30:51Z INFO  librespot_core:ession] Authenticated as "metalelite" !
[2022-08-30T13:30:51Z INFO  librespot_playback::mixer:oftmixer] Mixing with softvol and volume control: Log(60.0)
[2022-08-30T13:30:51Z INFO  librespot_playback::convert] Converting with ditherer: tpdf
[2022-08-30T13:30:51Z INFO  librespot_playback::audio_backend::alsa] Using AlsaSink with format: S16
[2022-08-30T13:30:51Z INFO  librespot::player_event_handler] Running ["/var/local/www/commandw/spotevent.sh"] with environment variables {"VOLUME": "0", "PLAYER_EVENT": "volume_set"}

[Tim Curtis]

Oops I forgot that it needs to run as root. I updated the launch string so "sudo librespot ...". This should eliminate the "permission denied" error.

I'm not sure how to interpret the other errors but they seem similar to errors reported in this issue
https://github.com/librespot-org/librespot/issues/972

[oasis1701]

Oops I forgot that it needs to run as root. I updated the launch string so "sudo librespot ...". This should eliminate the "permission denied" error.

I'm not sure how to interpret the other errors but they seem similar to errors reported in this issue
https://github.com/librespot-org/librespot/issues/972

oops. a lot of technical things there that i don't understand.
Is it possible that an updated librespot or the next version of moode fixes this? or this is an ongoing issue.