Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compatible alsa device(s): empty #676

Open
1 task done
y-lobau opened this issue Sep 19, 2024 · 1 comment
Open
1 task done

Compatible alsa device(s): empty #676

y-lobau opened this issue Sep 19, 2024 · 1 comment

Comments

@y-lobau
Copy link

y-lobau commented Sep 19, 2024

Due Diligence

  • I have done my due diligence

What can we help you with?

Setup:

  • RPI 5 on a bookworm
  • librespot 0.5.0-dev
  • raspotify 0.44.0

Problem:
Raspotify is running but list of supported ALSA devices is empty. What may cause this?

sudo systemctl status raspotify
● raspotify.service - Raspotify (Spotify Connect Client)
     Loaded: loaded (/lib/systemd/system/raspotify.service; enabled; preset: enabled)
     Active: active (running) since Thu 2024-09-19 21:44:09 BST; 8s ago
rpi@rpi:~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: seeed2micvoicec [seeed-2mic-voicecard], device 0: 1f000a0000.i2s-wm8960-hifi wm8960-hifi-0 [1f000a0000.i2s-wm8960-hifi wm8960-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
rpi@rpi:~ $ librespot -B ?
[2024-09-19T21:06:42Z INFO  librespot] librespot 0.5.0-dev fb5c0ef (Built on 2024-09-17, Build ID: jyRJ1a0M, Profile: release)
Available backends: 
- alsa (default)
- pulseaudio
- pipe
- subprocess
librespot -d ?
[2024-09-19T20:45:37Z INFO  librespot] librespot 0.5.0-dev fb5c0ef (Built on 2024-09-17, Build ID: jyRJ1a0M, Profile: release)


        Compatible alsa device(s):

        ------------------------------------------------------

Then the Raspotify is not recognized by Spotify connect, and I assume this may be because there's no available device for librespot.

@kimtore
Copy link
Collaborator

kimtore commented Sep 20, 2024

Not exactly sure what this could be, your ALSA setup looks fine.
Perhaps the ALSA device is claimed by some other software running simultaneously?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants