Scott Brio Synerator v1.1.0 [WiN-MAC]

• Product: Synerator // Synth Randomizer for Producers
• Developer: Scott Brio
• Version: 1.1.0
• Format: VST3
• Requirements: Windows 10 or later, macOS 10.13 or later
• Source: scottbrio.com/tools/p/synerator-vst3-synthesizer-randomizer

Synerator is a VST3 plugin that hosts another VST3 synthesizer inside its own window and randomizes that synth’s parameters rather than generating sound itself. An Amount slider sets how far a RANDOMIZE pass pushes parameter values, while individual parameters can be locked to exclude them from that pass. Parameter Search filters a hosted synth’s full parameter list in real time, and Refresh Parameters re-scans it when a synth’s module structure changes the count. It answers the search for randomizing an already-owned VST3 synth instead of programming every patch by hand.

Key Takeaway

Activates when an owned synth’s preset browser feels exhausted and a new starting patch is needed fast, without hand-programming every parameter. It displaces manual knob-turning across a hosted synth’s full parameter set, not sound design skill itself. Randomization only reaches parameters the hosted synth exposes to VST3 automation; anything hidden behind a synth’s own custom UI stays untouched.

Synerator Doesn’t Make Its Own Sound

Synerator doesn’t generate audio itself — it loads a separately-owned VST3 synth inside its own plugin window and manipulates that synth’s own parameters directly, so whatever sound comes out is entirely the hosted synth’s own engine responding to new parameter values. The hosted synth’s full interface remains visible and usable inside Synerator’s window, not replaced by a generic control panel.

The Amount slider sets how far a single RANDOMIZE pass pushes parameter values from their current position, rather than jumping every parameter to a fully random value regardless of setting. A low Amount nudges an existing patch toward variation; a high Amount can move a patch far enough from its starting point to sound like an entirely different preset.

Because randomization operates on whatever parameters the hosted synth exposes through the VST3 automation interface, a setting only accessible through a synth’s own custom, non-automatable UI element stays outside what RANDOMIZE can touch. Sound designers working with synths that expose most of their engine to automation get the widest randomization range; synths that hide key controls behind non-standard UI get a narrower one.

Locks Apply Per Parameter, Not Per Group

Individual parameters can be locked before a RANDOMIZE pass, excluding them from that pass while every unlocked parameter is still fair game. A locked filter cutoff or a locked envelope stays exactly where it was set, even as oscillator and modulation parameters around it randomize freely.

Unlock All clears every lock in one action rather than requiring each parameter to be unlocked individually, and Revert to Last Preset restores the previous state for a quick A/B comparison against whatever the most recent RANDOMIZE pass produced. Undo (Ctrl+Z) and Redo (Ctrl+Shift+Z) work per randomization pass, so an accidental re-randomize over a good result can be stepped back.

Locks apply to specific parameters, not to categories or parameter groups — locking every oscillator-related control on a synth with dozens of oscillator parameters still means locking each one, not toggling a single “lock oscillators” switch. Producers refining one specific element of a patch through repeated randomization passes benefit most from locking; producers exploring an entirely fresh direction skip locking and randomize everything each time.

Typing Beats Scrolling Past a Thousand Controls

Parameter Search filters a hosted synth’s full parameter list in real time through Ctrl+F (Cmd+F on Mac), narrowing a list that can run past a thousand entries down to whatever matches the search term. The example given specifically is Massive X, cited as exposing more than 1,300 parameters.

Without this filter, finding one specific parameter to lock on a synth with that many controls means scrolling and visually scanning the full list rather than typing a few characters. Producers working with smaller, simpler synths get less benefit from Parameter Search than producers locking specific controls on large, modular instruments.

Re-Scanning Catches What Changed

Refresh Parameters re-scans a hosted synth’s current parameter list on demand, which matters specifically for synths like Phase Plant, where loading or removing a module changes how many parameters the instrument exposes. Without a re-scan, Synerator’s view of the hosted synth’s parameters can fall out of sync with what the synth actually has active after a structural change like that.

A synth with a fixed, unchanging parameter set has less need for this feature than one where the parameter count itself is a variable, since nothing about its structure shifts mid-session to fall out of sync in the first place. Producers building patches on modular or generator-based synths use Refresh Parameters after any module change; producers on fixed-architecture synths rarely need to trigger it.

140+ Isn’t Every VST3 Synth

The Preset Browser saves and recalls Synerator’s own presets, organized automatically by which synth was hosted when the preset was saved, with subfolder navigation for finding a specific favorite. This preset system is Synerator’s own, separate from whatever preset browser the hosted synth itself already has.

140+ VST3 synths are confirmed working as of the current compatibility list, covering synths including Serum 2, Massive X, Rob Papen’s catalog, and Korg Collection 6 — but that list is a record of reports received, not a guarantee covering every VST3 synth in existence. A synth not yet on the list may still work through standard VST3 automation, or may expose parameters in a way Synerator hasn’t been tested against yet.

The compatibility list updates as new reports come in rather than as a fixed, one-time certification pass, so a synth that doesn’t work today could be added later without any change needed on Synerator’s own side — the variable is how that specific synth exposes its parameters through VST3, not a version of Synerator that needs updating to catch up.

FAQs