How’s progress on the release going? I assume it’s run into some difficulties since it should have been released by now. Any news would be appreciated. Thanks.
Don’t know where you get “should have been released by now” from.
Did anyone promise a fixed release date?
In my opinion, sometimes things need time to mature, rushing to release usually doesn’t work well.
1 Like
From Volumio’s statement of May 18th → “Our goal is to have something in about 10 days”.
There was an update since then though, to 4.0.5. It seems to work perfectly for some, but unfortunately not for everyone. I’m sure they’re working hard to resolve the remaining issues, but it seems to be moving target with Spotify.
Is there actually a change blog? I haven’t found anything here or on GitHub.
1 Like
I am also really looking forward to a stable spotify plugin.
After deinstalling / reinstalling the latest version the major issues are:
- Via Volumio no access to Spotify playlists etc. Just keeps loading forever…
- Spotify Connect only works sometimes. Mostly, just nothing happens when starting to play something.
But I guess, I am not the only one…
I know that it is a community plugin, but that should be reconsidered. A stable spotify integration is something users really expect today.
Best regards,
Michael
In a previous version the shuffle function via Spotify connect did work. In this last version it doesn’t anymore.
I’ve checked the latest updates. Toggling in Spotify the shuffle button. But doenst seems to work.
Is this a known issue?
I can confirm what’s been reported by other users regarding the queue not working on Spotify Connect. Auto-play doesn’t work either.
I’ve tried on Spotify Desktop and the Android Spotify app, both up-to-date. My Volumio is on the latest (3.703 as of today).
Issue still there with 4.0.5.
In general I’ve found the new plugin to be less stable as well. The previous versions were not perfect but still significantly better.
Hi, I’m curious whether you are referring to the old plugin from Balbuze? That thing worked like a charm, I need it! Could you be so kind to dm the latest install details? I have tried to find it before, but have not managed to get it to work… Maybe a wrong version?
@volumio Since you have been asking for suggestions… I can’t stress enough I’m really hoping you’re working on the basics first. A simply working connect implementation. All other stuff might be great, but Spotify is taking care of that as well. Unfortunately, this does not seem to be the case. Good luck!
1 Like
The old plugin did work fine until Spotify changed the interfaces. You wouldn’t get anywhere with the old plugin now.
finally I catch the bug:
Jul 20 19:37:14 main go-librespot[5196]: time=“2024-07-20T19:37:14+03:00” level=trace msg=“fetched new page 0 with 1 items (list: 1)”
Jul 20 19:37:14 main go-librespot[5196]: time=“2024-07-20T19:37:14+03:00” level=debug msg=“loading track spotify:track:3z7I7CP1WwU07Z1iNmeMFb (paused: false, position: 0ms)”
Jul 20 19:37:14 main go-librespot[5196]: time=“2024-07-20T19:37:14+03:00” level=debug msg=“put connect state because PLAYER_STATE_CHANGED”
Jul 20 19:37:14 main go-librespot[5196]: time=“2024-07-20T19:37:14+03:00” level=trace msg=“emitting websocket event: will_play”
Jul 20 19:37:14 main volumio[816]: SPOTIFY: received: {“type”:“will_play”,“data”:{“uri”:“spotify:track:3z7I7CP1WwU07Z1iNmeMFb”,“play_origin”:“go-librespot”}}
Jul 20 19:37:14 main volumio[816]: SPOTIFY: received: {“type”:“will_play”,“data”:{“uri”:“spotify:track:3z7I7CP1WwU07Z1iNmeMFb”,“play_origin”:“go-librespot”}}
Jul 20 19:37:14 main go-librespot[5196]: time=“2024-07-20T19:37:14+03:00” level=error msg=“failed handling status request” error=“failed loading context: failed loading current track (load context): failed creating stream: no playable formats for spotify:track:3z7I7CP1WwU07Z1iNmeMFb”
Jul 20 19:37:14 main volumio[816]: error: Failed to send command to Spotify local API: /player/play: Error: Internal Server Error
Is it possible to add an option to Volumio: Play Next Track if error
Spotify plugin stoping play randomly and regulary
I’ve suggested a quick workaround for tracks that are in an unplayable format.
But, in the SPOTIFY application for Windows, all tracks are played.
I assume that Spotify has an additional audio codec for playing such tracks in its application.
If Volumio is a SPOTIFY partner, can you request this codec to integrate it into your operating system?
If the go-lebrespot module is third-party, is it possible to contact the developer and clarify the situation?
Thank you.
I duplicate the log:
Jul 20 19:37:14 main go-librespot[5196]: time=“2024-07-20T19:37:14+03:00” level=error msg=“failed handling status request” error=“failed loading context: failed loading current track (load context): failed creating stream: no playable formats for spotify:track:3z7I7CP1WwU07Z1iNmeMFb”
in addition, the following tracks are played even in the browser, but not by the Volumio player:
Jul 22 01:36:49 streamer-c go-librespot[3201]: time=“2024-07-22T01:36:49+03:00” level=error msg=“failed handling status request” error=“failed loading context: failed loading current track (load context): failed creating stream: no playable formats for spotify:track:39OHQ8hRVgl6Jve9PnqZ8y”
Jul 22 04:00:49 streamer-c go-librespot[3201]: time=“2024-07-22T04:00:49+03:00” level=error msg=“failed handling status request” error=“failed loading context: failed loading current track (load context): failed creating stream: no playable formats for spotify:track:39OHQ8hRVgl6Jve9PnqZ8y”
Jul 22 04:53:04 streamer-c go-librespot[3201]: time=“2024-07-22T04:53:04+03:00” level=error msg=“failed handling status request” error=“failed loading context: failed loading current track (load context): failed creating stream: no playable formats for spotify:track:12kmgivtb8dyhxnko2doFt”
Jul 22 08:42:54 streamer-c go-librespot[3201]: time=“2024-07-22T08:42:54+03:00” level=error msg=“failed handling status request” error=“failed loading context: failed loading current track (load context): failed creating stream: no playable formats for spotify:track:10ly1SC9HsQvXwXBWZEfn5”
Jul 22 08:47:57 streamer-c go-librespot[3201]: time=“2024-07-22T08:47:57+03:00” level=error msg=“failed handling status request” error=“failed loading context: failed loading current track (load context): failed creating stream: no playable formats for spotify:track:64leFpj58XpvqWFy1yVJ4X”
Jul 22 11:14:19 streamer-c go-librespot[1133]: time=“2024-07-22T11:14:19+03:00” level=error msg=“failed handling status request” error=“failed loading context: failed loading current track (load context): failed creating stream: no playable formats for spotify:track:351kUprIhCD5A0ZWLHdJrn”
Jul 22 12:24:06 streamer-c go-librespot[1133]: time=“2024-07-22T12:24:06+03:00” level=error msg=“failed handling status request” error=“failed loading context: failed loading current track (load context): failed creating stream: no playable formats for spotify:track:0OnPKPkvfqFemDftNCgEaX”
Jul 22 12:48:46 streamer-c go-librespot[1133]: time=“2024-07-22T12:48:46+03:00” level=error msg=“failed handling status request” error=“failed loading context: failed loading current track (load context): failed creating stream: no playable formats for spotify:track:7a2daVekS4qRXvVS6N2t8J”
Jul 22 14:47:09 streamer-c go-librespot[1133]: time=“2024-07-22T14:47:09+03:00” level=error msg=“failed handling status request” error=“failed loading context: failed loading current track (load context): failed creating stream: no playable formats for spotify:track:7tXTCz8talef0AeZp7pWeT”
Jul 22 14:54:22 streamer-c go-librespot[1133]: time=“2024-07-22T14:54:22+03:00” level=error msg=“failed handling status request” error=“failed loading context: failed loading current track (load context): failed creating stream: no playable formats for spotify:track:6a9eB9AVWeLMY0BBsXGzYp”
Jul 23 03:09:26 streamer-c go-librespot[18967]: time=“2024-07-23T03:09:26+03:00” level=error msg=“failed handling status request” error=“failed loading context: failed loading current track (load context): failed creating stream: no playable formats for spotify:track:5FUTXldNmVK4wTW3yhGOsv”
Jul 23 06:23:00 streamer-c go-librespot[18967]: time=“2024-07-23T06:23:00+03:00” level=error msg=“failed handling status request” error=“failed loading context: failed loading current track (load context): failed creating stream: no playable formats for spotify:track:0qTbrvVqfnioE9XNI9KiWP”
Definitely a problem in go-lebrespot.
Presumably, go-lebrespot cannot play about 3-5% of the tracks in a playlist consisting of 800 tracks.
What version of go-librespot Volumio used ?
This one ? - github.com/arcspace/go-librespot
If so, then the developer indicates that the latest version is:
v0
v0.0.0-20231209073556-59dfc81fe1fe
Dec 9, 2023
is UNSTABLE!!!
version dates back to December 2023!!!
Friends! Have you really posted your project with a buggy main library for SPOTIFY?
I think it is this repo:
Anyway,
Are the Volumio team planing do something with this go-librespot library?
Or we have to search another Media Player OS ???
add 2 more buggy tracks in post above.
Besides, Volumio OS sometimes CPU failing, then the temperature grows, and finally freeze:
platform:
Raspberry Pi 4 B, Ethernet PoE
Volumio 3.703, Wi-Fi turned off
HiFiBerry DAC Plus
Spotify Premium
I was planning to purchase a subscription for Volmio, but after a week of testing I doubt the feasibility.
The Volumio player regularly stops (within 1-16 hours) to play or display current information in the Web interface - it shows the track on which playback or display has stopped, and the time of this track is, for example, 900 minutes.
nothing happens in the Web interface, if you update the browser, the track remains the one that was 900 minutes ago, but the time has been added to the time between opening the browser and updating it, for example, when opening the browser, the time is 900 minutes, after 5 minutes it was updated - time 905 minutes.
If Volumio did not stop playing, then it is impossible to find out what track is now.
With this bug, if you press the next track, Volumio switches to a new one, when the track ends, a new one plays, but the picture remains from the previous track and the time continues to accumulate… But this does not always happen.
3rd bug, if the Internet channel is interrupted, then it is possible to resume playback only if you log out and re-login to Volumio and Spotify.
4th bug, when I try to access the Volumio store from the Web interface (/iframe-page/https:~2F~2Fvolumio.com~2Fshop~2F), I get the answer: shop.volumio.com refused to connect.
However, the help page opens normally (/iframe-page/http:~2F~2Fhelp.volumio.com) and after navigation maneuvers you can get from it to the Volumio store.
However, the message: “shop.volumio.com refused to connect” indicates some active blocking on Volumio’s part.
Why block something through the Web interface on Raspberry Pi?
I believe that the Volumio application for Raspberry Pi has a lot more built-in blocking, due to the problems described above.
But why do this?
Today the player stopped 4 times.
playlist contains up to 1000 Spotify tracks.
Who knows how to understand why?
I read the forum and found the same problems 4 years ago, but I couldn’t find a solution here.
And I also noticed that if I connect to the web interface via my phone (Firefox), the Vlumio store opens.
But on PC Windows (MS Edge, Firefox, Google Chrome) it doesn’t open.
It’s funny!
I found out that problems in the SPOTIFY plugin with connecting to audio devices, playing, synchronizing, etc. are most often associated with various channels installed on end devices and control applications:
ap-gew1.spotify.com
ap-gew4.spotify.com
ap-guc3.spotify.com
ap-gae2.spotify.com
ap-gew1.spotify.com
etc.
i.e., if the audio output device has a channel ap-gew1.spotify.com
and the program or web interface is ap-gew4.spotify.com
then you will never pair the device.
These channels directly interact with IP geolocation.
If you have IPSEC or other tunnels, then if there are any problems with communication, the Spotify channel changes, after which everything breaks and intervention is necessary to restore playback.
Even if your devices are on the same network, but the controller has a VPN, then the Volumio frame works through this VPN, as a result authentication becomes a problem.
In addition, attempts to replace channels in HOSTS or even by replacing static DNS did not yield any results.
I haven’t tried more aggressive methods of bringing the channels to a single one, because… I think this may lead to other errors.