| # | Track | Duration |
|---|
Accepted duration formats
Each line can end with MM:SS for anything under an hour, H:MM:SS once a track or a whole set runs past sixty minutes, or a plain number on its own for a duration already given in seconds. Anything written before the duration is treated as the track name and is only used to label the row in the breakdown table, never in the maths.
Why transition gaps matter for a running total
Adding up track lengths alone underestimates how long a set actually takes, because a DJ set, a live show, or even a curated playlist rarely plays one track straight into the next with zero silence. A few seconds of crossfade, applause, or a beatmatched transition between songs add up quickly across a long list, which is why the gap field lets that per-track overhead be folded into a separate runtime estimate rather than hidden inside the raw total.
Estimating a finish time
Entering a start time projects when the playlist will actually end once transition gaps are included, which is useful when a set has to fit inside a fixed slot, such as a wedding reception or a support act before a headliner. The estimate rolls over midnight automatically if the total runtime pushes the finish time into the next day.
Building a setlist from a streaming export
Many streaming services let you export a playlist as plain text or a spreadsheet column with each track and its length already written out. Pasting that export directly into the track list, one line per track, usually needs no reformatting at all, since the duration only has to sit at the end of the line for it to be picked up correctly.