Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Need explanation of database&tag interaction (Read 1697 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Need explanation of database&tag interaction

I am just looking for some kind of explanation of what exactly the database in foobar is, relative to playlist and the original file tags.  Trying to figure when Masstagger or single-tag update effects the database, or the playlists etc.  And what "block update" does.  And what "scan" does, how is it different than just dragging a whole directory tree into a playlist.

I've look in this forum as well as the Wiki and can't seem to find anything relevant.

Thanks for any pointers.

+Reardon

Need explanation of database&tag interaction

Reply #1 –
The db is a cache of all the metadata in the files u add to foobar. Makes operations faster cos foobar doesnt have to open every file and parse all the tags every time it wants to do something with them, eg. u change the playlist formatting or u add files to the playlist that u've added before etc.

Need explanation of database&tag interaction

Reply #2 –
Also the database is used for interaction with many of the plugins that are available.

For example albumlist, the different searches (dbsearch, advanced serach, etc, come to ming), the playlist generators, etc.

This makes the database a quite powerfull tool for different uses.

Block update simply means that edited tags information only gets written to the database and not into the files tags.