What TagBot does.

A setlist tagger for live recordings. Built to keep you in control of what gets written.

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.

Supported: 2024-07-20 · 2024.07.20 · 07-20-2024 · with venue suffix

Setlists from DMBAlmanac and Phish.net

DMB shows pull the official setlist from DMBAlmanac.com, including set structure (set 1, set 2, encore), segues, and multi-part songs. Phish shows pull from Phish.net using the same workflow. If your parent folder contains a mix of DMB and Phish show subfolders, TagBot detects each and routes it to the correct provider automatically.

If your recording has more or fewer tracks than the setlist, TagBot shows you the discrepancy instead of guessing — you can manually assign or skip tracks before writing anything.

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. Tracks that match cleanly are marked ready. Tracks TagBot isn't sure about — wrong duration, ambiguous title, unusual track count — are flagged for your review. You can override any individual match before approving the batch.

TagBot
Review table: every track, its setlist title and status
Review table: every track, its setlist title and status

Standard tags: Vorbis comments for FLAC, ID3v2 for MP3

TagBot writes six fields:

  • TITLE—song title from setlist
  • ARTIST—performer (e.g., Dave Matthews Band)
  • ALBUM—show date and venue in standard format
  • COMMENT—source reference (setlist provider URL)
  • TRACKNUMBER—track position in the final write order
  • TOTALTRACKS—total tracks written for the show

TRACKNUMBER and TOTALTRACKS reflect the final write order, not the raw file position. All other existing tags (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 and inspects each one against the setlist. Shows that match cleanly are marked ready. Shows with uncertain matches or track count discrepancies are flagged for review. Ready shows can be written together in one click — flagged shows stay queued until you've reviewed them first.

TagBot
Batch Mode: inspect a parent folder, review each show, write the ready ones
Batch Mode: inspect a parent folder, review each show, write the ready ones
TagBot
Batch Mode, a real run

Write NFO: setlist titles in Plex, audio untouched

Write NFO adds an album.nfo file to the show folder and changes nothing else. Plex reads it through the TagBot NFO Agent and shows each song's setlist title, the show date and venue, the setlist as the album summary, and a year collection. Because no audio file changes, a torrent seeding that folder keeps seeding. Batch has a Write NFO for all ready folders button, and per show it asks before replacing an album.nfo it did not write (the old one is kept as album.nfo.bak).

TagBot
Write NFO, a real run
TagBot
The same show in Plex: setlist titles, date, venue, year collection
The same show in Plex: setlist titles, date, venue, year collection

Plex agent, scanner and collection repair

In Settings, TagBot installs the TagBot NFO Agent and the TagBot Music Scanner into your Plex plug-ins folder. The scanner keeps each show folder as its own album so one show is never merged into another. Give TagBot your Plex address and token and it refreshes the album after Write NFO. If your NAS and your PC name the same folder differently, two path prefixes in Settings map one to the other. Repair collections puts the year collection back on albums Plex re-created.

→ Plex setup, step by step

Protects seeding

Writing tags rewrites the file, so a torrent seeding that folder stops matching. Three protections: Write NFO, which touches no audio; the qBittorrent check, where TagBot refuses Write Tags on any folder a torrent covers (it only reads the torrent list and never starts, stops or removes a torrent); and the exact-restore copy, which saves each file's original bytes so History can put it back byte for byte.

TagBot
Write Tags confirmation: the seeding warning and the exact-restore option
Write Tags confirmation: the seeding warning and the exact-restore option

Updates in one click

When a newer version exists, a banner appears at the top of the window and one click installs it. Settings and History are kept. The check only downloads a small version file and can be turned off in Settings.

What TagBot does not do

  • · It does not rename or move your audio files
  • · It does not modify your folder structure
  • · It does not use AI or machine learning
  • · It does not require an internet subscription or account
  • · It does not upload your audio, file names or folders to any server
  • · It does not work with arbitrary music libraries — it is setlist-aware, not general-purpose