Capo 4.1 Now Available
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.
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.
I’ve been writing audio code for macOS since 2003, and it’s never been an easy task[…] But the problems were purely related to the inherent complexity of audio and hardware.
There is a high-level component in my training software that is responsible for executing each of the experiments that I need to perform in my chord detection research. I call it the driver, because it drives the training process on my behalf.
Buried in the list of features that we added to Capo 4 was the oft-requested ability to manipulate Capo’s detected beat locations.
Today's release introduces two all-new song views, and includes our significantly-improved, 4th-generation chord detection engine.
The software that trains Capo’s chord detection engine can learn from *hundreds* of songs per minute, and chews through more than *a month* worth of audio in a little over an hour.
To train Capo’s chord detector efficiently, the collection of songs and chord labels in our training data set must first get processed by a few tools.