mAirList allows you to keep track of the broadcasted files by maintaining customizable log files. Additionally, log information can directly be written to an SQL database. You can use the variables shown in Table 8.1, “Log variables” which are automatically expanded.
Table 8.1. Log variables
| variable | meaning |
|---|---|
| %Y | current year (4 digits) |
| %M | current month (2 digits) |
| %D | current day (2 digits) |
| %h | current hour (24h format, 2 digits) |
| %m | current minute (2 digits) |
| %s | current second (2 digits) |
| %1 | file name with path |
| %2 | file name without path |
| %3 | file name without path and extension |
| %a | artist |
| %b | title |
| %c | CueIn position (in mAirList units, 1/10,000,000 of a second) |
| %r | Ramp position (in mAirList units) |
| %o | Outro position (in mAirList units) |
| %f | FadeOut position (in mAirList units) |
| %E | end type |
| %t | tab stop |
| %d | effective broadcasted duration (in mAirList units, only available with stop logging) |
| %e | effective broadcasted duration (in seconds, only available with stop logging) |
You can write a log file both when a song is started (for example, for an online playlist) and when it is stopped (for example, for accounting). Log variables may be used in both the file name and the log file format used for each log file entry.
Log entries may also be written to an SQL database. A number of common
database servers are supported, but you need to copy the client DLL
to your mAirList folder (for example, libmysql323.dll is the
MySQL 3.23 client library, which can also be used to access version 4.x and 5.x
servers). Select the appropriate database type and enter the connection
information (host, database, user and password). Finally, enter an
INSERT statement to be issued when an element is started or
stopped, respectively.
You can use any log variable. If you want to deactivate start or stop
logging, leave the appropriate INSERT command field blank.
The database connection specified here is a special connection only used for logging, and does not interfere with the database connections used to access playlists and music archives (see Section 8.8, “Databases”).