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

Generated files produce customer-facing package screens

The HISE activation screen is the visible customer result of generated config, runtime files, branding values, support links, and activation mode setup.

HISE plugin activation screen with branded login and serial activation options.
HISE login activation

SoundSync

HISEScript package map

The script package is optimized for fast install and script/WebView activation.

AreaPurposeDeveloper edit policy
SoundSyncConfig.js/jsonProduct identity, API base, app/credential values, activation mode, subscription settings, support, and branding.Regenerate from SoundSync when product, credential, brand, domain, or support settings change.
Runtime/SoundSyncRuntime.jsScript runtime for overlay creation, startup validation, activation, deactivation, local cache, Test Connection, and support buttons.Package-owned. Do not edit in the HISE script editor.
ScriptsModular helpers for activation, validation, deactivation, connection ping, and offline grace.Use only through documented extension points.
UILicense overlay and component models.Customize product UI outside package-owned files unless docs name a supported hook.
DocsSetup, offline grace, regeneration, and release checklist guidance.Read before release testing.

SoundSync

HISE C++ package map

The native package adds source, tools, and WebView/native command bridging for stronger authority.

AreaPurposeDeveloper edit policy
Scripts/SoundSyncNativeGate.jsTiny HiseScript gate that initializes SoundSyncNative and asks the patched HISE/JUCE source to show the native activation window when needed.Package-owned. Include once from the host Interface script and call ssSoundSyncNativeGateStart().
Scripts/SoundSyncNativeRuntime.jsLegacy/internal native WebView bridge retained in the package while the native-authoritative gate path remains the production path.Package-owned. Do not wire for new native-authoritative installs unless explicitly testing the old bridge.
NativeCMake, public config, branding snapshot, include/src, and native licensing bridge over shared core.Stage into AdditionalSourceCode. Do not fork licensing policy.
ToolsInstall, source patch, verify, revert, export-project patch, and compatibility helper scripts.Run from PowerShell against the correct HISE project/source paths.
WebView/LicenseLocal activation UI that talks to the native adapter instead of calling the network directly.Treat as package-owned unless a supported theme hook is documented.
DocsSetup, offline grace, troubleshooting, source patch, release checklist, and migration guidance.Follow before export and release.

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.