Skip to content
SoundSyncAudio software platform

Documentation

Try the JUCE Integration

Use the current sample product source package with the customer and license created by the guided test store.

Download source, then build it

Start guided test prepares paid and free samples with their own matching JUCE source ZIPs. The guide and authorized customer library use the same private object for that product. Follow Docs/QuickStart.md and Docs/CMakeSetup.md with your existing JUCE installation. These are source examples, not precompiled standalone applications or installed plugins.

SoundSync

Use the same test customer in the plugin

Example test workspace with customer fields hidden. Mailbox availability depends on workspace setup.

SoundSync

Keep the product identity together

  1. Acquire the sample

    Use its sandbox purchase or verified free claim. Do not substitute the developer login for the generated customer.

  2. Choose its package

    Select paid or free in the guide, or download that product from the customer library. Its API origin, app/product IDs, storefront links and independent verification keys belong to that sample.

  3. Exercise the customer paths

    Try customer Account login, acquired Serial login and supported email activation. Store/My Products and notices use the same application routes, rather than a manufactured success state. Notices are available only when enabled in the test workspace.

  4. Check offline and deactivation behavior

    Offline access requires the authorized signed grant and is bounded by the product Access setting and any earlier access/license expiry. Deactivation does not create new grace or prove that an unreachable server released a slot.

  5. Refresh and rebuild

    The guide/customer download refreshes the matching private package when the source release, signing keys or sample configuration changes. Replace the package in your project and rebuild; an existing compiled binary does not update itself. During a staggered release, reopen Evaluate & Test when its matching source version is ready.

Move to your own product deliberately

The sample source can be integrated into your own JUCE plugin to test that sample’s customer path. Generate a matching package for the actual production product before shipping. Sample IDs, serials, accounts, test website keys and signed offline grants do not become production credentials. Ordinary production packages require HTTPS; a local operator demo permits HTTP only to its exact configured loopback origin.

Compatibility quick demo

The separate owner-only quick-demo API remains available for older tests. Its temporary serial lasts seven days and its hidden demo product stays outside your catalog. Reset revokes the old serial and online activations; an already-issued offline grant still follows its signed deadline. This is distinct from the guided paid/free customer store, and its serial expiry is not a seven-day limit on the whole evaluation workspace.