SDK Integration

Put the engine inside your product.

The Quilio SDK is the processing engine behind our own products, available for use inside yours. Pitch and time, effects, analysis, and synthesis, with a C++ API and bindings where a project needs them.

Integration is the part that decides whether an SDK is worth having. We do that work with you rather than handing over a header and a licence key.

What the work involves

Evaluation

Before any commitment, a build of your product with the engine in it, running on your material. You hear the result and see the CPU cost before deciding.

Integration

Wiring the engine into your signal path, your parameter system, your state saving and your build. Done in your repository, so the result is code your team can maintain.

Platform coverage

macOS, Windows and Linux, plus iOS, Android and WebAssembly where the product goes there. One engine across all of them.

Support and documentation

API documentation, worked examples, and a direct line to the people who wrote the engine while you are integrating.

What you get

  • A licensed build of the engine for your platforms
  • Integration work completed in your codebase
  • Documentation and examples covering the parts you use
  • A support arrangement for the life of the licence

Questions

How is the SDK licensed?

Per product, with terms that depend on distribution. Source licences are available for parts of the engine.

Can we try it before licensing?

Yes. Request access and we will arrange an evaluation build against your own material.

What if we need something the engine does not do?

We extend it. Several parts of the current engine started as a client requirement.

Start a project ยท All services