AudioKit – An Open-Source Platform For Audio Synthesis, Processing, And Analysis

audiokit-synthesizers-fxAudioKit is a new open source platform for audio synthesis, processing and analysis on iOS and OS X.

It’s evolved from the Csound computer language for audio. As CDM’s Peter Kirn notes, “what AudioKit is in effect is Csound as an audio engine, with Objective-C and Swift as the API.”

Features:

  • 100+ Synthesizers and FX – Physical Models, Spectral Effects, Granular Synthesis, Effects Processing, Filters, Reverbs, and more.
  • Built-in Sampler – Record audio streams, including from the microphone, into tracks you can name, recall, and process on-the-fly.
  • Powerful Sequencing – Sequences are not limited to the usual notes-on-a-score, but can contain blocks of any code that can be triggered at any time.
  • Full-featured Examples – The list of examples is growing, but already contains projects demonstrating audio techniques such as FM Synthesis, Granular Synthesis, Convolution, Effects Processing, and Pitch-Shifting, and more.
  • Simple, Human-readable Code – Coding with audio with audio metaphors – Conductors control Orchestras, which contain Instruments that produce Notes. Clear methods with Apple-style naming conventions, Xcode completion, documentation and tool-tips.
  • Write your audio-code along side your app logic – The same code that controls your data and user interface controls your sound in Objective-C or Swift.

Here’s a video intro:

Details on AudioKit are available at the project site.

If any readers are using AudioKit, let us know how you are using it and what you think of it!

via CDM’s Peter Kirn

9 thoughts on “AudioKit – An Open-Source Platform For Audio Synthesis, Processing, And Analysis

  1. Why can I not find what license it uses? “Open Source” is a vague marketing term not a legal term. This looks super awesome though!

    Like this comment?: Thumb up 1
      1. Ok, so for the question everybody really wants to know: is LGPL compatible with the Apple app store? This isn’t the thing you just want to assume without being certain. Moreover, this is the kind of thing that would be awesome to have plainly stated on the website. The fact that it’s not makes me nervous; almost like you want people to get hooked using it and then later “oh, sorry LGPL can’t be used on the app store, but if you pay us we’ll license it proprietarily to you for commercial use”. Not saying that’s the case but any time the FSF is involved you can be sure the code is anything but “free”.

        Like this comment?: Thumb up 3
        1. 4. Combined Works.
          You may convey a Combined Work under terms of your choice that,
          taken together, effectively do not restrict modification of the
          portions of the Library contained in the Combined Work and reverse
          engineering for debugging such modifications, if you also do each of
          the following:
          a) Give prominent notice with each copy of the Combined Work that
          the Library is used in it and that the Library and its use are
          covered by this License.
          b) Accompany the Combined Work with a copy of the GNU GPL and this license
          document.
          c) For a Combined Work that displays copyright notices during
          execution, include the copyright notice for the Library among
          these notices, as well as a reference directing the user to the
          copies of the GNU GPL and this license document.
          d) Do one of the following:
          0) Convey the Minimal Corresponding Source under the terms of this
          License, and the Corresponding Application Code in a form
          suitable for, and under terms that permit, the user to
          recombine or relink the Application with a modified version of
          the Linked Version to produce a modified Combined Work, in the
          manner specified by section 6 of the GNU GPL for conveying
          Corresponding Source.
          1) Use a suitable shared library mechanism for linking with the
          Library. A suitable mechanism is one that (a) uses at run time
          a copy of the Library already present on the user’s computer
          system, and (b) will operate properly with a modified version
          of the Library that is interface-compatible with the Linked
          Version.
          e) Provide Installation Information, but only if you would otherwise
          be required to provide such information under section 6 of the
          GNU GPL, and only to the extent that such information is
          necessary to install and execute a modified version of the
          Combined Work produced by recombining or relinking the
          Application with a modified version of the Linked Version. (If
          you use option 4d0, the Installation Information must accompany
          the Minimal Corresponding Source and Corresponding Application
          Code. If you use option 4d1, you must provide the Installation
          Information in the manner specified by section 6 of the GNU GPL
          for conveying Corresponding Source.)

          Like this comment?: Thumb up 0

Leave a Reply

Your email address will not be published. Required fields are marked *