> On Mon, 13 Apr 2015 17:55:52 -0400, Steven Brawer > <[email protected]> wrote: > […]
> I don't want C++ classes (I'm not using C++), I don't want convenience > routines. All these things are just wrappers around C (objective C) > functions. I want the relevant functions. I think you may be out of luck here. From Apple’s Audio Unit development guide (at https://developer.apple.com/library/mac/documentation/MusicAudio/Conceptual/AudioUnitProgrammingGuide/Introduction/Introduction.html ): > To go forward in developing your own audio units based on what you learn > here, you will need: > The ability to develop plug-ins using the C++ programming language, because > the audio unit class hierarchy in the Core Audio SDK uses C++. In particular, my understanding is that Objective C cannot give very strong real-time guarantees, due to dynamic binding issues, and that is why Apple chose to write the AudioUnit API in C++ instead. AFAIK there is no underlying Objective C API for that reason. See also: http://lists.apple.com/archives/coreaudio-api/2010/Oct/msg00163.html https://mikeash.com/pyblog/why-coreaudio-is-hard.html http://www.kvraudio.com/forum/viewtopic.php?t=259182 Jeremy
_______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com This email sent to [email protected]
