The Terrain Engine: The Last Few Seconds of Your Track as Landscape

Terrain is described in the catalog in six words: the last few seconds of the track rendered as receding landscape. That is the entire idea, and it makes this engine structurally different from every other one in the catalog.

Almost everything else draws this frame. A bar is a band right now; a ring is one frame of spectrum. Terrain is the engine where the last few seconds of the mix are the geometry.

How a landscape gets built

Each frame, the engine samples the spectrum into a fixed number of columns and pushes that row into a history buffer. Then it draws the buffer from back to front: the oldest row sits at the horizon, the newest at your feet, with rows bunching toward the horizon so parallel lines converge like a plane.

The trick that makes it read as terrain rather than as noise is a painter's-algorithm fill. Each row is filled with the background colour before its ridge is stroked, so nearer land occludes further land. Without that step the rows cross-hatch into a mess. It is the same hidden-line idea a plotter used in 1979, and it is still the cheapest way to make a wireframe look solid.

The beat is baked into the row that was born on it

A heightfield built purely from band levels drifts with the mix and reads as weather, not rhythm. So each new row is lifted by the beat envelope at the moment that row is created, and that lift travels backwards through the field with the row.

The result is the engine's signature: a kick becomes a ridge you can still see receding several seconds later. You are not watching the beat; you are watching the last dozen beats walk away from you. On a track with a consistent groove it produces regular ranges. On a track with a build, you can literally see the density of the ridges increase toward the horizon before the drop arrives at your feet.

Six ways to draw the same field

• Ridge Lines is the default and the most literal: stacked hidden-line ridges receding toward the horizon.
• Wire Mesh draws rows and columns and deliberately skips the occluding fill, because a wire mesh is supposed to be see-through.
• Contour Map fills each elevation band, with no hidden-line pass, so the field reads as a topographic plate rather than a landscape.
• Canyon Scroll mirrors the same field above and below a travelling corridor, which is the closest Terrain gets to a tunnel.
• Dune Field drops the roughness almost to zero for wide, soft forms. This is the mode built to sit behind lyrics and ambient material.
• Peak Silhouette draws three layered ranges, far to near, each from a different slice of history, against a sky that lights on the beat. A silhouette by definition cannot brighten, so the light behind it has to.

The controls that change the terrain, not the colour

• Relief is the vertical exaggeration: how tall a given amount of energy makes the land. It is the first control to reach for when a scene looks flat or looks like spikes.
• Horizon sets where the far edge sits in the frame, which is really a composition control. Push it up for more sky and room for a title; push it down to fill the frame with land.
• Row spacing controls the perspective compression and how much the rows narrow toward the horizon. Higher values read as a longer distance.
• Roughness blends a linear response against a squared one. Low is dunes; high is jagged peaks, because squaring the band exaggerates the loud columns and suppresses the quiet ones.
• History depth is how many rows the field holds, which is literally how many seconds of the past are on screen.

Speed deserves its own note, because it means something unusual here. Terrain has no clock of its own; its only motion is history advancing. Speed therefore sets how many rows are pushed per frame, normalised so that the shipped default is exactly one row per frame. It is capped low deliberately: each push repeats the current spectrum row, so a large value writes several identical rows and the relief flattens into plateaus.

Containment on a vertical offset

Most engines measure containment as a radius from the centre. Terrain cannot: a row's height is an offset from that row's own baseline, so the limit is the distance from the baseline to the top of the frame box. Passing a vertical offset through a radial limit is exactly how geometry ends up leaving the frame at the top while still measuring as contained.

Canyon Scroll is the sharpest case, because its corridor widens with distance until the furthest row sits on the frame edge, so any audio-driven height added to it would push the far walls straight off the canvas. Its wall offset is limited against the half-height it is measured from. The practical upshot for you: the frame margin holds on every mode at every reactivity setting.

When to reach for it

Terrain suits anything with a sense of journey: cinematic, ambient, post-rock, downtempo, and long-form mixes where a viewer is watching for minutes rather than seconds. It is one of the lighter scenes in the catalog to run (a default element budget of 96, 44 on mobile), which matters when the video is an hour long. The Terrain engine reference has the full control table.

It is the wrong engine when you want a hit to land visibly on the frame you are looking at, because by design the hit walks away. For that, Lattice switches geometry on the beat and Stage Lights strikes fixtures on it.