mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #238] Librespot playback stops after two songs #162
Labels
No labels
A-Alsa
SpotifyAPI
Tokio 1.0
audio
bug
can't reproduce
compilation
dependencies
duplicate
enhancement
good first issue
help wanted
high priority
imported
imported
invalid
new api
pull-request
question
reverse engineering
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librespot#162
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @daskorn on GitHub (Jul 22, 2018).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/238
When I use librespot with a LTE internet connection the playback stops after just two tracks. Currently I use the librespot plugin of Volumio on a RPi3 connected via WIFI to a LTE (~5-8Mbit/s) router. First noticeable difference to a standard DSL 16k or 50k connection is the late start of the music. It takes around 5-20 seconds before the music starts.
This is a trace of the moment where it stucks:
This error just appears for librespot. The Android/Windows/iOS apps of spotify are starting each track immediately and are playing continously.
Any suggestions what I can do to make librespot work along with LTE?
Kind regards
@abrakadabra2k commented on GitHub (Sep 16, 2018):
I am having the same issue via LAN and WiFi. :-
Sometimes after 2 songs, sometimes more...
@BjarkeVadPedersen commented on GitHub (Oct 21, 2018):
Hi,
I am experiencing a similar issue, playback stops after a few songs with the following error message:
INFO:librespot_playback::player: Track "1950" loaded ERROR:librespot_core::session: Error { repr: Os { code: 104, message: "Connection reset by peer" } }This is with librespot built from source on a Raspberry Pi 3B.
Thanks!
@skuligowski commented on GitHub (Oct 21, 2018):
Hi,
I am having the same issue, after 2-3 songs, it stops playing.
ERROR:librespot_core::session: Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" }Do you have any workaround for that issue?
@abrakadabra2k commented on GitHub (Oct 22, 2018):
I am using Spotify Connect with this config now:
https://github.com/RafaPolit/moode-spotify-connect-web
@skuligowski commented on GitHub (Oct 22, 2018):
Is it somehow still possible to get spotify_appkey.key from spotify
website? The site with the request form is dead.
I think sooner or later spotify-connect-web will be broken too and it would
be better to find a valid solution of ConnectionReset issue for librespot..
pon., 22 paź 2018, 08:50 użytkownik abrakadabra2k notifications@github.com
napisał:
@sashahilton00 commented on GitHub (Nov 3, 2018):
See https://github.com/librespot-org/librespot/issues/134 for this bug. Basically librespot doesn't handle reconnection, hence it crashes if your internet drops out. spotify_appkey.key is dead, the apis for using it don't even exist anymore afaik. Closing in favour of aforementioned issue.
@stargazer commented on GitHub (Aug 15, 2019):
For anyone experiencing the same issue. I've been struggling for months now with the infamous
ConnectionResetandInvalidating Sessionmessages. I tried multiple versions oflibrespot, multiple ways to install it, and still got the same.It turns out it was a network issue, on my end. I disabled my raspberrypi's ethernet interface and switched to the wifi. Never looked back. Works like a dream. Apparently my ethernet has some glitches. I can finally enjoy some music :)
@georgefst commented on GitHub (Jun 3, 2021):
Similar here after switching off bluetooth (wifi + bluetooth interfering with each other is a known issue on some Pi models). Of course, ideally
librespotshould be able to handle disconnects without falling over completely. But there's been recent activity at #609, so hopefully that will be resolved some day.