Project, API and platform documentation checked through 2026-10-28. Stack and workflow details describe the repository snapshot reviewed for this post; live service behaviour, regional catalogue results and platform terms can change.

Saturday was the Deftones at the Westfalenhalle in Dortmund. One of those concerts where the setlist is part of the experience — where you register, with something close to physical relief, that the arc landed exactly right, and you spend the Uber home mentally replaying the order.

Sunday I built a playlist from it. It took about four minutes.

This is the post about why that number is already too low, and also possibly too high.

The Ritual

There is a specific kind of concert listening that happens in the days after a show. You go home, you look up the setlist — setlist.fm is the canonical archive, maintained with an almost academic precision by people who care — and you build a playlist from it in whatever streaming app you use. Then you play it through, in order, and what comes back is not just the music but the spatial memory of the room, the sound mix, the moment the lights dropped for that particular song.

I have been doing this for years. It is a ritual, and like most rituals, part of its meaning is in the doing. The forty minutes of searching song by song, the occasional discovery that a deep cut is on Apple Music in one version but not another, the fiddling with live versus studio — that friction is not purely annoying. It is part of the processing.

And yet. The pile of unprocessed setlists sits in a folder. Shows I attended and never got around to. Setlists I meant to build into playlists and didn’t, because the forty minutes were not available that week, and then the moment passed. The ritual unrealised is just a list of song titles.

This is the dilemma, and it is not entirely trivial.

Why This Is Harder Than It Should Be

The setlist.fm API 1.0 returns structured set, song, artist, venue and version data [[1]]. It is wiki-derived and mutable, requires an API key, and its documented free use is limited to non-commercial projects [[1]] [[2]]. It does not supply Apple Music catalogue identifiers, whose availability and versions vary by storefront. The terms also forbid sharing the key with any third party [[2]], and a key shipped in browser code would be handed to every visitor.

Matching a title to the intended recording is ambiguous: covers, editions, punctuation and regional catalogues matter. No match rate is claimed here, because none has been measured.

Apple documents MusicKit user authorisation, playlist creation and developer tokens signed with a Media Services private key [[3]] [[4]] [[5]]; those requirements shaped this implementation.

This is partly why I built Showtape (originally published as setlist-to-playlist and since renamed) as a web app rather than reaching for an existing tool.

How It Works

The app is a web application you can open on your phone in the taxi home from a show. It ships a web manifest, but its documentation states that it needs network access and has no service worker or offline mode, so it is not an offline-capable PWA. It is a single Next.js application, and the workflow has three phases [[6]]:

Import. You paste a setlist.fm URL or ID. The app queries setlist.fm through a server-side proxy — the API key lives on the server and never touches the client — and returns a trimmed version of the structured setlist data: songs in order, with the original artist of each cover and setlist.fm’s free-text note on how a song was performed. Songs played from tape are dropped, and a medley arrives as a single entry with its titles separated by slashes [[1]].

Preview and matching. Matching runs in the browser, through MusicKit JS, against the Apple Music catalogue of your storefront. For each song, the app removes version labels in parentheses or after a hyphen, such as “(Live)” or “- Remastered”, and “feat.” or “ft.” credits from the title; a bare “Live” stays. It adds the artist (for a cover, the original artist, so the search looks for the original recording) and takes the first result of Apple’s catalogue search; a medley goes out as one query. Every song with a result arrives pre-selected, and before anything is written you can search yourself, pick another track or skip a song.

This is the step where the ambiguity problem is addressed manually. In the current code the app flags only the songs for which the search found nothing: a plausible wrong version, live instead of studio, looks like any other pick until you read the list.

Export. Once you are happy with the track list, the app creates a playlist in your Apple Music library and adds the selected tracks in order, in batches of 100 [[6]]. MusicKit handles your authorisation in the browser.

The Music User Token that MusicKit receives when you authorise goes only to Apple, never to Showtape’s server [[4]] [[6]]. The server keeps the Media Services private key from the Apple Developer account and uses it to sign developer tokens; the key never reaches the browser [[3]] [[5]]. The signed developer token, a JSON Web Token, is the one credential that crosses from server to browser: MusicKit is configured with it, and the team and key IDs written into it can be read there.

Apple allows a developer token to live for up to six months [[3]]; Showtape signs it for one hour [[6]]. Fig. 1 shows the four parties and what passes between them.

Figure 1. Apple traffic bypasses Showtape’s server: catalogue search, sign-in and playlist writes go from the browser straight to Apple, so the server never sees what goes into your library. Boxes are the four parties and arrows what passes between them (the page itself and a health check are left out); highlighted entries are credentials that never cross to the other side. Drawn from the repository’s documents and its code at commit edbdb1f [[6]].

The design keeps application-side retention small, and the repository documents what is kept where [[6]]. The server holds mapped setlists in process memory for up to an hour; the setlist.fm terms allow copies only as “cached information for short periods” and do not say how short [[2]]. There is no database, no user account and no analytics. The browser keeps your eight most recent setlist inputs in localStorage and, after an interrupted export, may keep the remaining track IDs in sessionStorage for up to 30 minutes. What a host logs, and what Apple and setlist.fm keep, lies outside the code; no live deployment was audited for this post.

The Actual Experience

After the Deftones show: opened the app on the phone, pasted the setlist.fm URL, had the playlist in Apple Music in about four minutes. Three tracks needed manual confirmation — two because of live-versus-studio ambiguity, one because a cover required a search adjustment, the kind of edge case where the name setlist.fm records differs from what appears in regional streaming catalogues.

