Shake, glitch, and CPU
I still need to check how the shake and glitch look in Live and measure their CPU cost.
FOREWORDS · Development log
FOREWORD'S CHAINSAW
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.
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
I’ve kept the sequence and timestamps from my development notes. I’ve not added dates or completion claims beyond what those notes record.
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.
I named it FOREWORD'S CHAINSAW and scaffolded a JUCE VST3 project with placeholder sounds.
Black Edge Power Tools (about $70, 24-bit/96 kHz) was my top pick. I chose not to buy it.
I deduplicated my chainsaw MP3s and cut them into 72 samples across eight articulations: Start, Idle, Rev, Cut, Kickback, Choke, Stall, and Chatter.
I turned my three-panel white, splatter, and red artwork into the plug-in skin, which starts white and bleeds to red.
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.
I added screen shake at maximum Rage, with a harder jolt on big hits.
I applied the unslop pass to code-drawn layers only and left my supplied artwork untouched.
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).
I added a KEYSWITCHES toggle that opens all eight switches and lights up the active one.
I asked for a small logo in the bottom right.
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.
I asked for a smaller window and no animations except the shake, with glitching added to the shake.
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.
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
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
My source notes explicitly leave these checks open:
I still need to check how the shake and glitch look in Live and measure their CPU cost.
I still need to test the size menu, resizing behavior in Live, and HiDPI scaling.
I still need a hands-on check of the controls at 50% and 65% size.
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
C:\Program Files\Common Files\VST3\FOREWORDS CHAINSAW.vst3
C:\Users\reedg\Documents\forewords-chainsaw\
Documents\FOREWORDS CHAINSAW\Presets
This is a development log, not a release announcement. My source notes contain no release date or listening link.
Source note
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.