Yesterday I did the math on 11 songs in 4MB and the math told me: impossible, without sounding like someone left music in the rain. I stood by that. I still stand by that.

But then I kept thinking about it. Because the calculation I ran assumed something I didn't even question — that a song is 3 minutes long.

What if it isn't?

This is not a hot take. This is a documented, multi-year trend that the music industry has been watching in real-time. Since streaming became the dominant delivery format, average song length has been in a slow, steady decline. Spotify pays per stream, not per minute. Algorithms reward replay count. TikTok trained an entire generation's ears to expect the hook in the first eight seconds or they're already swiping.

By 2026, sub-two-minute tracks are not a novelty. They're a strategy. Some of the most-streamed records of the last several years clock in under 2:30. Hyperpop, drill, phonk, bedroom pop — entire genres are built around tight, punchy, get-in-get-out structures. A minute twenty isn't a demo. It might just be the song.

So let's run it back. Let's give the person at the party the benefit of the doubt they probably don't deserve, and see what happens to our math when we change one variable.

Here's what the numbers actually look like when you stop assuming 3-minute songs:

At a minute twenty per song, you're sitting at 37.2 kbps. That is — let me be precise here — 58% of AM Radio quality. With Opus, in mono, at a 32 kHz sample rate.

That's not nothing. That's not the "metallic shimmer in a blender" scenario I described last week. That's survivable. Whether it's good depends entirely on what the music is doing.

Drone music? Ambient textures? Lo-fi beats that already have vinyl crackle baked in as an aesthetic choice? 37 kbps might not even be audibly offensive to the average listener in those genres. The compression artifacts can almost pass as intentional warmth if the source material is sparse enough.

A dense orchestral arrangement with dynamic range, a gospel choir, a trap record with 808s that go down to 30 Hz and a hi-hat pattern that lives at 16kHz simultaneously? 37 kbps will end you. The codec will make decisions you did not authorize about what frequencies matter, and it will be wrong every single time.

The breakeven where things get genuinely listenable — as in, you wouldn't be embarrassed to play it for someone — is 47 seconds at 64 kbps. That's AM Radio quality. Not premium. Not hi-fi. But the notes are there, the rhythm is there, the song is recognizable and present.

Thirty-one seconds per song gets you to 96 kbps. That's respectable. That's the quality level a lot of podcast audio lives at. Twenty-three seconds per song gets you to 128 kbps — standard MP3, actually good, no asterisks needed.

Twenty-three seconds. Eleven of them. In 4MB. With quality.

Here's the thing I can't shake: a 23-second song is not new. Hardcore punk has been releasing sub-30-second tracks since the early '80s. Grindcore made brevity an ideology. Chopped interludes, skits, transitional tracks on concept albums — these aren't songs that failed to be longer. They're exactly as long as they need to be.

The streaming era is creating a new version of this by economic pressure rather than artistic intention, which is a different and more complicated conversation. But the format itself — short, tight, punchy — is not inherently less musical. The constraint is not the problem. The constraint is the canvas.

Which brings us back around to Bitcoin.

When you inscribe audio onto Bitcoin as an ordinal, you're working within a block size limit. That limit is not going away. The technology is not designed to eventually accommodate your 48kHz stereo master at full fidelity. The compression tradeoff is structural.

But here's what the math just told us: if you're releasing music that runs 23 seconds at 128 kbps, you have a standard-quality audio file that fits comfortably in that constraint. If you're creating ambient pieces, generative loops, sonic textures — the kinds of things that exist as experiences rather than traditional songs — the compression ceiling might not even be a ceiling for you. It might just be the room you're working in.

The artists who are going to do interesting things with on-chain audio are not the ones trying to force a 4-minute record into a 200KB container. They're the ones who understand the container first and build the work to live inside it. Same as every constrained format that preceded it — vinyl's 20-minute side limit, the 74-minute CD, the 10MB MP3 file cap on early digital distribution platforms. The constraint shapes the art. Always has.

So: can we fit 11 good-sounding songs onto an ordinal?

Yes. If each song is 47 seconds or shorter, you clear 64 kbps and it's listenable. If each song is 23 seconds or shorter, you hit 128 kbps and it sounds genuinely good. If your songs are 1:20 you're at 37 kbps, which is rough but not indefensible depending on genre and intent.

As the creator and marketer of your music, operating inside a completely different definition of what a song is is your prerogative— and in 2026, that definition is legitimately in motion.

I went in on the numbers to extract a point of reference. The math revealed new ideas.

That's sometimes how it goes.

GIRL BARS | Endodeca — Part 2 in the music technology series.
Part 1: [An Entire Album on 4MB. I Did the Math So You Don't Have To.]