Log In
Members
Home
Topic RSS
Offline
I noticed that my MPD database is far from complete.
Only a small part of all the music on my NAS share has been added to the database and is shown in a random order.
I have run "the "Update database" a few times, and have waited for several hours to complete.
(Although the update-indicator in the Browse-button will never go away)
I also have the problem that I can't see the NAS option after powering up, I can can only see the Webradio option, although there is a green V in the NAS share.
Only after selecting Update Database the NAS and RAMplay options become available.
Yeah the Update function is very slow, we already figured out why. You should wait for the update indicator to stop in order to let mpd save your db. I know is unconfortable to wait for too long, but we'll solve this soon
Thanks for your swift reply!
Then I will be patiently waiting for an update (while listening to the webradio and database parts that do play wonderfully well BTW)
Great piece of work!
is there a way to manually create the db the first time… I've tried a couple times now and it has locked up…
cant get to the webpage or log in via ssh
when this happens i have to unplug the pi and reboot it
and when it comes back up i have to restart building the db with the update db button…
it is working, as i can see what has added to the db (and play files but they crackle), but something fails then i need to reboot it, and have to start the update db over from the beginning.
I also cant seem to figure out where the logs are for this (do they get wiped out when im forced to reboot) or am i just not looking in the right place?
Are there some manual steps I can try? so i can see what it does at the command line?
I think you can find the log somewhere at /var/log/mpd.log.
I looked there when I had problems and I found out that there were some music files that MPD was having great troubles with to add to the database.
There were lots of error messages complaining about some music tracks (unable to find the tag info). I could see from the timestamps in the log file that these errors took a lot of time, appearing to lockup the database creation process.
I removed these tracks from my NAS folder and then the database creation process went ok. My database is now stable.
Thanks for the reply. Yeah i was looking at that log file, I didn't really see anything (but this was after a reboot) so *maybe* it was working or maybe not, but since i couldn't get to the web ui, or ssh to it I have no way of knowing, it really seemed like something crashed…
I actually plugged the card into my newer version of the pi B with 512MB ram (the one i was using was the pi B with 256 MB RAM from the preorders)
Its been running for 10 hours or so now… but its chugging along… and looks like it will complete.
I Did see a few issues you referenced last night, but it got passed them..
So if anyone else is has the same issue with an early gen of the Pi, it may be a resource issue?
We figured out that there's a bug in mpd, when it updates the db when it founds certain tag types in some files, it hangs, taking cpu usage at 100% and taking hours to complete the db update. We found out that removing the FFMPEG option from the update process, it works flawlessly.. .It will be included in next release, which is coming soon and basically represents a bugfix version of 1.0
Thanks for all the precious feedbacks!
Most Users Ever Online: 200
Currently Online:
5 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Gyp: 82
yoghurtlidlicker: 37
PaulM: 36
icai: 35
Derek: 29
Karsten: 27
tc-fi: 22
Ronaldo: 21
ENSen: 21
chriz: 20
Member Stats:
Guest Posters: 3619
Members: 569
Moderators: 0
Admins: 1
Forum Stats:
Groups: 4
Forums: 10
Topics: 469
Posts: 13163
Newest Members: polo2016, dongdong8, wlpwlp, Sager, ninestab123, lmx66, lmx, jlgg, chenyan, guoyanying
Administrators: admin (401)
