Skip to content
SoundSyncAudio software platform

Lifecycle page

HISE Startup Lifecycle

Separate stored state, server authority, activation UI, and protected product access.

Start with getting startedExplore API docs

SoundSync

Startup decisions

  1. Load configuration

    Resolve the product, credential scope, activation mode, machine identity, and branding.

  2. Read local state

    Load the protected cache for this product and device. A stored identity is not proof that access remains valid.

  3. Validate silently

    Ask SoundSync for the current entitlement/device state where connectivity permits.

  4. Apply the result

    Use an accepted state to unlock; show activation for missing ownership, invalid credentials, or required customer action.

  5. Handle a network failure

    Use only the variant-specific permitted grace policy. Never convert a confirmed denial into offline access.

  6. Revalidate and deactivate

    Refresh access during use according to the package contract. Deactivation releases device use; it does not erase the order.

Native authority and UI are separate

In a native build the activation view communicates state, while the native authority must enforce access in the exported product. In HISEScript the script runtime provides the integration path. Do not infer native protection from a WebView rendering successfully.

Store, My Products, customer portal sessions, and audio licensing have separate responsibilities. Opening a storefront or an expired browsing session is not itself a device deactivation.

SoundSync

Unlocked product state

The activated plugin capture shows the product after the package has allowed access.

HISE plugin unlocked state after activation with product interface visible.
HISE plugin unlocked