Skip to content
SoundSyncAudio software platform

Architecture page

HISE Package Files

Understand the files generated for HISEScript and HISE C++ packages, which files are package-owned, and when regeneration is required.

Start with getting startedExplore API docs
SoundSync HISE package panel showing REST API integration status, package download, config copy, and setup docs.
HISE plugin activation screen with branded login and serial activation options.
HISE My Products view with sanitized customer identity, owned products, serial counts, downloads, subscriptions, and machine state.

SoundSync

HISE visual sequence

Package setup, activation, verification, unlocked access, Store, My Products, and device controls are shown in a consistent product flow.

SoundSync HISE package panel showing REST API integration status, package download, config copy, and setup docs.
HISE plugin activation screen with branded login and serial activation options.
HISE plugin serial activation screen with product branding, serial field, and customer email field.
SoundSync email verification message for serial activation with demo customer wording.
SoundSync serial activation verification success page for a demo product.
HISE plugin unlocked state after activation with product interface visible.
HISE in-plugin Store catalog showing product cards, categories, pricing, and cart access.
HISE in-plugin Store product detail page with pricing, license, format, and support information.
HISE My Products view with sanitized customer identity, owned products, serial counts, downloads, subscriptions, and machine state.
HISE plugin state showing customer login or serial activation after device deactivation.

SoundSync

Store files support product browsing and ownership

The HISE Store and My Products screenshots show the package surfaces developers should regression-test after regeneration and release packaging.

HISE My Products view with sanitized customer identity, owned products, serial counts, downloads, subscriptions, and machine state.
HISE My Products

Regeneration rule

Regeneration can replace package-owned files. Keep custom HISE project code outside generated package files and regenerate after credential, brand, domain, support, product, or package-version changes.