Been nearly 24 hours loading Music Library

Volumio Information

Volumio Version: ? System Version 2.882
Hardware: Raspberry Pi 4, 4 GB, 12" iPad 1st gen
DAC: Schiit multibit

I am new to both Volumio and the Raspberry Pi. I got it build and installed and can access with the iPad. It’s been loading the Music Library (portable USB hard drive attached to the Pi) for nearly 24 hours how (rotating arrows)

I do have a fairly large library (7890 CDs so about 96,000 tracks) and I don’t know how to tell if this is “normal” for a first time or if something is wrong. I just clicked on Albums and after over a minute nothing happened. Occasionally something appears and I can get things to play, but it is VERY slow operating, and I assume that is because of the Music Loading.

Can anyone tell me what’s going on? Is this too large of a library for efficient use?

1 Like

After about 26 hours it stopped, so I guess the Music Library is loaded. If I “click” on Albums, after about 20 seconds, a page full of icons show up. If I scroll that page up, there is blank space which fills in after 15-20 more seconds.

So it seems to work, but doesn’t seem to handle a large library,…

1 Like

It would appear that you have a problem. This is frequently caused by “unexpected/corrupt/malformed” audio files that causes mpd library scanning to fail. Have a look in the system logs and see if there are any particular files flagged up (and try removing them).

Would you share some system logs please?

Preferable from a fresh reboot, with minimal steps to reproduce the problem :slight_smile:

Fresh reboot, clicked on albums and it’s been 4 minutes and still nothing appears. It’s mostly just non-responsive

It doesn’t shutdown either. Since it never has, I’m not sure what it’s supposed to do, but clicking shutdown on the iPad brings up a black screen with rotating white spots that never go away. (The light on the power cord is still red)

You are not alone, many have problems, many so-called “experts” give useless advices.
More than one year to struggle with that !
After Rpi 3+ I have Rpi 4 : same problem.
Tried 3 different hdds.
I even asked if someone had really managed to make Volumio with an USB HDD : nobody answered…
I only use Rpi with an external DAC, as an UPNP (with Foobar).
I give up :frowning:

1 Like

IMHO Volumio is bloatware.
I shift to Daphile or any working software…etc.

1 Like

The most common issue with an external HDD, is lack of power from the Pi. Either you need an external power supply to power the USB HDD or via the same power supply but with an additional power lead.

The pi is limited to a max power. When exceeded it will reduce the voltage on the USB to limit the total power, which causes all kind of strange behavior.
So far I’ve only been able to get this stable by using a HDD enclosure from KingDian (powered by the pi) and with an old HyperX enclosure form Kingston.

But it’s difficult to solve this on a remote basis, as we’re all are “so-called-experts”

1 Like

I have tried 3 different HDDs, each one with its own PSU :frowning:

1 Like

and the DAC, external powered?
Keep in mind that the MAX current for all 4 USB ports combined is 1.2A , so 0.3A per USB port. or any combination like 2 ports, 0.6A per port.

Are you able to monitor the voltage on the USB port, to see if there is a dip when powering the Pi?

1 Like

Yes, the DAC is a separately powered DAC/headphone amp. I don’t know how to monitor voltage of the USB port, but if that is the problem, I do have a powered USB hub I could use for the hard drive, and connect that to the Pi… but that’s close to what Sernly_57 did with no results

Am I correct in understanding that, when you select “Albums”, Volumio actually returns all the indexed albums in one go (7890 entries in this case)?

I am sorry but I have no other suggestion.

1 Like

Isn’t that what’s supposed to happen? Select Albums and they all show up?

Well, now when I select Albums nothing happens at all (or takes far too long for me to wait for it.) But a couple of days ago that appears to be what happened. I got one page of album icons, and scrolled it up and sure enough, about 20 seconds later the 2nd screen of albums appeared. Of course this is unworkable and I concluded this was possibly too big of a library

After these 2 pages have loaded, will it have the same delay next time you go into the albums and visit these pages?
As I can confirm that I’ve experienced this behavior occasionally. But only when the library is still being build. As the turning wheel is not very persistence while the library is being built.

1 Like

A sane implementation would provide pagination so that only a subset of the entries are loaded and returned each time for display. Pagination can be in the form of page numbers (like Google search results) or on-the-fly loading where further results are fetched as you scroll to the end of the page (like Facebook). If Volumio simply fetches and returns all albums in one go, then you can expect the response time to be slow with a library of your size. Basically this is what happens when you select Albums (someone correct me if I’m wrong):

  1. Volumio fetches data for all 7890 albums
  2. Volumio sends this data to the browser
  3. For each album, the browser queries Volumio for the album artwork (i.e. 7890 requests made within a short interval)
  4. Volumio fetches artwork and returns it to the browser (i.e. 7890 responses)
  5. Browser displays album data and artwork (all on a single page)

So there’s considerable load on the Volumio device, network and browser. All this contributes to the slow response time.

Subsequent loading of the same pages should be faster because of caching, but remember the browser would still have to handle 7890 objects even when they are loaded from cache, so response time would still be far from ideal.

I have around 900 albums and use Jellyfin running on a separate device for library management. You might want to check it out. You can cast audio to the Volumio device through the web interface Jellyfin provides (which is way way better than Volumio’s), or use the plugin that I wrote.

1 Like

IMO the Volumio FE <—> BE communication is showing signs of age and is quite rough around the edges. As I recall, the websocket calls are quite rudimentary, just passing around JS objects, and doesn’t really support pagination.

I wish this gets rewritten into something more modular and expandable soon (hopefully vue based) :crossed_fingers:

The right configuration is HDD no bigger than 2tb and in a cage with own power, every album in is own directory with the cover photo in it eliminate all the trush file like txt uncheck the option of cover search in internet is too slow for large collections

Already done !
You are talking about albums, or about directories ???
You mean that the cover (and back) must be inserted (tagged) in the album, rather than separate ?

Only the front if you put the back the app can take the back as cover