Posts by awiouy

  • Librespot addon

    Quote from donski

    I'm running it on the new version 122 on a Raspberry Pi 3 using a nightly build from Milhouse and it works pretty well. Artwork is displayed and I also listened to a podcast, jumping in time etc.

    One issue: When I want to play a track from the auto-suggestions displayed below a playlist, it stops working (I removed timestamps etc.):

    Code
    [librespot_connect::spirc] Fetching autoplay context uri
[librespot_connect::spirc] Autoplay uri resolved to <"spotify:station:playlist:1rxlGK8SOz1PJgavHOXY7p">
[librespot_playback::player] Loading <Lesser Known Good> with Spotify URI <spotify:track:3vGnW6Pg1LCFDwHAMnHuXX>
[librespot_connect::spirc] Resolved 50 tracks from <"spotify:playlist:1rxlGK8SOz1PJgavHOXY7p">
[librespot_playback::player] <Lesser Known Good> (300972 ms) loaded
[librespot_connect::spirc] Fetching autoplay context uri
thread 'main' panicked at 'Spotify servers returned an error. Restart librespot.', core/src/mercury/mod.rs:201:13

    Hi donski

    The issue is known, but not a solution

  • Librespot addon

    Quote from met98

    Hi

    I have a problem that has plagued me for some time, I also tried to reinstall everything. when i start libreelerc, librespot crashes. Ever since I updated it to version 9.2.2. If I start it manually by deactivating and reactivating the service, it works fine.

    I have a Intel NUC

    Enable 'wait for network' in LibreELEC network settings

  • Librespot addon

    Quote from MikeCC

    I have updated to version 122.

    Now playing stops after a track with special character in the name (e.g. Beyoncé)

    Here my log from kodi.log

    Hi MikeCC

    This is a known issue, which is solved with revision 123.

    To fix until revision 123 is released, either revert to revision 121 or apply this fix manually (disable/enable the addon to activate the fix):

    librespot: handle non ascii track information · LibreELEC/LibreELEC.tv@967bb63 · GitHub

  • Help with DDNS

    Specify the configuration file with the '-f' or '--config' flag, ie inadyn --check-config --config your_file.

  • Librespot addon

    Quote from siz

    I had already copied service.librespot-alsa.service for version 121, which worked great. However, after autoupdate to 122, I had to enable and start the service before it worked for 122.

    You write that libresport does not use systemd anymore, but don't we use systemd to enable alsa? :)

    Hello siz

    Where had you copied your system.d file to?

    To /storage/.config/system.d ?

  • Librespot addon

    Librespot and VPN:

    VPN prevents adding users in discovery mode (but a VPN does not prevent discovered users to stream from Spotify).

    Therefore, switch your VPN off to add new users in discovery mode. You can turn it back on after they have been added.

    Librespot and systemd

    Librespot 122 does not use systemd anymore and logs in the Kodi log.

    Therefore, use the following command to read the log of Librespot 122:

    grep Librespot /storage/.kodi/temp/kodi.log

    Enjoy!

  • Librespot addon

    Hello pipsen,

    To keep your changes after updates, refer to the instructions in the sample system.d service.

    Code
    # Copy this file to '/storage/.config/system.d/service.librespot-alsa.service' and adapt it to your needs
# Enable the service with 'systemctl enable /storage/.config/system.d/service.librespot-alsa.service'
# Start the service with 'systemctl start service.librespot-alsa.service'
# If you update the file, reload units with 'systemctl daemon-reload' and restart the service

  • Librespot addon

    I am reworking Librespot and I would like some feedback.

    Preview for LibreELEC 9.2 for RPi2

    Preview for LibreELEC 9.2 for RPi4

    Preview for LibreELEC 9.80 for RPi2

    Notable changes:

    - fanart is displayed during playback

    - podcast information is displayed

    - settings are reset to default

    - autoplay is enabled by default and can be disabled

    - display name can be set and {} is a placeholder for the host name

    - RTP port can be set

    - librespot is build with mdns instead of dns-sd

    - the addon does not use system.d anymore

    The source are here and there.

  • Syncthing

    Have you tried http://YOUR_IP:8384?

    If that does not work, then provide the output of journalctl -u service.syncthing.

  • Librespot addon

    Hi Sappi,

    To solve your issue either enable avahi in LibreELEC services or set user name and password in user mode in Librespot settings.

    Also, wait for network is recommended for Librespot and for other services.

    Librespot for LibreELEC is built with dns-sd (avahi) rather than mdns, for historical reasons and also because user interaction is smoother.

    Hope this helps.

  • Librespot addon

    Quote from Sappi

    once again after autoupdate from 28. February: librespot binary is broken

    after replacing the binary with my self build one the device appeared back on spotify connect ... but trying to play a song I hear no audio, even though the the song appears to be played on the client device.

    Then I removed the --backend pulseaudio switch from librespot.start

    now everything works again.

    any thoughts why this is would be highly appreciated.

    Hi Sappi,

    According to the log you provide, the binary is not broken but something in your configuration is.

    First, if you remove the --backend flag then librespot does not use pulseaudio but alsa, which is out of the scope of the addon.

    Then, your logs report a DNS issue, so let us try inspecting this:

    1. What version of LibreELEC are you running (hardware and version)?

    2. Have you set the wait for network option in LibreELEC network configuration?

    3. Is Avahi enabled in LibreELEC services configuration?

    4. Do you have a Spotify Premium account?

    5. Have you tried running in user mode, where you set Spotify username and password in the settings of the addon?

    6. Can you provide the output of "ldd /storage/.kodi/addons/service.librespot/bin/librespot", the version shipped with the addon?

  • Syncthing

    Quote from newuser_

    Um I have another question. I've connected my IntelNUC (LE) with my other PC (Win). But the folder which I've synchronized is on my PCs end on an external HDD. So I was wondering what is happening if I run my NUC and my PC at the same time and the external HDD is not plugged to my PC. So it won't find the path on my PCs end. In this case will it just remove the data on the NUC? Or does it only sync when I start the tool on windows? Because on LE it seems to be running in the background.

    That is a question for the Syncthing forum.

    If I remember well, there is an option for only adding files, ie no deletion.

  • Syncthing

    Quote from newuser_

    Hi, can someone explain me how this is working? Is it normal that the addon isn't shown in my addon list after installation?

    Do I just have to edit the config file manually? And if yes what do I have to change?

    Hi,

    Have you tried the web interface?

    See the first post of this thread