+- 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)
RE: Spotify went crazy!! - TheOldPresbyope - 08-30-2022
@oasis1701
Sorry I'm late to the game but I've now repro'd your issue running 64-bit moOde 8.1.2 on an RPi3A. I'm located in Maryland/USA using Comcast ISP services and librespot is connecting with a different server: ap-guc3.spotify.com:4070. I'm using the Spotify app on my iPad. Everything worked fine for enough longer than 2 minutes that I thought I was in the clear but then saw the same error
Code:
[2022-08-30T15:09:24Z ERROR librespot_playback::player] Unable to load audio item: MercuryError
[2022-08-30T15:09:24Z ERROR librespot_core::session] Connection reset by peer (os error 104)
[2022-08-30T15:09:24Z ERROR librespot_connect::spirc] subscription terminated
[2022-08-30T15:09:24Z WARN librespot] Spirc shut down unexpectedly
[2022-08-30T15:09:24Z INFO librespot_core::session] Connecting to AP "ap-guc3.spotify.com:4070"moOde 8.1.2 incorporates librespot 0.4.1.
The test team is now wringing bugs out of a pre-release version of moOde 8.2.0 which incorporates librespot 0.4.2. As you've seen in other posts, the librespot maintainer has said this is the last, most stable version of the 0.4 series.
I've just spun up a copy of moOde 8.2.0 pre1 on the same RPi3A. Things started off on the right foot
Code:
pi@m820pre1:~ $ sudo librespot --name "Moode Spotify" --bitrate 160 --format S16 --mixer softvol --initial-volume 50 --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
[2022-08-30T15:18:25Z INFO librespot] librespot 0.4.2 22f8aed (Built on 2022-08-18, Build ID: LQ4hikXT, Profile: release)
[2022-08-30T15:18:25Z WARN librespot_core::apresolve] Ignoring blacklisted access point ap-gew4.spotify.com:443
[2022-08-30T15:18:25Z INFO librespot_core::session] Connecting to AP "ap-guc3.spotify.com:4070"
[2022-08-30T15:18:25Z INFO librespot_core::session] Authenticated as "<--elided-->" !
[2022-08-30T15:18:25Z INFO librespot_playback::mixer::softmixer] Mixing with softvol and volume control: Log(60.0)
[2022-08-30T15:18:25Z INFO librespot_playback::convert] Converting with ditherer: tpdf
[2022-08-30T15:18:25Z INFO librespot_playback::audio_backend::alsa] Using AlsaSink with format: S16
[2022-08-30T15:18:25Z INFO librespot::player_event_handler] Running ["/var/local/www/commandw/spotevent.sh"] with environment variables {"VOLUME": "32767", "PLAYER_EVENT": "volume_set"}
[2022-08-30T15:18:25Z INFO librespot_core::session] Country: "US"
[2022-08-30T15:19:08Z INFO librespot::player_event_handler] Running ["/var/local/www/commandw/spotevent.sh"] with environment variables {"PLAYER_EVENT": "started", "TRACK_ID": "05YcMrnmypzN34kfDy01Vc"}
...A long track played to the end, nearly 10 minutes. Then I tried to start playing a new set of tracks and kerplooey
Code:
[2022-08-30T15:29:01Z INFO librespot_playback::player] Loading <Changing the Way> with Spotify URI <spotify:track:5aUAsHcy5yKC0j6TIKOJyL>
[2022-08-30T15:29:01Z INFO librespot_playback::player] <Changing the Way> (508466 ms) loaded
[2022-08-30T15:29:01Z INFO librespot::player_event_handler] Running ["/var/local/www/commandw/spotevent.sh"] with environment variables {"TRACK_ID": "5aUAsHcy5yKC0j6TIKOJyL", "PLAYER_EVENT": "preloading"}
[2022-08-30T15:29:31Z INFO librespot::player_event_handler] Running ["/var/local/www/commandw/spotevent.sh"] with environment variables {"OLD_TRACK_ID": "1FMYNBIfIA8p5IxPU2wiBu", "TRACK_ID": "5aUAsHcy5yKC0j6TIKOJyL", "PLAYER_EVENT": "changed"}
[2022-08-30T15:29:31Z INFO librespot::player_event_handler] Running ["/var/local/www/commandw/spotevent.sh"] with environment variables {"DURATION_MS": "508466", "TRACK_ID": "5aUAsHcy5yKC0j6TIKOJyL", "PLAYER_EVENT": "playing", "POSITION_MS": "0"}
[2022-08-30T15:37:18Z ERROR librespot_core::session] Connection reset by peer (os error 104)
[2022-08-30T15:37:18Z WARN librespot_audio::fetch::receive] Error from channel for data receiver for range 9195520 (+16384).
[2022-08-30T15:37:18Z WARN librespot_audio::fetch::receive] Error from channel for data receiver for range 9244672 (+16384).
[2022-08-30T15:37:18Z WARN librespot_audio::fetch::receive] Error from channel for data receiver for range 9211904 (+16384).
[2022-08-30T15:37:18Z WARN librespot_audio::fetch::receive] Error from channel for data receiver for range 9228288 (+16384).
[2022-08-30T15:37:18Z ERROR librespot_connect::spirc] subscription terminated
[2022-08-30T15:37:18Z WARN librespot] Spirc shut down unexpectedly
[2022-08-30T15:37:19Z WARN librespot_core::apresolve] Ignoring blacklisted access point ap-gew4.spotify.com:80
[2022-08-30T15:37:19Z INFO librespot_core::session] Connecting to AP "ap-guc3.spotify.com:4070"
[2022-08-30T15:37:19Z INFO librespot_core::session] Authenticated as "uj2jxg6mwq5qds68p1xg9yksd" !
[2022-08-30T15:37:19Z INFO librespot_playback::mixer::softmixer] Mixing with softvol and volume control: Log(60.0)
[2022-08-30T15:37:19Z INFO librespot_playback::convert] Converting with ditherer: tpdf
[2022-08-30T15:37:19Z INFO librespot_playback::audio_backend::alsa] Using AlsaSink with format: S16
[2022-08-30T15:37:19Z INFO librespot::player_event_handler] Running ["/var/local/www/commandw/spotevent.sh"] with environment variables {"PLAYER_EVENT": "volume_set", "VOLUME": "32767"}
[2022-08-30T15:37:19Z INFO librespot_core::session] Country: "US"The Spotify app has disconnected from moOde and reverted to playing via the iPad speaker.
Effectively the same behavior showed up in the librespot issues log (Issue #1035) 29 days ago, to which the maintainer commented "Typical case of temporary channel errors. If you search this repo you will find many cases like it." He asked the issue poster for verbose debugging output which was not provided so that particular issue was closed. I'll have to gen up some of my own and post it.
Regards,
Kent
RE: Spotify went crazy!! - oasis1701 - 08-30-2022
Hi Kent
IF you do end up making an issue, do paste the link here so I could add my logs to it as well as i'm experiencing the same exact issue.
You're correct that if I play a 10 minute song, everything works well for2 minutes, then moode keeps playing the song, while my spotify app shows itself as paused and not connected to anything.
The song then plays for another 7 minutes or so then stops.
Is it possible to try out different Spotify servers?
RE: Spotify went crazy!! - Tim Curtis - 08-30-2022
You can try the new 0.4.2 version from our repo
Code:
sudo apt -y install librespotRE: Spotify went crazy!! - TheOldPresbyope - 09-01-2022
@oasis1701
Sorry, I don't think I'm going to go any farther with this. It's tedious to catch librespot in the act and AFAICT all the diagnostic info I've been able to gather so far merely replicates what's already been posted many times in the librespot issues log so I have nothing new to add. As well, I'm not knowledgeable in either the Spotify Connect protocol or the Rust programming language in which librespot is implemented so effectively I'm just one of the blind men feeling the elephant.
For what it's worth, the behavior we're seeing has been reported for other players which incorporate librespot besides moOde.
Regards,
Kent
RE: Spotify went crazy!! - peter - 09-03-2022
(08-30-2022, 06:21 PM)Tim Curtis Wrote: You can try the new 0.4.2 version from our repo
Code:sudo apt -y install librespot
Yesterday I updated to the new librespot version and everything seems to work fine now again (as far as I've tested)
RE: Spotify went crazy!! - roderickvd - 09-04-2022
99.9% of cases the channel errors are on Spotify's end, librespot can do nothing about it. Usually after a day or two the errors go away automatically as it seems that Spotify fixes something on their end.
Again the future 0.5.0 version should be safe from this, as it downloads audio files over another API.
RE: Spotify went crazy!! - Falco - 09-13-2022
(09-03-2022, 04:02 PM)peter Wrote:(08-30-2022, 06:21 PM)Tim Curtis Wrote: You can try the new 0.4.2 version from our repo
Code:sudo apt -y install librespot
Yesterday I updated to the new librespot version and everything seems to work fine now again (as far as I've tested)
Updated librespot just now. At first a new version of librespot wasn't available, however I obviously forgot to do "sudo apt update" before installation....
After upgrade and removal of the workaround everything seems to work fine. Looking forward to MoOde 8.2.0!
RE: Spotify went crazy!! - rph-r - 12-23-2022
Spotify renderer doesn't work again...
before and after 8.2.3 update.
[edit]
sorry, it was another bug. I have 3 or 4 that reappear periodically...
https://moodeaudio.org/forum/showthread.php?tid=157
RE: Spotify went crazy!! - Tim Curtis - 12-23-2022
(12-23-2022, 10:05 AM)rph-r Wrote: Spotify renderer doesn't work again...
before and after 8.2.3 update.
[edit]
sorry, it was another bug. I have 3 or 4 that reappear periodically...
https://moodeaudio.org/forum/showthread.php?tid=157
I don't have a Spotify account to test. What specific errors or behaviors are you seeing?
RE: Spotify went crazy!! - Tim Curtis - 12-23-2022
(12-23-2022, 03:21 PM)Tim Curtis Wrote:(12-23-2022, 10:05 AM)rph-r Wrote: Spotify renderer doesn't work again...
before and after 8.2.3 update.
[edit]
sorry, it was another bug. I have 3 or 4 that reappear periodically...
https://moodeaudio.org/forum/showthread.php?tid=157
I don't have a Spotify account to test. What specific errors or behaviors are you seeing?
Actually, this thread is prolly best to close. It will be much easier to troubleshoot if a new thread is posted with your specific issue and include some details for example moOde version, any errors that may appear, startup log (moodeutl -l), audio device, etc.