I’ve just tried to record some additional records for IR-Remote config.
.
Now I connot play music anymore…
Any idea?
Reboot doesn’t help.
GUI is there, I can select spotify songs (nothing other done than this) but I cannot PLAY anymore.
Neither from spotify, nor from Web nor from volumio app.
Skipping songs with remote works, volume up/down as well.
Play don’t work----
HELP!
Dear @Wheaten ,
NO, play doesn’t work in any of the accessible GUIs - neither web nor app nor playing via spotify app.
System is currently booting, will send a log URL shortly.
In the meantime I’ve tried a local MP3 file - ran into “Error Failed to open “alsa” (alsa). Failed to open alsa device “volumio” no such device”…
because I’m brand new in this forum I get blocked if posting more than three times (happened in the IR-Thread - reason for this posting) so I guess I have to update this single entry again and again …
Feb 14 22:09:46 volumio volumio[1069]: warn: Spotify API method getTrack failed due to "Too many requests". Stop all API requests for 10000 milliseconds.
Feb 14 22:09:46 volumio volumio[1069]: warn: Spotify API method getTrack failed due to "Too many requests". Stop all API requests for 10000 milliseconds.
Feb 14 22:09:46 volumio volumio[1069]: warn: Spotify API method getTrack failed due to "Too many requests". Stop all API requests for 10000 milliseconds.
Please use these steps.
Clear your queue
Reboot device
Load a single track or album, instead of huge play lists.
And try again.
At least I have disabled the DAC card (HAT) and the alsa-error is gone - can play a MP3 through headphone-jack…
Weird…
I will last the system for a while.
API call is “understandable” but when I try to play via Spotify App - there is no API call and this doesnt work either …
Really strange…
DAC is re-enabled again…
Works now after reboot.
Plays the playlist but volume control is not working…
(REALLY weird) (via GUI it is scattered and doesn’t do anything, via IR-Remote at least volume level is displayed and changed but loudness is unchanged…
here config and userconfig:
volumio@volumio:~$ cat /boot/config.txt
### DO NOT EDIT THIS FILE ###
### APPLY CUSTOM PARAMETERS TO userconfig.txt ###
initramfs volumio.initrd
gpu_mem=128
gpu_mem_256=32
gpu_mem_512=32
gpu_mem_1024=128
max_usb_current=1
[pi5]
usb_max_current_enable=1
[all]
include volumioconfig.txt
include userconfig.txt
#### Volumio i2s setting below: do not alter ####
dtoverlay=hifiberry-dacplus
volumio@volumio:~$ cat /boot/userconfig.txt
# Add your custom config.txt options to this file, which will be preserved during updates
# Power-LED vom Raspberry Pi abschalten
dtparam=pwr_led_trigger=none
dtparam=pwr_led_activelow=on
# Status-LED vom Raspberry Pi abschalten
dtparam=act_led_trigger=none
# dtparam=act_led_activelow=on
volumio@volumio:~$
THANKS a LOT for your time and effort!
Ralf
(I’m tired now and go to bed…)
Will try anything else tomorrow…
Did you check to which GPIO you can connect your IR-Receiver?
As your DAC need a few of them and HB is not a fan of sharing them.
As your issues started when adding additional commands to lircd.conf.
Dear @Wheaten , thanks again!
Yes, indeed I did check the GPIO usage of HifiBerry upfront.
I have HifiBerry DAC 2 plus which uses GPIO2&3 and GPI18 to GPIO21.
My first attempt was using GPIO25 (standard) and afterwards 23 (because 25 doesn’t work).
Left it on 23 and then found the hack with the IR_signal recording.
So currently IR is still connected to GPIO23, wich is not used by HAT DAC.
To my surprise “wait and see” seems to have solved the problem.
Today in the morning i started the Pi after being off the whole night.
Works OK.
Volume control still didn’t work.
So I’ve re-configured to headphone-jack, rebooted, Again reconfigured to DAC - rebooted.
NOW it works as expected…
First of all I now will copy the SD card in this stable state
Thanks a LOT for all your activity and contribution.
Warm regards,
Ralf