A song has a fixed length and ends. Game music does not get to know how long it will play, so it has to loop with no seam, stay bearable for hours, and often change with what the player is doing. That is three jobs a normal track never has.
Applies to any instrument and any DAW. The ideas are the technique. The instruments at the end are just a fast way to make the material.
A normal track has a fixed length. It starts, it plays, it ends, and you move on. Game music does not get to know how long it will play, so it has two jobs a song never has: it must loop with no audible seam, and it must stay bearable while it does that for a long time. On top of that it often has to change with the game, calmer while the player explores, tense while they fight.
A three minute song is written to be listened to once, closely. A piece of game music might play for forty minutes while a player wanders a single area, so it is usually written the other way round, to sit under attention rather than grab it. Anything that grabs you the first time, a big hook, a memorable fill, a vocal line, becomes the thing you dread by the twentieth loop. Good game beds tend to be a little under-composed on purpose.
So most of the craft here is not writing a better tune. It is writing material that survives repetition, leaves room for the game to change it, and stays out of the way of the rest of the audio, the effects and the dialogue, that has to sit on top.
Write a section that ends exactly where it began so there is no seam, then keep the material even enough that nothing in it demands to be noticed on the tenth pass. Those are two separate problems and a loop needs both solved.
The end of the loop has to flow into the start with no click, no gap, and no obvious moment where it snaps back to the beginning. The usual catch is reverb and delay tails: a sound near the end rings out past the loop point and gets chopped off, which the ear hears as a click. Leave the last moment clean, or let the tail wrap around so it rings over the start of the next pass. Avoid a big one-off gesture right before the loop point, because that is exactly what makes the repeat obvious.
The enemy of a loop is anything you can remember. A distinctive fill, a drum roll, a lead line that peaks. On the first pass it is pleasant. By the twentieth you are waiting for it, and then it grates. Keep the material even and textural, spread the interest around instead of parking it in one memorable spot, and the loop wears far more slowly.
A short two bar loop fatigues fast because the ear learns it in seconds. A longer loop takes longer to learn. A bed that slowly evolves and never quite repeats fatigues least of all, because there is no exact seam to memorise. That is why so much exploration music is closer to a drifting texture than a tune.
Set it to repeat and leave it playing while you do something else for ten minutes. If you catch yourself waiting for a particular moment, that moment is what will grate, so even it out or take it off the loop. If you can hear the exact point where it jumps back, the seam or a cut-off tail is the problem, not the writing.
You do not write one clever track that reacts. You write it in pieces, either as layers that can fade in and out, or as short sections that can follow each other in any order, and the game decides which pieces play. Two approaches cover almost everything a solo or indie developer needs.
Write the same piece as separate layers on one shared key and tempo. A quiet bed on its own, then drums, then a lead, then whatever a full combat moment needs. While the player explores, only the bed plays. As danger rises, the game fades the other layers in on top. Because every layer shares the same harmony and tempo, any combination fits, so the music swells and calms with the action without ever changing song.
Write several short sections that can play in any order, and usually a calm set and a tense set, then let the game jump between them. When the player enters a fight it moves to the combat sections; when the fight ends it returns to the calm ones. The jumps are lined up to musical boundaries so they land on the beat rather than cutting off mid-phrase.
In practice both approaches usually mean writing the same idea twice: a calm exploration bed, sparse and steady, and a tense or combat version on the same chords with more drive, more percussion and a harder sound. Keeping the two on the same harmony and tempo is what lets the game move between them cleanly, whichever approach it uses.
The switching itself is normally handled by audio middleware rather than by the music file. FMOD and Wwise are the two you will hear named most often. You do not need to run either to write the music. Your job is to deliver clean layers or sections at a steady, shared tempo and key, so whatever system plays them can line them up. Even a small game with no middleware at all can crossfade between a calm loop and a tense loop in its own engine.
Leave room in it. In a game the sound effects and the dialogue carry the information the player actually needs, so the music has to sit underneath them rather than compete. A bed that stays out of the way is doing its job, even when nobody notices it is there.
A footstep, a reload, a warning sound, a line of dialogue: each of those tells the player something. If the music is too loud or too busy in the same frequency range, it buries them, and the player misses what they needed to hear. So game music is usually mixed quieter than you would mix a song, and kept clearer in the midrange where voices live.
Everything above works by hand in any DAW, and it is worth doing once so the technique is yours. The three instruments below just remove one hard part each: an evolving bed that never repeats, a loop that stops sounding like a loop, and lines you can drag out to build a louder layer.
ARGISH self-plays endless evolving beds that never land on the same bar twice, which is most of an exploration loop already done for you. SILT takes a loop you already have and turns it into something that never quite repeats, so the seam stops being a seam. REHEAT writes lines you can drag out and layer on top for a combat version. Between them you can build the looping, layered, non-fatiguing material a game needs.
The three come together as the Collection with three licence keys. Whatever you make in them is yours to ship in your game.
No download and no signup to try one in the browser. Everything on this page works by hand in any DAW too, which is rather the point of writing it down.
We write these when there is something worth writing down. One email when a new one lands or a new Tunary instrument ships. No newsletter, no schedule.
Tunary