Capo was not playing audio for some users on Intel Macs running Sonoma. After spending almost two weeks (and about $850) I discovered that macOS Sonoma had a rather nasty bug that was triggered by loading JPEG images.
I was very fortunate to get an invite from Dave Hamilton and Paul Kent to appear on the Gig Gab Podcast. I had a blast chatting with them…
When you place an A# chord in Capo, you probably don’t want it to get replaced with a Bb. That kind of strange behavior is what I set out to fix in 4.3.1. Unfortunately, during the QA cycle I learned that my fix is incomplete…
Only a few (long!) months after sending 4.2 out the door, we’re back with another bite-sized update that continues to nudge Capo forwards. Here’s what we’ve got for you…
In case you've not already seen it, you can grab the latest version of Capo from the App Store on iOS or macOS.
It’s not uncommon for me to start my day with a random song stuck in my head. I don’t necessarily hear the song on TV or the radio—it just starts playing in my mind, uninvited, and wants to come out.
Judging by the release notes, the latest minor update to Capo might seem a little thin on changes. There are a few reasons for that.
I found the cause of the most recent of my AVAudioEngine + AirPods issues, and an end-user workaround to go along with it. Sadly, this isn’t something I can easily patch with code.