Tutorial
HISE Quick Start
Start with HISEScript for the shortest path or HISE C++ for stronger native-authoritative release builds.
SoundSync
HISE visual sequence
Package setup, activation, verification, unlocked access, Store, My Products, and device controls are shown in a consistent product flow.
SoundSync
Start from the customer activation screen
The HISE activation screenshot shows what the generated package is working toward: account login, serial activation, product identity, and support context in the plugin.
SoundSync
Quick start choice
The first decision is package type.
| Path | Use this when | First include/build step |
|---|---|---|
| HISEScript | You want the fastest script/WebView integration and can accept the client-script security boundary. | Copy SoundSync to Scripts and include Runtime/SoundSyncRuntime.js. |
| HISE C++ | You need stronger enforcement and can patch/rebuild HISE source for native authority. | Copy SoundSync to Scripts, stage AdditionalSourceCode, apply the HISE source patch, rebuild/export, include Scripts/SoundSyncNativeGate.js, and call ssSoundSyncNativeGateStart(). |
SoundSync
Implementation sequence
Run this sequence before creating release builds.
-
Create product
Set product identity, licensing, activation mode, device limits, offline grace, delivery, subscription behavior, support, and storefront settings.
-
Set brand and domain
Confirm logos, colors, support email, reply-to, main/root or subdomain, email sending domain, and SSL readiness.
-
Generate package
Generate HISEScript or HISE C++ package for the selected product and environment.
-
Install package
Follow the package-specific setup file map and include/build requirements.
-
Run Test Connection
Confirm package credentials and product binding without unlocking a customer license.
-
Test customer flows
Verify serial, account, email claim, validation, deactivation, offline grace, support, Store, My Products, subscriptions, and regeneration for the release build.
SoundSync
Verify Store and My Products before release
The HISE My Products screen shows the logged-in ownership state developers should test alongside serial, account, offline, subscription, support, and regeneration checks.
Security choice
If a product needs the strongest HISE path, use HISE C++ and complete the source patch/build workflow. HISEScript remains the easier implementation path and should be described honestly as script/client-side rather than native-authoritative.
