Getting Started
This is the five-minute path from download to your first shader running in Resolume. If you can add an effect in Resolume, you can do this.
1. Download
Download Shader Engine from the Shader Engine page. It’s a free download — no account, no payment. The free build is fully functional but shows a periodic watermark until you unlock it (see Licensing).
Pick the build for your operating system (Windows or macOS).
2. Install the plugin
Unzip the download and drop the plugin into Resolume’s FFGL plugin folder — the same place any other extra effect goes:
| OS | Default location |
|---|---|
| Windows | Documents\Resolume Arena\Extra Effects\ (or Resolume Avenue) |
| macOS | ~/Documents/Resolume Arena/Extra Effects/ (or Resolume Avenue) |
Then restart Resolume so it scans the new plugin. If you’re not sure where your plugin folder is, or you keep plugins somewhere custom, see Installing the Plugin.
3. Add Shader Engine in Resolume
Shader Engine installs as two plugins, both named Shader Engine:
- an Effect — apply it to a clip, layer, or the composition to run a shader over your existing visuals, and
- a Source — drop it in as a clip to generate visuals from scratch.
Find it the way you’d find any effect or source:
- Effect: open the Effects panel, search for Shader Engine, and drag it onto a clip or layer.
- Source: open the Sources panel, find Shader Engine, and drop it into an empty clip slot.
At this point nothing is rendering yet — no shader is loaded. That’s expected.
4. Load your first shader
Select the layer/clip with Shader Engine on it and look at its parameters. In the Load group you’ll see:
- Shader Path — a file picker. Point it at any
.isf,.fs,.frag,.glsl, or.jsonshader file to load it immediately. - Browse Library — a button that opens the full Shader Engine window (library browser, Shadertoy/ISF search, and the editor).
- Status — shows an error message if a shader fails to load. Empty means all good.
The fastest first result: click Browse Library, go to the SHADERTOY or ISF
tab, search for something (try plasma or tunnel), and load a result. You’ll see it
render in Resolume right away. See Importing Shaders for details.
Prefer to work locally? Any shaders in your library folder appear under the LOCAL tab. See The Library Browser.
5. Make it yours
Once a shader is loaded, its inputs show up as Control parameters in Resolume, right alongside Rate (time/speed) and the plugin’s other controls. Map them to MIDI, OSC, or automation exactly like any Resolume parameter. See Parameters & Live Performance.
That’s it
You now have a shader running in Resolume and its controls under your fingers. From here:
- Build up a local collection → The Library Browser
- Pull more shaders from the web → Importing Shaders
- Tweak or fix a shader’s code → Editing Shaders
- Something not rendering? → Troubleshooting