Track System Attributes

Introduction

Each track in database has the following six system attributes:

(0) New file (added in the last update)
(1) Unused track (not used in any playlist)
(2) File might not be found (information about existence of the file was not confirmed)
(3) Current File size is different from the previous value stored in database
(4) Current partial MD5 Checksum is different to the previous value stored in database
(5) Track contains Artwork (album image, etc.)

Each attribute can be either set or cleared.

Track System Attribute (0)

During your first database update, each track added to database will have this attribute set, since each file is new. When you run the second update, all existing files in database will have this attribute cleared, and only new files which are added in this update will have this attribute set.

Subtrack system attribute - Subtracks have their own system attribute (0), i.e. when you create new subtrack (either during database update or manually in Subtracks information window, they will have this attribute set. After next database update, this attribute in these subtracks will be cleared.

Track System Attribute (1)

If track is not used (copied) in any playlist, this attribute will be set. It just indicates that track is not part of any playlist. When you copy it to some playlist, the attribute is cleared (i.e. the icon is no longer present). Term "playlist" means only classic playlists in Playlists window, not quick access panel, music board and music sphere (these are ignored). This attribute is checked during operations like copy, move or delete.

Regarding usage of subtracks, only if the track is directly used in playlist the attribute is cleared. If track directly is not used in playlist and some of its tracks are used, the attribute will be still set.

Subtrack system attribute - Subtracks have their own system attribute (1), i.e. when subtrack is not used in playlist, its attribute is set; otherwise it is cleared.

Track System Attribute (2)

Definition of this attribute is as follows: file might not be found (information about existence of the file was not confirmed). When you do your first database update, all tracks which are added to database will have this attribute cleared (since the files did exist when they were added). Let's say you moved some files to another disk and you run the database update again. First thing that database update does is that this attribute is set for each file in database (because system does not know anything about the files now, they might have been moved, deleted, etc). After the existence of files is checked, the attribute is cleared.

When you select only specific folders in database update (e.g. you want to add quickly just a few music files), most of the tracks will have this attribute set after database update, because these files do not exist in the few specific folders and system does not verify them.

This attribute is also checked when you start playback of track or its subtrack. It is also checked when you edit the track or its subtracks.

Subtrack system attribute - When subtrack is displayed in playlist, attribute (2) of its parent track is shown.

Track System Attribute (3)

When this attribute is set, it means the file size of track has changed. This can happen when you overwrite your file by a better one, or when you edit some tags e.g. in Winamp. In order to clear this attribute you can run the database update when "Accept changed files" is checked, or you can open Track information window and click "Accept" button.

This attribute is also checked when you start playback of track or its subtrack. It is also checked when you edit the track or its subtracks.

Subtrack system attribute - When subtrack is displayed in playlist, attribute (3) of its parent track is shown.

Track System Attribute (4)

When this attribute is set, it means the MD5 checksum of track file has changed. This can happen when you overwrite your file by a better one, or when you edit some tags e.g. in Winamp. In order to clear this attribute you can run the database update when "Accept changed files" is checked, or you can open Track information window and click "Accept" button.

This attribute is also checked when you start playback of track or its subtrack. It is also checked when you edit the track or its subtracks.

Subtrack system attribute - When subtrack is displayed in playlist, attribute (4) of its parent track is shown.

Track System Attribute (5)

If file contains artwork, this attribute is set. This way you can easily see which tracks contain artwork. This attribute is updated during database update, playback start, editing of track or its subtracks. Only MP3 and FLAC artwork is supported.

Subtrack system attribute - When subtrack is displayed in playlist, attribute (5) of its parent track is shown (in other words, subtracks as such cannot have own artwork).

Example

In figure below, the following tracks and subtracks and their system attributes are present:

Track which is not used in playlist and contains artwork (blue "U" icon and green "A" icon).
Subtrack which is also not used in playlist and since its main track contains artwork, the green "A" icon is displayed.
Subtrack which is new (either it was added in last update or manually), it is used in some playlist (blue "U" icon is not present) and since its main track contains artwork, the green "A" icon is displayed.
Track which is new (was added in the last update), is not used in any playlist and its MD5 checksum has changed (orange "C" icon). Filesize did not change.
Track which is not used in any playlist, its filesze and its MD5 checksum have changed (orange "F" and "C" icons).
Track which is new (was added in the last update), is not used in any playlist and file is not found (this attribute could not have been set during update since it is a new file, it was set either when playback was tried or when it was opened in "Track Information" window.

Totalamp system attributes examples, tracks and subtracks

Example of system attributes in tracks and subtracks