9Fourteen
Algorhythms 9Fourteen turns a finished game world into a musical score. A typical pipeline drops a library over a level and crossfades when the designer trips a volume. We do the reverse of procedural generation: take the rendered landscape and parse it. Grammar theory calls that graph parsing, or an inverse graph grammar. The dressed space – heightfields, rooms, portals, navmesh, the routes a player can actually walk – collapses to a topological tree. Ridges, chokes, plains, hubs, and dead ends become nodes and rewrite rules, not mood tags.
Those spatial rules are the generative music grammar. Elevation can lift contour. Branching can thicken harmony. Tight geometry can compress pulse and range. Open ground can lengthen the line. A corridor and a desert cannot share a cue, because they do not share a graph.
Four steps carry the world into the ear. First, parse the landscape into playable structure rather than every decorative mesh. Second, extract the graph-rewrite blueprint: what connects to what, what constricts, what opens, what repeats. Third, map that blueprint onto the composer’s grammar: motifs, instruments, chord vocabulary, rhythm scales, so the human still authors the language and the level performs it. Fourth, serialize the result as MIDI and play it at runtime, following the player as the graph changes underfoot.
The soundtrack is not accompaniment. It is an auditory mathematical mirror of the ground the player is standing on. That is beyond a sample library: the form of the world is the form of the piece, scene to scene.
9Fourteen will ship as a plugin for Unity and Unreal. It does not replace the composer or the middleware you already run. It sits next to Wwise, FMOD, or MetaSounds and does the job those tools were never asked to do: read the playable layout of a scene and perform a human score from that layout.
The plugin listens to what the level already knows; navmesh, rooms, portals, elevation, density, and not every decorative mesh goes into the process of creating the graph. That graph is the rewrite blueprint. The composer drops in motifs, instruments, and chord rules. At runtime 9Fourteen maps space onto that grammar and serializes MIDI (or feeds MetaSounds) so a choke and a plain cannot share a cue. When the player moves, the graph underfoot changes and the line follows.
Studios keep the credit. The composer writes one language; motifs, instruments, rules, not a stem for every biome. 9Fourteen Studio holds that grammar. The runtime plugin, in Unity or Unreal, lets each scene speak this grammar. The composer still owns the score. The world no longer needs a new recording for every place the player can stand.
9Fourteen is not only a game plugin. It is useful wherever a person moves through a designed space and the sound should follow the shape of that space, not a playlist.
Museums, galleries, and walkthroughs already have the graph generated: rooms, sightlines, dead ends, atria. Theme parks score the queue, the reveal, the choke, and the plaza as loops. Architecture and real estate can walk a BIM or a scan and hear the plan – useful in review before it is useful as art. XR which includes; VR (headset, fully virtual), AR (graphics on the real world), mixed reality (both in one view), and location-based venues are the same problem as a game, and often richer in information, a scanned warehouse or a rebuilt ruin can speak a grammar instead of a single stem.
Sparser uses still count. Wayfinding (airports, hospitals, campuses, museums, malls, subway stations) and accessible buildings can thicken tone at junctions and thin it in long halls. Digital twins and city models can sonify congestion and connectivity for people who work from maps all day. Virtual-production stages change geometry between takes; a grammar tied to the current volume stays honest and more realistic as the set moves.