Skip to main content
Sergio Frias UBERVERB v1.0.0 [WiN]
On request Software WiN

Sergio Frias UBERVERB v1.0.0 [WiN]

1 min read 8 MB
UBERVERB is a x64 VST3 reproduction of the original 1986 algorithmic reverb, all the original algos were recreated using the exact same topology from the original, including some others not present in the original (like the classic BLOOM) You have access to a vast variety of room sizes, from small, medium, large, extra-large and even bloom for ambient atmospheres. Also included is the reproduction of the frequency response of the original unit, and also the noise. The original unit was well known for its classic sound heard on thousands of records, like 90's warp. You can disable/enable (harmonic distortion/frequency response/noise) with "HD", "ADC" "NOISE" buttons. note: windows only ( mac version is not possible at the moment since flowstone only exports to windows.) tested in fl studio win 10 the programs:

Frequently Asked Questions

How can I access Sergio Frias UBERVERB v1.0.0 [WiN]?

Sign in to check availability for Sergio Frias UBERVERB v1.0.0 [WiN]. Free accounts can download ready non-premium posts totaling at most 1 GB through 3 ad steps, with up to 20 archives per calendar month. New processing and Telegram delivery require Advanced or Ultimate.

What formats are included in Sergio Frias UBERVERB v1.0.0 [WiN]?

This pack includes: multiple professional formats. All formats are industry-standard and compatible with major DAWs.

Is Sergio Frias UBERVERB v1.0.0 [WiN] compatible with my DAW?

Yes, Sergio Frias UBERVERB v1.0.0 [WiN] works with all major DAWs including FL Studio, Ableton Live, Logic Pro, and more.

Curated by

Music Production Curator

  • since 2020
  • 72,000+ resources
  • 20+ formats
About Pluggi
Pluggi is the editorial curator behind Plugg Supply. The role combines resource discovery, catalog taxonomy, source review, and practical explanations for producers working with plugins, sample packs, Kontakt libraries, presets, and MIDI.
Review Methodology

Catalog records begin with source and availability data. A public verification badge is added only when its evidence has been recorded: documentation reviewed, source verified, archive verified, or a separately documented hands-on test.

Pluggi recommends