← The Church Audio SUPERDAW /01 · Dev Journal

FOREWORDS · Development log

FOREWORD'S CHAINSAW

Chainsaws, chromatically tuned.

I’m building a Windows VST3 instrument for Ableton Live 12 that turns chainsaw recordings into a playable, chromatically tuned instrument. I modeled its playability on Solemn Tones Odin and built the sound set around eight chainsaw articulations.

Latest archive note · November 9, 2026 · 5:41 AM CSTv0.4.0 in progress
Installed milestone · November 9, 2026 · 12:09 AM CSTv0.3.0 · 534 × 492 opening size
Reported v0.3.0 automated checks726/726 mouse · 33/33 Wine

What I have—and what I haven’t checked: The archive records an installed v0.3.0 build and automated mouse/Wine test totals. I have not yet hand-tested the listed behavior in Ableton Live. My latest note says v0.4.0 is in progress; it does not say that work is finished.

Build notes · all times Central Standard Time

From placeholder instrument to v0.3.0

I’ve kept the sequence and timestamps from my development notes. I’ve not added dates or completion claims beyond what those notes record.

  1. Kickoff

    I asked for an Odin-style VST3 instrument built around power tools instead of guitars. I studied Odin III on THEENTERPRISE: a multisampler with keyswitches, velocity layers, round robin, and humanize.

  2. I named the instrument

    I named it FOREWORD'S CHAINSAW and scaffolded a JUCE VST3 project with placeholder sounds.

  3. Sample-pack research

    Black Edge Power Tools (about $70, 24-bit/96 kHz) was my top pick. I chose not to buy it.

  4. I shaped my own sample set

    I deduplicated my chainsaw MP3s and cut them into 72 samples across eight articulations: Start, Idle, Rev, Cut, Kickback, Choke, Stall, and Chatter.

  5. UI mockup

    I turned my three-panel white, splatter, and red artwork into the plug-in skin, which starts white and bleeds to red.

  6. –

    Blood effect, v1 through v4

    I iterated from splatter, to a top-down bleed, to smoother liquid drips. In v4, the splats evaporated within about a second and the skin flooded fully red. I also rendered a rough audio demo.

  7. Rage shake

    I added screen shake at maximum Rage, with a harder jolt on big hits.

  8. Code-drawn layer cleanup

    I applied the unslop pass to code-drawn layers only and left my supplied artwork untouched.

  9. First Windows build installed

    I cross-compiled with MinGW and JUCE 7.0.12 because the PC has no Visual Studio, then installed the VST3. I pitch-stabilized the samples (median 0.22 cents off; worst 6 cents) and set up 16 voices, round robin, and keyswitches on MIDI notes 12–19 (C-1 to G-1 in Live).

  10. Keyswitch panel

    I added a KEYSWITCHES toggle that opens all eight switches and lights up the active one.

  11. Logo

    I asked for a small logo in the bottom right.

  1. Finish-up pass

    I reported that presets wouldn’t flip, most buttons were broken, and the knobs spun the wrong way. I traced the likely causes to guessed hit areas, wrong rotation centers, and screen shake that did not move the hit areas with the art. I re-measured every control from the artwork. I added a preset browser with 12 factory presets, arrows, a dropdown, the scroll wheel, and Live’s program list; user Save/Load in Documents\FOREWORDS CHAINSAW\Presets; and the footer logo. The archive reports 325/325 automated mouse tests and 30/30 Wine VST3 tests passed.

  2. Simplify request

    I asked for a smaller window and no animations except the shake, with glitching added to the shake.

  1. v0.3.0 installed

    I installed v0.3.0 opening at 75% size (534 × 492), with 50%, 65%, 75%, and 100% size options, plus corner drag. I removed all blood animation: the skin is white with Rage off and red with Rage on. Rage shake now includes sliding bands, RGB split, scanlines, block noise, and rare inverted patches. The glitch is visual only so the controls stay clickable. The archive reports 726/726 mouse tests and 33/33 Wine tests passed.

  2. v0.4.0 in progress

    My latest note records tempo-locked rev up/down synced to Live’s BPM, with rates from 4 bars to 1/32, including dotted and triplet values, plus several shapes. It also records saturation, distortion, and EQ planned on a new FX panel. The archive labels this work in progress; I’m not presenting it as a finished or installed feature.

Archive images · dates follow the milestone log

Screenshots and art

I’ve brought the archive images into this local page. They illustrate the logged design and build stages; they are not proof of an in-Live hand test.

Open work · not yet hand-tested in Live

What I still need to try

My source notes explicitly leave these checks open:

Not yet hand-tested

Shake, glitch, and CPU

I still need to check how the shake and glitch look in Live and measure their CPU cost.

Not yet hand-tested

Window size and HiDPI

I still need to test the size menu, resizing behavior in Live, and HiDPI scaling.

Not yet hand-tested

Controls at smaller sizes

I still need a hands-on check of the controls at 50% and 65% size.

WIP in latest note

FX panel and tempo-locked rev

The November 9, 5:41 AM note records this work in progress. I have no source-backed completion or installation claim for v0.4.0.

Windows machine locations

Where I keep it

Installed plug-in

C:\Program Files\Common Files\VST3\FOREWORDS CHAINSAW.vst3

Project copy

C:\Users\reedg\Documents\forewords-chainsaw\

User presets

Documents\FOREWORDS CHAINSAW\Presets

Release status

This is a development log, not a release announcement. My source notes contain no release date or listening link.

Source note

What I based this page on

I used the supplied FOREWORDS_CHAINSAW_DEVLOG.md and its seven included PNG images as the source. The notes state that all times are Central (CST); I retained their milestone dates and times. I did not run any archive scripts or binaries. This page and its copied images remain local; I did not publish or deploy the site.