Four minutes instead of forty in this one personal run — not a benchmark or a guarantee for another setlist, storefront or network.

And yet.

I noticed, processing the setlist that quickly, that something was missing. Not the music — the music was all there, in order, correct. What was missing was the time spent inside the setlist. The forty minutes of handling each song is also forty minutes of thinking about each song, of remembering where in the set it fell, of deciding which album version you want to hear. The automation removed the friction and also removed the processing.

I am not sure this is a problem. It is probably more accurate to say that it is a trade-off, and that what trade-off you want depends on what you are doing with the ritual. If the backlog is the problem — the pile of unprocessed shows — the automation solves it cleanly. If the processing itself is the point, you probably should not automate it, and the tool is there for when you want it.

That is the correct relationship to automation, I think. Not “this should always be automated” or “this should never be automated”, but “here is a tool that removes the mechanical part; use it when the mechanical part is not the point”.

A Note on the Tech Stack

The current repository (checked 2026-10-28 at commit edbdb1f, version 0.3.0-alpha.1) is one Next.js 16 application with React 19, managed with pnpm 9. The core, api, shared and ui workspace packages named here on 2026-10-03 had been replaced by this single package in a commit of 2 October 2026. The matching rules sit in a framework-free domain layer, separate for tests and possible reuse. The app uses MusicKit JS v3 in the browser, setlist.fm API 1.0 on the server and jose for token signing [[6]]. The repository’s known-issues page says that a complete live run (sign-in, catalogue search, playlist creation) has not yet been confirmed for this alpha; the run described above predates version 0.2.0 (22 March 2026). These are repository claims; the app was not installed or run for this revision.

Showtape writes to Apple Music only; its README lists other export targets among the things it deliberately does not do. The repo is at github.com/sebastianspicker/showtape, and a static, simulated click-through demo shows the workflow without calling setlist.fm or Apple Music. PRs welcome, particularly around the matching heuristics — that is the part where there is the most room for improvement.


The Deftones were exceptional, for the record. The Westfalenhalle was loud in the way that only a concrete hall that size can be loud, which is to say: correctly loud.

The playlist is good. I am glad it took four minutes and not forty.

I am also glad I know what I gave up.


References

[1] setlist.fm. setlist.fm API 1.0 documentation (overview; setlist and song data types), Guidelines and Tutorial (sections “Medleys”). Retrieved 28 October 2026 from https://api.setlist.fm/docs/1.0/index.html, https://www.setlist.fm/guidelines and https://www.setlist.fm/tutorial

[2] setlist.fm. Terms of Use (last updated 14 October 2019), sections “Ownership of Content and Grant of Conditional License” and “Use of Setlist.fm API”. Retrieved 28 October 2026 from https://www.setlist.fm/help/terms

[3] Apple. Generating developer tokens (Apple Music API documentation). Retrieved 28 October 2026 from https://developer.apple.com/documentation/applemusicapi/generating-developer-tokens

[4] Apple. User authentication for MusicKit and Create a new library playlist (Apple Music API documentation). Retrieved 28 October 2026 from https://developer.apple.com/documentation/applemusicapi/user-authentication-for-musickit and https://developer.apple.com/documentation/applemusicapi/create-a-new-library-playlist

[5] Apple. Create a media identifier and private key (Apple Developer account help). Retrieved 28 October 2026 from https://developer.apple.com/help/account/capabilities/create-a-media-identifier-and-private-key/

[6] Showtape repository at commit edbdb1f (version 0.3.0-alpha.1): README.md, CHANGELOG.md, docs/architecture.md, docs/tech/apple-music.md, docs/tech/setlistfm.md, PRIVACY.md, ALPHA_KNOWN_ISSUES.md and src/; the single-package reconstruction is commit 9b74623 of 2 October 2026. Retrieved 28 October 2026 from https://github.com/sebastianspicker/showtape


Changelog

  • 2026-07-11: Removed an unmeasured 80/20 matching rate and platform- ecosystem comparison; dated the stack; added setlist.fm usage limits and qualified privacy, retention and four-minute workflow claims.
  • 2026-10-03: Removed the leftover “20% problem” and “former 80/20 split” wording that still referred to the matching rate deleted on 2026-07-11. Refreshed the project description against the current repository: it is now Showtape (renamed from setlist-to-playlist), runs on Next.js 16 in a pnpm workspace without Turbo, and has a web manifest but no service worker or offline mode, so it is no longer called a PWA; added the link to the static demo.
  • 2026-10-28: Changed “forty minutes” to “four minutes” in the opening to match the three later statements of the app run (to be confirmed by the author). Replaced sentences left over from the 2026-07-11 edit (the Spotify–Apple ecosystem remark, the note on benchmarking and a quoted “No stored data”) with what the repository keeps and for how long. Updated the description to the repository at edbdb1f: one Next.js package since 2 October 2026, so the workspace named on 2026-10-03 was already gone; tape songs dropped and a medley imported as one entry; Apple’s first search result pre-selected for every song, with only empty searches flagged; a complete live run not yet confirmed for the current alpha. Added that the setlist.fm terms forbid sharing the API key, and that the developer token (signed for one hour; Apple allows six months) reaches the browser while the Apple private key stays on the server. Added Fig. 1 and references.