Navigation: Operation > Technical information >
Additional information storage
Additional information consists of various track properties that RadioBOSS uses in its operation. This information includes: playback count (playcount), last played date, additional track properties (gender, language, BPM, etc), user defined tag fields and some other information.
There are three ways to store the additional information:
•File tag (APEv2) - the default
•Database (MySQL) - requires MySQL 5.7 or MariaDB 10.2 (or newer)
All methods have their pros and cons. No configuration is required for APEv2 and SQLite storage methods. MySQL option requires a MySQL or MariaDB server, the connection details need to be entered into RadioBOSS. The storage method is configured in the settings. Switching between the storage methods is always possible: the Music Library allows to convert information from one storage method to the other, use the Tools->Convert additional info command.
Storing information in an APEv2 file tag
oThe information is persistent, as it's stored in the music file: when you copy or move a file, the information is preserved
oNo additional files are created
oThe music file is modified each time it's played (to update playcount and other data)
oNot all music files support APEv2, in this case NTFS alternate data streams are used to save the data
oRequires write access to music files which is not always possible or desired, especially when network storage is used
Storing information in SQLite or MySQL database
oMusic tracks are not modified as information is stored externally
oCan be used with read-only music folders, e.g. network folders, read-only NAS access
oSlightly faster operation: loading information from the database is faster than reading the file tag
oMySQL database allows working with music library from different computers. Important! File paths have to be the same on all computers. E.g. if a network drive with music is mounted, it needs to be mounted under the same drive letter on all computers.
oThe information is linked to the music track via its file path, if the file is moved or renamed, the information will be lost.
oMySQL database: file names, including path, must not exceed 767 characters.