Hello CoreAudio,
I'm seeking advice on migrating from CoreAudio/ObjC++ to
AVAudioEngine/Swift/ObjC: should I do it or when should I start worry?
I have a legacy macOS/iOS project that uses CoreAudio heavily, mainly just
AudioQueue, but right now on Mojave / iOS 12 things start to breakdown or
throw "deprecated" warnings at me, e.g.:
AudioSampleType is deprecated: The concept of canonical formats is
deprecated.
And I need to at least bring in AVFoundation. This prompts me to shop
around for other solutions.
My project is not a synth/FX app. It would only use metering/spectrogram
and some visualization at best. Low-latency is essential though. The info
about latest CoreAudio stack on the internet seems increasingly scarce and
I'm hesitating to adopt 3rd-party frameworks such as JUCE for such a small
project. So I'd love to give the Swift stack or even just ObjC/C stack a
serious try.
Now my concern is mainly in the performance and latency. I've seen these
posts regarding using AVAudioEngine:
https://stackoverflow.com/questions/1877410/whats-the-difference-between-all-these-audio-frameworks
https://stackoverflow.com/questions/26115626/i-want-to-call-20-times-per-second-the-installtaponbusbuffersizeformatblock/26600077#26600077
https://stackoverflow.com/questions/45644079/performance-between-coreaudio-and-avfoundation
It seems there aren't a lot of agreements on whether or not the Swift stack
could achieve low-latency using its AU wrapper. Some says that the
performance is 30-40% worse than the CoreAudio stack. But there is also a
positive report:
https://stackoverflow.com/questions/45644079/performance-between-coreaudio-and-avfoundation
Before I dive into a whole new world (Swift newbie), any suggestions from
the list would be greatly appreciated!
Thanks,
Beinan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (Coreaudio-api@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
