Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Problem: V4.4 Spotify - track selection problems
#21
(02-22-2019, 08:34 PM)theengineer Wrote: Strange - worked like a charm for me.
And I do not envy you having to do the compilation on an RPi Zero.

In the meanwhile I would be glad if anybody finds a need for my binary:
Commit height = daeeeaa (Link to Github)
Built on RPi 3 (not compatible with RPi 1 & Zero)
Download Link

  1. Copy the binary to your RPi (Filezilla / SCP)
  2. Disable the Spotify renderer service in the webinterface (Config --> Audio)
  3. Move the binary to /usr/local/bin/librespot
  4. Re-enable the renderer

I followed these instructions on 3b+ and now spotify does not work at all. No longer see moode from spotify. Is it a file permission problem? Any ideas.
Reply
#22
(03-03-2019, 02:56 PM)Cussco Wrote:
(02-22-2019, 08:34 PM)theengineer Wrote: Strange - worked like a charm for me.
And I do not envy you having to do the compilation on an RPi Zero.

In the meanwhile I would be glad if anybody finds a need for my binary:
Commit height = daeeeaa (Link to Github)
Built on RPi 3 (not compatible with RPi 1 & Zero)
Download Link

  1. Copy the binary to your RPi (Filezilla / SCP)
  2. Disable the Spotify renderer service in the webinterface (Config --> Audio)
  3. Move the binary to /usr/local/bin/librespot
  4. Re-enable the renderer

I followed these instructions on 3b+ and now spotify does not work at all. No longer see moode from spotify. Is it a file permission problem? Any ideas.

@Cussco

You should see ownship/permissions like the following:

Code:
pi@moode:/usr/local/bin $ ls -l librespot
-rwxr-xr-x 1 root staff 11304548 Mar  2 09:25 librespot

If the "x" (execute) flags are missing, the renderer won't start.


When the librespot renderer has been enabled you should see it among the running processes, something like:

Code:
pi@moode:/usr/local/bin $ ps aux|grep librespot
root       961  0.0  0.3   8256  3348 ?        S    Mar02   0:00 sudo librespot --name Moode Spotify --bitrate 160 --initial-volume 0 --cache /var/local/www/spotify_cache --disable-audio-cache --backend alsa --device plughw:1 --onevent /var/local/www/commandw/spotevent.sh
root       975  0.4  0.8  27868  8428 ?        Sl   Mar02   3:59 librespot --name Moode Spotify --bitrate 160 --initial-volume 0 --cache /var/local/www/spotify_cache --disable-audio-cache --backend alsa --device plughw:1 --onevent /var/local/www/commandw/spotevent.sh
pi       23214  0.0  0.0   4372   576 pts/0    S+   10:40   0:00 grep --color=auto librespot

That third entry is not relevant. It's an artifact of the way I used ps|grep.

Regards,
Kent
Reply
#23
(03-03-2019, 03:49 PM)TheOldPresbyope Wrote:
(03-03-2019, 02:56 PM)Cussco Wrote:
(02-22-2019, 08:34 PM)theengineer Wrote: Strange - worked like a charm for me.
And I do not envy you having to do the compilation on an RPi Zero.

In the meanwhile I would be glad if anybody finds a need for my binary:
Commit height = daeeeaa (Link to Github)
Built on RPi 3 (not compatible with RPi 1 & Zero)
Download Link

  1. Copy the binary to your RPi (Filezilla / SCP)
  2. Disable the Spotify renderer service in the webinterface (Config --> Audio)
  3. Move the binary to /usr/local/bin/librespot
  4. Re-enable the renderer

I followed these instructions on 3b+ and now spotify does not work at all. No longer see moode from spotify. Is it a file permission problem? Any ideas.

@Cussco

You should see ownship/permissions like the following:

Code:
pi@moode:/usr/local/bin $ ls -l librespot
-rwxr-xr-x 1 root staff 11304548 Mar  2 09:25 librespot

If the "x" (execute) flags are missing, the renderer won't start.


When the librespot renderer has been enabled you should see it among the running processes, something like:

Code:
pi@moode:/usr/local/bin $ ps aux|grep librespot
root       961  0.0  0.3   8256  3348 ?        S    Mar02   0:00 sudo librespot --name Moode Spotify --bitrate 160 --initial-volume 0 --cache /var/local/www/spotify_cache --disable-audio-cache --backend alsa --device plughw:1 --onevent /var/local/www/commandw/spotevent.sh
root       975  0.4  0.8  27868  8428 ?        Sl   Mar02   3:59 librespot --name Moode Spotify --bitrate 160 --initial-volume 0 --cache /var/local/www/spotify_cache --disable-audio-cache --backend alsa --device plughw:1 --onevent /var/local/www/commandw/spotevent.sh
pi       23214  0.0  0.0   4372   576 pts/0    S+   10:40   0:00 grep --color=auto librespot

