Skip to content

Treefall SDK documentation

Use these pages as task-oriented integration guidance. Start with the integration overview to choose a path, then follow the build and package procedure before linking an application.

  • Install the package: Build and install covers the minimum CMake and language requirements, the required SndFile provider for the documented evidence build, and failure outcomes.
  • Render host-neutral transport output: Link the SDK shows exact package discovery and the Treefall::transport target.
  • Read and write media: Audio files covers control/background-thread preflight, WAV PCM16 writing, probing, reading, and cleanup.
  • Embed the C interface: C ABI negotiation shows how to request ABI 1.0 and reject incompatible results.

The host-neutral core, session, transport, routing, analysis, and file utilities are the portable starting point. They are designed for offline operation and do not require an audio device. The Dummy driver is useful for tests and device-free integration.

Device-backed operation is a separate concern. CoreAudio is the shipped production device backend on macOS. Linux currently advertises no production device backend, and the Windows WASAPI package entry remains source/fake-test capable rather than release-supported. Do not promote a device backend because its source compiles; check the installed target and the capability API for the build you are using.

The examples shown on these pages are rendered from the tracked product bundle with their source revision, digest, and producer-reported command. They are not copied snippets that can silently drift from the verified source. The audio-file example specifically proves WAV PCM16 through the required libsndfile provider; it is not a claim that every codec or provider combination was executed.

Later mainline suite and realtime-qualification corrections are not included in this pinned preview. They are outside the evidence boundary documented here. To reproduce this release’s package surface, use the exact source revision in the banner and keep the install prefix isolated from other SDK builds.

Read the architecture overview · Read the support matrix · Read the realtime audit