Spotify killed the New Releases by Genre function of Every Noise at Once when they laid me off and cut off my website from its internal data sources. As I've described previously, the fact that a functional new-release tool required internal data-access, to begin with, was a result of minor structural contingencies, not conceptual or business objections, but in 10 years of working at Spotify I do not remember ever successfully persuading the API team to change a feature. If we're going to get NRbG back, we're going to have to figure out how to rebuild it with the tools we are allowed.  

But since I need NRbG myself, emotionally not just logistically, I've kept experimenting with ways of recreating it. It didn't actually take me very long to build a personal version of it. Spotify still does have the best music-service API, by far, and the brute-force approach of searching for artists by genre, and then checking the catalogs of each of those artists one-by-one for new releases every week, does basically work. It just doesn't scale. I'm willing to wait a few minutes for the things I care about the most; it doesn't work to make everybody wait for everything anybody cares about. When I worked at Spotify, I could try to solve some problems for everybody at once; from outside, I am too constrained by API rate limits.  

The code I wrote, however, would work for you as readily as for me. Even my "personal" tools are general-purpose, because I assume I'll be curious tomorrow about something I didn't care about today. Maybe it's more accurate to say that I tend to build tools to extend my curiosity as much as to satisfy it, or that extending and satisfying describe a propulsive cycle of curiosity more than alternative goals. I would love to inspire this same kind of curiosity in you, but I would settle for giving you some power and letting you discover what you do with it.  

And a few days ago it occurred to me that I can. Or, rather, I can give you the power of my knowledge and experience embodied in code, and you can get the power of running it for yourself by signing up for your own API keys. Which is easy and free.  

Here's how:
- go to developer.spotify.com
- click "Log in", and log into your regular Spotify account
- click your name in the top right, and pick Dashboard
- read and accept the developer terms of service
- on the Dashboard page, click "Create app" in the top right
-- App name: NRbG
-- App description: New Releases by Genre
-- Website: (leave blank)
-- Redirect URIs: localhost (NRbG doesn't actually use this)
-- [x] Web API (leave the others unchecked)
-- [x] I understand and agree etc.
- click Save
- on your new NRbG app page, click Settings in the top right
- click "View client secret"
- copy your "Client ID" and "Client secret"
- go to NRbG (DIY version)
- paste your client ID and secret into the boxes
- hit Enter  

Now you have power.  

The new version of NRbG is a little different from the old one. Instead of a list of all the genres in the world, it has a text box. Type a genre name there and hit Enter, and it will start looking for new releases by artists in or around that genre that came out in the last release week (from Saturday through Friday, because Friday is the traditional music-industry release day).  

 

After a while it might start finding some.  

 

The orange letters are the first letters of each song-title, and you can click on them to hear samples. If a new release has songs that already came out some other way, they will (usually) be grayed out here, like with the gray S above for the advance single "Sekuyiso Isikhathi" from THANDAZANI's album Sasibaningi.  

If you click "show track URIs", at the bottom, you'll get a list of the URIs for all the new tracks from the releases you have checked in the list, which you can copy and paste into a blank (or existing) Spotify playlist (using command-C, command-V in the Spotify desktop app). There's also a "save playlist" option, which create a new playlist for you directly if you want.  
 

Because I built this for myself, there are a few non-obvious features.  

The text box actually takes a list of things, separated by + signs, and the things can each be any of these:
- a genre (e.g. maskandi or gothic symphonic metal)
- a Spotify artist link/URI
- the name of an individual artist, in quotes, like "Nightwish", although this will find the most popular with that name, so URIs are always safer
- a Spotify playlist link/URI, to be interpreted as a list of artists
- @ and then the name of a record label (e.g. @Profound Lore; the spelling has to be exactly right, but see the note later about playlists)  

If your list starts with a +, the results will be added to the bottom of the current list; otherwise the current results will be replaced.  

The ">>" link encodes your current parameters, so if you click that, you can then bookmark the resulting URL for reuse.  

New releases for selected labels, because labels are the only thing that works properly in new-release API searching, are each shown individually, in labeled groups. Everything else in a given list is combined to make a consolidated set of artists, those artists are then checked for their closest related artists (via Fans Also Like), and the whole thus-expanded list of artists is reordered by collective relevance and then checked individually in order for new releases.  

If you don't know the exact genre names you want, offhand, you can also just type a partial name and an asterisk, like metal*, and it will give you a list of all the genre names that include that word. Or you could go to everynoise.com and type an artist name into the search box in the top right to see what genres they belong to.  

The words "new" and "releases", in "new releases by genre" at the top, are both actually mode controls. "new" switches back and forth between "new", for new-release mode, and "top", for one-top-release-per-artist sampler mode, not constrained by dates. "releases" cycles through "releases" (everything), "albums" (no singles or compilations) and "singles" (no albums or compilations).  

If you want to get only 1 track per release, for sampler purposes, you can put "1/" before your list. Or indeed any number and then a "/". This will pick the most popular however-many tracks on each release, and gray out the rest (and exclude them from the URI list) like the non-new tracks on new releases.  

 
 

You might notice that this app, although it requires your API keys, does not itself log into your Spotify account. This is intentional. Many Spotify features are personalized for you in complicated ways, if you are logged in, and for exploratory purposes we don't want that. This means, too, that this app cannot access or modify your personal information. But if you want to control its behavior by giving it more information, it can look up non-private playlists, so that's the mechanism.  

If you use a playlist as input (yours or anybody else's), it will look for new releases by the primary artists of the tracks in that playlist and their related artists, but excluding the specific releases already in the playlist. So if you, like me, spend a lot of time using this tool every Friday to make a playlist of new releases you want to hear, you can put that playlist's URI back into the same tool and it will check to see if there's anything else related that you might have missed.  

In addition, once you've set up your API keys and NRbG is working, the playlist-profile page in the everynoise research tools also gets a couple added features for finding new releases. Put a playlist link or URI into that view, and it already shows you genres and record labels for every track in the list. But scroll to the bottom of the page, and you'll also see something like this:  

 

The "see new releases" line gives you three links to NRbG for different ways of expanding on this list, each with a set of parameters pre-filled from the data in this playlist.  
 

And, for one last bonus feature, you can check an earlier week by putting that week's Friday date (in YYYY-MM-DD format) at the beginning of your input as an override, like this:  

 

and hit Enter to get:  

 

You can even check whole years by including just a year, although be warned, in both cases, that release-date data gets unreliable pretty quickly once you go back beyond the very recent past.  
 

I don't know what else I'll do with this. Probably more, because it's fun. Feedback, error reports and ideas are all welcome, in the meantime.  

See what you find.

I'm keeping a running list of book-related media links at the bottom of this post, but here are a few new things from an interestingly global week:  

- I'm featured in an article about AI and the future in the French magazine Usbek & Rica this month. My copy hasn't arrvied yet, and I think it's in French, so I'm as curious as anybody what I said.  

- Iveta Hajdakova and Tom Hoy at the London international consulting group Stripe Partners, who I know from some work they did for Spotify while I was there, interviewed me about algorithms and music for their Viewpoints series.  

- There's an interview/feature with/about me and You Have Not Yet Heard Your Favourite Song both in print and online in the Polish magazine Polityka.  

- I'll be making my second ever visit to the southern hemisphere, and first to New Zealand and Australia, to appear in conversation at Going Global Music Summit 2024 in Auckland, August 29-30, and then BIGSOUND 2024 in Brisbane, September 2-6!  

You Have Not Yet Heard Your Favourite Song began in a Google doc I had provisionally titled Every Noise at Once: New Fears and New Joys From the Streaming Liberation of All the World's Music. The first chapter-list I made there was mostly just a chronological free-association of stories I tell. That structure was useful in suggesting that there was probably a book's quantity of words involved, but when we started sending this outline and a few sample chapters to publishers, the fairly unanimous response was that I was not famous enough for strangers to want to read about my adventures in music just because I had them.  

I couldn't really argue with that, nor did I actually want to write a memoir. I wanted to try to formulate an argument. Not an entirely straightforward or linear argument, exactly, but still, something more like an essay than a memoir: not every noise, and not at once, but particular noises, in an order with progressions and resolutions.  

Restructuring the list of stories into the outline of an essay was easy and encouraging, and a couple of the chapters I had written already nearly fit the new structure, but the first version's first chapter was quite clearly the first chapter of a memoir, and I just deleted it and started over.  

And by "deleted", I mean that I copied it into a different doc in case I thought of some other use for it later. I just came across that doc again, and blogs solve the not-famous-enough problem by not asking anybody but you to care whether you care. So here, for no other reason than that I wrote it once, is that original first chapter of the memoir I didn't write:  

 

Filter "bubbles" are charmingly weightless, delightful to pop. Sure, there's a slight soapy residue afterwards, but check your backpack: there are probably still a few old hand-sanitizer packets you shoved in there during the pandemic. Except sometimes you reach out, flirtatiously, to pop the shimmering bubble, and hit an intransigence made of polarized glass. Less bubble, more dome.  

Spotify generates a lot of playlists that are "made for you", which generally means they have been aggressively adjusted to prioritize your previous listening. This is excellent for comfort, but terrible for exploration.  

For example, Spotify is currently giving me a Synthwave Mix playlist on my Made For You page. I like synthwave, but I haven't been paying much focused attention to it lately, so it would be useful to me to hear what's going on there. "My" Synthwave Mix is made for me, though, so what it suggests is going on in synthwave is a) the handful of synthwave-adjacent bands I already specifically follow, and b) a lot of other bands I also already follow who are very definitely not synthwave.  

