Volumio Debian Buster Beta - Raspi images debugging

@ashthespy the difference between the 3.10 and the 3.14 is the implementation of my volumio to…:wink:

Pi 3 / HiFi DAC HAT PCM5122
Same results here, the exception disappears if ‘MPD Clients Volume Control’ is enabled.

I’m sorry @dvo but those logs don’t give me any new ideas - I would suggest again that you request the plugin’s developer do some debugging to help figure out what it could be.

Sure, and over ~3500 commits b/w the 5.4.59 kernel in 3.10 and 5.4.79 kernel in 3.14…
(the reason I bring this up is because I’m currently debugging a network issue on my pi4 with 5.4.79 and particular switch setups that wasn’t there on 5.4.59 kernel…)

Either way it would be good to isolate first if the source of this problem that shows up only while using this plugin. Or do you face this high cpu+delay issue with other sources as well?

no overal the version is slow as hell … 30 sec between actions… is 2 mutch …

Can you send me a log?

they are above 2 2x… 3.10 and 1 3.14 live log and journal . in 1 of both…

Like I said before, those logs don’t help… If you’d like me to try and help figure out why only you seem to have such a slow system, then please provide the logs as described in that link…

Unfortunately I’m not psychic and can’t look into a crystalball and figure out what is wrong with each unique system, can only look at logs and try and guess what is wrong :wink:

In the meantime, did you confirm that this slow 30sec b/w track changes is ONLY when you use this plugin? That would really save a lot of time, because no one else seems to be complaining about a slow system so far…

i just finished logging for the youtube plugin there was a bug to … with the playlist…

now can i start your logging do you want both?
and if you wait long enough outside you will have crystal balls for shure…

3.14 tested local is direct … and radio switch from channel 25 sec… and youtube 42.7 sec

Hi ashthespy!

Your job is wonderful! I thank you very much for doing it.

After a week I ran a test of Raspberry Pi Volumio-3.014 and got the following results:
Good sound, fast speed. I love it.
The problem has been resolved:
1- My volumio works well
2- Touch Display works well
3- I2S Pi4 works well.
4- youtube 2 works well.

The problem is not working yet:

Airplay is not working.
App mconnect not connected.

Thank you very much!
Mac

Hello,
I 3ant to switch also to buster, but I have some questions :
Qobuz will work?
My I2C 13 inch display will work?
Also radios stations are there?
Thanks

@mac
Glad your enjoying it :slight_smile:
could you check if shairport-sync is up and running?
From a console try

$ systemctl list-units --failed
# You probably would see that both shairport-sync and upmpdcli have failed?
# So then check why they have failed with 
journalctl -u shairport-sync.service
# similarly for other failed services in the above list

If you don’t see shairport-sync it could be that the service was not included. I recall there were initially some issues, so please confirm with

systemctl list-units | grep shairport
$ which shairport-sync
# Should be /usr/local/bin/shairport-sync
$ shairport-sync --version
# Should be 3.3.6-OpenSSL-Avahi-ALSA-soxr-metadata-dbus-sysconfdir:/etc
# If we have shairport-sync, then it's just a matter of creating the proper service file for it again
sudo wget "https://raw.githubusercontent.com/volumio/Build/13c723d98523acfdb1d282b7aa95a6b74d33cad8/
volumio/lib/systemd/system/shairport-sync.service" -O /lib/systemd/system/shairport-sync.service
# Confirm that it's in the there 
cat /lib/systemd/system/shairport-sync.service
systemctl daemon-reload
systemctl start shairport-sync
systemctl status shairport-sync
systemctl strop shairport-sync
# Now restart Volumio's Node Back end 
systemctl restart volumio
# and you should be good!

Let me know if that works for you :slight_smile:

Yes 014 version has Qobuz :slight_smile:
Radio stations as in Webradio? yes also there
For the display it depends on which plugin you are using, but it should work, if not we need to figure out why and fix it!

Great :slight_smile: since I have some spare SD card I will try it.
I use mpd_oled plugin for I2C display.
https://github.com/antiprism/mpd_oled
This thing keeps me busy :)). I like it.

Ah as far as I recall @Adrii’s mpd_oled already works on the buster builds…

Great. :slight_smile:
Also gpio buttons plugin is available?

Yep, all plugins should be available - if something doesn’t work please report so that things can be fixed here, or in the plugin as required :slight_smile:

Understood the message :slight_smile:
Sory one last question.
Qobuz has the latest implementation as in stable release? The beta one

To be honest, I don’t use myvolumio, so can’t say. :smiley:
As far as I understand, all the myVolumio stuff happens on Volumio’s servers, so it should be the same…

@volumio since I want to switch to buster, the qobuz implementation is the last one? As on stable release. Thanks

I tried also this buster release, all is working fine but sound does not play.
I got an error "Error Failed to open “alsa”: Failed to open ALSA device “hw:2,0”: No such file or directory

Any idea what’s wrong here?

Without logs, we are blind…

Also of interest - what device, what DAC, etc etc…

Logs are either from the /dev page using the livelog feature or via ssh.

# Volumio logs
journalctl -f 

# Look at what outputs are recognised 
aplay -l