Skip to content
SoundSyncAudio software platform

Guide

Before You Begin

Prepare the product, integration, and test identities before implementing licensing.

Start with getting startedExplore API docs

SoundSync

Prepare the integration

  1. Save the product

    Configure the intended license mode, activation mode, device allowance, price, and delivery.

  2. Choose a package

    Use HISEScript, native HISE, JUCE, or your own HTTP runtime; do not mix their include/build instructions.

  3. Match the credentials

    Use the generated contract for that product and environment. Native public identity is different from the standard key/secret path.

  4. Prepare test identities

    Use permitted test customers, owned and unowned products, and distinct devices. Never use another customer's serial to test a claim.

  5. Plan enforcement

    Determine which audio and features remain locked before valid access. An activation overlay alone is not audio enforcement.

  6. Plan diagnostics

    Log operation and safe error codes, not passwords, serials, tokens, or customer details.

Use the right success criterion

Credential verification, customer sign-in, entitlement, device activation, and audio unlock are different checks. Test each instead of treating one successful request as proof of the entire integration.

JUCE 0.7.0 requires online renewal at startup. Valid saved credentials are reused without repeated sign-in, but offline audio access is unavailable in this release. HISEScript offline grace is a different package policy.