Treating AI Models Like a Team (My Aha! Moment) So here’s a scruffycat-style confession: I used to treat AI models like a box of random tools. Need something done? Grab whatever’s closest and hope for the best. But that’s not how these digital critters work. Each one’s got its own quirks, strengths, and blind spots. Once I started thinking of them as a team—each with a job title and personality—my workflow got way smoother (and a lot more fun).

Why I Built This Template I am not a fan of Xcode. There, I said it. As someone who prefers VSCode for development, I was tired of being forced into Apple’s IDE ecosystem just to work with JUCE. So I created juce-cmake-template—a modern CMake-based starter that lets you build JUCE projects with your favorite editor. What You Get Modern CMake: Uses CPM (C++ Package Manager) for automatic dependency management VSCode Ready: Works seamlessly with CMake Tools extension, includes debugging support No Xcode Required: Avoids Xcode project files completely Professional Structure: Separated headers/implementation, asset management, testing framework Multiple Plugin Formats: Supports VST3, AU, and Standalone formats C++20 Standard: Modern C++ features out of the box Getting Started Prerequisites You’ll need:

Introduction So, I was messing around with a project using those endless pots that everyone loves (you know, the ones that turn and turn and turn and never stop turning). The goal was to use the Raspberry Pi Pico and the MCP3204 ADC to read the pots’ values. Simple enough, right? Well, turns out the universe had other plans. While everything worked perfectly fine on my trusty Bluepill using the Arduino framework, when I moved the code over to the Pico, things went… not so smoothly.

Howdy, folks! Today’s post might not be the most thrilling, but after spending days wrestling with this, I figured it deserved a little attention… Why This Exists I’ve mentioned before how I like the Arduino framework but dislike the IDE. PlatformIO has been a game-changer for the hardware I’ve used so far, including Teensy, Arduino, and BluePill boards (for the most part). Recently, I decided to dive into the DaisySeed because it seems like the best option for audio developers tackling DIY projects.

In this post, we will discuss how to get an analog signal out of our microcontroller. To produce a control voltage for our modular synth, we need a circuit that can convert a digital value—like an audio sample, MIDI CC, or mapped value—into an analog signal. This type of circuit is called a digital-to-analog converter, or DAC. There are many types of DACs, and choosing the right one can be a bit intimidating.

Hey, everyone! This video is long overdue, and I apologize for the delay. I’ve been away tending to family obligations abroad and unfortunately, I managed to kill my laptop while away. My laptop has now been fixed but all the material I had already prepared was lost so I am re-recording this for you all. I’m going to do things a little bit differently since the first time around it was more than I could chew.