AudioKit 1.2 and the future of Audio Development

Recently, we launched version 1.2 of AudioKit. We've included what we like to call sensible defaults for most operations. With sensible defaults, you can create an instance of an AudioKit object without having to initialize the object's parameters.  

Additionally, most operations now include tests. These tests let you hear what an individual operation is capable of doing, so it's easier for you to figure out what operations you need to get the sound you want!

I'm extremely excited for this release, as I think it's going to go a long way in helping iOS and OSX developers use audio in their apps in new and exciting ways. 

If you're developing for iOS or OSX, for example, you're probably at least aware of Core Audio. While Core Audio is extremely powerful, it's low-level nature makes it extremely difficult to prototype and deploy quickly...you're spending so much time working with low-level samples and buffers that you're not able to focus on making great sounds!

Before AudioKit, there were other 3rd party audio development solutions, such as libpd and Csound for iOS. However, both of these required developers to use other environments: Pure Data and Csound. If you were a developer and wanted to make interesting audio, you were stuck either trying to decipher Core Audio's cryptic nature, or learn how to use another environment. 

That's why AudioKit is so special...it allows developers to implement audio in a high-level way using Objective-C or Swift, without having to learn another environment such as Pure Data or Csound. 

In order for audio to be integrated into more and more applications, it has to be easier for software developers to work with audio. Csound for iOS started to solve this problem, but; for the actual audio implementation, you still had to use Csound...which, at it's best, can be described as having a rather cryptic syntax, even if the audio engine is extremely powerful. 

And, I'm not saying that their is no need for visual programming environments, such as Pure Data or Max/MSP (I for one am extremely excited about Max7).What I am saying is that software developers in the 'traditional' sense who want to write apps for iOS or OSX will be able to leverage the power of AudioKit

I believe that with AudioKit, developers will be able to create new and interesting experiences for users through high-level audio. And we're going to keep on improving AudioKit as we go.