@guyp2k
There will be some good news about it soon.
I can assure you that @2aCD is working on some new features on the screensaver work also me working on that. I already have that working with the @balbuze peppymeter plugin and alsa modular…still work in progress. Would be good to merge also balbuze in the way but i guess he’s pretty busy with the development of some new plugins for Volumio Buster.
Best Regards
Hello. For sure we can merge all improvement. I didn’t follow exactly what has been done, but if you point me exactly what you need, I will integrate it. Or if someone else want to do it, no problems!
Hey!
Nice to hear that @balbuze !
I really hope that chance to be true for all the members and to be official plugin on Volumio Buster 
@2aCD is making an awesome work and big improvements on the screensaver vumeter with infos.
So let’s just wait that and then if @2aCD also wants to merge it, we can do it for all members and push commits to GitHub
I dont want to mess with your work or @2aCD work 
Best Regards
Thanks @balbuze for the reply and to answer your question, using your peppymeter plugin, would it be possible to add the ability function as a screensaver instead of a permanent overlay i.e., when ever you press play/pause from an app the Volumio UI is available and once you press play, peppymeter is visible again. Lastly, if you touch the Volumio display the UI would appear and once you press play, peppymeter is engaged again.
Thanks
If someone point me where to find the modified version, I would update the plugin 
First problem. Updating the UI results to a non updatable system without resetting it…
Understood…
Thanks
One issue I came across I think is related to @balbuze peppymeter plugin, is if I play a file greater than 44.1/16 I receive the following error:
Error
Failed to open ALSA (alsa) faild to
open alsa device “volumio” snd_pcm_hardware_params_set_buffer_time_near_failed() illegal argument
If I uninstall the plugin, no issues. Volumio 3.074 and HIFIBerry DAC2HD.
Thanks
i cant get the pepptmeter work on my intel nuc on volumio3 buster
here is the error from Xorg.0.log
[ 35.827]
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[ 35.827] Build Operating System: Linux 4.19.0-12-amd64 x86_64 Debian
[ 35.827] Current Operating System: Linux volumio 5.10.35 #1 SMP Fri Jan 22 21:30:44 CET 2021 x86_64
[ 35.827] Kernel command line: BOOT_IMAGE=/vmlinuz biosdevname=0 splash plymouth.ignore-serial-consoles quiet ro rootwait imgpart=UUID=57e8d8c6-13b2-47f7-9726-80ce12b1407f bootpart=UUID=D83A-828B datapart=UUID=15ab55b1-0e82-413c-aefb-4e10eabae8cf imgfile=/volumio_current.sqsh logo.nologo vt.global_cursor_default=0 acpi_backlight=vendor use_kmsg=yes net.ifnames=0 loglevel=0
[ 35.827] Build Date: 01 December 2020 05:59:57PM
[ 35.827] xorg-server 2:1.20.4-1+deb10u2 (Debian -- Support)
[ 35.827] Current version of pixman: 0.36.0
[ 35.827] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 35.827] Markers: (–) probed, () from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 35.827] (==) Log file: “/home/volumio/.local/share/xorg/Xorg.0.log”, Time: Fri May 28 01:36:58 2021
[ 35.836] (==) Using system config directory “/usr/share/X11/xorg.conf.d”
[ 35.836] (==) No Layout section. Using the first Screen section.
[ 35.836] (==) No screen section available. Using defaults.
[ 35.836] () |–>Screen “Default Screen Section” (0)
[ 35.836] (**) | |–>Monitor “”
[ 35.836] (==) No monitor specified for screen “Default Screen Section”.
Using a default monitor configuration.
[ 35.836] (==) Automatically adding devices
[ 35.836] (==) Automatically enabling devices
[ 35.836] (==) Automatically adding GPU devices
[ 35.843] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 35.843] (WW) The directory “/usr/share/fonts/X11/cyrillic” does not exist.
[ 35.843] Entry deleted from font path.
[ 35.847] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 35.847] (==) ModulePath set to “/usr/lib/xorg/modules”
[ 35.847] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 35.847] (II) Loader magic: 0x55706b214e20
[ 35.847] (II) Module ABI versions:
[ 35.847] X.Org ANSI C Emulation: 0.4
[ 35.847] X.Org Video Driver: 24.0
[ 35.847] X.Org XInput driver : 24.1
[ 35.847] X.Org Server Extension : 10.0
[ 35.847] (EE) systemd-logind: failed to get session: PID 1071 does not belong to any known session
[ 35.848] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 35.860] (–) PCI:*(0@0:2:0) 8086:193b:8086:2064 rev 9, Mem @ 0xdb000000/16777216, 0x90000000/268435456, I/O @ 0x0000f000/64, BIOS @ 0x???/131072
[ 35.860] (II) LoadModule: “glx”
[ 35.861] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 35.889] (II) Module glx: vendor=“X.Org Foundation”
[ 35.889] compiled for 1.20.4, module version = 1.0.0
[ 35.889] ABI class: X.Org Server Extension, version 10.0
[ 35.889] (==) Matched modesetting as autoconfigured driver 0
[ 35.889] (==) Matched fbdev as autoconfigured driver 1
[ 35.889] (==) Matched vesa as autoconfigured driver 2
[ 35.889] (==) Assigned the driver to the xf86ConfigLayout
[ 35.889] (II) LoadModule: “modesetting”
[ 35.892] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 35.895] (II) Module modesetting: vendor=“X.Org Foundation”
[ 35.895] compiled for 1.20.4, module version = 1.20.4
[ 35.895] Module class: X.Org Video Driver
[ 35.895] ABI class: X.Org Video Driver, version 24.0
[ 35.895] (II) LoadModule: “fbdev”
[ 35.895] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 35.896] (II) Module fbdev: vendor=“X.Org Foundation”
[ 35.896] compiled for 1.20.0, module version = 0.5.0
[ 35.896] Module class: X.Org Video Driver
[ 35.896] ABI class: X.Org Video Driver, version 24.0
[ 35.896] (II) LoadModule: “vesa”
[ 35.896] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 35.899] (II) Module vesa: vendor=“X.Org Foundation”
[ 35.899] compiled for 1.20.1, module version = 2.4.0
[ 35.899] Module class: X.Org Video Driver
[ 35.899] ABI class: X.Org Video Driver, version 24.0
[ 35.899] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 35.899] (II) FBDEV: driver for framebuffer: fbdev
[ 35.899] (II) VESA: driver for VESA chipsets: vesa
[ 35.899] (EE)
Fatal server error:
[ 35.899] (EE) parse_vt_settings: Cannot open /dev/tty0 (Permission denied)
[ 35.899] (EE)
[ 35.899] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 35.899] (EE) Please also check the log file at “/home/volumio/.local/share/xorg/Xorg.0.log” for additional information.
[ 35.899] (EE)
[ 35.900] (WW) xf86CloseConsole: KDSETMODE failed: Bad file descriptor
[ 35.900] (WW) xf86CloseConsole: VT_GETMODE failed: Bad file descriptor
[ 35.900] (EE) Server terminated with error (1). Closing log file.
Blockquote
Hi @balbuze
I tried to install the volspotconnect2 from the alsa_modular branch following the instructions given. I get an error in the service.
The status volspotconnect2.service command returns the below
ExecStart=/bin/bash /data/plugins/music_service/volspotconnect2/startconnect.sh (code=exited, status=127)
and the journalctl -f -o cat -u volspotconnect2.service returns the below
/data/plugins/music_service/volspotconnect2/startconnect.sh: line 4: ./vollibrespot: No such file or directory
The plugins UI shows the plugin as active.
I am running the volumio beta version 3.077 on my Minix Z64 and the vollibrespot-i686.tar.xz was downloaded and extracted successfully.
Please let me know if there is anyway to resolve the issue. I can help with the logs needed.
Regards
Ashok
Hello. I didn’t check but my guess is that this i686 version of vollibrespot is not Compatible with i686… The install.sh shouldn’t allow to install it.
Hi @ashthespy
Will you please advise if there is anyway to get the vollibrespot-i686 to work on the X86_64 systems running buster beta versions.
Did you try
dpkg --add-architecture i386
It should be trivial, but I haven’t found the time to add x64 builds to the system…
I tried now
The packages listed there are the prebuilt ones - the i686 build should work on Debian’s i386
I tried now. It did not work.
I still get the message
/data/plugins/music_service/volspotconnect2/startconnect.sh: line 4: ./vollibrespot: No such file or directory
i can see that dpkg --print-foreign-architectures now shows i386 in my system
Am i missing something
Yes, the binary is built for a different architecture i686 (32bit), you are trying to run on x86_64 (64bit).
Try launching the binary, and it should complain about an invalid format.
cd /data/plugins/music_service/volspotconnect2/
file ./vollibrespot
When i tried these commands, i get
-bash: ./vollibrespot: No such file or directory
Though i can see vollibrespot when i do the ls command.
Mine has the amd64 architecture. Is there any chance a binary will be available for this architecture.
You can also compile it your self if you are inclined – GitHub - ashthespy/Vollibrespot: Spotify Connect daemon for Volumio