DB update
#1
so…what exactly is happening when the DB auto-updates? it seems to happen every time the tangara crashes, and it slows down the entire interface by quite a bit until it finishes.i see there’s an option to turn off auto-updating but it’s not clear to me why it’s auto-updating in the first place, or why it might be useful.
  Reply
#2
The database holds records of tracks (music, audiobooks, podcasts) on the SD card, sorted by different properties. It's what enables all the indexed views like "Tracks by Artist" or "All Albums" to quickly show tracks in a sorted order. Updating the database involves checking the existing tracks the database knows about haven't changed or been removed, and scanning the filesystem for new tracks, which it then collects metadata from to store in the database. If you have a lot of files, this can take a while.

If you're not adding new tracks to your SD card often, or you want to control when this happens, then you can disable the automatic update and run it manually when you modify the tracks on the SD card.

Without the database entries, you can still play tracks through the file browser or playlist files, but a lot of features like sorting and queuing up multiple tracks are still unimplemented when not using database indexes.
  Reply


Forum Jump: