Every Noise at Once
@everynoise.bsky.social
everynoise.com and associated curiosity; see also @glennmcdonald.bsky.social
You can compare a playlist to *multiple* others at once, too.
November 23, 2025 at 3:31 PM
You can compare a playlist to *multiple* others at once, too.
Reposted by Every Noise at Once
I talked to PJ Wehry on the Chasing Leviathan podcast, and now you can hear us:
www.youtube.com/watch?v=iCTd...
www.youtube.com/watch?v=iCTd...
Every Noise at Once: Spotify, Music Discovery, and Human Connection with Glenn McDonald #podcast
YouTube video by The Chasing Leviathan Podcast
www.youtube.com
October 7, 2025 at 2:45 PM
I talked to PJ Wehry on the Chasing Leviathan podcast, and now you can hear us:
www.youtube.com/watch?v=iCTd...
www.youtube.com/watch?v=iCTd...
Thanks! At the moment there's nothing for which soliciting donations would be worthwhile, but I will post if that changes.
October 5, 2025 at 12:34 PM
Thanks! At the moment there's nothing for which soliciting donations would be worthwhile, but I will post if that changes.
This is unlikely to happen, but here's a simple Chrome extension that will let you control the volume for any site:
everynoise.com/site-volume-...
Download, unzip, go to chrome://extensions/, turn on Developer Mode, hit Load Unpacked, pick the unzipped folder.
everynoise.com/site-volume-...
Download, unzip, go to chrome://extensions/, turn on Developer Mode, hit Load Unpacked, pick the unzipped folder.
September 24, 2025 at 7:33 PM
This is unlikely to happen, but here's a simple Chrome extension that will let you control the volume for any site:
everynoise.com/site-volume-...
Download, unzip, go to chrome://extensions/, turn on Developer Mode, hit Load Unpacked, pick the unzipped folder.
everynoise.com/site-volume-...
Download, unzip, go to chrome://extensions/, turn on Developer Mode, hit Load Unpacked, pick the unzipped folder.
(As best I can tell, since it also has no list.)
September 2, 2025 at 6:13 PM
(As best I can tell, since it also has no list.)
The genre system we created at the Echo Nest and expanded for a subsequent decade at Spotify had, by its unnecessary demise, over 6500 genres, every one of them picked and guided by humans. The automated ML system that replaced it has 708 tags.
Every Noise at Once
everynoise.com
September 2, 2025 at 6:12 PM
The genre system we created at the Echo Nest and expanded for a subsequent decade at Spotify had, by its unnecessary demise, over 6500 genres, every one of them picked and guided by humans. The automated ML system that replaced it has 708 tags.
NRbG uses the reverse of "related artists in", essentially, and the two are not necessarily symmetrical. But if you also hook up Curio, you can use "myartists" as an NRbG genre to search all your liked artists. I do that plus a bunch of particular genres...
July 27, 2025 at 10:51 PM
NRbG uses the reverse of "related artists in", essentially, and the two are not necessarily symmetrical. But if you also hook up Curio, you can use "myartists" as an NRbG genre to search all your liked artists. I do that plus a bunch of particular genres...
Sometimes I come across a very long playlist and I want a quick sense of how my own listening intersects with it. There are lots of ways to quantify this, but here's one of them in Curio query form (you can copy and paste the query from the alt-text):
![?28pRQNZyF8cHagMgrpLBOR.other playlists.tracks
/my artist=(.artists:@1.id.artists)
||apoints=(.my artist.counts.points...._,(1),total),alignment=[=apoints*count]#alignment](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:v7a2vpz7hyepe2upz6bmxtxe/bafkreieoo53akq4co56g3sdod7hbojhkrlzgjt5ayjljkba5gvqjpkq3dy@jpeg)
July 24, 2025 at 7:34 PM
Sometimes I come across a very long playlist and I want a quick sense of how my own listening intersects with it. There are lots of ways to quantify this, but here's one of them in Curio query form (you can copy and paste the query from the alt-text):
If you're curious about how different streaming-royalty allocation schemes would affect you and your artists, or could be tempted into curiosity if you thought there was a way to see this, there's a way to see this:
furia.com/log/517
furia.com/log/517
July 19, 2025 at 10:15 PM
If you're curious about how different streaming-royalty allocation schemes would affect you and your artists, or could be tempted into curiosity if you thought there was a way to see this, there's a way to see this:
furia.com/log/517
furia.com/log/517
But if you'd rather have an unweighted shuffle by artist, just group before shuffling:
tracks/artist....shuffle.1:@<=100
tracks/artist....shuffle.1:@<=100
July 9, 2025 at 5:58 PM
But if you'd rather have an unweighted shuffle by artist, just group before shuffling:
tracks/artist....shuffle.1:@<=100
tracks/artist....shuffle.1:@<=100
You can reshuffle the created playlist from its Curio page, too.
This query randomizes all your tracks, but then groups the random list by artist and takes only the first track per artist, up to 100 total. This is effectively a weighted shuffle by artist.
This query randomizes all your tracks, but then groups the random list by artist and takes only the first track per artist, up to 100 total. This is effectively a weighted shuffle by artist.
July 9, 2025 at 5:56 PM
You can reshuffle the created playlist from its Curio page, too.
This query randomizes all your tracks, but then groups the random list by artist and takes only the first track per artist, up to 100 total. This is effectively a weighted shuffle by artist.
This query randomizes all your tracks, but then groups the random list by artist and takes only the first track per artist, up to 100 total. This is effectively a weighted shuffle by artist.
People complain about Spotify's shuffle mode, and I never listen on shuffle so I don't care, but if you do, you can make your own in Curio:
tracks....shuffle/artist;.1:@<=100
Run that on the query page, and then save the results as a playlist.
tracks....shuffle/artist;.1:@<=100
Run that on the query page, and then save the results as a playlist.
July 9, 2025 at 5:53 PM
People complain about Spotify's shuffle mode, and I never listen on shuffle so I don't care, but if you do, you can make your own in Curio:
tracks....shuffle/artist;.1:@<=100
Run that on the query page, and then save the results as a playlist.
tracks....shuffle/artist;.1:@<=100
Run that on the query page, and then save the results as a playlist.
Do not let the world's deluge of grievous wrongs numb you to your own tiny useless delightful errors.
July 2, 2025 at 4:18 PM
Do not let the world's deluge of grievous wrongs numb you to your own tiny useless delightful errors.
If you want to scrutinize algorithmic playlists Spotify makes for you, you can copy their tracks into normal playlists and then use Curio to run queries on those. E.g.:
playlists:~<[DW 2025-06-27].other playlists
.tracks.(.artists:@1).other artists
/label=(.artist catalogs.catalog.label)#count
playlists:~<[DW 2025-06-27].other playlists
.tracks.(.artists:@1).other artists
/label=(.artist catalogs.catalog.label)#count
![Screenshot of my Curio query page, showing this query:
playlists:~<[DW 2025-06-27].other playlists.tracks.(.artists:@1).other artists
/label=(.artist catalogs.catalog.label)#count
returning results like
283 label countβ of
1 Independent 3 of [...3]
2 Art Gates Records 2 of [...2]
3 Artistfy Music 2 of [...2]
4 FRIENDSHIP. 2 of [...2]
5 QOOLONG 2 of [...2]
6 recordJet 2 of [...2]
7 1964251 Records DK2 1 of [Anteeter]
8 2019 We are Suburban 1 of [Rebecca Lou]
9 2023 maddy irene Β©οΈ 1 of [maddy irene]
10 2023 Wormholedeath Records 1 of [Conspiracy of Blackness]
11 2074559 Records DK2 1 of [Re:O]
12 2080792 Records DK 1 of [DIGITAL LOVE]
13 210485 Manhatten Discs 1 of [DIGITAL LOVE]
14 2285049 Records DK 1 of [Crimson Crisis]
15 3105988 Records DK 1 of [Caldera]
16 3151900 Records DK2 1 of [The Hunt]
17 3304016 Records DK 1 of [DJ MIX-ICON]
18 3677236 Records DK2 1 of [Queen of Dreams]
19 3947540 Records DK2 1 of [DIGITAL LOVE]
20 5880853 Records DK2 1 of [Diamond Riot]
21 655386 Records DK 1 of [Gone Are the Days]](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:v7a2vpz7hyepe2upz6bmxtxe/bafkreid5dp2fogkz4tshefuqiebr7t73gvibyztsn7rundxkvcprqp2mxy@jpeg)
July 1, 2025 at 5:20 PM
If you want to scrutinize algorithmic playlists Spotify makes for you, you can copy their tracks into normal playlists and then use Curio to run queries on those. E.g.:
playlists:~<[DW 2025-06-27].other playlists
.tracks.(.artists:@1).other artists
/label=(.artist catalogs.catalog.label)#count
playlists:~<[DW 2025-06-27].other playlists
.tracks.(.artists:@1).other artists
/label=(.artist catalogs.catalog.label)#count
E.g. here "Umbral Exorcism" is properly grayed out on _Moonbow Rebellion_, since it was previously released, but not grayed out on the single where it was new.
June 28, 2025 at 6:24 PM
E.g. here "Umbral Exorcism" is properly grayed out on _Moonbow Rebellion_, since it was previously released, but not grayed out on the single where it was new.
Oh, wait, in order to support multiple releases by each artist we need to get first dates by songkey, but mark oldness by track id:
June 28, 2025 at 6:21 PM
Oh, wait, in order to support multiple releases by each artist we need to get first dates by songkey, but mark oldness by track id:
Here, for example, is ?? in a Curio query that gets a playlist and some albums, annotates the track, album and artist overlaps between them (in that order of priority), and flags the tracks in each album that were previously released (by that artist) before their album appearances.
June 28, 2025 at 3:35 PM
Here, for example, is ?? in a Curio query that gets a playlist and some albums, annotates the track, album and artist overlaps between them (in that order of priority), and flags the tracks in each album that were previously released (by that artist) before their album appearances.
Need some slightly less-final word than "mourn" here. But you're welcome for everything so far.
June 27, 2025 at 4:34 PM
Need some slightly less-final word than "mourn" here. But you're welcome for everything so far.
DACTAL changes that might affect you if you're doing Curio queries:
filter negation was :! now :-
reverse index-number filtering was :@- now :@@
repeat was ?? now !
filter negation was :! now :-
reverse index-number filtering was :@- now :@@
repeat was ?? now !
Today in obsessive buffing of rough spots:
Filter negation is now done with -, instead of !.
tracks:-=Amaranth
This was the only use of ! as a suboperator, which frees it up to be the repeat operator, instead of ??.
messages._,replies!
Filter negation is now done with -, instead of !.
tracks:-=Amaranth
This was the only use of ! as a suboperator, which frees it up to be the repeat operator, instead of ??.
messages._,replies!
June 19, 2025 at 5:31 PM
DACTAL changes that might affect you if you're doing Curio queries:
filter negation was :! now :-
reverse index-number filtering was :@- now :@@
repeat was ?? now !
filter negation was :! now :-
reverse index-number filtering was :@- now :@@
repeat was ?? now !
This affects several of the Listening History queries in Curio, but none of the ones that get cached, so it would likely only matter to you if you have your own saved queries derived from Listening History views, or similarly adventurous.
June 18, 2025 at 9:03 PM
This affects several of the Listening History queries in Curio, but none of the ones that get cached, so it would likely only matter to you if you have your own saved queries derived from Listening History views, or similarly adventurous.
Previously in DACTAL this would have been:
tracks/artist...count,_count
which was an unlovely quirk left over from Thread, where aggregators all started with underscores, and appeared as magic pseudo-properties instead of a separate (and thus more easily extensible) operation type.
tracks/artist...count,_count
which was an unlovely quirk left over from Thread, where aggregators all started with underscores, and appeared as magic pseudo-properties instead of a separate (and thus more easily extensible) operation type.
June 18, 2025 at 8:56 PM
Previously in DACTAL this would have been:
tracks/artist...count,_count
which was an unlovely quirk left over from Thread, where aggregators all started with underscores, and appeared as magic pseudo-properties instead of a separate (and thus more easily extensible) operation type.
tracks/artist...count,_count
which was an unlovely quirk left over from Thread, where aggregators all started with underscores, and appeared as magic pseudo-properties instead of a separate (and thus more easily extensible) operation type.
Today's tiny DACTAL tweak that probably affects nobody: in an aggregation, semicolons explicitly identify aggregators. So this query is a count of counts; the first "count" is a property (of groups), the second "count" is the aggregator.
tracks/artist...count;count
tracks/artist...count;count
June 18, 2025 at 8:49 PM
Today's tiny DACTAL tweak that probably affects nobody: in an aggregation, semicolons explicitly identify aggregators. So this query is a count of counts; the first "count" is a property (of groups), the second "count" is the aggregator.
tracks/artist...count;count
tracks/artist...count;count
Made some improvements to playlist comparisons. (Also, did you know Curio does playlist comparisons?)
June 14, 2025 at 2:34 AM
Made some improvements to playlist comparisons. (Also, did you know Curio does playlist comparisons?)
My guess would be that they were tracks that were released but then retracted or rescheduled. But no way to tell after the fact.
Happy to help figure out if queries could help you.
Happy to help figure out if queries could help you.
May 2, 2025 at 7:12 PM
My guess would be that they were tracks that were released but then retracted or rescheduled. But no way to tell after the fact.
Happy to help figure out if queries could help you.
Happy to help figure out if queries could help you.