Chapter 4. Browsing and playing
31
Ignoring Directories During Database Initialization
You may have directories on your player whose contents should not be added to the
database. Placing a file named
database.ignore
in a directory will exclude the files in
that directory and all its subdirectories from scanning their tags and adding them to the
database. This will speed up the database initialization.
If a subdirectory of an ‘ignored’ directory should still be scanned, place a file named
database.unignore
in it.
The files in that directory and its subdirectories will be
scanned and added to the database.
4.2.3. The Database Menu
Load To RAM
The database can either be kept on flash storage (to save memory), or
loaded into RAM (for fast browsing). Setting this to
Yes
loads the database to
RAM, allowing faster browsing and searching. Setting this option to
No
keeps the
database on the flash storage, meaning slower browsing but it does not use extra
RAM and saves some battery on boot up.
Auto Update
If
Auto update
is set to
on
, each time the player boots, the database
will automatically be updated.
Initialize Now
You can force Rockbox to rescan your disk for tagged files by using the
Initialize Now
function in the
Database Menu
.
Warning:
Initialize Now
removes all database files (removing runtimedb data
!
also) and rebuilds the database from scratch.
Update Now
Update now
causes the database to detect new and deleted files
Note:
Unlike the
Auto Update
function,
Update Now
will update the database
b
regardless of whether the
Directory Cache
is enabled. Thus, an update using
Update now
may take a long time.
Unlike
Initialize Now
, the
Update Now
function does not remove runtime
database information.
Gather Runtime Data
When enabled, rockbox will record how often and how long a
track is being played, when it was last played and its rating. This information can
be displayed in the WPS and is used in the database browser to, for example, show
the most played, unplayed and most recently played tracks.
Export Modifications
This allows for the runtime data to be exported to the file
/.rockbox/database_changelog.txt
, which backs up the runtime data in ASCII
format. This is needed when database structures change, because new code cannot
read old database code. But, all modifications exported to ASCII format should
be readable by all database versions.
The Rockbox manual
(version 3.14)
Sansa Fuze+