The temptation to mirror a jump sound into a landing sound is structural, not aesthetic. The two events are paired in the player’s mind: press jump, leave the ground; hit the ground, land. A designer who has an upward sweep for the jump naturally reaches for a downward sweep for the landing, because the motion is inverted and the inversion feels like it should be audible.
That instinct produces a sound that is technically paired and functionally wrong. A landing is not a jump played backwards. It is a different event with a different job, and the job is not to describe motion. It is to confirm contact, weight, and the end of a state. The sections below work through the three axes where mirroring fails — time, spectrum, and function — and the parameters that hold up when the landing is designed on its own terms.
Time Is Not Symmetric: A Jump Has a Duration, a Landing Has an Instant
A jump is an event with an extent. The character leaves the ground, the upward motion continues, and the sound has a duration that matches the perception of travel. The documented retro recipe gives the jump a length of 0.1–0.2 seconds, with a pitch that rises quickly from low to high and an envelope that starts immediately and decays gradually[reference:0]. The CRI Middleware breakdown separates the jump into an impulsion of 75–100 ms and a motion layer of at least one second, which reinforces the same idea: the jump is not a single click, it is a short event with a body[reference:1].
A landing is not an event with an extent in the same way. It is a collision. The documented retro landing recipe is noise-based, under 0.05 seconds, with an immediate attack and an extremely fast decay[reference:2]. The same source warns that a longer landing sound starts to read as an explosion, not a landing[reference:3]. That is not a stylistic preference. It is the difference between a sound that describes motion and a sound that marks a contact event.
Mirroring the jump’s duration into the landing produces a landing that lingers. A 150 ms landing with a gradual decay reads as the character sinking into the ground rather than hitting it. The duration benchmark guide covers the category ranges; the landing case is one where the correct duration is shorter than the jump’s, not equal to it.
Spectrum Is Not Symmetric: A Jump Is Harmonic, a Landing Is Noise and Body
A jump that sweeps upward is a pitched event. Its identity is carried by a moving fundamental and its harmonics, which is why the retro recipe uses a square or triangle wave rather than noise[reference:4]. The pitch direction is the signal: rising reads as upward motion, and the harmonic content makes that motion legible on a small speaker.
A landing that mirrors the jump would also be pitched, just downward. That is the wrong spectral structure. A landing is a contact event, and contact is carried by broadband noise, not by a moving fundamental. The Unreal Engine impact synthesis example describes a layered system: a modal sinusoidal output for the resonant body, a band-pass filtered white noise burst for the contact transient, and a low-pass filtered pink noise signal for the low-frequency body thud[reference:5]. The noise is not decoration. It is the part that makes the impact read as physical.
A downward pitch sweep on a landing can work as an additional layer, but it cannot be the primary layer. A landing that is only a downward tone reads as a “descending blip,” not as a body meeting a surface. The frequency range guide covers the band placement for the jump; the landing’s identity lives in a different spectral structure entirely.
The documented double transient on a landing is a good example of a structure that has no jump equivalent. One platformer’s development notes describe implementing a double transient “to give the impression of two feet hitting the ground”[reference:6]. That is a landing-specific affordance: two contacts, not one sweep. A mirrored jump has no reason to contain two transients, because a jump is a single push-off.
Function Is Not Symmetric: One Confirms Departure, the Other Confirms Arrival and Weight
The third axis is the one that makes the mirroring failure most audible in play. A jump sound answers the question “did my input register?” It is a departure confirmation. A landing sound answers a different set of questions: “did I arrive,” “how hard,” and “what did I land on?” It is an arrival and weight confirmation, and it is tied to the surface.
The platform documentation for a footstep system makes the distinction explicit: “we want the sound played when landing after a jump to be different to regular footsteps,” and the system passes a “Land” state separately from the movement states[reference:7]. That separation is not about pitch. It is about the fact that the landing is a different kind of event from the footstep, and it needs a different sound.
Weight is the part of the landing function that a mirrored jump cannot carry. Research on pitch and weight perception consistently finds that lower pitch is associated with heavier objects, and higher pitch with lighter ones[reference:8]. A jump that is mirrored into a downward sweep may end on a low pitch, but it does not have the body that makes the low pitch read as weight. The weight comes from the low-mid energy around 200–400 Hz and the short, dense transient, not from the pitch direction alone.
A landing that is designed on its own terms can also scale with the fall height or impact velocity. The documented platformer approach is to use relative velocity to play the sound at different volume levels, so a soft landing is quiet and a high-speed landing is loud[reference:9]. A mirrored jump has no velocity parameter, because a jump’s departure speed is set by the input, not by the fall.
What the Pair Actually Shares: Timing and a Thin Contextual Link
The rejection of mirroring does not mean the two sounds should be unrelated. They share a timing relationship and a contextual relationship, and those are worth keeping.
The timing relationship is simple: the landing fires on the contact frame, not on the frame the character is detected as grounded. One implementation places the landing thud “on the LANDED-promote frame (cd=2, ~1 frame before exact landing)” to anticipate the contact[reference:10]. That is a scheduling detail, not an acoustic one, and it matters more than any pitch relationship between the two sounds.
The contextual link is that both sounds belong to the same character and the same surface. A landing on grass and a jump from grass should share a surface identity, which is why the landing is usually built from the same foley material as the footstep, not from the jump. The footstep surface guide covers the surface vocabulary; the landing inherits it, and the jump does not.
There is one case where a thin mirror can work: a stylized game where the jump and landing are deliberately presented as a pair of “blips,” one rising and one falling. A course exercise on jump sound design describes exactly this: “a takeoff blip and a landing blip are the entire sound budget” [reference:11]. That is a valid design, but it is a minimal confirmation pair, not a full landing. It confirms that the events happened without trying to carry weight, surface, or impact. The moment the game needs the landing to feel physical, the mirror stops being sufficient.
A Landing Patch That Is Not a Mirrored Jump
The table below gives a starting configuration for a landing that is designed on its own terms. The values are starting points, not a specification, and the contrast with the jump is the point.
| Property | Jump | Landing |
|---|---|---|
| Primary structure | Pitched sweep, harmonic | Noise burst + low body + optional pitch layer |
| Pitch direction | Upward | Not required; if present, secondary |
| Duration | 0.1–0.2 s | Under 0.05 s for the core impact; tail can extend if needed |
| Transient | One onset | One or two onsets (double transient for two feet) |
| Velocity scaling | Not typical | Volume and/or filter scales with fall speed |
| Surface identity | Usually character-level | Inherits from footstep material |
The landing patch is not a rejection of the jump. It is a separate design that happens to share a character and a timing window. The jump and landing guide covers the movement system as a whole; the anti-mirroring principle is that the pair should be designed as two events, not as one event and its inversion.