I have a tool for this, though. If you stick the link to a Spotify made-for-you playlist into this:  

https://everynoise.com/playlistprofile.cgi, e.g. Synthwave Mix  

you can see what that playlist looks like before it gets personalized. In my case, this is almost completely different from what I end up with; only one artist* from the underlying source playlist ends up in my personalized version. That's not a lot of discovery potential. If there were a product feature to turn off the personalization, at least I could have discovered something here. Agency unlocks curiosity.  

But since there are still, for the moment, better tools for genre exploration, I'm content to just ignore almost everything they make for me. In practice there is exactly one personalized Spotify playlist I use: Release Radar. This one is different because you actually do have some control over it, albeit not in a way that is totally apparent from looking at it. Release Radar will do its own inscrutable magic for you if you let it, but first it will find you new releases by artists you Follow. So if you follow enough artists, you can crowd out the "suggestions" and get a very useful release monitor. I follow 5124 artists, but you probably don't have to be that obsessive if you aren't me. Release Radar maxes out at 200 tracks. Even with 5124 artists to monitor, there are usually not more than 200 of them with new releases in any given week, so this is OK-ish. If you aren't me it's probably way more than enough.  

In weeks when there are fewer than 200 new releases by artists I follow, Release Radar will fill out the rest of the 200 tracks with releases from the previous 3 weeks. This is an earnest idea, but counter-productive for me, personally, because I monitor new releases every week and I don't want to have the old tracks shown to me again as if they are new. So I generally stick my Release Radar playlist into the same playlist viewer linked above, where I can see the release dates of the tracks, and extract just the ones from the current week into a new playlist.  

I usually do this first, and only really look at the new tracks once they're in the new playlist. This morning I went for a run before I'd done this, so I just put on Release Radar itself. The older tracks come at the end, and I wasn't going to be out for 12 hours, so it didn't matter. Later when I went to make my new-songs-only copy, though, I noticed that the first few tracks in my no-personalization viewer were not the same ones I had just heard. Weird. Flipping back and forth between the two views, it was clear that they were very different. Every Release Radar is unique, so my Release Radar is already filled with my artists, and thus you might think that this is the one time when "made for you" can't do any harm.  

But oh, wait. Those older songs. Ugh.  

