The pocket doesn't fit in a prompt: what an AI beat generator can't hold
A prompt is a description; a beat is a set of decisions at resolutions a description can't reach. What breaks first: step-level timing, a vocalist who hasn't turned up, and a sound with a name instead of a category.
Fifty words is a generous prompt for a beat. Genre, tempo, a mood, maybe an artist name typed in for reference. The Afroswing pattern on the Fun Lab cheat sheet doesn't take much more than that on paper either: snare on the 3, kick borrowed from dancehall's dotted shape, swing in the high fifties. Type it into a text box and you get something back. It will be playable. It will not be a record, and the gap between the two is structural, not mystical. Worth being precise about, because the parts a prompt genuinely can't reach are the parts of the job worth keeping.
The spec stops one resolution too high
The cheat sheet gives you positions, and positions are the easy half. Under every lane of the grid, each hit carries its own offset in ticks and its own velocity, and that layer is where the record actually lives. The boom bap pattern's notes on the same page say it outright: the pocket is in what isn't quantised. Quantised to the sixteenth, the pattern is playable by anyone. The version that makes a producer lean in is the one where the hat on step 14 sits a couple of ticks late, every bar, because whoever programmed it kept dragging it until their head nodded.
The Jersey Club five-count is the cleanest way to see the problem. Kick on steps 1, 5, 9, 12 and 15: two quarters, two dotted eighths, then an eighth. You can write that sentence, a model can read it, and the output will still be wrong, because the whole forward pull of the genre sits in the fifth kick landing just before the bar turns over. Early by a sixteenth and it reads as a mistake. Late and it drags. The information that decides it is one tick wide. A prompt has room for "Jersey Club" and "140 BPM" and nowhere to put the tick.
The loop is the easy half
Generating a loop is the part machines got good at first, and it was never the hard half. A beat is built against a vocalist who doesn't exist yet. When I cut an Afroswing beat for a B Young brief, the gaps in the pattern are shaped like how he phrases: short pockets, space after the hook line, room underneath for the ad-lib. When the brief names Alicai Harley, it's a different set of holes. The notes barely move. Where the empty space falls moves everything.
That makes the arrangement conditional, and conditionality is where a text prompt falls over. What happens at bar 9 depends on what the rapper did at bar 8. If she runs past the downbeat, you pull the kick out and let her land alone. If she leaves the last beat empty, the rim answers it. None of that can be written in advance because none of it has happened yet. A prompt describes a finished object; this half of the craft is a conversation with a person who hasn't turned up. It's the line between the beats and the records. Juice with B Young and Proper Paper with Alicai Harley sit on the discography page as released tracks, and the beats underneath them were finished the way all beats are: locked before anyone sang a note, but built around the shape of the person who would.
A sound has a name, not a category
Ask a text box for a warm Rhodes and you get the average of every Rhodes in its training data: competent, in tune, anonymous. The sound that carries a record is specific. It's the chopped vocal with the formant shifted wrong on purpose, the log drum patch that slides just sharp of the note it's supposed to find. Generative systems regress towards the mean of a genre because that is what an average is. The identity of a beat is the part that deviates from it.
There's a second layer a prompt has no access to at all: what clears. Sampling touches two copyrights, the composition and the recording, and what a flip costs decides how the beat gets written. A beat built to hold a cleared one-shot is structured differently from one built around a four-bar loop that needs a licence. That is a constraint from contracts, and it shapes the writing from the first bar. The clearance piece on this blog covers the two-copyright structure; the point here is narrower. You can tell a prompt to use a sample. It has no way of knowing which samples are available to you, or at what price.
Interrogate it at step level
None of this is an argument against the tools. The spec half is real work and a prompt does it in seconds, and a competent genre grid is a fine place to start. The craft argument is about which half you keep.
So if you use one, interrogate it at the resolution that matters. Ask what is on step 15. Ask whether the third hat is early or late, by how much, and whether it is late in the second bar the same way. The answer usually collapses into vagueness exactly where the pocket should be, which is useful to know, because it shows you where the actual work goes. Drag the tick. Write the bar that answers the vocalist you have in mind. Pick the sound with a name instead of a category.
The pocket survives a prompt the same way it always survived the cheat sheet. You can copy every visible position and still miss it, because the deciding information is the part nobody could print. That part is still yours. For now it is the whole job.
