Published by PitchChanger · Updated · How these guides are made

Hear the difference

Compare the same noise burst with only high cut changed.

Pause your workspace preview before comparing these clips.

Original noise burst50 ms burst, then silence
Download original noise burst (WAV)
Reverb at 8 kHz high cutMedium Room; 1.5 s decay; mix 0.30
Download reverb at 8 khz high cut (WAV)
Reverb at 2 kHz high cutSame settings except high cut
Download reverb at 2 khz high cut (WAV)

Actual local browser exports; no singer or acoustic room was measured.

How to use this workflow

  1. Choose a revealing passage

    Use a short consonant, cymbal or transient with space afterward. Start with a copy of the original.

  2. Change high cut alone

    In Reverb & Delay, hold the room, decay, pre-delay and mix steady; compare a higher cutoff with a lower one.

  3. Generate both results

    Download a fresh result for each setting. Match playback volume and listen after the dry attack as well as during it.

High cut reduces brightness in the reverb path

A high-cut filter attenuates higher-frequency energy rather than removing everything above a hard frequency wall. In this tool the control shapes the generated reverb response. The dry component is still present when the mix is below fully wet, so an unchanged sharp dry attack does not prove the control failed.

The available range is 1,000–10,000 Hz in 100 Hz steps. A lower value is a comparison choice, not a universal vocal preset. Ableton’s effect documentation likewise distinguishes frequency shaping from decay and wet balance; its algorithms and parameter behavior are not identical to this site.

A controlled comparison with one original burst

The source is a 50 ms seeded broadband noise burst in a two-second mono WAV. We generated both results through the actual browser interface using Medium Room, Decay 1.5 s, Pre-delay 0.010 s, Reverb mix 0.30 and Feedback delay off. Only high cut changes: 8,000 Hz versus 2,000 Hz.

The samples are synthetic and intentionally simple. Listen after the burst, where the dry source is silent, to judge the tail. These files demonstrate this rendering path; they do not establish that 2 kHz is preferable for a singer, room or commercial mix.

Swipe or scroll sideways to read all columns.

ParameterBrighter comparisonDarker comparison
High cut8,000 Hz2,000 Hz
Decay1.5 s1.5 s
Pre-delay / mix0.010 s / 0.300.010 s / 0.30

Choose the control that matches the symptom

If the entire reverberated contribution is too prominent, reduce Reverb mix. If a tail lasts across the next phrase, shorten Decay. If the tail length and level work but its upper-frequency splash distracts, lower high cut in small steps.

Changing a room preset also resets its underlying reverb settings, so select the room first and then set the comparison values. Otherwise you may accidentally compare several changes and attribute the result to high cut alone.

Check the saved tail and avoid stale results

Changing the control invalidates the old result. Select Generate effect again before downloading WAV or MP3. Do not rename an older file as though it contains the new setting.

Listen at a comfortable matched level on the playback system you will use. This is a browser render comparison, not a physical room measurement, hearing test or promise of de-essing. A harsh source may still need source-level editing outside the reverb path.

Common questions

Does high cut shorten the declared decay?

It changes the reverb response’s frequency balance; use Decay when the intended tail length is the problem.

Why can the dry sound stay bright?

The dry component remains in a mixed result. Listen after its attack to isolate the reverb tail.

Technical references