- Declarative: Elementary makes it simple to create interactive audio processes through functional, declarative programming. Describe your audio process as a function of your application state, and Elementary will efficiently update the underlying audio engine as necessary.
- Dynamic: Most audio processing frameworks and tools facilitate building static processes. But what happens as your audio requirements change throughout the user journey? Elementary is designed to facilitate and adapt to the dynamic nature of modern audio applications.
Every Elementary application starts with the @elemaudio/core package, which provides the framework for defining your audio processes and a generic set of utilities for performing the graph rendering and reconciling steps.
Next, because Elementary is designed to be used in a number of different environments, there are several different ways to integrate. If you're new to the project, we recommend studying the following workflows to get the feel of working in Elementary:
- Use the @elemaudio/web-renderer package with your favorite frontend UI library to make an audio web application
- Use the @elemaudio/offline-renderer package with Node.js for static file processing
Once you're ready to dive in, we suggest starting with one of these ideas:
- Jump into the online playground for the quickest way of experimenting with sound
- Make an audio effects plugin following the SRVB plugin template (opens in a new tab)
- Try the small command line tool (opens in a new tab) here in this repository to explore an example native integration
- Check out the Native Integrations guide for embedding Elementary's C++ engine in your own native code
- Read the Custom Native Nodes guide for extending Elementary's built-in DSP library with your own low-level processors