AAP-JUCE: JUCE audio plugin and hosting support for AAP (Audio Plugins For Android)

AAP-JUCE is a part of AAP (Audio Plugins For Android) project that integrates JUCE apps (plugins and hosts) to Android.

This repo is the place where we have the common JUCE integration support modules, as well as various patches for handful of different JUCE versions.

CAUTION: the entire AAP framework is still under active development and will keep bringing in breaking API/ABI changes. Also, since JUCE itself does not support AAP or anything like AAP that works as an Android Service, there are handful of local changes that try to make it work within the AAP basis.

We partially care about backward compatibility, but everything is still subject to change. Contributions are welcome but please bear in mind, documentation is poor and source code is ugly. We have GitHub discussions for AAP enabled at aap-core, not in aap-juce repo, so please feel free to shoot your questions there.

Existing ports

We have lots of JUCE plugins ported to AAP already. They are listed at AAP Wiki.

aap-juce-simple-host can enumerate the installed AAP plugins on the system (not limited to aap-juce ones), and instantiate each plugin.

At this state, this repository itself is almost about a set of build scripts that lets you port your (or others') JUCE audio plugins and hosts to AAP world, as well as a bunch of JUCE patches to make it realize. And probably more importantly, this README.

Why JUCE for AAP?

JUCE is a popular cross-platform, multi-plugin-format audio development framework. JUCE itself does not support AAP, but it can be extended by additional modules. JUCE also supports Android (you can even run UI), which makes things closer to actual app production. Still, JUCE is not designed to be extensible enough, additional code to support AAP is needed in each app. And when it comes to GUI support, many apps are not quite ready for Android.

While JUCE itself is useful to develop plugin formats like AAP, it is designed to be independent of any other audio development toolkits and frameworks. We stick to minimum dependencies, at least on the public API surface.

JUCE API is stable-ish, while AAP API is not. So if anyone wants to build AAP plugins portable without fear of API breakage, JUCE can be your good friend.

Note that JUCE plugins are usually designed for desktop and not meant to be usable on mobiles. In particular -

• their UIs usually don't build, and/or are usually useless on mobile.
• those plugins that lets user pick up local files would not fit well with Android paradigm.
• they frequently expose performance issues too.

Code origin and license

This repository itself is licensed under the AGPLv3 license (in sync with JUCE itself).

More details...

Check out the GitHub repository README for more details.