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
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)
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?
shall i put my 3.10 version into it … and show you the difference i got 255 down and 25 up and 1 gbit lan …
it should not take so long ash… the 3.10 starts direct…
Sure, but it would be way faster to confirm that it only happens with this plugin - and then start debugging with the plugin dev why/what could be causing the delay/high cpu usage…
@ashthespy
4% use … 48degrees celsius it’s not only the plugin the 3.10 is really fast…
gonna switch my card … to 3.10 Average load: 4%, Temperature: 48°C, same plugin’s, same settings, same playlist on youtube, 2sec. load and play (i could say it plays direct not even 2sec. ) instead of 30 sec. so load time you can skip… rpi 4 / 4gig yessssssssss! no same adapter only different version of 3.10 or 3.14
i will make a log from this one … ok… it’s not the plugin it’s overall slower responce …
and even with the 2.xx i have a slower responce it’s not a plugin …
@dvo - I am not contesting your net speeds - but just pointing out, that this seems to be an issue particular to one specific plugin. Correct? Or do you have this lag b/w song changes with all playback?
If it is on all types of tracks, then I we need to really spend some time debugging.
If it only with this particular plugin, then I request that the plugin dev to investigate what changed in b/w 3.10 (5.4.59) and 3.14(5.4.79) that could have such a significant impact… Probably some networking quirk on the ethernet adapter driver in the newer kernel? who knows!
