-[AEAudioController start:] isn't always called when first connected to Audiobus in background
It seems there's a race condition in
-[AEAudioController audiobusConnectionsChanged:] where
self.running is returning
YES even though the engine hasn't started, and
start: is never called. I'm not quite sure why it's happening, but is it possible that the Inter-App Audio connection is starting the ioUnit?
I first noticed the problem when the
AEMessageQueue filled up and started emitting errors, this was because the polling thread was never started.
@Michael, is it as simple as changing the check from