It suffices to add the symlinks:
sudo ln -s /opt/vc/lib/libdtovl.so /usr/lib/libdtovl.so
sudo ln -s /opt/vc/bin/dtoverlay /usr/bin/dtoverlay
sudo ln -s /opt/vc/bin/dtoverlay-pre /usr/bin/dtoverlay-pre
sudo ln -s /opt/vc/bin/dtoverlay-post /usr/bin/dtoverlay-post
After that dtoverlay command works 
FYI for those following the mpd2chromecast issue with this latest beta… I’ve pushed changes now to handle the absence of volume from the MPD server.
Please share logs and details of how to trigger the error, as I don’t have issues here…
just say how i can get the log ash btw is there a version 2.853 with a mpd upgraded to 0.21.16?
this is needed for the new youtube plugin …
Either from the /dev page using the livelog feature or via ssh.
# Volumio logs
journalctl -f
Note try to include minimal steps that triggers the issues you are facing to reduce noise in the logs
No clue, to be honest I haven’t run a jessie volumio image for a few years now, been either on Stretch or Buster…
@ashthespy i think it’s the wait between pressing buttons… of 30 sec…
now it’s seems to work on the 3.14… only bit slower than the 3.10
and getting pretty hot 67 °C added extra fan … 48°C
if i press a song i have to wait 30 sec before playing…and every song next…
System information plugin : if closed on pc stays open on rpi 7inch screen…
Version: 2020-12-10, version 0.014 on PI 4
Seeing an exception in mpd.log when changin songs.
Blockquote
Dec 16 20:13 : exception: Failed to open mixer for ‘alsa’: no such mixer control: PCM
Dec 16 20:13 : player: played “INTERNAL/Tango_3.0/01_Tango_Square.mp3”
Dec 16 20:13 : exception: Failed to open mixer for ‘alsa’: no such mixer control: PCM
Dec 16 20:13 : player: played “INTERNAL/Tango_3.0/02_Rayuela.mp3”
Dec 16 20:13 : exception: Failed to open mixer for ‘alsa’: no such mixer control: PCM
Dec 16 20:14 : player: played “INTERNAL/Tango_3.0/03_Desilusion.mp3”
Dec 16 20:14 : exception: Failed to open mixer for ‘alsa’: no such mixer control: PCM
Dec 16 20:16 : player: played “INTERNAL/Tango_3.0/02_Rayuela.mp3”
Dec 16 20:16 : exception: Failed to open mixer for ‘alsa’: no such mixer control: PCM
Dec 16 20:17 : player: played “INTERNAL/Tango_3.0/03_Desilusion.mp3”
Dec 16 20:17 : exception: Failed to open mixer for ‘alsa’: no such mixer control: PCM
What DAC (and type of pi) do you have? It looks like the mixer setup is having trouble for some reason.
Could you share output of:
aplay -l
cat /data/configuration/audio_interface/alsa_controller/config.json
amixer
Using a Pifi DAC+ on a Pi 4
{
"volumestart": {
"type": "string",
"value": "disabled"
},
"volumemax": {
"type": "string",
"value": "100"
},
"volumecurvemode": {
"type": "string",
"value": "logarithmic"
},
"outputdevice": {
"type": "string",
"value": "2"
},
"mixer_type": {
"type": "string",
"value": "Hardware"
},
"mixer": {
"type": "string",
"value": "Digital"
},
"volumesteps": {
"type": "string",
"value": "10"
},
"outputdevicename": {
"type": "string",
"value": "HiFiBerry DAC Plus"
}
}
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
Subdevices: 4/4
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
Subdevices: 4/4
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
card 2: sndrpihifiberry [snd_rpi_hifiberry_dacplus], device 0: HiFiBerry DAC+ HiFi pcm512x-hifi-0 [HiFiBerry DAC+ HiFi pcm512x-hifi-0]
Subdevices: 0/1
Subdevice #0: subdevice #0
amixer
Simple mixer control 'Master',0
Capabilities: pvolume pswitch pswitch-joined
Playback channels: Front Left - Front Right
Limits: Playback 0 - 65536
Mono:
Front Left: Playback 65536 [100%] [on]
Front Right: Playback 65536 [100%] [on]
Simple mixer control 'Capture',0
Capabilities: cvolume cswitch cswitch-joined
Capture channels: Front Left - Front Right
Limits: Capture 0 - 65536
Front Left: Capture 65536 [100%] [on]
Front Right: Capture 65536 [100%] [on]
Seeing the same exception in mpd.log on a Pi3.
Only seeing the exception when changing tracks with forward and back arrows in the UI.
Pi 3 / HiFi DAC HAT PCM5122
------------------------------
**Dec 17 06:21 : player: played "INTERNAL/1964_Live_at_Peps/05_Gee_Sam_Gee.mp3"**
**Dec 17 06:21 : exception: Failed to open mixer for 'alsa': no such mixer control: PCM**
**Dec 17 06:21 : player: played "INTERNAL/1964_Live_at_Peps/06_Rogi.mp3"**
**Dec 17 06:21 : exception: Failed to open mixer for 'alsa': no such mixer control: PCM**
-------------------------------
volumio@v2:/var/log$ aplay -l
card 2: BossDAC [BossDAC], device 0: Boss DAC HiFi [Master] pcm512x-hifi-0 [Boss DAC HiFi [Master] pcm----------------------------
volumio@v2:/var/log$ amixer
Simple mixer control 'Master',0
Capabilities: pvolume pswitch pswitch-joined
Playback channels: Front Left - Front Right
Limits: Playback 0 - 65536
Mono:
Front Left: Playback 65536 [100%] [on]
Front Right: Playback 65536 [100%] [on]
Simple mixer control 'Capture',0
Capabilities: cvolume cswitch cswitch-joined
Capture channels: Front Left - Front Right
Limits: Capture 0 - 65536
Front Left: Capture 65536 [100%] [on]
Front Right: Capture 65536 [100%] [on]
Hmm, does volume control work fine for you from the VolumioUI?
I need some more debugging info
cat /etc/mpd.conf
# Replace <card_num> with the card number from `aplay -l` that matches your card
# So if you dac is card 2, command is amixer -c2 scontrols
amixer -c<card_num> scontrols
FYI I can also recreate the same error in mpd.log:
Dec 17 09:18 : exception: Failed to open mixer for ‘alsa’: no such mixer control: PCM
In my case, there is no add-on card… output is set to HDMI, mixer to hardware and MPD Clients Volume Control set to off. All of these are defaults as far as I can tell. While I can see the error, tracks do in fact change fine when clicking next/previous.
If I enable MPD Clients Volume Control, MPD will restart and then that error no longer appears in the mpd log.
That log entry seems to be from MPD. When that “clients volume” option is off on this new beta, the MPD status no longer provides a volume level and it’s possible the issue is tied to that somehow where it tries but fails to determine the volume.
Looks like there is mismatch in the mpd configuration options that Volumio sets (old mpd version).
If you can share /etc/mpd.conf when you face the errors, (and mpd.log warnings about the missing/redundant config options, will start adjusting things for that as well)
Yes I fixed it some time ago but never published it… Maybe this weekend 
oke tnx balbuze we looking forward for it 
Done!
tnx, balbuze gonna test it where did you put it ? url plz…
best regards,
dvo
30seconds it probably how long it takes to download the track from youtube. I am not aware of what/how it is doing this, but that is probably also the reason for the high CPU usage.
Please check if the 30s song changes are also present with local tracks, or Spotify/tidal for example?