Dev Diary #4

Hi! Timo this time, from a sunny office on a cold winters day where we’re working hard to bring you the next update!

That’s right, the next update: the final beta of v1.1.0 is now out (available at our Discord server), and unless any major bugs are found, v1.1.0 stable will be released next Wednesday, 19th February.

Now that the updater and all the related infrastructure is ready, we should advance faster on the features. However, to start with this update, there’s a few items of technical debt we’re paying off. First, our panic handler, which deals with displaying any critical errors, basically crash data, when things go really wrong, was written in a way that might not be compatible with future compiler updates or other changes. Of course, hopefully you’ll never see it, though some of those who tried the beta know the “guru meditation” screen. Anyway, we wanted to make sure that there are no errors in our errors, at least!

On the voice side, while the LFO code works perfectly well, it was originally written in a rush for Superbooth 2024, and that shows. I’m applying some TLC to the code to make it easy to write tests that make sure that I won’t accidentally change the waveforms in subtle ways (thus breaking existing presets) when doing the next change: refactoring the code to take it’s internal phase from a clock. That clock can then be either an internal BPM based clock, or one following a MIDI beat clock, which are the headliners of the next update.

Hopefully we’ll get the technical debt repayments done in a few days, and then get to features. Once we have some, we’ll kick out the first beta of 1.2.0 and you’ll all get to try it out!