raspotify: Can`t find Raspotify on device list
Compatible Device
- I’m running Raspotify on a compatible Device
Are you sure?
- I’m not trying to run Raspotify on a ARMv6 device
Compatible OS
- I’m running Raspotify on a compatible OS
Compatible Configuration
- I’m running Raspotify on a compatible Configuration
Latest Version
- I’m running the latest version of Raspotify
Are you sure?
- I’m not running Raspotify 0.31.8.1 on a on a Pi v1 or Pi Zero
Due Diligence
- I have done my due diligence
What happened?
I will hook up to this topic. Recently I`ve installed DietPi + Alsa + Raspotify. Everything worked till todays update (got a prompt in the system). After it i cant find Raspberry in Spotify app. I have reinstalled the system, installed Alsa, installed Raspotify just like I did before and it didnt work. Command sudo service raspotify status give back a message:
root@DietPi:~# sudo service raspotify status ● raspotify.service - Raspotify (Spotify Connect Client) Loaded: loaded (/lib/systemd/system/raspotify.service; disabled; vendor preset: enabled) Active: active (running) since Mon 2022-12-05 18:39:34 GMT; 46s ago Docs: https://github.com/dtcooper/raspotify https://github.com/librespot-org/librespot https://github.com/dtcooper/raspotify/wiki https://github.com/librespot-org/librespot/wiki/Options Process: 462 ExecStartPre=/bin/sleep 10 (code=exited, status=0/SUCCESS) Main PID: 522 (librespot) Tasks: 1 (limit: 4531) CPU: 161ms CGroup: /system.slice/raspotify.service └─522 /usr/bin/librespot Dec 05 18:39:24 DietPi systemd[1]: Starting Raspotify (Spotify Connect Client)… Dec 05 18:39:34 DietPi systemd[1]: Started Raspotify (Spotify Connect Client).
I assume everything should work, but it doesnt
Relevant log output and/or the contents of /etc/raspotify/crash_report if any
root@DietPi:~# sudo journalctl -u raspotify -b
-- Journal begins at Mon 2022-12-05 18:39:12 GMT, ends at Mon 2022-12-05 18:40:55 GMT. --
Dec 05 18:39:24 DietPi systemd[1]: Starting Raspotify (Spotify Connect Client)...
Dec 05 18:39:34 DietPi systemd[1]: Started Raspotify (Spotify Connect Client).
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 99
You’re welcome.
librespot defaults to software volume control. I’m just saying don’t fall for the lie that hardware volume control is always better than software volume control.
I personally set:
LIBRESPOT_INITIAL_VOLUME="100"andLIBRESPOT_VOLUME_CTRL="fixed"because I just use the volume control on my receiver. But that’s just personal preference.So now in
/etc/raspotify/confyou no longer need to manually specifyLIBRESPOT_DEVICEsince your DAC is now your “default” device. You do however wantLIBRESPOT_FORMATto beLIBRESPOT_FORMAT="S32"(make sure it’s also uncommented ofc)Thank you very much for all your help and efforts 😃
I know my login and password, and i think i know what else I should do. I`m installing the newest version of Raspotify now. Then will edit conf file. If something fails I will let you know for sure 😃
Thanks a lot for all your help, you are doing really good job with this project. Just keep on!
Go to your account overview page.
If you’re in the US:
https://www.spotify.com/us/account/overview/
Or you can click the the account link in the web client:
Well shit.
librespot supports
S16,S24,S24_3,S32,F32, andF64at 44100. For bit depth you want the highest your DAC will support.The reason being is that Spotify streams lossy audio and lossy audio doesn’t have a real bit depth it has to be quantized back to having a bit depth while converting it back to PCM so the higher the bit depth the less quantization noise and the more headroom for digital volume control.