10-14-2024, 05:24 PM
I don't see how Tim and his merry band of devs (including backbenchers like me) can solve this problem. Since moOde is simply a conduit for the output of the third-party librespot app it would seem disconnection/dropout issues arise in librespot or upstream.
I note that there has been an ongoing librespot github discussion thread about how to "Handle reconnection for Sessions" that started in 2018 and continues today. The librespot devs don't seem to have a definitive answer. I don't understand the Spotify protocols well enough to know if that discussion topic covers your issue or not but it certainly rhymes.
Recently, one of the participants on that thread remarked "I'm testing go-librespot now. My experiences are much better. Very stable connection." Another responded "I see that go-librespot is just retrying a bunch of times, rotating around the access points. That isn't what librespot does but we might as well go down this route and paper over whatever problem this is. Maybe it is just Spotify's shoddy servers." (Here, access points refers to Spotify servers.) The principal dev responds that this papering over might work but would require substantial code rewrite on their part. This doesn't suggest to me that they have even identified the root causes.
Comcast is my ISP as well and I don't believe they're doing anything untoward with Spotify service (or any other music streaming service I dabble with). Spotify isn't my usual source but as a reference point, I've been listening to one of Spotify's "Radio" channels for the past hour without interruption. I'll keep it on in the background all today to see if it ever glitches.
Perhaps we have different experiences because our clients are connecting to different Spotify access points. I'm in Maryland on the east coast of the USA. Where are you located.
Regards,
Kent
I note that there has been an ongoing librespot github discussion thread about how to "Handle reconnection for Sessions" that started in 2018 and continues today. The librespot devs don't seem to have a definitive answer. I don't understand the Spotify protocols well enough to know if that discussion topic covers your issue or not but it certainly rhymes.
Recently, one of the participants on that thread remarked "I'm testing go-librespot now. My experiences are much better. Very stable connection." Another responded "I see that go-librespot is just retrying a bunch of times, rotating around the access points. That isn't what librespot does but we might as well go down this route and paper over whatever problem this is. Maybe it is just Spotify's shoddy servers." (Here, access points refers to Spotify servers.) The principal dev responds that this papering over might work but would require substantial code rewrite on their part. This doesn't suggest to me that they have even identified the root causes.
Comcast is my ISP as well and I don't believe they're doing anything untoward with Spotify service (or any other music streaming service I dabble with). Spotify isn't my usual source but as a reference point, I've been listening to one of Spotify's "Radio" channels for the past hour without interruption. I'll keep it on in the background all today to see if it ever glitches.
Perhaps we have different experiences because our clients are connecting to different Spotify access points. I'm in Maryland on the east coast of the USA. Where are you located.
Regards,
Kent
