
ReaVerb's Max FFT is a performance and latency choice, not a room-size control. The REAPER guide describes larger FFT sizes as using less CPU while adding latency, and smaller sizes as using more CPU with the work spread more evenly. Keep that tradeoff separate from the impulse response that defines the reverberation.
Key Takeaways
- A larger FFT setting is not automatically a higher-quality room.
- Monitoring latency and offline rendering have different requirements.
- Set all applies these performance settings to other ReaVerb instances.
Identify whether the problem is sound design or playback
A narrator may like the chosen room but find live monitoring uncomfortably delayed. Alternatively, a dense mix may have playback dropouts despite an acceptable reverb character. Record the symptom before replacing the impulse.
The room-design guide covers selecting a useful reverberant character. This article addresses how the convolution is processed rather than choosing another fictional hall.
Compare the documented Max FFT relationship
The REAPER 7.81 manual says the FFT choice should not itself change the sound, while affecting CPU usage, latency and possible dropouts. Retain the starting setting and the same source passage when comparing.
Do not describe a lower displayed CPU load as proof of more responsive monitoring. A setting can reduce load while increasing delay. Inspect both properties under the actual playback conditions.
Treat ZL, LL and global application deliberately
The feature summary documents ZL for zero-latency operation and LL for an extra thread to improve low-latency performance. It also notes that rendering may work better with both disabled. That wording describes a possibility, not a benchmark or a universal instruction for every system.
Check the target instance before using Set all, which applies these performance settings across ReaVerb instances. An experiment on one voice should not silently become an unexplained policy for every convolution in the film.
Verify monitoring and the final file separately
Keep the approved impulse and creative controls fixed while comparing performance choices. Listen for interruptions and inspect the practical monitoring response. Then render a representative passage and check its audio independently.
If a doubled voice remains, examine direct versus software monitoring rather than assuming FFT scheduling explains every echo-like symptom. These checks are proposed; no latency measurement, processor benchmark or successful render has been performed.
Related tasks
- How Do I Make Dry Narration Belong in a Fictional Hall Without Adding Obvious Echo?
- Why Do I Hear My Voice Twice in Headphones While Recording Narration?
Sources and scope
- REAPER User Guide 7.81: ReaVerb feature summary: lower FFT higher CPU spread more evenly; higher FFT less CPU more latency; should not change sound itself; ZL zero latency, LL extra thread; Set all applies performance settings all ReaVerb instances; render might improve with ZL LL disabled.
Based on the official REAPER 7.81 user guide downloaded on October 23, 2026. Examples are proposed checks, not executed application tests or measured production results.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: William Liu / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.