Daily Files

Everything DayTracker writes goes into a single, predictable folder on your Mac. You don't need to look at these files day to day — DayTracker reads and writes them automatically — but it's worth knowing where they are.

The DayTracker Folder

All recordings, markers, and side files live in:

~/Documents/DayTracker/

That's the Documents folder in your home directory, inside a subfolder named DayTracker. You can open it in Finder any time — there's no harm in looking.

One Set of Files Per Day

Each day produces four files, all named with that day's date:

File	What it is
DayTracker_YYYY-MM-DD.mp3	The audio. Always 22050 Hz mono; the bitrate is whichever quality level you had set when the day started.
DayTracker_YYYY-MM-DD.csv	The markers. One row per event — songs, breaks, voicetracks, live mic, silence, custom notes. Plain text; opens in any spreadsheet or text editor.
DayTracker_YYYY-MM-DD.manifest.json	Bookkeeping — when recording started, sample rate, total samples written, quality level. DayTracker uses this to keep the audio anchored to wall-clock time.
DayTracker_YYYY-MM-DD.peaks.bin	Pre-computed waveform peaks. This is what makes the gray waveform under the timeline draw fast. Regenerated automatically as needed.

Airchecks Live Elsewhere

Exported airchecks go to a separate folder, organized so they're easy to find later:

~/Station/Logs/Airchecks/

Filenames carry the label, the date, and the hour window: Aircheck_MorningDrive_2026-05-12_06-10.mp3. Both scheduled and manual exports land here. The DayTracker folder is for the rolling daily logs; the Airchecks folder is for the keepers.

The Manifest, in More Detail

The .manifest.json file is the anchor for the day. It records the moment recording started, in absolute wall-clock time, plus the sample rate and the total samples written so far. DayTracker uses this to make sure every incoming buffer of audio lands at the correct second of the day — even if the audio link briefly stalls and resumes. The manifest is what lets DayTracker tell a real interruption from a small network hiccup and pad-fill the difference with silence rather than silently letting the recording slide out of sync.

The Markers CSV

Markers are stored in a simple comma-separated file with four columns:

Column	Meaning
timestamp	Time of day in ISO format (for example, `2026-05-12T14:23:07.420`).
kind	The marker type: `song_start`, `song_end`, `break_start`, `break_end`, `vt_start`, `vt_end`, `mic_start`, `mic_end`, `hour`, `custom`, `silence_start`, `silence_end`.
label	The human-facing text — song title, voicetrack name, break number, your custom note.
source	Where the marker came from: `autocast`, `partyline`, or `user`.

You can do offline analysis on this file with any tool you like — count voicetracks per shift, list every song played in a given hour, compare day to day. Nothing about the CSV is proprietary; it's plain ASCII.

💡

The four files for a given day are self-contained. If you ever want to archive a day, copy all four to your archive disk and you have everything DayTracker needs to load that day's timeline again later.

Managing Disk Space

DayTracker doesn't delete old days. The recordings will accumulate in ~/Documents/DayTracker/ until you do something about them. You have two reasonable strategies:

Archive and remove — Once a month or once a quarter, drag old days to an archive disk or a cloud-synced folder, then delete the originals from ~/Documents/DayTracker/.
Let them accumulate — At the default Good quality (≈ 253 MB per day), a 1 TB disk holds about ten years of recordings. For many stations, that's enough that the answer is simply "don't worry about it."

Either way, the choice is yours. See Recording Quality for per-day disk-budget numbers at each quality level.