That third entry is not relevant. It's an artifact of the way I used ps|grep.

Regards,
Kent


Thanks TheOldPresbyope

All working now. Changed permission via Filezilla.
Reply
#24
(03-03-2019, 04:35 PM)Cussco Wrote:
(03-03-2019, 03:49 PM)TheOldPresbyope Wrote:
(03-03-2019, 02:56 PM)Cussco Wrote:
(02-22-2019, 08:34 PM)theengineer Wrote: Strange - worked like a charm for me.
And I do not envy you having to do the compilation on an RPi Zero.

In the meanwhile I would be glad if anybody finds a need for my binary:
Commit height = daeeeaa (Link to Github)
Built on RPi 3 (not compatible with RPi 1 & Zero)
Download Link

  1. Copy the binary to your RPi (Filezilla / SCP)
  2. Disable the Spotify renderer service in the webinterface (Config --> Audio)
  3. Move the binary to /usr/local/bin/librespot
  4. Re-enable the renderer

I followed these instructions on 3b+ and now spotify does not work at all. No longer see moode from spotify. Is it a file permission problem? Any ideas.

@Cussco

You should see ownship/permissions like the following:

Code:
pi@moode:/usr/local/bin $ ls -l librespot
-rwxr-xr-x 1 root staff 11304548 Mar  2 09:25 librespot

If the "x" (execute) flags are missing, the renderer won't start.


When the librespot renderer has been enabled you should see it among the running processes, something like:

Code:
pi@moode:/usr/local/bin $ ps aux|grep librespot
root       961  0.0  0.3   8256  3348 ?        S    Mar02   0:00 sudo librespot --name Moode Spotify --bitrate 160 --initial-volume 0 --cache /var/local/www/spotify_cache --disable-audio-cache --backend alsa --device plughw:1 --onevent /var/local/www/commandw/spotevent.sh
root       975  0.4  0.8  27868  8428 ?        Sl   Mar02   3:59 librespot --name Moode Spotify --bitrate 160 --initial-volume 0 --cache /var/local/www/spotify_cache --disable-audio-cache --backend alsa --device plughw:1 --onevent /var/local/www/commandw/spotevent.sh
pi       23214  0.0  0.0   4372   576 pts/0    S+   10:40   0:00 grep --color=auto librespot

That third entry is not relevant. It's an artifact of the way I used ps|grep.

Regards,
Kent


Thanks TheOldPresbyope

All working now. Changed permission via Filezilla.

There is probably and easier way to do this but this is how I managed it on win 10 machine

Disable the Spotify renderer service in the webinterface (Config --> Audio)

THIS WORKS USING MOODE 4.4

1. Download Filezilla and Putty
2. Download the Binary from theengineers post in this thread (RRI 3 only)
3. Using Filezilla connect to PI (quickconnect)
IP: 192.168.0.39 (Replace with your Moode IP address)
UserName: Pi
Password: Moodeaudio
Port: 22
4. Transfer the binary to the directory /home/pi in Filezilla (hope this does not need explaining)
5. Launch Putty and connect to Pi with IP address from above
6. Login as at prompt "Pi" with "Moodeaudio" as password
7. Type cd /home/pi to navigate to the directory you transferred the binary to
8. Type "sudo mv librespot /usr/local/bin" to move the binary to the correct directory
9. Go back to filezilla and navigate to /usr/local/bin
10. Right click the newly copied librespot binary and allow the execute permissions
11. Restart PI (possible not needed) and enable Spotify renderer service 
12. Enjoy track selection again

Hope this helps others. I am new this too and thought I would describe what I did.
Reply
#25
Hi,
Can you add an update to moode 4.4 to fix the track selection. Please Smile
Reply
#26
(03-03-2019, 09:27 PM)servulus Wrote: Hi,
Can you add an update to moode 4.4 to fix the track selection. Please Smile

I don't understand your request.

I am using Moode 4.4.
Reply
#27
Hi all

I would also appreciate a binary for RPI1 if possible (or an estimate on when this can be fixed in the official distribution).

Thanks
adixor
Reply
#28
Thx Cussco

I managed (with my rudimentary Linux knowledge) by following your instructions to get a working Spotify client.

Thx again

Andreas
Reply
#29
Here’s a new build of librespot for the Raspberry Pi: https://github.com/librespot-org/libresp...respot.zip

Tested on moOde and it’s working fine!
Reply
#30
(03-07-2019, 11:12 AM)timoho Wrote: Here’s a new build of librespot for the Raspberry Pi: https://github.com/librespot-org/libresp...respot.zip

Tested on moOde and it’s working fine!

What RPi is that for? 

Thanks!
Reply


Forum Jump: