can't connect #1
Assignees
Labels
bug
Something isn't working
documentation
Improvements or additions to documentation
feature
New feature or request
review
Comments
|
I've seen the issue before - I don't remember off the top of my head what the cause is but I'm looking into it. This is also a reminder to myself to make the name of the spotify connect speaker configurable :) |
|
@theovermaze There might be an issue with either the sound being sent to the incorrect audio device, or the audio device being busy (in the case of ALSA, pulse is a separate feature flag). Could you give me the output of the following commands?
|
|
Here is the output. Thanks for the help! So no PulseAudio? |
|
@theovermaze Seems like Kodi is correctly starting the plugin service and the binary seems to be launching. Is installing pulseaudio an option for you? I think ALSA is only really an option if you have no other software running using the sound card, because the ALSA backend takes over the soundcard completely. If it is, please;
I'm not sure that will fix the problem as I don't expect the connection to kick you off with an ALSA backend, but I'm not sure. The problem seems to be related to the spotifyd binary, but I can't reproduce it yet. If this does fix the problem, I'm guessing the root cause is either MPRIS or somehow indeed ALSA. |
|
I can't risk my osmc-installation. So no PulseAudio for me :( |
jhjdekker98
added
documentation
|
TODO:
|
|
Maybe this is based on: Spotifyd/spotifyd#1044 |
|
Tried it with the libreelec nightly (Kodi20) as of 20230210. Cannot connect either. Android sees the instance only for some minutes before it disappears. |
|
Btw. librespot runs fine here. |
|
Successfully reproduced on latest LTS LibreElec release for RPi4 as of today (LibreELEC-RPi4.arm-10.0.4). After following the instructions in the readme, I see the Spotify Connect speaker show up in the app. After trying to connect it disappears and doesn't seem to reappear again unless I reboot. Intererstingly, the spotifyd-full release I used doesn't seem to support the pulseaudio back-end like @chrisgo67 suggested. Removing pulseaudio from the service and trying to start is seems successful, but when trying to connect the following occurs: My previously used spotifyd binary was compiled for amd64, so I cannot use that here on rpi4. Will report back after compiling on Debian with pulseaudio feature flag and reinstalling with that binary. |
|
Confirmed to be an issue with the spotifyd binary. Looking into running librespot instead. |
|
Seems like Librespot works because it's using the rodio backend by default. Spotifyd can be compiled with the optional rodio audio backend too (Spotifyd/spotifyd#400). Compiled on rpi4b with OSMC 20230124. Compiled spotifyd binary seems to run fine with rodio backend on OSMC. |
|
This sounds great! I would like to try. Any tips on how to compile spotifyd with the rodio audio backend? |
|
@theovermaze You'd need to install rust through rustup with the correct host architecture (in the case of the rpi4 and I believe the vero box; I'm running the compilation again because I managed to accidentally delete the build folder. Once that's done and I verify a clean OSMC installation will run spotifyd-client I'll post the binary online somewhere so you can test it out too. If everything works as expected I wanna add some precompiled binaries to this repo and some autodetection in the service for which binary needs to be run. |
|
Thank you! Looking forward to testing! |
|
@theovermaze compiled binary for armv7 available here. My uname -a output looks similar enough, although I'm running major version 5 of OSMC. I don't think that will cause any issues with the binary though. Right now running spotifyd directly in OSMC with the rodio audio backend seems to work, but using the plugin it crashes to |
|
@theovermaze I pushed some fixes to the I haven't tested on a clean installation yet but I'm quite positive everything will work now (aside from some minor GUI bugs). With the diff on that branch, I see the song metadata being pushed to the temporary file and I hear the music from Spotify. |
|
just to make sure: the filesize of spotifyd_armv7.tar is 969,62 mb and consists of the folders "build", "deps", "examples", "incremental" and the files spotifyd and spotifyd.d. The whole content must be placed into /resources/lib/spotifyd? |
Absolutely correct |
|
Here are my testresults: Starting the addon via kodi shows an error message. cat ~/.kodi/temp/kodi.log After executing spotifyd in /home/osmc/.kodi/addons/plugin.audio.spotifyd-client/resources/lib/spotifyd i see the device in the android app. Connecting is not possible. The app shows "connecting" for a long time. |
|
@theovermaze The addon's error message is related to the That doesn't address the issues with spotifyd not launching though. Could you run spotifyd with the following command: |
|
here is the output: |
|
@theovermaze Weird, the dbus daemon is unable to start - probably because you're accessing the Vero box over SSH. On my OSMC setup (on rpi4) this works fine though, but I've seen the same error before on other installations. Could you additionally give me the contents of your |
|
spotifyd.conf: uncommenting But starting the addon with kodi-gui crashes kodi: |
|
@theovermaze Seems like the way I'm retrieving the path to the binary in the new |
|
The addon crashes again. Here is the log: Connecting with
I always need to |
|
Very odd, looking back at the error log from the earlier commit, it looks like the path to both the executable and the config file are correct. For some reason the addon is not executing the executable, even with the correct parameters passed. The path |
|
No fix yet, more information / note to self: Running spotifyd from Why running spotifyd manually from SSH (either running the binary directly or executing |
|
Recompiled with all audio backend features - testing all gives different results, none functional yet. I'm convinced the problem lies somewhere in there. I also feel like it should be possible to get everything to work with the rodio backend, somehow. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi. I just tested your addon on a Vero4k+ with osmc 2022.10-1. Results:
Compilation of SpotifyD failed with the following error:
So i just downloaded spotifyd-linux-armhf-default.tar.gz for the spotifyd file.
Addon installed successfully in kodi.
After chmod+x of /.kodi/addons/plugin.audio.spotifyd-client/resources/lib/spotifyd/spotifyd i could see the device "JeroenMediaServer" on the Spotify Android App.
But it just says "connecting" for some time and the stops.
Client ID and Client Secret is configured.
spotifyd.conf:
Is there something i could try?
The text was updated successfully, but these errors were encountered: