Spotify went crazy!! - Printable Version

Spotify went crazy!! - Printable Version

+- Moode Forum (https://moodeaudio.org/forum)
+-- Forum: moOde audio player (https://moodeaudio.org/forum/forumdisplay.php?fid=3)
+--- Forum: Support (https://moodeaudio.org/forum/forumdisplay.php?fid=7)
+--- Thread: Spotify went crazy!! (/showthread.php?tid=4973)

Pages: 1 2 3 4 5

Spotify went crazy!! - starbender - 07-15-2022

I'm using fresh 64bit 8.1.2 image. It was working fine yesterday. But now it acts weird. I can connect to moode spotify renderer.
When I try to play something spotify endlessly jumps to next song without playing anything.

Sometimes it shows it playing fine but there is no sound at all.

Any suggestion?

Thanks!

RE: Spotify went crazy!! - Paccidat - 07-16-2022

Yeah same issue here, and an angry wife as result ;-)

I experience exactly the same behavior. Totally impossible to playback spotify streams.

Any others with this issue? Is it moode related or librespot or spotify changing something ?

It may have something to do with https://github.com/librespot-org/librespot/issues/972

IT seems this so called channel error is temporary, originating from spotify and dependent on you location. I am in western europe (NL)

RE: Spotify went crazy!! - Paccidat - 07-16-2022

I manager to fix it by doing the following (as described in the link above):

login through ssh

type ' sudo nano /etc/hosts ' (without the ')

Add '104.199.65.124 ap-gew4.spotify.com' to the end of that file

press ctrl-x
press y en y again .

Then retry. It should work.

RE: Spotify went crazy!! - Sander - 07-17-2022

Thank you so much for posting this. I had the same issue since 8.1.2. Already reset a bunch of stuff to no avail. This fixed it!

@Tim Curtis in case you haven't seen this issue yet...

RE: Spotify went crazy!! - Tim Curtis - 07-17-2022

Interesting. Maybe @roderickvd from the librespot crew can provide some guidance.

RE: Spotify went crazy!! - starbender - 07-19-2022

(07-16-2022, 06:34 PM)Paccidat Wrote: Add '104.199.65.124 ap-gew4.spotify.com' to the end of that file

This does not work for me.
With this line in hosts file, client connects to moode and disconnects in seconds.

I also tried picoreplayer&lms with spotify plugin.
Exactly the same behaviour.

RE: Spotify went crazy!! - Tim Curtis - 07-20-2022

Try posting a new issue or adding to an existing issue in the librespot Git repo so the devs can get a sense of what might be happening. https://github.com/librespot-org/librespot/issues

RE: Spotify went crazy!! - jonners - 07-21-2022

I've been getting a similar problem. Spotify begins playing but stops after a few seconds and Moode then becomes unreachable and has to be powered down and booted up again.
Following a suggestion posted in the Github link above I added the following to /etc/hosts

Code:
0.0.0.0        apresolve.spotify.com

Spotify is now playing fine.
EDIT: Oops, posted too soon! Spotify played for about 15 minutes but has now disconnected again.

RE: Spotify went crazy!! - Tim Curtis - 07-21-2022

Nice :-)

If you have a GitHub account you may want to add your data point to the Spotify issue.

RE: Spotify went crazy!! - TheOldPresbyope - 07-22-2022

As I read the librespot github repo issues log, there seem to be at least two different problems cropping up.

One is the inability sometimes to reach certain Spotify "AP" servers by their FQDN. This error prevents connection. It seems not to happen to all the users having problems but this is the reason some believe all one has to do is add some lines to the /etc/hosts file.

The other problem has to do with a recurring issue with certain Spotify servers throwing "channel" errors. This error occurs after connection has been made and prevents playing the selected track.

It would seem these errors are affecting mostly European users. I have never seen them, which has made it impossible for me to gather my own diagnostic data.

However, anyone with a working knowledge of the Linux command line can gather their own diagnostic data.

First:

Using a host on the same LAN as your moOde player, visit the site https://apresolve.spotify.com in your favorite web browser to get the list of Spotify AP servers being offered in your region.

Here's the response I get using a Chromium browser on my Linux laptop connected to the Internet via an ISP located in Maryland/USA. (I prefer the way Firefox formats this JSON list but I couldn't easily copy the formatted output.)

Code:
{"ap_list":["ap-guc3.spotify.com:4070","ap-guc3.spotify.com:443","ap-guc3.spotify.com:80","ap-gew1.spotify.com:4070","ap-guc3.spotify.com:443","ap-gae2.spotify.com:80"]}

All of these AP servers are resolvable and accessible from my location but apparently librespot will use only the first instance in the list.

Then:

Disconnect any Spotify app which may be connected to the moOde player
Turn off the Spotify renderer in the moOde player's Audio Config panel.
Start the following on the moOde player's command line
sudo librespot --name SpotifyTest -v > SpotifyTest.txt 2>&1
Using your favorite Spotify App, connect to the resulting "SpotifyTest" device
In the Spotify App, select and play a track or at least a portion of it
Disconnect the Spotify App from the "SpotifyTest" device
Kill the librespot process you started on the moOde player's command line (Hint: use ctrl-C).
Still on the command line, review the content of the file SpotifyTest.txt left in the current directory.

Candidly, I don't know if and which various keys in the output are "secrets" but the output is voluminous so I'm not posting all of it. Here's the beginning of the output collected on one of my moOde players

Code:
[2022-07-22T02:13:33Z INFO  librespot] librespot 0.4.1 88e64bd (Built on 2022-07-07, Build ID: KpGv9iLt, Profile: release)

[2022-07-22T02:13:33Z TRACE librespot] Command line argument(s):

[2022-07-22T02:13:33Z TRACE librespot]         --name "SpotifyTest"

[2022-07-22T02:13:33Z TRACE librespot]         -v

[2022-07-22T02:13:33Z DEBUG librespot_discovery::server] Zeroconf server listening on 0.0.0.0:34759

[2022-07-22T02:13:49Z DEBUG librespot_discovery::server] POST "/" {}

[2022-07-22T02:13:49Z INFO  librespot_core::session] Connecting to AP "ap-guc3.spotify.com:4070"

[2022-07-22T02:13:50Z INFO  librespot_core::session] Authenticated as "<<user id redacted>>" !

...

As can be seen, librespot connected to the first AP server in the list I presented above. This is where the first known error would become apparent.

Later in the output, after I had told my Spotify App to play a specific track, there appears the snippet

Code:
[2022-07-22T02:13:50Z INFO  librespot_playback::player] Loading <24 Preludes, Op. 28: No. 15 in D-Flat Major "Raindrop"> with Spotify URI <spotify:tr

ack:<<track ID redacted>>>

[2022-07-22T02:13:50Z DEBUG librespot_audio::fetch] Downloading file <<file id redacted>>

[2022-07-22T02:13:50Z DEBUG librespot::component] new ChannelManager

...

and, of course, this is where the second known error ("Channel error...") would become apparent. Any other types of errors you observe should be reported to the librespot github repo issues log.

Note that the two known problems are due to Spotify's services. See the librespot github repo issues log to get a feel for how the librespot devs feel about them.

Regards,
Kent