v0.1.4

What's Changed

• Say what the plugin does, in the field Resolume shows by @stoatworks-labs in #4

Full Changelog: v0.1.3...v0.1.4

v0.1.3

Full Changelog: v0.1.2...v0.1.3

v0.1.2

Two fixes and one new mode, all three from field reports.

Speed and Spin no longer move the picture

Changing either used to jump the whole wheel to a different arrangement — a lurch a few seconds in, and an hour into a show a small nudge was worth hundreds of turns. Reported as "unusable in performance", which is exactly right.

The phases were computed as time × rate, so changing the rate rescaled the entire history rather than changing what happened next. They are now carried forward across a change instead. Moving Speed or Spin now changes the pace and leaves the wheel where it is.

The OpenFX builds and the browser demo keep the old form deliberately: both re-render when you scrub, and neither has anybody moving a slider live.

Matte — a fourth Mode, so the wheel can mask something else

Flenser as a source was an opaque rectangle: everywhere the oil was not, the picture was the bare lamp, so it could not be laid over anything.

Matte drops the clip entirely and gives you the lit oil over transparency. Everywhere the oil does not cover is transparent — and black, so a host that ignores alpha still gets a clean field to key. It is the one mode that works in both plugins and renders identically in each, so it does not matter which one you reached for.

If you have a clip and want the oil composited onto it, Over already did that and still does. Matte is for when you want the wheel on its own layer.

The About panel was calling this plugin Afterglow

Both previous releases shipped an About block naming a different plugin and linking to its repository, with no User guide or Project page button. Fixed.

Also

• Both Resolume plugins now load and register in Arena 7.27.1 on Windows — checked with the build this release ships. Resolve and Linux are still unverified, and the guide says so.
• The user guide documents Matte, and no longer claims the plugin has never been in a host.
• This repository finally has issue templates, so a bug report has somewhere to put a version and a log.

Thanks to @VJPandaAU, who found both defects and asked for the mode.

v0.1.1

Also in this release

• AGENTS: the Windows and Linux claims, after the first release
• docs: what the release actually left outstanding
• docs: v0.1.0 shipped, and the Linux jobs ran
• The download block, from gen-downloads.py
• The Instagram grid cover
• Embed the project video
• The demo is live
• The generated user-guide PDF
• The hero image: four looks, rendered by the harness

---

Full changelog: v0.1.0...v0.1.1

Flenser v0.1.0 — a liquid light show

The first release. Oil, water, alcohol and dye between two watch glasses on an overhead projector, as four plugins from one model: an FFGL source and effect for Resolume Arena/Avenue, and an OpenFX generator and filter for DaVinci Resolve, Nuke, Natron and Vegas — on macOS, Windows and Linux.

The colour is subtractive. Every cell is a dye filter, so where two cross they multiply: cyan over magenta is blue, not white, and all three inks together are nearly black. That is the difference between a dyed wheel and every blob effect that adds its colours.

Every cell's edge is a lens. The meniscus displaces what is behind it, splits it by wavelength, and throws a bright caustic just inside a dark rim — an edge band, because the middle of a cell is flat oil between two flat glasses and bends almost nothing.

Flenser Lamp puts your clip where the projector's lamp was, so the footage is what shines through the oil. Three modes: project through it, lay the lit oil over it, or take only its brightness and let the dye supply the colour.

Eight factory presets, shared by all four plugins from one table — Overhead Projector, Optikinetics, Alcohol Burn, Ink in Water, Sodium, Clear Water, Beading, Slow Bloom.

What is verified

Everything is a pure function of position and time, which is what makes the model checkable at all:

• the GLSL half and the C++ half agree across 1,625,010 values over every control, with nothing past 5e-4
• a clear wheel leaves a picture byte-identical: 0 of 230,400 bytes differ through the Resolume build, 0 of 921,600 through the OpenFX build
• all 33 controls measurably reach the picture, in both bundles
• 8 presets × 3 host behaviours × 2 bundles
• the Linux OpenFX bundle is built for glibc 2.28 and proved to dlopen on Rocky 8, reporting both plugins

Simmer — a bounded feedback trail — is Resolume-only by design: an OpenFX host renders frames out of order and cannot match its own preview with a feedback buffer.

What is not

It has not been loaded into Resolume, or into Resolve. Everything above runs the plugin directly or through a probe host. No Windows build has been run, and the Linux load test is a load, not a render. Check it in your own rig before trusting it in a show.

Try it in a browser first, with nothing uploaded: https://flenser-demo.stoatworks-labs.com