SoundSync for HISE
Two Licensing Packages for HISE
Choose HISEScript for a fast script integration or native HISE C++ for deeper compiled enforcement.
SoundSync
Choose your build path
| Package | Installation | Enforcement |
|---|---|---|
| HISEScript | Copy and include the generated script package | Script-level access integration; no HISE source rebuild |
| HISE C++ | Install native sources, patch/rebuild HISE, patch/build the export | Native authority in the compiled product |
Two packages, two installation paths
HISEScript runs in your HISE project without editing HISE source. Native HISE adds a C++ licensing authority and requires a patched, rebuilt HISE executable plus a rebuilt exported plugin. Generate the variant you intend to ship; their runtime files and build steps are not interchangeable.
Both connect product credentials, serial or account activation, device access, branding, and customer Store/My Products workflows. You still own your instrument or effect interface, DSP, release builds, and customer-facing product support.
SoundSync
Before generating
| Requirement | Check |
|---|---|
| Saved product | Correct product ID, publication state, license mode, activation mode, and delivery |
| Product credentials | The generated variant's product/app contract: standard key/secret for HISEScript; supported public identity for current native clients |
| Brand | Logo, colors, support identity, storefront location, and package configuration |
| Build choice | HISEScript or native HISE; native requires source/build access |
Security and evidence
Credentials and enforcement shipped in client software can be extracted or modified. Native enforcement raises the integration barrier; it is not a piracy-proof guarantee. Keep developer account tokens and partner secrets out of distributed plugins.
This guide describes the current implementation and package instructions. Source review does not certify every host, operating system, provider delivery, or payment lifecycle. Test the exact build and environment you intend to release.
SoundSync
Installation and runtime guides
HISEScript quick start
Copy, include, configure, and exercise the activation paths.
Native HISE setup
Install sources and build the native enforcement path.
Package files
Which files belong to each variant.
Troubleshooting
Differentiate installation, credentials, ownership, and device failures.
SoundSync
HISE and JUCE package cards in the developer workspace
The package workspace separates HISE and JUCE package status, product selection, connection readiness, and package download context so developers choose the right integration before release testing.
SoundSync
Branded HISE activation
The HISE activation surface shows product identity, serial/account paths, support access, and SoundSync-powered licensing inside the plugin context.
SoundSync
HISE in-plugin Store
The HISE Store screen lets customers browse available products, open product detail, and move toward purchase without leaving the plugin context.
SoundSync
HISE product detail
The HISE product screen shows product artwork, price, description, highlights, and the customer action to view or buy through the connected storefront.
SoundSync
HISE My Products
The HISE My Products screen shows owned products, downloads, serial counts, subscription state, and machine-access context with public-safe customer data.
Choose offline access in the product Access settings
HISEScript and native HISE use the offline grace selected in product creation > Access. A prior successful activation or validation is required. Zero days or disabled grace requires online authorization. Cached access ends at the server-issued deadline; reconnection refreshes it only after successful validation. Confirmed invalid, refunded, revoked or deactivated access must not be treated as a network failure.
HISE 0.5.1 removes unlimited cached-access shortcuts and checks expiry while the plugin is open. Earlier binaries are not updated by changing website copy: regenerate, rebuild and test the shipped plugin. A policy change takes effect on that machine after its next successful online validation; a disconnected client cannot learn about a later revocation before reconnecting or expiry. JUCE has a separate package contract: consult its current package guide rather than treating HISE grace as JUCE authorization.
Subscription grace cannot extend the server-authorized subscription access period. Billing-payment recovery and offline plugin grace are different deadlines. Test the exact exported build on each supported host and operating system.
Account security and product access stay separate
JUCE 0.7.2 and HISE Native C++ 0.5.2 account login can request an authenticator or recovery code when the customer has enabled two-factor authentication. Completing account sign-in still requires an entitlement and device activation for the selected product. Use the current package sources and rebuild existing plugins; a sign-in challenge does not create offline permission. See the package update and account-security guides for the required versions.