sorry for late response, I’ve been busy with work
I just got a 4.3" DSI touchscreen, I’ll use that one for testing the plugin on RPi.
If I will manage to have my 3.5" SPI running with my RockPi S I can also try the plugin on that one
That would be helpful. If you should not start from a fresh system and have already attempted to install the touch display don’t forget to remove chromium-browser before you install touch_display_1_1_9beta01.
For future versions of the plugin I am currently extending the uninstall script to remove the packages the plugin pulled in.
I just destroyed the sd-card I was using for testing, I’m flashing the latest image on a new one from scratch, it will be a fresh system 
I did some testing on following configurations:
and
I had no issue with both of them.
With Buster-based setup I also tried to reboot from UI and to rotate the screen (with display_lcd_rotate=1 and selecting 90deg under plugin options). Both of them work fine for me.
Well done!
1 Like
Thanks for the builds.
For some reason installing cec-utils seems to break it. I’m getting kernel errors on startup. It was working a while ago (can’t remember what build). I have installed kodi using saiyato’s script.
New version of the Touch Display plugin: touch_display_1_1_9beta02.zip (849,4 KB)
Mainly uninstall.sh has been extended: Uninstalling the plugin now removes the packages that got installed by the plugin.
hi,
i’ve tried the latest buster-img 3.008 on a pi3 with hifiberry dac adc pro. looking good, simple equalizer plugin functional.
i only noticed little misbehavior so far:
-
volume-slider always jumps to 100 after any setting, but volumio plays at the correct level.
-
the music library states ‘no item’, volumio did not scan after installation. maybe there was a problem mounting my usb-ssd-harddisk. however, after a reboot i started scanning manually, worked.
-
on my pc, after a reboot the gui is always flashing X times before becoming accessable, where X is the number of items in the actual playlist, in the logs these entries loop for every playlist item while “node” process is between 30-100% cpu load:
Aug 13 14:56:29 volumio volumio[889]: info: Listing playlists Aug 13 14:56:29 volumio volumio[889]: info: CoreCommandRouter::volumioGetQueue Aug 13 14:56:29 volumio volumio[889]: info: CoreStateMachine::getQueue Aug 13 14:56:29 volumio volumio[889]: info: CorePlayQueue::getQueue Aug 13 14:56:31 volumio volumio[889]: info: CoreCommandRouter::volumioGetState Aug 13 14:56:31 volumio volumio[889]: info: CorePlayQueue::getTrack 0 Aug 13 14:56:31 volumio volumio[889]: info: CoreCommandRouter::executeOnPlugin: multiroom , getMultiroom Aug 13 14:56:31 volumio volumio[889]: error: Could not retrieve plugin audio_interface multiroom Aug 13 14:56:31 volumio volumio[889]: info: CoreCommandRouter::volumioGetVisibleSources Aug 13 14:56:31 volumio volumio[889]: info: CoreCommandRouter::executeOnPlugin: my_music , getDisabledSources
- rotary encoder plugin fails to start, logs complain that it was compiled under a previous node.js version. after a reboot system did not start until i deleted the folder “/data/plugins/user_interface/rotaryencoder” via ssh.
after all, thanks a lot guys, looks very promising, i will test further.
regards,
phil
phil you can decrease volume by setting max in the setting …
not sure what you mean, but if change the max-volume-value in the playback settings it has no effect right after, but after a reboot volumio sets the volume of the dac to 100%, the sliderbar states “NaN/100”, and the volumecontrol is no longer working.
i will take fresh image without the equalizer-plugin and test again.
the equalizer is bugging with some install’s i think the old node.js was version 12
tested now without plugins, setting a max-value has simply no effect all. i can still go to the maximum volume of my 60w-hat-amp.
further testing:
-
i noticed, that the volume-slider only jumps to 100 when volumio is playing. if it’s paused the slider stays at the selected position until i click play again.
-
i further noticed that when volumio is paused, after the first click on that volume-ring the selected value stays (on the slider too). second click 100, third click stays again, then again 100, and so on.
-
the volume-/+ buttons below the ring do work, but are setting the ring/slider always to 100, even if volumio is paused.
-
the mute button only mutes and does not switch to green color, and isn’t unmutable by another click. for this i have to click vol+/- or the slider.
-
using the mousewheel on the ring-control works, but also jumps to 100 after a second. then again using the mousewheel volumio shifts the 100% to the dac. huh, neighbours are jumping to 100 now, too
except the last point, all these are only visual issues, the volume i set is always what i hear.
i would say try a older build … maybe that will work…
it’s about volumio3-debugging here, not volumio2 
I’m just bringing up issues with the new debian-buster image.
i’m planning rfid-reader plugin (pi-rc522 without cpu-issues), but that will require python3.5>=, so i’m really interested in the buster-based image.
you got a point there phil977 … i’m interested in the 64bit version…
gonna try the last beta 
it seems that if you rewite the eeprom to 64 bit it doesn’t start 32bit any more
on ssd and sd card… so are there any 64bit images?
I reverted back to node v8.x to avoid plugin compatibility issues. This also lets me go back to the default Volumio Node back end repo, instead of my custom fork for the node v12/14 compatibility.
Raspberry Pi Volumio-3.009-2020-08-21-pi
I also thought I’d add more fun to the mix – a build with 5.4 kernel
Raspberry Pi Volumio-3.010-2020-08-21-pi
- Music library doesn’t seem to auto detect the USB disk if plugged in during the first boot. If you boot up and then plug in the disk, does it work without a reboot?
- For the volume issues, I opened an issue a while ago about it, but didn’t investigate in detail. Can you counter check if the new versions also exhibit these issues?
- You should be able to use the rotary encoder plugin without having to recompile the native
node_modules.
EDIT:
As @Darmur figured out, it would seem that the version of Nodejs is wrong for armv6 - so you’ll need the fixup script again to get these builds up and running on Rpi0/1 boards. Apologies for that!
PS: Set NODE_VERSION=8. I’ll fix this in the next build.
I spent some time testing those two releases, most of the small issues present in the previous releases are now gone, most probably they were due to different node version used.
Some observations:
- Both releases work fine on RPi0 after applying the nodejs script from @ashthespy, don’t forget to change version from 14 to 8 otherwise you will get a gray screen at boot (UI not loading)
- BassOwl drivers integrated in 4.19 release work fine, I already sent a pull request to official Volumio repository for adding BassOwl on the dacs.json list
- Kernel 5.4 behaves differently compared to kernel 4.19 regarding I2S DAC mapping. to always have I2S DAC mapped to card2 (hw:2,0) it is required to use a different argument on cmdline.txt
For 4.19
snd-bcm2835.enable_compat_alsa=1 snd_bcm2835.enable_headphones=1
For 5.4
snd-bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_headphones=1
If string for 4.19 is used on 5.4 (like it is right now in 5.4 build), I2S DAC is mapped as card3.
I’ve been testing this on RPi0 only at the moment, I need to confirm for other RPi versions too.
Is there a way to install cec-client without breaking this?
Thanks
I wonder if it is more to do with my node12 fork not being synced to current master. Will investigate later!
Thanks for that heads up, will toggle compat to 0 for the 5.4 kernel.
Sure, cec-utils should install out-of-the-box as I’ve included libcec4 into the image. If not, remove the kernel pinning and install it - but this is untested.
cd ~
sudo mv /etc/apt/preferences.d/raspberrypi-kernel ./
sudo apt install cec-utils
tried the latest 5-4-img on a pi 3 + hifiberry amp2 (which is autodetected as hifiberry dac+ by wizard).
- sound is only working when i change “hw:2,0” to “hw:3,0” in /etc/mpd.conf, because of
volumio@volumio:~$ aplay -l | grep hifiberry
card 3: sndrpihifiberry [snd_rpi_hifiberry_dacplus], device 0: HiFiBerry DAC+ HiFi pcm512x-hifi-0 [HiFiBerry DAC+ HiFi pcm512x-hifi-0]
-
startup sound isn’t working anymore
-
volume is stuck at maximum, with no possibility to change it.
-
slider/ring-position is no longer jumping to 100.
-
no longer issues with startup-flickering of gui and enabling rotary encoder plugin.
-
i verified via ssh that the usb-ssd is mounted and accessable before starting the wizard, but still no music library/usb after the wizard ends.
-
manual scan did succeed now without having to reboot.
however, i catched this before i changed the mpd.conf, right after a reboot:
volumio@volumio: ~avolumio@volumio:~$ sudo journalctl -f
Aug 23 14:36:57 volumio mpd[1142]: config_file: config parameter “id3v1_encoding” on line 99 is deprecated
Aug 23 14:36:57 volumio mpd[1142]: Aug 23 14:36 : exception: Failed to bind to ‘[::]:6600’
Aug 23 14:36:57 volumio mpd[1142]: Aug 23 14:36 : exception: nested: Failed to bind socket: Address already in use
Aug 23 14:36:57 volumio systemd[1129]: e[0;1;39me[0;1;31me[0;1;39mmpd.service: Main process exited, code=exited, status=1/FAILUREe[0m
Aug 23 14:36:57 volumio systemd[1129]: e[0;1;39me[0;1;31me[0;1;39mmpd.service: Failed with result ‘exit-code’.e[0m
Aug 23 14:36:57 volumio systemd[1129]: e[0;1;31me[0;1;39me[0;1;31mFailed to start Music Player Daemon.e[0m
Aug 23 14:36:57 volumio systemd[1129]: Reached target Default.
Aug 23 14:36:57 volumio systemd[1129]: Startup finished in 1.572s.
To fix this issue, instead of changing /etc/mpd.com please edit /boot/cmdline.txt
snd-bcm2835.enable_compat_alsa= 0