AUAudioUnit subclasses: Obj-C vs Swift
AUAudioUnit subclasses: Obj-C vs Swift
- Subject: AUAudioUnit subclasses: Obj-C vs Swift
- From: Chris Adamson <email@hidden>
- Date: Thu, 23 Feb 2017 18:59:47 -0500
Would like a fact check on something for a talk next week…
When I create a v3 Audio Unit app extension, even if I specify the language as Swift, the template stubs out the AUAudioUnit subclass itself in Objective-C, allowing Swift only for the view controller.
Wondering about the reasons for this… could I rewrite my AUAudioUnit subclass as Swift, provided that the internalRenderBlock is in C/C++ with all the usual realtime caveats? Or is it this way because on macOS, the audio unit can optionally be loaded into the host process, and that’s not gonna fly with Swift until its ABI is stabilized?
Thanks!
—Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden