Integration with 3rd Party Products

In past incarnations of Smaart, most notably SmaartLive v4 and v5, we incorporated control of 3rd party DSP devices into Smaart’s user interface. As our industry’s technology expanded, became more powerful, flexible and generally just cooler, it became impractical to support the full capabilities of DSPs as simple interfaces within the Smaart GUI.

When we built Smaart v7 (and now v8), we did so with 3rd party collaboration in mind, adding a backend API and organizing the codebase into flexible objects that can easily be packaged for external use.

The Smaart API (SAPI)

The Smaart API represents the quickest and easiest way for developers to provide Smaart integration in their products. SAPI allows 3rd party applications (Clients) to query and issue basic commands to Smaart (Host) as well as request the output data of any running measurements.  Access to, and use of Smaart’s API, is provided for free, and because SAPI is integrated into the program, any installation of Smaart can be enabled to act as a host via a simple checkbox in the programs options controls.

SAPI DiagramThe primary use case for SAPI is to allow external applications to obtain measurement data from Smaart and plot it in their own environment. Smaart measurement engines run in real time and are capable of producing large amounts of data. This data is being sent over the wire and if transmitted in real time could easily swamp the local network. To alleviate these concerns SAPI uses a request/response paradigm. No data is served unless explicitly requested by a client. This allows clients to control the update speed and thus throttle how much data is being transmitted and how often. Note that Smaart will process data independently of the update speed of clients. Thus regardless of how often a client requests data, Smaart will continue to process data in real time.

One of the design requirements for SAPI was to be platform and language independent thereby enabling clients written in any language and running on any platform access to the API. To facilitate this requirement all communication with SAPI is done over a simple TCP/IP connection.

Developers that are interested in obtaining a copy of the SAPI SDK (Software Development Kit) or for more information should contact moc.scitsuocalanoitar@troppus.

Our API is currently utilized in the control software for the following products*:

Licensing Smaart Code Modules for 3rd Party Programs

For some 3rd party developers, a SAPI-based (Client/Host) solution for integrating Smaart measurement technology into their products may be too cumbersome or impractical. In those cases, licensing Smaart code modules for implementation within their applications may be the best solution. Again, the good news here is, when we built Smaart, we did it with specifically this type of code portability in mind. The fundamental object-oriented nature of our codebase makes breaking out virtually any process in Smaart for licensing into other programs or devices a relatively simple endeavor.

Again, developers that are interested in licensing Smaart code modules for integration into their products or for more information should contact moc.scitsuocalanoitar@troppus.

Smaart Measurement Code Modules are currently integrated into the following products:

  • PreSonus Universal Control software, bundled for use with the StudioLive 16.4.2, 24.4.2 and AI-series mixers (16.4.2AI, 24.4.2AI, 32.4.2AI, RM16AI and RM32AI)
  • Studio 6 Digital “Smaart Tools” for their AudioTools suite of apps for iOS
    Visit for more information.