Release Radar actually does assemble the list of new songs by artists I follow, like it's meant to. The pre-personalization view shows that this week 199 of my artists had new releases; only the 200th song in the underlying list is filler from a previous week. But then the made for you filter-dome snaps down, and songs I want to hear from this week are obtusely replaced with older songs by artists Spotify thinks are more familiar to me. Which are exactly the songs I am most likely to already have contemplated in the weeks when they were new. Two algorithms later, I end up with only 79 of the 199 new songs the first algorithm had in mind for me. "Catch all the latest music from artists you follow", Release Radar promises at the top. That's exactly what I want, and exactly what it could give me if it wanted to.  

Algorithms, though, don't want things. We want things, and the algorithms do what they are ordered to do. I want all the latest music I might care about. Somebody who still works for Spotify wants something else. If you aren't me, maybe it still doesn't matter. If you only care about a few artists, you won't have this problem. If a streaming service only cares about people who only care about a few artists, they won't fix it**. If they don't employ enough people who care about everything, they may not even know. Maybe what they really want is to not have to care or know, and they have a comfort metric that allows them not to.  

But all of this, the domes and the not caring and the not knowing, makes the world worse. I don't want to miss joy in favor of somebody else's obliviously generalized idea of my comfort. Neither should any of us.  
 

* The one artist isn't even actually a synthwave artist. You can't really blame Spotify for that, though, as it's hardly their business to know the internal jargon of zero-cost content makers.  

** One might reasonably ask why, given that I no longer work for Spotify, I haven't switched to some other streaming service, and the answer is that whatever they do or don't fix in the app, they still have the most useful programmatic API. That's how the playlist viewer works, and if you want new releases by all the artists you follow bad enough to write code, you can have that, too. And if you're me, now you do. One playlist minus one is zero. Ultimately the only person in "personalization" is the one doing it, and if you want your personalization to be personal, that person has to be you.  
 

