Quick answer: Wave Hammer is a two-stage dynamics processor. The Compressor shapes the difference between loud and quiet material; the Volume Maximizer then raises or limits the result against an output ceiling. Start with the maximizer bypassed, aim for roughly 1–3 dB of gain reduction on the loudest passages, level-match the bypass, and only then set the final peak ceiling.
The name invites the wrong approach. Wave Hammer is not a button for hitting a file harder until it looks loud. It is useful precisely because the two jobs are separate. Compression can change punch, density, and envelope. Maximizing can raise the average level and restrain peaks. If both stages are pushed at once, it becomes difficult to hear which one damaged the transient or caused the pumping.
The current Boris FX Sound Forge 2026 documentation describes Wave Hammer DirectX as a classic compressor followed by a volume maximizer. Wave Hammer and Wave Hammer 2.0 remain familiar parts of the Pro workflow, while exact menu placement can vary between builds. This guide focuses on how to make the processor behave—not on a magic preset.
What Wave Hammer Actually Does
Wave Hammer runs its two sections in series. Audio reaches the Compressor first and the Volume Maximizer second. The original Sound Forge documentation describes the same order, and the Sound Forge Pro 12 manual identifies Wave Hammer 2.0 as the advanced mastering plug-in. That basic signal flow matters more than the version number.
| Stage | Main job | What to listen for | Typical failure |
|---|---|---|---|
| Compressor | Reduce dynamic range above a threshold | Punch, sustain, vocal consistency, pumping | Flat transients or audible level breathing |
| Volume Maximizer | Raise level and control peaks at the output | Peak density, distortion, loss of impact | A loud but brittle or clipped render |
Neither stage replaces measurement. Before and after processing, check the file with Sound Forge Statistics or the LUFS and true-peak meters. A waveform that looks full is not evidence that the delivery is correct.
Open Wave Hammer Without Committing the Effect
- Open a copy of the source file, not the only master.
- Select the full file or the passage you want to process.
- Open Effects → Wave Hammer and choose Wave Hammer 2.0 where both versions are listed. In builds that organize processors differently, find it through FX Favorites or add it to the Plug-In Chainer.
- Turn on preview and bypass the Volume Maximizer while setting compression.
- Save a named preset only after the controls work for this source.
The Chainer is the safer place to work when Wave Hammer is part of a larger chain because you can change order and bypass individual processors before rendering. Applying the effect directly is faster, but it also makes A/B checks and revision harder.
Set the Compressor from the Signal, Not a Recipe
Threshold
Threshold determines where compression begins. Lowering it does not merely make the file louder; it makes more of the signal eligible for gain reduction. Start high, play the loudest representative section, and lower it until the gain-reduction meter moves only when the material needs control.
For a stereo master, 1–3 dB of reduction on the loudest passages is a sensible audition range, not a rule. A spoken-word file may tolerate more consistent compression. A transient-heavy mix may sound smaller after only 2 dB if the attack is too fast.
Ratio
Ratio controls how strongly levels above the threshold are reduced. A 2:1 ratio means that a 2 dB rise at the input produces roughly a 1 dB rise above the threshold at the output. For mastering, I begin around 1.5:1 to 2:1. For dialogue or an unruly single source, 3:1 or 4:1 may be appropriate—but only after listening to consonants, breaths, and room tone.
Attack
Attack decides how quickly the compressor reacts. A very fast attack catches peaks but can shave the front off drums, picked strings, and consonants. A slower attack lets the initial transient pass and controls the body that follows. On a full mix, start slowly enough to preserve the kick and snare, then shorten the time only if the peaks remain uncontrolled.
Release
Release determines how quickly compression relaxes. If it is too short, the background and reverb can surge between hits. If it is too long, the next phrase arrives while the processor is still holding the level down. Listen through several musical bars or complete spoken sentences; a loop of one loud hit cannot reveal bad release timing.
Output Gain, Auto Gain, and Smooth Saturation
Output gain restores level after reduction. Use it to match the processed preview to bypass—not to win the comparison by being louder. Auto-gain can be convenient, but verify what it does with the meters because automatic compensation may exaggerate a setting that only sounds impressive from the level jump.
The original Wave Hammer documentation also describes a Smooth Saturation option for softening the character of strong compression. Treat it as colour, not protection. If the source needs saturation, choose it deliberately; if the goal is transparent peak control, first reduce the amount of compression.
How to Level-Match the Bypass
Human hearing is easily biased toward the louder version. If the processed side is 1 dB louder, it can appear clearer, wider, and more exciting even when the envelope is worse. A fair comparison needs approximately equal perceived loudness.
- Preview the Compressor with the maximizer bypassed.
- Use output gain to bring the processed signal close to the bypass level.
- Switch bypass on and off during the same section.
- Ignore loudness and judge the attack, low-end stability, vocal position, and room movement.
- Reduce compression if the processed version loses impact or breathes audibly.
Don’t chase a perfect LUFS match during every small move. A close meter match plus repeated listening at moderate monitoring level is enough to expose a preset that works only because it is louder.
Set the Volume Maximizer Second
Once compression is stable, enable the Volume Maximizer. Its threshold determines how much material is driven into limiting; its output level or ceiling determines the highest allowed output. Lowering the threshold makes the result denser. It does not automatically make it better.
For a streaming-oriented master, a -1.0 dBTP final ceiling is a practical starting point because lossy encoding can create inter-sample overs. However, Wave Hammer documentation from older builds labels the control in sample-peak terms, and a displayed -1.0 dB value is not proof that a true-peak-compliant limiter is active. Measure the rendered file with a true-peak meter and follow the destination specification.
For speech, the limiter should catch occasional peaks rather than sit in continuous heavy reduction. For music, listen to kick, snare, cymbals, and bass together. If the top end turns grainy or the low end makes the whole mix duck, back off the maximizer threshold.
Three Starting Points That Do Not Pretend to Be Presets
| Source | Compressor starting point | Maximizer approach | Stop when |
|---|---|---|---|
| Stereo music master | 1.5:1–2:1; slow enough attack to preserve transients; 1–3 dB reduction | Set the required ceiling; lower threshold cautiously | Kick or snare loses impact |
| Podcast or voice | 2.5:1–4:1; moderate attack and release; control phrases, not every breath | Catch occasional peaks after level balancing | Room tone pumps or consonants dull |
| Sound effect | Choose attack from the transient you must keep | Use only if a hard output cap is required | The effect loses its intended contrast |
These ranges are audition points. Threshold cannot be copied reliably from one file to another because source level changes where the compressor works. A threshold of -18 dB can be gentle on one recording and relentless on another.
Wave Hammer for Mastering vs Voice
On a stereo master, the processor affects everything at once. One bass hit can trigger gain reduction across the entire mix, so small moves matter. Correct frequency-balance problems before asking a broadband compressor to solve them. My complete five-step Sound Forge mastering workflow places corrective EQ before dynamics and final measurement after rendering.
On voice, the goal is normally intelligibility and consistent phrases. Remove distracting clicks and long level jumps first. Then use compression to narrow the difference between ordinary speech and louder words. The maximizer is the last guardrail, not the primary levelling tool. The dedicated Sound Forge podcast workflow covers the rest of the chain.
Presets, Reopening, and the Sound Forge 18 Behaviour
A preset is a stored control state, not a diagnosis. Preview the loudest and quietest relevant passages before saving it. Name useful presets by job and source—such as “voice light control” or “stereo master 2 dB GR”—rather than “make loud.”
There is also a current workflow trap worth documenting. In a March 2026 MAGIX community discussion about Wave Hammer in Sound Forge 18, users reported that reopening the processor does not necessarily return to the transient state they expected; the last saved preset is the reliable recall point. That is community evidence, not a vendor specification, but it is a good reason to save named settings and record them in the project notes.
Common Wave Hammer Mistakes
- Adjusting both stages together: you cannot tell whether compression or limiting caused the damage.
- Comparing at different loudness: the louder preview wins even when it sounds worse at matched level.
- Copying a threshold: threshold depends on the source level.
- Using a fast attack by default: transients disappear and the master feels smaller.
- Using a short release on bass-heavy material: the file pumps between low-frequency hits.
- Trusting a preset name: “Smooth Compression” or “Mastering” cannot know the source dynamics.
- Double limiting: Wave Hammer maximization followed by another hard limiter can remove impact without providing useful extra loudness.
- Skipping the final render check: codec conversion can change true-peak behaviour.
Wave Hammer FAQ
Is Wave Hammer a compressor or a limiter?
It is both in series. The first stage is a compressor; the second stage is a Volume Maximizer that limits peaks while raising the overall level.
Should I use Wave Hammer or Normalize?
Use Normalize for a defined gain or loudness change when dynamics already work. Use Wave Hammer when peak-to-average balance, transient control, or limiting needs to change. Measure first so you know which problem exists.
What ratio should I use for mastering?
Start around 1.5:1 to 2:1 and listen for roughly 1–3 dB of reduction on loud passages. The correct value depends on the mix; preserving punch matters more than matching a number.
What output ceiling should I use?
Use the value required by the destination. -1.0 dBTP is a practical streaming starting point, but verify the rendered file with a true-peak meter because the Wave Hammer control may be labelled or measured as sample peak in older builds.
Why does Wave Hammer make the audio pump?
The threshold may be too low, the release may be too short, or low-frequency peaks may be driving excessive gain reduction. Raise the threshold, lengthen the release, and reduce the amount of compression while listening through complete phrases or bars.
Should I use Wave Hammer 2.0 instead of the original?
Use the version available and stable in your Sound Forge build. Wave Hammer 2.0 is the newer mastering processor, but the method is the same: set compression first, level-match bypass, set the ceiling second, and measure the render.
The Practical Rule
Use Wave Hammer as two processors, not one loudness button. Shape dynamics with the Compressor, make the bypass comparison fair, then use the Volume Maximizer only as hard as the delivery requires. Save the setting, render a new file, and verify loudness and true peak again. If the processed version is merely louder—not tighter, clearer, or more controlled—the setting has not earned its place.