trying to wrap my head around volumio

I got a Raspberry Pi 2 quite a few years ago from my brother in the UK. It was cool to tinker with but ended up relegated to shelf only to be forgotten about. I had been using a small HTPC that has since died of old age to do my audio streaming. Now I need a new solution. I fell onto Volumio as it seemed to catch the most number of boxes for what I wanted in a music stream app taking me forward.

I have played with it on and off for about 6 months with some mixed results. I had it running on the Pi2 with a USB dac feeding into my Anthem AVM60, and for the most part it worked pretty good, but every so often it had sound hicups. I just upgraded to a Raspberry Pi HIFI DiGi+ board and connected it to the Anthem via spdif (RCA) and the sound problems seems to have gone away only to be replaced by a new issue.

Now when playing, it is as if the user interface just goes away on holiday for several seconds to sometimes up to 2 minutes. The web interface just goes totally unresponsive, for browsing the library to select music. Sometimes you have a list on the screen but cannot scroll up or down. most often the back button just doesn’t work and you have to press it multiple times before it goes back (and often then it goes back way too far) I’ve had it twice decide that the unit wants to go into a reboot spree where your web browser comes back as location unresponsive and you can hear the startup music from volumio every 20-30 seconds as it just keeps rebooting. To fix it, you need to pull the power from the Pi and when you plug back in all is fine again.

My setup has all my music pretty much residing on a Synology NAS and am connected via cat6 ethernet to the network (not wifi). My music is all FLAC and spread out over a sorted directory structure.

I really want to get something that works reliably. I know that Volumio has most of what I am looking for and am willing to wait and hope that the missing navigation features could and will be added in some future update. I am committed to trying to work this out and am wondering if it might be caused by my older Pi2. Would I gain any benefit moving to a newer and faster Raspberry Pi3+ to gain wifi (thus eliminating possible network issues?), a faster 64bit processor and a second board just in case it’s my old pi that is causing the issues.

Is what I am experiencing something that is known and easy to fix, or is this something that you start throwing time troubleshooting testing etc to try and work past?

Any help or insight is much appreciated

Matt

I took the huge leap of faith and just bought a new Raspberry Pi3b+. The problems with the pausing and everything going away seems to have resolved itself. I gather that getting a faster board in the setup fixes the timing issues were I gather that one process is not getting enough interrupts to take processor time for screen updates without affecting the sound produced.

Glad to hear that. I think that the pi zero is a nice concept, but the extra 30 euros for a PI3B+ are super worth it…

on first read, I was going to suggest trying a newer RPi3B or B+ and it seems that cured the problem.

I wonder if we need some hardware compatibility charts. The Pi2s (and 1s!) might not have enough processing power to handle lossless files in some conditions. Might also be worth profiling the web interface to see if there are any obvious performance improvements that can be made there.