Support and General Use > Audio Playback, Database and Playlists
Database Building and Album Track Number Sorting Issue
bennor:
I have checked both the Clip+ drive and the microSD card for errors and none were found. I even copied the file to the Clip+ internal memory and with the Sandisk 16GB microSD card in the player the database fails to build. When the file is deleted the database builds properly and finds all content on the Clip and the memory card. But, the strange thing is if memory card isn't present in the device while the file resides in the Clip+ memory the database reads the file. For some reason the database doesn't build when the file and the microSD card are both present in the Clip+.
I'll have to see if I can lay my hands on another microSD card and test it out to see if it also exhibits this strange problem.
bennor:
An update. Bought a brand new 16 GB Sandisk (mobile ultra sdhc I) microSD card yesterday, loaded 33 folders containing audiobook files (approximately 13 GB's of files) to it and the Rockbox database appeared to read the files correctly and operate correctly. However this morning when loading a one more audiobook folder the database failed to generate properly. When the Clip+ is rebooted the Rockbox indicates its "committing database x/9" then goes to the main screen. When Database is then selected it indicates the database is not ready, initialize now yes/no.
Reformatting the microsd card and randomly loading just a few audiobook folders, the database generation appears to work. Sometimes the database appears to properly generate yet shows the individual media length to be "00.00". Then if the Clip+ is rebooted I get the "committing database" message above along with database is not ready, initialize now message when selecting Database from the menu.
Does the Roxbox database feature have the same file number limitation (8,000 or less) as the Sansa firmware on the Clip+? Using the stock Sansa firmware the Clip+ stopped recognizing files (from the same collection of audiobook files) at around 5,000 files. Beyond that no additional media would be listed, displayed, or played by the Sansa Clip+ firmware. It appears something similar is happening with the Rockbox firmware, either that or there is some kind of a bug in the Clip+ when using larger capacity microSD cards that can store large amounts of individual files.
Currently falling back to using the Rockbox File -> microSD to search through all of the content on the microSD card to play the media content.
bennor:
Another update. After some fiddling around with the Clip+ it seems when the database crashes it leaves the file database_tmp.tcd file which is 2,296 kb in size in the .rockbox directory on my Clip+ that has, on a 16GB Sansa microSD card, 11.4GB of media (audiobook MP3 files) in 5514 individual files in 69 folders.
After much experimentation I think I found a way around this database building crash issue. Here is my workaround to get the database to build without crashing that's worked twice now on my Sansa Clip+.
* Initialize the database by selecting Initialize Now from the Settings/General Settings/Database menu and let it crash (usually at Committing Database 7/9, then Building database 6154 is displayed). Do not reboot or power off the Clip+.
* Then connect Clip to PC and delete the .TCD files including the database_tmp.tcd file which is 2,296 kb in size in the .rockbox directory.
* Then disconnect the Clip+ from the PC, do not reboot or power off the Clip+, and enable Gather Runtime Data from the Settings/General Settings/Database menu.
* Then select Initialize Now from the Settings/General Settings/Database menu, the database will start to build and after a minute or so the Clip+ crashes with the message Undefined Instruction on the screen.
* Press any button (I pressed the play/pause button) and the Clip+ will reboot.
* After rebooting, the message Committing Database 1/9 is displayed and cylces to 9/9, then the Clip+ loads and the database is populated and accessable.
blr_p:
I encountered a similar failure of database rebuild when i installed a 64GB micro SD card. The initialise never got beyond the 4th stage. So everytime i booted up i'd get that database building message....
Pulled the 64GB out and stick the older 32 GB one in and everything worked fine.
Ran the metalogging on the 64GB and when looking at the file its gone through all the files on the 64GB card. Cannot tell where the problem was or even if there was a bad file.
My work around to is was to pull the card out, let the db initialise on the onboard memory. Switch the clip+ off, stick the 64GB card in and never update the db at all. Its worked fine ever since. Everything on the 64GB is accessible via the files option.
thesebastian:
--- Quote from: saratoga on February 26, 2012, 07:15:33 PM ---The hang sounds like a bad file crashing the parser. If you could find and upload the file, it would be helpful to us in fixing that bug. If you go into System -> Debug there is a metadata log. This will make a txt file in the root of the player with a list of each file the database parsed. If it crashes, the last item listed there is probably the one that crashed it.
As for sorting, I think changing the tagnavi file should fix it, and that we should probably update the default order to handle this. That said I don't use the database, so I'm not too sure what to change.
--- End quote ---
THANKS, i just solved this issue thanks to your post. I was trying to link 50GB of Music.
The problem was 1 mp3 of "Steve Vai".
Navigation
[0] Message Index
[*] Previous page
Go to full version