This article aims to explain the differences between the previous and the new Virtual Console Collection Metering and the path that led us to this solution.
VCC Behavior
The VCC is a group of saturation modules for VMR. Each console has its own Clip Threshold.
When the input is below this threshold, the signal is inside the Non-Clipping Zone, meaning that there is no clipping nor extra saturation involved.
When the input is above the threshold, the algorithm starts clipping, which means more saturation and more audio artifacts and non-linearities.
- Clip Threshold is the point where the console stops behaving linearly.
- Meter Calibration is the dBFS Peak audio level for a 1kHz sine wave that would read 0VU. Changing Meter Calibration does not affect sound.
Previous VCC Metering
The previous VCC metering displayed the output level. It was calibrated to show 0VU when fed a 1kHz sine wave at the Meter Calibration dBFS Peak.
Why This Was a Problem
Each VMR module’s meters should reflect its function. For example:
- Trimmer shows signal after gain adjustment
- FG-116 shows gain reduction
- VCC should indicate where the signal lies within the saturation algorithm
Showing only the output level doesn't tell you whether you're below or above the console’s Clip Threshold.
New VCC Metering
Simply displaying input level wouldn’t solve the problem — it could read +2VU even while the console clips at -1VU.
So we implemented two important changes:
This new metering point shows the true signal level just before output — perfectly reflecting saturation and matching what you'll hear post-console (excluding makeup gain).
Clip-LED added: Lights up once the signal crosses the Clip Threshold — which is console-dependent. This gives immediate visual feedback on saturation.
Summary
- Clip-LED off: Linear, non-saturated signal
- Clip-LED on: Saturation engaged above threshold
For example, if you install a module or bundle at version 3.2, both the rack plugin and all installed modules must also be updated to 3.2.
Still have questions?
We're here to help! Contact us via our support form.
Comments
Article is closed for comments.