Skip to content
RENDERWAVERENDERWAVE

Parameter Presets

Dial in a visual you like, and you will want to keep it. Parameter presets save the exact state of a shader, every slider, toggle, and color, plus its audio reactivity assignments, under a name you can come back to any time.

What a preset saves

Section titled “What a preset saves”

A parameter preset captures two things for the shader you are working on:

  • Every parameter value. Whatever the sliders, toggles, and color pickers are set to at the moment you save.
  • Audio reactivity assignments. Which bands are driving which parameters, and how. See How audio reactivity works for what that assignment actually does.

Presets belong to one shader. A preset saved on one visual only shows up in that visual’s own preset list, not anywhere else.

Saving a preset

Section titled “Saving a preset”

Dial the shader in however you want it in Creator view, then save the current state as a new named preset. RENDERWAVE writes it right away, and it shows up in that shader’s preset list from then on.

Save as many presets as you want for a single shader. Each one is a full, independent snapshot, so saving a new preset never touches the ones you already have.

Applying a preset

Section titled “Applying a preset”

Pick a saved preset and its values load onto the live shader. A preset changes only the parameters it stores, so one you saved before adding a new control to your setup leaves that control alone. Its saved audio assignments load in alongside the parameter values.

Setting a default preset

Section titled “Setting a default preset”

Mark one preset as a shader’s default and it becomes a fallback starting point. RENDERWAVE checks two things ahead of it: an auto-saved session from your last time on that shader loads first if one exists, and the shader’s own saved defaults (see below) take priority too. The marked default preset loads when neither of those applies, most often the first time you select that shader.

If a default preset goes missing, whether you deleted it or an older reference no longer resolves, RENDERWAVE falls back to the shader’s normal defaults instead of leaving the parameters in a broken state.

Resetting a shader’s own defaults

Section titled “Resetting a shader’s own defaults”

Separately from named presets, you can save your current tweaks as the shader’s own default state, the state it starts from before any preset is applied, and you can clear that back to RENDERWAVE’s factory settings at any time. This adds nothing to your preset list. It changes what “blank” means for that one shader.

Presets vs. saved looks on the grid

Section titled “Presets vs. saved looks on the grid”

Parameter presets are a Creator-view tool for switching between parameter states on a single shader. The grid cells you trigger in Performance view are a separate thing. Those saved looks come from the step sequencer and carry more than parameters, including a step-automation pattern, and that is what fills your Performance grid. Parameter presets never appear on the grid.

Next steps

Section titled “Next steps”