What TagBot does.

Show detection from folder name and metadata

TagBot reads folder names and embedded audio metadata to identify the show date. It handles common taper naming conventions: YYYY-MM-DD, MM-DD-YYYY, and variations with venue or source info appended. When detection is ambiguous, it shows you what it found and asks you to confirm before proceeding.

Setlists from DMBAlmanac

Each matched show pulls the official setlist from DMBAlmanac.com, including set structure (set 1, set 2, encore), segues, and multi-part songs. TagBot reconciles track count differences gracefully — if your recording has more or fewer tracks than the setlist entry count, it shows you the discrepancy and lets you manually assign or skip tracks.

Every match visible before write

The tagger UI shows a side-by-side comparison for each track: the current tag value versus what will be written. Unmatched tracks are flagged. Tracks with conflicts are highlighted. You can override any individual match manually before approving the batch.

Standard ID3v2 tags

TagBot writes four fields:

Existing tags in other fields (e.g., ENCODER, REPLAYGAIN) are left untouched.

Write history and one-click restore

Every write session is logged with a timestamp, the folder path, and the exact changes made to each file. The History view shows all past sessions. Select any session and restore — TagBot writes back the previous tag values exactly as they were.

Process multiple shows in one pass

Point TagBot at a parent folder. It discovers all show subfolders, inspects each one against DMBAlmanac, and presents a batch review panel. Each show has its own status chip (uninspected / needs review / ready / blocked). You step through each show's review before the batch write begins.