[23 August 2024 update: this week the post-processing reduces the underlying 200 songs in my Release Radar to just 30. That's pathetic.]

It's probably not the one I wrote. It would be weird if my book were your favorite book. It's a geeky book about music-streaming and music and algorithms and technology and curiosity and morality and where we are right now, and your favorite book should probably be an immortal novel about how we always are, or something you have re-read every year since you were 12 because it reminds you what you love and believe.  

But my book about how streaming changes music is also kind of a book about loving and believing things, and the fears and joys that love and belief produce, because everything is if you really think about it, and I wrote a book about this stuff because I really think about it and didn't know how to stop.  

As a method of not thinking about something any more, writing the book seems to have been fairly ineffective. I have kept thinking and writing about music and algorithms and technology and humanity. My new job, which doesn't have music anywhere in the wording of the mission, is just as fundamentally about figuring out how to use math and machines to amplify humanity instead of phase-cancelling it.  

As an organized explanation of why I think streaming is good for music and music-streaming is good for humanity, though, I made it as coherent as I could. (And then a really good editor goaded me methodically into making it more coherent than that.) If you love music, you might like reading this book while you listen to whatever you are currently discovering or wondering or doubting. It's a book about discovery and wonder and productive doubt.  

And it was officially published today.  

You Have Not Yet Heard Your Favourite Song; Canbury Press, 2024.
US: bookshop.org or amazon.com or kindle
UK: uk.bookshop.org or amazon.co.uk or kindle UK  

In London: Waterstones or Blackwells or Foyles
In Montreal: featured at Librairie Résonance  

 
 

Some related links as I notice them:  

- A review in the Telegraph, also available via Yahoo News
- A whole bonus episode of Your Morning Coffee Podcast, August 30.
- An appearance on the NZ podcast The Fold
- A article based on an interview with Radio New Zealand in advance of appearing at Going Global
- A mention on Your Morning Coffee Podcast (August 19, from about 7:40-10:20) teasing an upcoming special episode with me
- A (second) appearance on Your Morning Coffee Podcast (August 5, from about 19:09-27:45)
- An interview with Tom and Iveta at Stripe Partners for their Viewpoints series
- An interview/feature in the Polish magazine Polityka
- A conversation with Mark Richardson for the Third Bridge Creative blog
- A conversation with Walt Hickey on the Numlock Sunday podcast
- An appearance on The Ray D'Arcy Show on RTE Radio 1 Ireland (June 25 from about 26:10-50:37; clip)
- An appearance on Your Morning Coffee Podcast (June 24 from about 7:00-18:00)
- A conversation on the podcast The Gist
- A short interview on Newstalk in Ireland (with a Cactus World News shout!)
- A radio piece in German on Deutschlandfunk Kultur (with blasts of gothic metal and wisps of theremin!)
- A print rendition of the same interview from that German radio piece in Die Tageszeitung
- A "new book" mention on Tinnitist
- A conversation with Chris Dalla Riva in his newsletter Can't Get Much Higher
- A book citation as part of my introduction into a story about algorithms and music discovery in Mission magazine (with the excellent pull-quote "If you don’t want algorithms to feed you passive listening, get active.")
- An earlier appearance on Ari Herstand's The New Music Business podcast with some book-anticipation towards the end
- The book's page on Goodreads

1. The technical goal is to organize music so it is explorable. Exploration rewards curiosity.


2. The product goal is to help listeners find joy. Joy is various.


3. The feature goal is to connect individuals to communities. Music is a social energy.


4. The business goal is to make money for artists. Not from.


5. There should be one reward system, consistently applied. All financial contracts should be public.


6. Listeners are entitled to their own data. Their stories, their love.


7. Artists are entitled to their own data. Their audiences, their work.


8. People are collectively entitled to their collective knowledge. Coherences, congruences.


9. Musical taste and preference are emergent transiences of humans, yearned after by empathetic systems. Not imperious instruments of control.


10. Never refer to music as “content”, even to yourself.

Spotify's Loud and Clear site includes an analogy between musicians and football players, ostensibly to explain how "aspirations" to make money from creative/athletic pursuits are more widespread than actual career success.  

This comparison is not original or unique to Spotify, and does make some limited sense. With both art and sports, you can choose to spend your time on them, and the process of making music or training for football is labor in the sense of requiring time and effort, but most of the people making this choice are not going to end up being financially compensated for their labor. A small minority are able to make a living from it, but you cannot join this minority simply by wanting.  

The key difference between music streaming and football, however, is that in music, every stadium is Wembley.  

If you are an amateur soccer player, you know that you are an amateur soccer player. You play on an amateur team, in an amateur league, probably with amateur referees in a random city park that has other uses the rest of the week. No matter how astonishing a goal you score, it is a goal in an amateur game in a park on Sunday.  

In music, however, everybody plays in the same venue, nominally in the same league. Any song on any of the major commercial music-streaming services could be streamed 1 billion times tomorrow. Structurally, in the music version of football, an amateur player from a local park could kick a ball and it could slip past Caoimhin Kelleher in the 121st minute to send Liverpool crashing out of the FA Cup.  

That game was at Old Trafford, not Wembley, but the point is that this mostly doesn't happen. The statistical economic dynamics of music and football are very similar, which is why the analogy presented itself in the first place. But the aspirations are exactly why it doesn't work. In football, not only do you know your current status, but you can see the potential future steps in your career, and how they might happen. You could impress a local scout with your park goal, and get a tryout for a local semi-pro team. You could lead the semi-pro league in assists and get signed for a year by a second-division team. You could captain your second-division team to promotion, and like a fairy-tale, three years later you are getting crushed 7-0 by Manchester City and trying to claw your way out of the relegation zone so your dream can continue just a little bit longer.  

In music, there used to be a story like this. You played club gigs in your hometown, and gave demo tapes to your friends. Somebody who ran a local label maybe heard you and liked you enough to help you put out a record. Maybe that record got played on college radio a little, and got you a chance at a deal on a minor major label. Maybe your minor major-label debut had a minor hit. Maybe your label stuck with you and you got to make more records. Maybe your third album has a song about getting drunk alone in your hometown and introducing yourself again to your friend's mother and it blows up and suddenly you are playing in Wembley. Or Fenway Park, at least.  

Streaming offers the tantalizing illusion that these laborious steps have been eliminated by technology. But really they haven't. Music is an attention economy. The dominance of the biggest attention companies used to be reinforced by constraints of physical distribution, but it mostly survives the format shift. Most of the songs on the biggest playlists still come from the three major labels.  

Which doesn't mean that the story of your potential career hasn't changed. The new steps might involve playlists instead of clubs, viral videos instead of college radio, and maybe a judicious distribution deal instead of an old-school contract with an advance you will never recoup. And these new steps, if they happen, could happen more suddenly than the old steps, and thus it can feel like they could happen suddenly at any moment.  

But, still, mostly they won't. Mostly the paths to big success still go through labels, particularly major ones. Mostly the old major-attention economy survives through minor adaptations. Whatever aspirations they have, or labor they expend, most of the 10 million artists on streaming services will never get beyond semi-professional status in the most marginal sense of "semi". I have songs on Spotify, too. They took labor to make. A few people have streamed them, and I have been paid a few cents for those streams. Last time I checked, my lifetime earnings from streaming music were well on the way to $5. From $4.  

But I am an amateur. I know I'm an amateur, I'm not trying to make a living by making music. If streaming services all start imposing minimum stream-thresholds for royalty payouts, I may never get to that glittering $5 in the distance, and that will be morally disappointing but practically fine.  

If you're trying to become a professional, it's not fine. If regressive thresholds take away your sense of progress, that's not fine. If the successes you aspire towards operate like lotteries, so that you can't work towards them, that's not fine. If the people who operate the economy in which you will or will not be able to make a living sound like they are dismissing you as a non-participant, that's not fine.  

I like the football analogy, actually, but I think it applies the other way around: if you own a stadium, and you invite all the players in the world to come in and play in front of all the fans, you don't have to promise them all glory, but you better not try to tell them that some of their goals won't count.

I like legislation as a tool for social change, so I'm positively predisposed towards the Living Wage for Musicians Act as a tactic, and I agree with its goal of making it possible for more people to make better livings as musicians.  

But I don't think this proposed law, as written, will work.  

Here's how it would operate:  

Music-streaming subscriptions in the US would have a federal government fee of 50% added to them...  

This ought to be in the headline of every article covering this story. "Make Streaming Pay", the UMAW slogan for this effort, sounds like a vendetta against streaming services, especially coming from the same people who brought us "Justice at Spotify" previously, but as a music listener you should understand that the people who would pay this time are you. The proposed bill would add fees to music subscriptions. Fees are a well-established tactic, but not exactly a well-loved one. It's at least faintly ironic that Congress is scrutinizing Ticketmaster's excessive fees at the same time that this bill is proposing to add one to music streaming.  

And 50% is a lot. A $10.99/month subscription would get an added $5.50 government fee, raising the total to $16.49. The bill even specifies a minimum of $4, so a $5.99 student subscription would rise to $9.99. While I don't think either of those are unreasonable prices for all the music in the world, they're giant relative jumps. I would fully expect them to be publicly unpopular as a proposal, and thus hard to find support for in Congress. If enacted, they would probably cause many existing subscribers to downgrade to free (ad-supported) alternatives. Enough people doing so could cancel out the monetary benefit, so this should not be proposed without careful modeling of likely price flexibility. I doubt that has been done, and certainly no evidence of it has been presented by the bill's advocates. I would also expect most or all streaming services to lobby vigorously against this change because of these effects, even though the fee itself is not paid by them. Except...  

and music-streaming services would have a 10% tax on their "non-subscription" (meaning mainly advertising) revenue in the US...  

You can't add fees to free, so here's the other half of the plan. Most streaming services already pay ~70% of revenue to licensors, keeping ~30% for themselves. A 10% tax on revenue thus cuts gross advertising profit by a third. Since Spotify (whom I single out here only because as a public company they report music-specific financial results, which Apple/Amazon/YouTube Music as divisions of larger companies do not) has mostly not turned a net profit at all, this proposed tax will almost certainly be taken as intractably punitive, and I expect all the services with ad-supported tiers to resist it. Spotify probably cannot afford to threaten to pull out of the US like it threatened to pull out of Uruguay when a (different) version of this idea was proposed there, and would presumably not want to increase their own prices again having only recently raised them in most countries, making it hard to take the tactic they are taking in response to a 1.2% tax in France. So I would expect Spotify to lobby against this as if it is an existential threat.  

There's also a very important question here about what constitutes a music service, and in particular whether YouTube (not YouTube Music) and TikTok count. The bill doesn't address this, although the UMAW advocacy for it strongly implies that YouTube, at least, is meant to be included. I do not expect Google to quietly accept a 10% tax on any meaningful subset of YouTube advertising revenue.  

which would be collected into (and by) a new government fund/agency...  

Streaming music royalties are already split into three different components: to licensors, to publishers (for songwriters), and to performing-rights agencies (also for songwriters; it's a long story). This bill would add a fourth. That seems to me like the wrong direction, and grounds for skepticism even before we get into how the new fund would work. As an example it also implies that every country would need to create a similar fund of their own, although the bill as written seems to ignore the fact that it applies to the flow of money in only one country, while the music itself is global.  

which would also collect and tabulate monthly streams by unique master recording...  

This detail is unexplicated in the bill, but introduces a very serious technical requirement. Music is delivered to streaming services by licensors in releases composed of tracks, and it's normal for there to end up being many different tracks that have the same original audio, e.g. a single and that same song on the subsequent album and the same song again later on a compilation, and all these again in many different countries. Reconciling these requires audio-analysis software that can correctly match two tracks of the same recording even if they've gone through slightly different processing, and correctly differentiate between two different pieces of music even if they contain substantial similarity (like a song and a remix of it that adds a guest verse). And even after you've correctly matched tracks by their audio, their credits might differ, so you have to figure out which credits you're going to use. I can testify from 12 years of involvement with the process at the Echo Nest and Spotify that this is all not a trivial problem, and can be error prone even in a long-running production system. The administrators of the new fund are going to have to hire more programmers than they probably realize.  

impose a cap of 1 million streams/month on each such recording...  

This is arguably the most critical, progressive and interesting detail in the bill. Rather than just increasing all artists' current income by a small proportional amount, the bill attempts to specifically support artists who might not currently be making a living from their music, by effectively redirecting some or most of the money from songs with >1m streams back into the payment pool. This is why the recording-matching has to be accurate, but sadly is also the key to trivial manipulation of this scheme to evade its intent. Each detected "unique recording" is subject to a 1m cap, but it's not hard to produce multiple tracks that sound the same to listeners, but intentionally defeat the usual methods for automatic matching. Were this bill to be passed, I expect it would become normal practice to do this across releases and services, to make every track of the same recording register uniquely, so that each one gets its own 1m cap. The producers of very popular songs would have a strong incentive to also try to do it over time for each song during a given month, hoping to accumulate N million streams 1m at a time across N variations of the same song.  

The 1-million-stream threshold here is arbitrary. The bill itself doesn't justify or explain it. Rep. Tlaib has mentioned in speaking about this bill that it takes 800,000 streams/month at a current average rate of $.003/stream to make the equivalent of minimum wage, which is correct math, but that's per artist, not per track. The unavoidable market truth about music (like most non-commissioned art) is that financial reward is not a function of quantity of labor. You can spend any amount of time making a song, and maybe nobody will play it. If we really want, as a society, to give people a living wage for the labor of making music, as opposed to lucking into popularity, then we need to spend our government energies on grants or Universal Basic Income, not on streaming taxes and fees.  

and then divide payments proportionally by capped streams...  

This sounds like just unremarkable process, but is sneakily the most serious flaw of the whole bill as written. The fund combines all streams from all services, and all money from all services, and distributes that combined money according to those combined streams. This sounds like the pro rata royalty-allocation method already in use by all major streaming services. The crucial difference, though, is that services do not do this with one big pool of money and streams, they do it with an individual pool of money and streams for each payment plan (in each country). This is essential, because the revenue per listener varies widely across countries and plans. A stream from a Spotify Premium subscriber in Iceland is worth considerably more than a stream from an ad-supported listener in India.  

By combining all the streams and all the money, this plan would make it possible to use the cheapest form of artificial streaming to accumulate fraudulent streams that would share money from the most expensive ones, thus inaugurating a golden age of streaming fraud.  

This is not only a fatal flaw of the bill as written, it's one that reveals that the writers of the bill do not know how the existing royalty methods work, and didn't consult with anybody who does.  

90% to "featured" artists and 10% to "non-featured" artists...  

It's a minor selling point of this bill that it would result in some royalties being paid to "non-featured" artists, like session musicians and backing vocalists, who do not (usually) get royalties at all from the current system. The amount is small, though, and administering it would be a procedural headache. Because those people don't currently get paid royalties, their participation isn't necessarily included in the licensors' metadata. And, conversely, because those people don't get royalties, they're currently mostly paid for their work in old-fashioned wages. Give them a share of the royalties and we might find that that becomes an excuse to pay them less up front, in the same way that tip workers are often given lower base wages.  

The bill does not say how royalties would be split between multiple featured or non-featured artists. I guess it's loosely implied that it would automatically be equal shares to each, since there's no mention of any mechanism to specify otherwise. The bill does specify that "artists" means individual humans, not corporations or generative AIs (!), which seems to mean that bands are not part of this scheme, only each person one at a time.  

And, notably, the bill as written specifically does not include songwriters. This is a little surprising to me, since I think of advocacy for higher royalty rates for songwriters as part of the same family of social-justice causes as higher royalty rates for performers, and songwriters get the smallest share of royalties in the current system. I'm not looking forward to the antagonism between "performers" and "songwriters" that this omission might provoke.  

who sign up with the fund and provide payment information.  

This, too, is both a distinguishing characteristic of this plan and a drawback. The whole point of this fourth royalty scheme is to route it around the first three, although in practice it's mainly the payment of recording royalties to licensors (and thus to labels) that the writers are trying to avoid. Labels, particularly major ones, often write artist contracts in which advances are paid up front, and artists not only get a small percentage of the royalties later, but even that small percentage is accounted for as repaying the advance as a loan. So an artist might, in practice, get no royalties for a while, or ever. (Although, again, they were paid an advance, and if their royalties don't earn back the advance, they don't have to repay it any other way.)  

But, of course, you don't have to sign a label contract in order to release music on streaming services. DIY distributors either charge small flat fees, or take very small shares of your royalties. But labels provide services in addition to taking royalties (and paying advances), and maybe you want those. I suspect that musicians signed to major labels are mostly doing OK, at least temporarily during their maybe-short label tenure. And if they aren't, and their label contracts are why, maybe that's where the laws should be pointed.  

But that means this fund is yet another thing an artist has to sign up for and manage, and which in turn has to manage and verify them. I have not found any good estimates of how many artists currently do not do the work to register their songs to collect performance and mechanical rights, and how often there are contradictions between ownership claims, but I'm sure both are common. There's precedent in performance-rights organizations for international cooperation, but I don't know if any of those operate on this scale, and even if they do, this bill doesn't propose to use them, so this new fund (and its equivalents in other countries, if they exist) would have to reinvent all of that process.  

The stipulation about individuals, not companies, seems obviously like a preemptive attempt to keep labels from registering on their artists' "behalf" and collecting this new windfall too, but I'm not immediately convinced that won't happen somehow anyway. And indeed it might have to for the scheme to accommodate the estates of dead artists, whom I assume it doesn't intend to exclude.  

Even if we imagine that nobody attempts to evade this rule, though, the existence of a fourth royalty that bypasses labels is likely to push labels, and the three major-label companies in particular, to object to this bill too. And were it enacted, I would expect to see labels begin to change the terms of their contracts to reduce or eliminate artist shares of the recording royalties since they're now supposedly getting this new Living Wage paid separately.  
 

The notable thing this bill does not include is any mechanism or support for this claim that the UMAW, who collaborated on it, continue to make here:

The Living Wage for Musicians Act is built to pay artists a minimum penny per stream, an amount calculated specifically to provide a working class artist a living wage from streaming.

The bill, as written, is very definitely not "built" to pay $.01/stream. UMAW's intro puts the current average stream rate at $0.00173 (including YouTube), and after an hour or so of spreadsheet noodling I could not see any way it would more than double this for the biggest beneficiaries (artists whose tracks all approach 1m streams without going over), even if nothing else in the industry changed in reaction. That would be $0.00346/stream, still a long way from $0.01. It doesn't help my confidence in UMAW's math diligence that their "calculator" to show the effects of this bill not only just multiplies streams by $0.01, but doesn't even bother to apply the 1m-stream cutoff.  

Nor have I seen any explanation of why the suspiciously round penny is coincidentally the magic living-wage level, and I'm willing to bet a large number of pennies that no such explanation exists. There are many very-good bands who do not have 1 million streams total, all time, across all their songs on Spotify. That's not a multi-year living wage for a group of people even at a dime per stream.  
 

But OK, it's easy to criticize. If I'm in favor of laws, and I share the goal of improving the lives of musicians, what should we do instead?  

When in doubt, try to remove imbalances of power. Reduce complexity, reduce secrecy. Personally, I would start by trying to simplify and improve the existing royalty process, rather than adding another incompletely-thought out layer with uncertain consequences.  

We got a good idea about how to do this, by accident, recently, when Spotify and Deezer and UMG collaborated to change their contractual rules for recording royalties to pay nothing to tracks that don't reach 1,000 streams over the course of the last year. This is a regressive measure I personally despise, but the interesting part is that they actually couldn't pay those songs nothing, because the performance and mechanical rates are set by law (at least in the US). If the recording rates were also set by law, those wouldn't have been subject to secret contract negotiations either. Moving all the rates into law would also allow them to be determined (and debated in public) as a coherent set, which would make a lot more sense. And while we're at it, we could eliminate the spurious performance royalties, reducing the number of royalty components to two, one for the performers and one for the songwriters. And, in fact, if we allowed artists to designate original songs, so that this information was passed on by licensors to streaming services, then both royalties could be paid at once for those tracks, reducing the reporting overhead for artists and services both, and recovering some of the money currently lost on the way to artists who never took the time to sign up for BMI or ASCAP.  

Those simplifications would not, in themselves, provide a predictable living wage for all working musicians, either. But they would make the current streaming model less mysterious, and less beholden to secret agreements between a few giant corporations. Plenty more work would remain to be done. But that work would be easier think about, and easier to do. And less likely to produce earnest laws that probably have no chance of living up to their authors' hopes for them, or ours.

Talking to Robots About Songs and Memory and Death
Infinite Archives, Fluctuating Access and Flickering Nostalgia at the Dawn of the Age of Streaming Music
(delivered at the 2024 Pop Conference)  

Let me tell you how it used to be. Songs were written and sung and recorded, but then they were encased in finite increments of plastic, and our control over our ability to hear them relied on each of us, sometimes in competition, acquiring and retaining these tokens. The scarcity of particular plastic could shroud songs in selective silence. A basement flood could wash away music.  

Imagine, instead, a shared and living archive. Music, instead of being carved into inert plastic, is infused into the frenetic dreams of angelic synapses. Every song is sung at once in waiting, and needs only your curious attention to summon it back into the air. Nothing, once heard, need ever be lost. The rising seas might drive us to higher ground, but our songs watch over us from above.  

When I proposed this talk, Spotify held 368,660,954 tracks from 61,096,319 releases, and I could know that because I worked there. The servers of streaming music services are unprecedented cultural repositories, diligently maintained and fairly well annotated. We pour our love into them, and in return we can get it back any time we want.  

That's the techno-utopian version, at least. In the real-life version, the angels are only robots, and the robots aren't even actual robots. The infinite generosity of technology is constrained by relentless pragmatic contingencies: corporations, laws, contracts, stockholders, greed. All those songs are there, technically poised, but whether we are allowed to hear them depends on layers of human abstraction and distraction. This is what people mean when they object to streaming as renting the things that you love. The erratic logistics of music licensing control whether any given song is permitted to escape from the streaming servers. Licensing, in turn, is permuted by artists and labels and distributors and streaming services, and then again by the borders of countries and the passage of time. The song you want to hear again is still there. But that may not be enough.  

"Renting the things you love" sounds bad. But so too, I think, does "purchasing the things you love". I don't philosophically need or want my love to be materialized in a form for which I have to transact, and which I then have to store. I want to be able to recall joys effortlessly. The system model of instant magical recall, which is an illusion that streaming can sustain under conducive network conditions, is what I think we want, what music wants. If renting is reliable, maybe it's fine. But how reliable is it?  

If you don't work for a streaming service, you can only really assess this by anecdote. Joni Mitchell objected to Spotify's podcast deal with Joe Rogan, and revoked its rights to her whole catalog. Because rights are complicated, though, it didn't entirely work. When I proposed this talk, there was one Joni Mitchell song still accessible on Spotify in the US, a stray copy of "A Case of You" from a random compilation released in roundabout evasion by some label other than hers. If you didn't know this context, you would have no immediate way to tell Joni wasn't an emerging artist with just the one complicated, hopeful first single so far. A complicated hopeful first single with 103,102,704 plays, apparently, so you might wonder a little bit. Promising, I think. I'd like to hear more.  

Since then, the license police caught up to that rogue compilation, and "A Case of You" is gone again. As of my drafting of this talk, Joni Mitchell's Spotify catalog was a 10-song 1970 BBC live album, and a single pointlessly overbearing cover of "River" by somebody else that was gamed onto Joni's Spotify page by the trick of labeling it as a classical composition, which causes Spotify to treat its composer as one of its primary artists. If the only artists with the power to withhold their songs were ones of Joni's stature, that would actually be fairly manageable. The plastic tokens of Blue are not scarce or expensive. If only artists had the power to withhold songs, actually, this would be a conversation about art and the limits of authorial control, and whether Joni is allowed to come take your copy of Blue away from you if you listen to Joe Rogan.  

If you do work for a streaming service, though, and you can manage not to resign in protest of anything it does that you disagree with, then you don't have to rely on annecdote, you can use data. So I did. I ran the historical analysis of all post-release licensing gaps in song availability from 2015 to 2023, both overall and aggregated by licensor. In practice, in turns out, almost all songs available today have been available for streaming continuously since release. There are a handful of licensors whose tracks are routinely retracted, and there are good reasons for this, which I'm not allowed to tell you but I can reassure you that those are not the tracks we're worried about. Actual licensing gaps for actual songs with actual audiences are, statistically speaking, vanishingly rare. I made a nice graph of this.  

If you work for a streaming service, however, you can also get laid off by that streaming service, which I also did. When this happens you have a surprise 10-minute call with an HR rep you've never seen before at 9:15 on a Monday morning, and then your laptop is remote-locked and you don't have those graphs any more. The robots are not allowed to talk to me now. Who will sit with them when they are sad? The problem with externalizing our memories and our note-taking into the cloud isn't technological reliability, it's control. The problem with renting the things you love is not the fragility of the things, it's the morally unregulated fragility of the relationship between you and the corporate angels.  

We'll be OK without that graph. It was not, shall we say, the "A Case of You" of data graphics. The things that really belonged to Spotify, Spotify can keep. The goverance models for modern corporations are still painfully primitive. We understand that local democracies and a little bit of international law are a better model than crusader feudalism for communities of place, and I feel like it's morally apparent that corporations, as communities of purpose, ultimately deserve the same models and protections. If you move away from a city, you're still allowed to come visit. I should probably be allowed to visit my graphs. I like to imagine Joni ripping copies of her own CDs and adding them to Spotify as local files just as a jurisdiction flex.  

My listening, on the other hand, is my own. Consumer protections are slightly more advanced than employee protections, so you can request your complete listening history from Spotify any time you want. For much of the decade I spent working at Spotify, though, I also maintained an abstruse weekly annotated-playlist series called New Particles, so I have my own record, not just of what I heard, but what I cared about. Over the course of 454 weeks, I cared about 35,900 tracks by 13,951 different artists. This is small for data, but big for annecdotes. What I find, going through it, is that almost every week beyond the recent past has at least one song that is now, or at least currently, unavailable. Some of the earliest lists from 2015 are missing 3 or 4, but by 2017 and 2018 it's usually 1, plus or minus 1.  

Counting is not an emotional exercise, though, and all interesting music-data experiments begin with some kind of counting but don't stop there. So I went through the playlists I was listening to in my birthday week each year, cross-checking the specific tracks that had gone gray in Spotify, to see if I could tell a) how missing they really are, and b) how much I care. This is mostly what my job at Spotify was like, too: short bursts of math, and then the long curious process of trying to understand the significance of the resulting numbers. And I did consistently say that I would be doing this even if they weren't paying me.  

From my March 31st 2015 list I am missing the song "Kranichstil" by the Ukrainian/German rapper Olexesh. His albums before and after seem to all be available for streaming still. This one isn't, but the song is easily found on YouTube. It's still sinuous and boomy and great.  

2016: I'm missing "Rolling Stone" by the Pennsylvania emocore duo I Am King. They're still putting out sporadic emo covers of pop songs, which is one of my numerous weaknesses. "Rolling Stone" was an original, and I admit I don't remember it super-well, so maybe the version that is currently available on Spotify is different from the unavailable one I liked in 2016, but it's definitely close enough.  

2017: "Por Amor" by the Chilean modern-rock band Lucybell. I had the single of this on my playlist, and you can't play that any more, but the slightly longer version is still the first track on the readily-available album Magnético, and still sounds like a stern Spanish arena-rock transformation of a New Order song.  

2018: The whole album MASSIVE by the K-Pop boy-band B.A.P. is unavailable, but the song I liked, the cartoonish rap-rock rant "Young, Wild and Free", was originally on a 2015 EP, which is still available.  

2019: The trap-metal noise-blast "HeavyMetal!" (no space between the words, exclamation point at the end) by 7xvn (spelled with the number seven, then x-v-n) is off of Spotify, but you can still find it on Soundcloud, which in this case feels about right.  

2020: A gothic metalish song called "Menneisyyden Haamut" by the Finnish band Alter Noir. Their Spotify page is empty now, and if you Google this song, the results are the orphaned Spotify page, two links from their own Facebook page to that empty Spotify page, and then my playlist that I put the song on. I sent myself an email to see if I knew what the story is with this, but I haven't heard back from myself yet.  

2021: "Fuck You Nnb" by lieu. I am old and do not know what "Nnb" stood for, but I do know that lieu was supposedly a 15-year-old kid deliberately switching between distributors so their songs would end up strewn across disconnected artist identities. Perfect public memory of what we thought was a good idea when we were 15 is not necessarily a civic virtue. In some cases forgetting is probably the right way to remember.  

2022: ANISFLE were an ornate Japanese rock band, or at least a heavily embroidered impression of one. Their Spotify profile is blank, their web store is empty, I guess something catastrophic happened to them. But there are still a few of their videos on YouTube, and they're still ridiculous and magnificent.  

2023: The only new thing I loved last April 4th that didn't even survive for a year was a maskandi song called "UYASANGANA YINI" by uMjikelwa. It seems to still be available on Apple Music. One of his other albums is on Spotify, and I will be completely honest that although I adore maskandi and follow hundreds of maskandi artists to make sure I have a constant supply of new maskandi to listen to, I usually pick one random song from each album and I do not pretend I can really tell them apart. If you snuck into my web archives and swapped this for anything similar, I would almost certainly not notice.  

I think I can live with that much loss. Individual human obstruction occludes individual archives, but the network of archives, from the well-regulated to the unruly, tends to route around suppression. It's hard to make everybody forget.  

And meanwhile, my database memory is far, far better than my brain memory. How many of those 13,951 artists could I list without looking? Some. Lots, but not most. But this is how I live, now. How old was my kid when we had the birthday party where their best friend's brother fell on a brick and had to be taken to the ER? I don't remember, but I can look through Google Photos and find it by the pictures we took before the panic. Which China Mieville book did I read first? I don't remember, but I bet I can find the email I wrote you right afterwards. Or maybe I sent it from a work address and so I can't.  

So yes, our technically perfect externalized memories are imperfected by our insistence on staging them behind our contentious and fluctuating rules. We produce a compromised projection of our archives by fighting over their access controls. Our human systems hold back our information systems.  

But I think we'd rather have that than the other way around. If my record store, in 1989, had made a ridiculous deal with Joe Rogan and Joni had pulled her whole divider out of the M bins, we had no collective recourse. We could check the used stores, but who gets rid of Joni Mitchell albums? Recovering from this, later, would require re-shipping a case of Blue to, oh, Canada? And everywhere else. The grayed-out tracks on Spotify playlists are more like the coy ropes across the wine shelves in Whole Foods on Sunday in blue-law states. Not only are we ready when the laws and processes finally relent, but we are reminded, every moment until then, how arbitrary and ridiculous it is that they still have not.  

What would better laws and processes involve? What we need here, I think, is a legal and syntactical structure for asserting music rights as layers, starting with the artist. Right now, each licensor of a recording makes a deal with its artist, with terms and dates, but then turns around and sends the streaming services only enough data to assert that licensor's own isolated claims. If licensors were required to pass along both the span of their claim, and the underlying artist ownership to which the rights will subsequently revert, then royalty attribution could fluctuate without affecting availability. And by the way, while we're building that, we could also use the same structure to embed the composition rights with the recording rights, eliminating the completely insane indirection in which the publishing rights for streaming songs have to be re-asserted separately by writers and then rediscovered separately by collecting societies.  

If this last idea appeals to you so much that you would like to read it again in print, it also appears in my upcoming book, titled You Have Not Yet Heard Your Favorite Song: How Streaming Changes Music, which comes out in June on Canbury Press. A book is another kind of externalized memory. It's good to remember how we thought things were. In my case I wrote this one while I was working at Spotify, but not because I was working at Spotify, and at least I got laid off in time to edit a bunch of present- and future tenses into the past before they were printed on paper. Memory, too, is a system: of layers and contingencies and adaptation and revelation. Underneath, somewhere, there's always love. We fall in love three minutes at a time, and we might forget the songs but we won't forget the falling.  

Meanwhile, we improve the world when we can, with whatever tools and influence we are currently allowed. When we can't, we try to preserve it's potential in hiding, if not in angelic invulnerability, then at least above the water line. We leave the robots on guard, not because we trust them, but because it makes them feel useful and we don't have the heart to tell them that they aren't real. We let new songs invoke the ones we're not supposed to hear. We name our loss, and we try to not die before the day when we're allowed to remember everything again.  

If you are interested in hearing me speak, in person, and you live in LA, you have two opportunities coming up.  

On Friday, March 8, I will be at UCLA speaking about human complications of simple numbers in music data, as part of a day-long Music + Data Symposium. The event is free, but seating is limited and you should register in advance.  

On Saturday, March 9, at 9:00am, I will be at USC speaking about infinite archives, fluctuating access and flickering nostalgia at the dawn of the age of streaming music, as part of the three-day Pop Conference. This too is free but limited, and you should register in advance.  
 

If you aren't near LA and just want to hear my voice, I was also on an episode of the new NeuralZen Venture Podcast. I don't know that anything I said there qualifies as Neural, Zen or relevant to venture capital, but it's a good medley of a bunch of things I have been saying over and over to many people in the last few weeks as I talk to them about the state of music and what my next steps in it might be.