Database not initialising on iAudio X5

[TheQuickBrownFox]

I'm posting this here and not in the X5 forum as it may not be a player specific problem.

I just updated to today's build and found that when I try to initialise the database it appears to begin doing so but it stays at 0 files found indefinitely. The player does not freeze and I can exit this screen and continue using it. However if I go back to the database I still get the "Database is not ready" screen. Rebooting makes no difference. I read about other people who've had their initialisation freeze at a particular file but I assume my problem is different as it doesn't even manage one file. It appears to make no attempt at initialising the database. I tried deleting the first few albums (assuming that scans occur in alphabetical order) but the problem remains.

Another issue that may or may not be related is that when I select a file to play in the file browser I get the message: "Error accessing playlist control file (-116)". However the file does play and the folder's playlist is created in the expected way.

The last build I used used the "tag cache" rather than "database". Was the change to database just a matter of naming or has it changed the way it works?

Please help!

EDIT:
Almost all my files are MP3 with ID3 v2.4 tags.

[TheQuickBrownFox]

Reverting to an earlier build appears to have fixed this problem. I chose the June 24th build because it happened to be my birthday. =]

According to http://www.rockbox.org/since-4weeks.html there has only been one change to apps/tagcache.c since June 24 and it was made on June 25 by Dan Everton with the following description:

"When building the database and a track doesn't have an album artist tag, copy the value from the artist tag. This should make browsing through album artist in the database a bit nicer. Same as FS# 7342 but different. You may need to rebuild your database to actually see any change."

Does anyone think this change could have caused the problem? If so, what's the most efficient way of getting it fixed?

[Lear]

Not related to the database at all, I think. Sounds like the FAT filename check that was broken for a short while. The most recent build (not the most recent daily build, as of this writing) should be fine.

And the tagcache to database change was just a change of the name. No change in functionality.

[TheQuickBrownFox]

Good stuff. Thanks. =]