All open Album and Track databases will be searched for either the first selected track or the album containing the first selected track. This is based on the current metadata values and paths. This is typically the best method of locating tracks in a database and will use Yate Track and Album IDs as well as metadata.
All open Album and Track databases will be searched for either the first selected track or the album containing the first selected track. The search is based on the original metadata and file paths. Searches in an Album database attempt to match the Album field and the folder path. Searches in a Track database attempt to match the file path. If any of this data has changed, the previous command will fail. This menu item allows you to locate records where the search criteria has changed.
An attempt will be made to update all open databases with the metadata in all loaded files. If a database is locked, this function is ignored.
All visible tracks will be removed from any open database. Album and Track databases associate entries with open files by either a folder path or file path. When tracks are moved and possibly when renamed, these paths are invalidated. In order to solve the problem you can use this function to remove the database items associated with the current open files before you move or rename files. After the move or rename function you can use the Update Databases menu item to repopulate the moved files. You can get mostly around this issue by using Yate Album and Track Database IDs. Note that most of these matching issues can be avoided by using Yate Album and Track Database IDs. You cannot use this functionality to remove individual tracks from an Album Database. Removing any track in an album in an Album database will remove the associate row. If a database is locked, this function is ignored.