What began as a routine maintenance update quickly spiraled into one of the most extensive under-the-hood overhauls since Body Shifter’s launch.
It all started innocently enough. Producers began noticing strange interference noises when running multiple instances of Body Shifter on separate busses or chains in certain DAWs. At first, we assumed it was just an edge case. But after digging in, we discovered it was a deeper issue, a fundamental flaw in how plugin instances were sharing internal buffers to enhance CPU performance. Fixing it meant rethinking our entire architecture. This update became v1.1.2
Shortly after, another issue surfaced, this time, exclusive to macOS. Users were reporting sporadic crashes: sometimes the plugin would fail to load entirely; other times, simply resizing the frame would cause it to crash. The bug was hard to reproduce and even harder to trace. After weeks of debugging, we uncovered the culprit: a nasty, low-level data transmission bug buried deep in Body Shifter's code. That overhaul became macOS update v1.1.3.
While we were deep in the codebase, we also addressed a long-standing annoyance for automation-heavy users: the Width knob's reversed automation direction. It was a small detail, but one that had real workflow impact, so we made sure automation now behaves exactly as expected.
We’re a tiny team, just a few of us, wearing way too many hats, juggling code, QA, support, design, and coffee refills. Most of our time in the past months went into these two updates. It was blood, sweat, and many, many late nights, but we couldn’t let these issues slide. Body Shifter means too much to us, and to you.
So yes, we set out to do a quick tune-up… but ended up rebuilding the engine while the car was still on the road. These updates might just look like version bumps, but they represent weeks of intense refactoring, testing, and cross-platform stress-testing.
The result? A much more stable and more reliable Body Shifter than ever before.