I have also changed these values in mpd.conf and it seems to be working fine now. It is still scanning and will be busy for a while as I have over 275K tracks to import, will post an update when it (hopefully) reaches the end…
max_playlist_length to “81920”
max_output_buffer_size to “81920”
Editing mpd.conf with the values suggested and then restarting MPD (via systemctl) has improved things for me.
The scan completes and I have re-gained access to my library. No errors in mpd.log. I hope this persists,
All good for me, the import has completed… browsing the library really is painfully slow and if I open the list of albums the interface crashes… but one thing at the time, at least all my music is there
The posted suggestion is still working for me – 11 hours and a re-boot later. Similar to what amatala reported , though, the system is sluggish – cover art doesn’t appear, or appears only very slowly, refreshing the browser display is slow and so on. But there is no memory allocation exception reported in mpd.log and playback seems fine so far.
Since version 2.729 it stopped working again for me and I’ve been waiting for an update for weeks now… Need to give up on this as it’s clearly not stable enough to used in decent conditions…
I didn’t have any luck with newer versions than 2.699. Any more recent would have the same issue as described here. 2.699 is the most stable version I’ve found and I’m sticking to it, give it a try.
The issue originates by some buffer sizes of MPD (which can allow to browse big libraries without problems). Issue is, they work on some platform while they absolutely don’t in others. We need to understand how\where they work.
SIDE NOTE: We are working on our own database engine which will be able to handle 1) Big libraries 2) Libraries with corrupted files. Its about one year we work on that, not easy task but we are seeing the end of it…
audio_output {
type “alsa”
name “alsa”
device “hw:1,0”
dop “no”
audio_output {
type “fifo”
enabled “no”
name “multiroom”
path “/tmp/snapfifo”
format “44100:16:2”
}
I am also having a trouble getting volumio working with a large db.
just updatet volumio to 2.861 on a raspberry PI3 with music attached to NAS.
Right now the system is not useable for me.
Some things i recognized so far:
if mpd starts and auto_update is on (default!) it takes more than 90 secs -> so systemd will kill mpd.service! So setting TimeoutStartSec=600 in /etc/systemd/system/multi-user.target.wants/mpd.service helped keep it running after a reboot
mpd can index 1.4TB of music (around 200k files)
volumio process tries to access mpd and kills it… thats why i have connection refused or socket errors
mpc or volumio kann kill mpd with e.g. “mpc ls NAS/music”
Jan 03 13:14 : client: [8] process command “lsinfo “NAS/music””
Jan 03 13:14 : exception: std::bad_alloc
Jan 03 13:14 : exception: std::bad_alloc
it should return aroung 1800 directorys - mpd gets killed… “bad_alloc”
while mpc ls NAS/music/Superartist works fine (listing subdirectorys)
So due to the crashing mpd volumio itself can not get any information about the db for its interface, but also webradio does not work
But mpd itself with mpc add “url to stream” and playing works fine
The volumio image from 02.2020 worked fine with exact the same music db till yesterday.
Hi everybody,
i have similar problems with my raspi 3 and hifiberry DAC+.
Library update stops somewhere in the middle. Then the indexed part of the library might be searchable for some time. Then the library gets lost. The network drive is still shown as connected in the sources menu but the number of titles is 0.
The library is on a usb 3.0 harddisk connected to the fritzbox router. Network access is with samba share.
I also tried to connect the harddisk directly to the raspi. I also gave it a try with an usb 3.0 ssd drive.
I tried ntfs and ext3 formatted drives.
My library has about 100.000 songs.
The library update stops or hangs not always at the same point. At 2.000 songs at 50.000 songs - what ever. So i guess it is not a wrecked file in the library.
I have tried various smb mounting options from this and other communities.
Changing the mpd.conf parameters as suggested made no difference.
No difference in using volumio-2.853-2020-11-20-pi.img or volumio-2.698-2020-01-16-pi.img
My next try is the 3.x beta