Spotify Connect on RuneAudio

marksmanaz

I have rpi3 with .04 image with a hifiberry dac+ pro. This is what I get, any help would be appreciated.

[/root/spotify-connect-web.sh --name RuneAudio --device 0 --mixer Digital --username xxx --password xxx --bitrate 320
Traceback (most recent call last):
  File "main.py", line 9, in <module>
    from connect import Connect
  File "/usr/src/app/connect.py", line 8, in <module>
    from console_callbacks import audio_arg_parser, mixer, error_callback, connection_callbacks, debug_callbacks, playback_callbacks, playback_setup
  File "/usr/src/app/console_callbacks.py", line 28, in <module>
    mixer = alsa.Mixer(args.mixer)
alsaaudio.ALSAAudioError: Unable to find mixer control Digital,0 [default]

marksmanaz

OK I am using an analogue DAC hifiberry with two rca jacks for left right. I tried setting the device to 1 and the mixer to analogue but it wont go. If I use device 0 and mixer PCM it starts. Not sure what I need to do to get it to use the DAC in analogue working

Attachments

: Capture.PNG (35.87 KiB) Viewed 5647 times

rando_geekn

RuneAudio --playback_device 'sysdefault:CARD=IQaudIODAC' --mixer_device_index 1 --mixer Analogue

Thanks, That last bit helped, took me a while to figure that my DAC was device 1 and the sysdefault parameter was absolutely necessary.

tml3nr

rando_geekn wroteRuneAudio --playback_device 'sysdefault:CARD=IQaudIODAC' --mixer_device_index 1 --mixer Analogue

Thanks, That last bit helped, took me a while to figure that my DAC was device 1 and the sysdefault parameter was absolutely necessary.

Have fun bro!

tml3nr

Setup Spotify Connect on Hifiberry Digi+ & Allo DigiOne:

Many thanks to domars@volumio & triton@vnav about this tip.

Step 1. Edit file connect.py:

nano /root/spotify-connect-web-chroot/usr/src/app/connect.py

Find and replace:

mixer_volume = int(mixer.getvolume()[0] * 655.35)

to:

mixer_volume = 1 #int(mixer.getvolume()[0] * 655.35)

Step 2. Edit file console_callbacks.py:

nano /root/spotify-connect-web-chroot/usr/src/app/console_callbacks.py

Find and replace:

#1:

playback_device_group.add_argument('--device', '-D', help='alsa output device (deprecated, use --playback_device)', default='default')

to:

playback_device_group.add_argument('--device', '-D', help='alsa output device (deprecated, use --playback_device)', default='0')

#2:

playback_device_group.add_argument('--playback_device', '-o', help='alsa output device (get name from aplay -L)', default='default')

Hifiberry Digi+:

playback_device_group.add_argument('--playback_device', '-o', help='alsa output device (get name from aplay -L)', default='snd_rpi_hifiberry_digi')

Allo DigiOne:

playback_device_group.add_argument('--playback_device', '-o', help='alsa output device (get name from aplay -L)', default='sndallodigione')

#3:

if self._args.playback_device != 'default':

Hifiberry Digi+:

if self._args.playback_device != 'snd_rpi_hifiberry_digi':

DigiOne:

if self._args.playback_device != 'sndallodigione':

#4:

corected_playback_volume = int(min_volume_range + ((volume / 655.35) * (100 - min_volume_range) / 100))

to:

corected_playback_volume = 1 #int(min_volume_range + ((volume / 655.35) * (100 - min_volume_range) / 100))

Step 3. Create service:

nano /usr/lib/systemd/system/spotify-connect.service

[Unit]
Description=Spotify Connect
After=network.target

[Service]
ExecStart=/usr/bin/sh /root/spotify-connect-web.sh --name RuneAudio --username abc --password xyz --bitrate 320
Restart=always
RestartSec=10
StartLimitInterval=30
StartLimitBurst=20

[Install]
WantedBy=multi-user.target

Step 4. Test the service execute:

systemctl start spotify-connect

Step 5. If everyting OK, enable service (start on boot):

systemctl enable spotify-connect

Done!

dynobot

Tried the spotify web connect with varied success.

In the meantime I ran across Spotifyd, its supposed to use the API from Spotify and works/connects like the original.

No special configurations required like spotify web connect etc. just unzip the file, move it to /usr/bin and create a service and update the conf file.

Seems pretty solid with 4 different Dacs XMOS, Amanero, and with Allo digi one sig. Volume etc works but seems to be picky with Amanero.

And best of all the SQ is exceptional, Raspotify, liberspot etc all seemed a tad dull...just enough to where I knew it was not directly from Spotify but through something. Spotifyd sounds clean and airy not dull at all.

https://github.com/Spotifyd/spotifyd

tml3nr

dynobot wroteTried the spotify web connect with varied success.

In the meantime I ran across Spotifyd, its supposed to use the API from Spotify and works/connects like the original.

No special configurations required like spotify web connect etc. just unzip the file, move it to /usr/bin and create a service and update the conf file.

Seems pretty solid with 4 different Dacs XMOS, Amanero, and with Allo digi one sig. Volume etc works but seems to be picky with Amanero.

And best of all the SQ is exceptional, Raspotify, liberspot etc all seemed a tad dull...just enough to where I knew it was not directly from Spotify but through something. Spotifyd sounds clean and airy not dull at all.

https://github.com/Spotifyd/spotifyd

Many thanks for your information. Spotifyd works as i expect on my Rune. Spotify volume on app syncs to alsa very well.

SQ is very impressive. Clean and airy.

root@runeaudio(rw):~# systemctl status -l spotifyd
● spotifyd.service - A spotify playing daemon
   Loaded: loaded (/usr/lib/systemd/system/spotifyd.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2019-04-22 20:19:32 ICT; 2min 3s ago
     Docs: https://github.com/Spotifyd/spotifyd
 Main PID: 4691 (spotifyd)
    Tasks: 3 (limit: 512)
   CGroup: /system.slice/spotifyd.service
           └─4691 /usr/bin/spotifyd --no-daemon

Apr 22 20:19:32 runeaudio systemd[1]: Started A spotify playing daemon.
Apr 22 20:19:32 runeaudio spotifyd[4691]: 20:19:32 [INFO] Using alsa volume controller.
Apr 22 20:19:32 runeaudio spotifyd[4691]: 20:19:32 [WARN] Failed to register IPv6 receiver: Os { code: 97, kind: Other, message: "Address family not supported by protocol" }
Apr 22 20:19:32 runeaudio spotifyd[4691]: 20:19:32 [INFO] Connecting to AP "gae2-accesspoint-a-26lh.ap.spotify.com:443"
Apr 22 20:19:33 runeaudio spotifyd[4691]: 20:19:33 [INFO] Authenticated as "xxxxxxx" !
Apr 22 20:19:33 runeaudio spotifyd[4691]: 20:19:33 [INFO] Using alsa sink
Apr 22 20:19:33 runeaudio spotifyd[4691]: 20:19:33 [INFO] Country: "VN"

Ema_82

Hello,
I'm new to RuneAudio and in the last few days I'm unsuccessfully trying to install spotifyd.
I have a Raspberry Pi 3 Model B with a Kuman SC07C Raspberry Pi HIFI DiGi+ Digital Sound Card (that I know it's more ore less equivalent to Hi-Fi Berry Digi+ and it uses the same driver). RuneAudio version is RuneAudio_rpi2_rp3_0.4-beta_
I followed all the instructions on https://github.com/Spotifyd/spotifyd/wiki/Installing-on-a-Raspberry-Pi and I uncommented the line dtoverlay=hifiberry-digi on config.txt.
But when I start spotifyd.service and check its status, I get what you read in the picture.

Can someone help me to understand what the problem is?

Thank you

Attachments

: spotifyd.jpg (93.72 KiB) Viewed 4787 times

janui

Hi Ema_82,

Ema_82 wrote...But when I start spotifyd.service and check its status, I get what you read in the picture...

Try running spotifyd like this:

spotifyd --help

You should get the help message and call instructions. But you may get an error message, if so please post it.
janui

Ema_82

Hello janui, thanks for the answer.

I get the spotifyd command list correctly. No error.

janui

Hi Ema_82,

Ema_82 wrote...I get the spotifyd command list correctly. No error...

Thats great, then try this:

/usr/bin/spotifyd --no-daemon

This is the line from spotifyd.service which is failing. You should get some more information by running it directly.
You may need to use this format in the 'ExecStart' line in spotifyd.service:

ExecStart=/usr/bin/spotifyd --no-daemon -c /etc/spotifyd.conf

janui

Ema_82

Thanks again janui,
this is what I get:

[root@runeaudio ~]# /usr/bin/spotifyd --no-daemon
22:41:13 [INFO] Using software volume controller.
22:41:13 [ERROR] Caught panic with message: called `Result::unwrap()` on an `Err` value: Os { code: 98, kind: AddrInUse, message: "Address already in use" }

dynobot

Ema_82 wroteHello,
I'm new to RuneAudio and in the last few days I'm unsuccessfully trying to install spotifyd.
I have a Raspberry Pi 3 Model B with a Kuman SC07C Raspberry Pi HIFI DiGi+ Digital Sound Card (that I know it's more ore less equivalent to Hi-Fi Berry Digi+ and it uses the same driver). RuneAudio version is RuneAudio_rpi2_rp3_0.4-beta_
I followed all the instructions on https://github.com/Spotifyd/spotifyd/wiki/Installing-on-a-Raspberry-Pi[b] and I uncommented the line dtoverlay=hifiberry-digi on config.txt.[/b]
But when I start spotifyd.service and check its status, I get what you read in the picture.

Can someone help me to understand what the problem is?

Thank you

Don't know why you modified the config.txt file....the instructions don't say anything about uncommenting lines in the config.txt file.

I use it with a HAT as well, no issues. I would suggest putting the config.txt file back to its original state and restarting the service. Use the service information found in the instructions exactly.

I have installed this maybe a dozen times or more on different types of configurations, RPi's with HATS work especially well with no volume control issues.

Ema_82

Already tried with untouched config.txt: same error

dynobot

Ema_82 wroteAlready tried with untouched config.txt: same error

I have a HiFi Digi+ on hand, I'll try it on my end and see what happens.

Just for kicks can you copy and paste the contents and locations of these three files.

spotifyd.conf
spotifyd.service
spotifyd

Also the output of aplay -L
Oh and did you enable the I2S kernel in settings?

Thanks
D

Ema_82

Thanks for the help but I have already turned off the pc and I can only do this test tomorrow.
I did not enable the I2S kernel

dynobot

Ema_82 wroteThanks for the help but I have already turned off the pc and I can only do this test tomorrow.
I did not enable the I2S kernel

No worries I can't get the Digi running right now either.

But you will need to enable the I2S kernel because the RPi communicates to the HAT via I2S as its plugged into the GPIO pins.

More than likely the I2S not being enabled is your problem....just enable it, let it load and reboot. Provided your files are in the correct locations and have the correct info in them you should be fine.

Ema_82

I'm at work, so I can't do the tests now, but I think it is useful to make some considerations:

1) RuneAudio, via its interface, works like a charm. I played music from a powered HDD without any problem and, when I tried it, I didn't have to change anything in the config.txt.
2) I'm pretty sure that the spotifyd files are in the correct paths.
3) I would tend to exclude that the problem could be in spotifyd.conf, considering that "Every field is optional; Spotifyd can even run without a configuration file" (https://github.com/Spotifyd/spotifyd)
4) The .service file is in folder path /usr/lib/systemd/system/ and, as you can see in the picture in my first post, it seems to be correctly found and loaded, but it stops immediately. So I think there is something wrong with this service, and maybe the log part I attached here could be useful to find what causes the problem.

dynobot

Ema_82 wroteI'm at work, so I can't do the tests now, but I think it is useful to make some considerations:

1) RuneAudio, via its interface, works like a charm. I played music from a powered HDD without any problem and, when I tried it, I didn't have to change anything in the config.txt.
2) I'm pretty sure that the spotifyd files are in the correct paths.
3) I would tend to exclude that the problem could be in spotifyd.conf, considering that "Every field is optional; Spotifyd can even run without a configuration file" (https://github.com/Spotifyd/spotifyd)
4) The .service file is in folder path /usr/lib/systemd/system/ and, as you can see in the picture in my first post, it seems to be correctly found and loaded, but it stops immediately. So I think there is something wrong with this service, and maybe the log part I attached here could be useful to find what causes the problem.

That line about everything being optional is not exactly true. You need spotify premium to use connect and the file has your credentials....

Ema_82

dynobot wrote
Just for kicks can you copy and paste the contents and locations of these three files.

spotifyd.conf
spotifyd.service
spotifyd

D

/root/.config/spotifyd/spotifyd.conf


[global]
username = USER
password = PASS
backend = alsa
device = card 1
# Given by `aplay -L`
mixer = PCM
volume-control = softvol
device_name = runeaudio
bitrate = 320
cache_path = /tmp/spotifyd
volume-normalisation = false
normalisation-pregain = -10

/usr/lib/systemd/system/spotifyd.service


[Unit]
Description=A spotify playing daemon
Documentation=https://github.com/Spotifyd/spotifyd
Wants=sound.target
After=sound.target
Wants=network-online.target
After=network-online.target

[Service]
ExecStart=/usr/bin/spotifyd --no-daemon
Restart=always
RestartSec=12

[Install]
WantedBy=default.target

/usr/bin/spotifyd

Here's also my RuneAudio debug info: https://pastebin.com/cn163Gw5

Please someone help me, I'm going crazy with this problem!

« Previous Page Next Page »