News: A Brief Catch Up! April 2025
Hey everyone,
It’s been a little while since I checked in, so I want to bring you up to speed on what I’ve been doing with Audiocube over the past few months. This release has taken a slightly different path than earlier updates, but I think the result will be worth the wait.
New Users, New Challenges
First, thank you to everyone who’s joined recently. We’ve just passed 2,000 registered accounts and 300 licences. Seeing that level of support is both humbling and motivating. When I started Audiocube back in 2020 I had no software‑development experience - just an idea I was excited about. Getting the app out of the kitchen and into your studios has been a long haul, but I’m finally starting to see the work pay off. Audiocube is beginning to look like a product people love and a viable business.
A growing user base also means more feedback. As Audiocube runs on more machines and workflows, it uncovers bugs and edge cases I’d never met before. That feedback has given me a clear to‑do list. The most urgent issues to address are:
UI scaling - on some displays the text and controls are too small. There is a scale slider, but it’s hard to reach when you can’t read the screen.
File & folder management - the current system forces projects and recordings into Audiocube’s internal folder. That isn’t practical for everyone.
Login quirks - despite earlier tweaks, the sign‑in flow can still trip people up.
General performance & bugs - unusual GPU/CPU usage, timeline bugs, a range of random issues.
Documentation - parts of the manual no longer match the software.
What I’ve Been Working On
It’s been two months since the last release - longer than I aim for - but there’s a good reason. The bugs you’ve reported live in code I wrote four years ago, back when I was still teaching myself to program. Because that code sits at the heart of Audiocube, quick fixes won’t hold; I’ve had to rip out and rebuild big chunks of the foundation.
Over the past year I mostly chased the fun stuff: new features, better graphics, anything that made the app look cool and feel exciting. That work mattered, but it left a pile of duct‑taped patches underneath. I’ve hit the point where a proper rewrite is the only sane path forward, so I’m refactoring roughly half the codebase and re‑architecting the core systems to be cleaner and more future‑proof.
Doing this as a self‑taught developer has been a steep learning curve, but it’s worth it. A stable base now means faster, safer updates later. I’ve been buried in this overhaul for a couple of months, and it’s nearly ready to share - though every layer I peel back reveals one more thing to fix, so the exact date keeps sliding a bit. Almost there.
Here’s what the next build will bring, straight from the to‑do list you’ve helped me shape:
Completely redesigned UI – I spent almost a month on this alone. It’s cleaner, more flexible, and much easier to read. I’ve even ditched the standard OS window chrome, so the whole thing feels tighter and more polished.
File‑system overhaul – Save or load projects anywhere, point your library to any drive, browse more comfortably, and import a wider range of formats. It should feel a lot closer to the file workflows you already know.
Faster, cleaner login – The sign‑in screen looks better and gets out of the way faster. If your licence is already authenticated, you’ll jump straight into the studio.
Improved acoustic visualisation – Ray‑tracing lines now fade with each reflection, giving you a clearer sense of acoustic density at a glance.
Extensive code rewrite – You won’t see this, but you’ll feel it: smoother performance, and a foundation that lets me add new features without piling on hacks.
All this core work should make future updates quicker to build, and generally make it less of a headache to add new features. I’m aiming to ship the new version within the next month
Once it’s live, I’ll bring the user manual up to date and give the website a fresh coat of paint - the current docs lag behind the software, and I’d rather fix them after the dust settles than twice in quick succession.
Thank you to everyone who’s bought a licence or sent feedback. Because of your support, I’m getting close to working on Audiocube full‑time, which means more rapid progress and room for the ideas I’ve been stockpiling. I’m excited to see how far we can push the software over the next six months.
Speak soon!
Noah
