DeadSpread, and Why Jam Bands Are Archived Like No Other Music
An app for the Grateful Dead, Widespread Panic and the wider scene — built around a recording culture that has no real parallel.
DeadSpread is an app for fans of jam bands, centred on the Grateful Dead and Widespread Panic. It runs on iOS, Android, Amazon Fire devices and in a browser — links to all four are in the navigation and on the home page.
Why this music is archived and other music is not
The premise of the whole scene is that the recording is the work, because no two performances are the same song. A jam band treats a composition as a structure to depart from: the same title can run six minutes one night and thirty the next, segue into something else entirely, or be unrecognisable but for a phrase.
That makes a specific date meaningful in a way it is not for most music. "Cornell '77" identifies a particular night, and fans argue about it the way other people argue about pressings.
The taping culture
The Grateful Dead did something almost unheard of: they allowed audience recording, and from 1984 set aside a dedicated taper section behind the soundboard with its own ticket allocation. Trading tapes was permitted as long as no money changed hands.
The consequence is an archive of thousands of shows across three decades, recorded by fans, catalogued by fans, and eventually digitised. Very little popular music from that era exists in comparable depth, and it exists because a band decided not to enforce a right it clearly had.
Widespread Panic and much of the scene since have followed similar conventions, which is why the same cataloguing habits — setlists, dates, venues, source lineages — extend across the genre.
Why the metadata is the hard part
Anyone building software for this discovers the same thing: the interesting questions are all about structure, not playback. When was this song last played? How long is this version against the average? What segued into what? Which source recording is the good one — soundboard, audience, or a matrix of both?
That last question has no clean answer. A soundboard feed is clean and can sound sterile; an audience recording captures the room and the crowd. Many shows exist in several sources of genuinely different character, which is why archives track lineage rather than assuming one canonical file per date.
Setlists as data
A setlist looks like a list and behaves like a graph. Songs connect by segue, they recur at intervals worth tracking, and a "bust-out" — a song not played in years — is an event in its own right. Fans track gaps between performances as a first-class statistic.
Handling that properly means treating a performance as a distinct entity from a song, with its own duration, position, transitions and source recordings. Get that model wrong and no amount of interface work fixes it.
Where to start listening
The usual advice is to pick a well-regarded date rather than a compilation, and to listen to a full set in order — the sequencing and the segues are the point, and a shuffled playlist removes exactly what makes the recording worth having.
App Store · Google Play · Browser version · Back to all articles