THE VOID V2 logo
Everworks Clean Suite

THE VOID V2 User Guide

THE VOID V2 preserves the original Everworks model and its 3.8 ms live path in a faster cross-platform engine. Turbo adds a stronger 100-200% cleanup range without adding latency.

Version 2.0.0 182 samples / 3.8 ms at 48 kHz Optimized native engine Turbo 100-200% AU / VST3 / Standalone

What Changed in V2

Optimized Engine

The original Everworks cleanup response runs locally in a faster engine built for Apple Silicon, Intel and Windows x64.

Turbo

Turbo changes the Void Amount display from the normal 0-100% range to 100-200% for difficult sources.

Same Live Timing

Normal and Turbo report 182 samples at 48 kHz, approximately 3.8 ms. Turbo adds no extra latency.

Lower CPU

The measured full stereo VST3 process fell from 31.914% to 19.044% on an M3 Max at 48 kHz / 128 samples, a 40.3% reduction.

The 40.3% result is a same-processing, same-audio comparison against the previous release on the stated test system. Host, CPU, sample rate and block size affect absolute usage.

Current Interface

THE VOID V2 with Matter and Turbo enabled
THE VOID V2 2.0.0 with Matter and Turbo enabled. The header remains at 3.8 MS LIVE and Void Amount is operating in its 100-200% range.

Main Controls

ControlWhat it doesPractical use
ActiveEnables or bypasses the complete processing path.Use for level-aware A/B checks and emergency bypass.
Void AmountControls the original cleanup response from 0-100% in normal mode.Raise it until the source becomes cleaner, then stop before body or articulation is damaged.
TurboSwitches Void Amount to 100-200% for stronger cleanup.Use when 100% is useful but insufficient. Compare against normal 100% before pushing further.
MatterEnables the source-aware restoration stage and reveals Body.Turn it on only when strong cleanup removes useful density or continuity.
BodyControls the Matter restoration amount and starts at 0%.Increase gradually while checking consonants, room tails and bleed.
SizeChanges the plugin window size only.It does not alter sound, CPU or latency.
Turbo is intentionally stronger than normal 100%. It is not a louder wet mix and is not sample-equivalent to placing two plugin instances in series.

Turbo Transfer

SettingCleanup behaviourLatency
Normal 0-100%Preserves the original Everworks response and normal amount range.3.8 ms measured path.
Turbo 100%Matches full normal cleanup.Same measured path.
Turbo 200%Extends cleanup depth with protected output limits.Same measured path.
In the six-second 48 kHz mono test fixture, Turbo 200% produced 5.27 dB more reduction than normal 100%. This is a controlled fixture result, not a guaranteed reduction for every source.

Consistency and Matrix

Consistency

Optional low-latency level control
ControlFunctionStarting point
ConsistencyReveals and enables Target and Speed.Leave off unless source level varies materially.
TargetSets the desired loudness direction from -30 to -15 LUFS.-24 LUFS.
SpeedSelects Slow, Medium or Fast response.Medium for general use; Slow for natural long-form speech.

Matrix Control

Four-band cleanup distribution
THE VOID Matrix Control

Matrix 1

Rumble, proximity build-up and low-frequency stage wash.

Matrix 2

Mud, boxiness, room tone and vocal body.

Matrix 3

Intelligibility, source focus and mid-range pressure.

Matrix 4

Hiss, air, bright bleed and high-frequency cleanup.

ControlFunctionUse
AmountSets cleanup intensity independently for each band.Reduce the affected band if the source loses body, presence or air.
TrimRebalances each band after cleanup.Set Amount first; use Trim for small corrections.
Bypass / SoloDisables or auditions one Matrix region.Use to locate a problem, then judge the full signal with Solo off.
CrossoversSet the three band boundaries. Defaults: 200 Hz, 900 Hz and 4 kHz.Move only when the source problem falls across a default boundary.

Fast Workflow

Start in normal mode

Leave Turbo, Matter and Consistency off. Set Void Amount from 0% while listening at matched level.

Use Turbo only after 100%

If normal 100% still leaves unwanted spill or room energy, enable Turbo and move gradually toward 200%.

Restore only what is missing

Enable Matter and raise Body from 0% only if cleanup removes useful density.

Solve regional problems with Matrix

Use Solo to locate the band, disable Solo, then adjust Amount before Trim.

Add Consistency last

Use it for level movement, not as a substitute for cleanup. Begin at -24 LUFS / Medium.

Measured Performance

M3 Max ยท 48 kHz / 128Previous releaseV2 optimizedReduction
Full stereo process CPU31.914%19.044%40.3%
Full mono process CPU15.629%9.734%37.7%
Stereo prepare time282.026 ms19.504 ms93.1%
Stereo memory delta63.625 MB29.766 MB53.2%
True mono uses one Primary engine path and remains close to half the stereo processing cost. The V2 benchmark recorded zero 128-sample deadline misses.
The Windows x64 release includes dedicated performance improvements. A native Windows percentage is not quoted until the matching Studio One A/B has been repeated.

Troubleshooting

ProblemLikely causeFix
Void Amount starts at 100%Turbo is enabled.Disable Turbo to return to the normal 0-100% range.
Body is hiddenMatter is disabled.Enable Matter, then raise Body from 0%.
Target and Speed are hiddenConsistency is disabled.Enable Consistency.
The result is thin or over-suppressedTurbo or one Matrix Amount is too high.Return to normal mode or lower the affected Matrix band before adding Trim.
The host reports the wrong buildAn older THE VOID binary is still installed or cached.Run the included uninstaller, install V2, then force the host to rescan plugins.
Windows shows SmartScreenThe current Windows x64 beta is functionally tested but unsigned.Verify the package checksum and allow it only when downloaded from everworks.dev.

Tester Feedback Checklist

Report itemInclude
SystemHost, OS, CPU, plugin format, sample rate and host block size.
SourceHandheld vocal, lavalier, headset, lectern, dialogue, vocal bus or other material.
SettingsVoid Amount, Turbo, Matter / Body, Consistency, Matrix values and crossovers.
PerformanceHost CPU with true mono or stereo routing and the number of simultaneous instances.
ResultUseful extra cleanup, over-suppression, tonal loss, artifacts, recall issue or host issue.