Why DERIVA Does Not Use a Traditional Preset Browser

Most audio plugins assume that the user either knows the desired result or wants to browse a collection created by someone else. The interface provides parameters for the first case and presets for the second.

DERIVA starts from a different question: what if the useful sound has not been designed or named yet?

A preset begins with a destination

A conventional preset is a stored answer. It may describe an instrument, genre, technique or mood. This is useful when a session needs a familiar starting point and the user wants to move quickly toward a known result.

The limitation is not technical. It is behavioural. A long browser can encourage scanning names faster than listening to sound. The next option is always visible, so the current one may receive only a few seconds of attention.

DERIVA was designed around listening to one active state long enough to make a decision about it.

Fracture creates a proposal

Pressing Fracture generates hidden values for four processing Engines and displays descriptive tags rather than a traditional wall of knobs. The state is called a Fragment.

It is not stored in a factory list. It exists in the current plugin instance and processes whatever audio the musician sends through it. Engine order, mute, solo and broad controls can still be shaped, but the starting combination arrives as a proposal rather than a destination selected by name.

This shifts the first interaction from choosing a label to hearing a result.

Offer turns saving into a decision

A conventional save command asks for a filename. DERIVA uses Offer.

Offering the active Fragment submits it to The Keeper. The initial outcome is balanced between Preserved and Lost, with a subtle capped bias after repeated outcomes. If Preserved, the Fragment becomes a Remnant. If Lost, it disappears.

The uncertainty is not intended as punishment or artificial scarcity. It gives the act of saving weight. The user must decide whether the current result is worth risking before immediately generating another one.

The Archive is personal by construction

The Archive contains only Preserved Remnants. It does not become larger because the user clicked Fracture many times. It becomes larger because certain results survived a decision.

Remnants can be renamed, favourited, searched, recalled and revisited through several Archive views. Over time, the collection records which colours, movements and accidents repeatedly caught the user’s attention.

A factory preset browser reflects the choices of the sound designer. The Archive reflects the choices of the person using the plugin.

This approach has a cost

Removing a traditional preset browser is not automatically better. It asks more from the user:

• there is no genre-labelled shortcut to a guaranteed result;
• not every generated Fragment will fit the current session;
• a useful state may be Lost;
• listening and resampling are more important than collecting options.

For sessions that demand exact recall from a predefined library, a conventional preset system is faster. DERIVA is intended for moments when the destination is still open.

Clear controls still matter

An exploratory instrument should not be confusing. DERIVA keeps the main sequence explicit: Fracture, shape the Engines, Offer, then Remember or continue.

Erosion provides destructive colour. Scatter creates granular clouds. Veil adds filtering and spectral movement. Mirror introduces reverse bloom and ambient space. The Archive provides recall after a Fragment has earned a place there.

The unusual language gives the process character, but each step still maps to a concrete audio action.

Discovery requires selection

Generation without curation produces accumulation. Curation without uncertainty can become routine. DERIVA connects the two: it produces states that did not need to exist beforehand, then asks the musician to decide which ones matter.

That is why the plugin does not begin with a traditional preset browser. Its central instrument is not the list. It is the decision.

Explore DERIVA’s workflow and hear the effect on different sources.