More on AVAudioEngine + AirPods
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.
We exist to tackle big problems — combining top-notch design with cutting-edge research to create world-class audio applications.
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.