SoundSync for HISE
Generate the licensing package. Connect your interface. Ship.
Choose HISEScript for a fast drop-in implementation or HISE C++ for stronger native-authoritative verification, with activation, validation, device access, offline grace, branding, support, and customer access connected to SoundSync.
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
Choose the HISE package path
Pick the package that matches the amount of HISE source work and runtime authority your product needs.
| Package | Best for | Verification strength | Developer work |
|---|---|---|---|
| HISEScript package | Fast HISE projects that need a simple script/WebView integration path. | Strong product-scoped verification, but not as tamper-resistant as the native C++ path because distributed script/client code is easier to inspect and modify. | Copy the generated SoundSync folder into Scripts, include Runtime/SoundSyncRuntime.js, run Test Connection, then test activation states. |
| HISE C++ package | Commercial plugin releases that need stronger copy-protection and native runtime authority. | Stronger native-authoritative verification: transport, storage, device identity, cache, and entitlement decisions move through SoundSync native code and public state. | Stage native source into AdditionalSourceCode, apply and verify the SoundSync HISE source patch, rebuild HISE where required, export, and run release checks. |
SoundSync
What both HISE packages connect
The package choice changes integration depth, not the customer business model behind it.
Product-scoped credentials
Generated package configuration is tied to the selected product, app ID, environment, package version, and credential state.
Activation paths
Customer login, serial activation, login-or-serial, email verification, activation limits, and machine identity are handled through SoundSync licensing flows.
Validation and offline grace
Startup validation refreshes access when online. Offline grace requires a previous valid state and confirmed denials such as revoked, refunded, expired, or deactivated access must lock.
Brand and support
Store name, logos, accent colors, light/dark treatment, product imagery, support email, support URL, and generated package values come from product setup and Brand Manager.
Customer access
Store, My Products, downloads, serial counts, subscription visibility, and support routing are available through the separate HISE in-plugin storefront package where enabled.
SoundSync
HISEScript setup path
Use this path when the launch priority is a fast HISE integration with a script-managed overlay.
-
Generate package
Create product credentials and download the HISEScript package from the product package area.
-
Place package
Copy SoundSync into the HISE project Scripts folder.
-
Include runtime
Load include("SoundSync/Runtime/SoundSyncRuntime.js"); from the main Interface script.
-
Run Test Connection
Verify product credentials and API reachability without activating a customer license.
-
Release test
Test login, serial, claim verification, deactivation, offline grace, support routing, and package regeneration before shipping.
SoundSync
HISE C++ setup path
Use this path when stronger runtime authority matters more than the shortest install path.
-
Generate native package
Download the native-authoritative HISE package for the selected product.
-
Stage native source
Run the installer helper to place SoundSync native files under the HISE project AdditionalSourceCode path.
-
Patch HISE source
Apply and verify the SoundSync HISE script/native API patch against the HISE source checkout.
-
Rebuild and export
Rebuild HISE where required, reopen the project with the patched executable, export the plugin, and patch the exported project when needed.
-
Verify authority
Run the package release checklist, native public-state checks, validation matrix, and host/runtime tests for the target build.
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.
Security reality for client packages
HISEScript is easier to implement and can be strong enough for many releases, but distributed script/client code should be treated as inspectable by determined attackers. HISE C++ requires more build work because it moves sensitive runtime decisions into native code and should be used when stronger enforcement is required.
Start with the package path that matches your release.
Read the HISE docs, compare package files, or choose JUCE/custom API if your product is not built in HISE.
SoundSync
Product proof
Screenshots and diagrams are placed near the workflows they explain, so visitors see the actual SoundSync surfaces instead of abstract feature claims.
Questions developers ask
Is SoundSync only for plugins?
No. SoundSync supports plugins, instruments, sample libraries, digital downloads, subscriptions, and custom audio tools.
Can I use my own site?
Yes. You can use hosted storefronts, embedded storefronts, standalone embeds, and custom domains depending on the surface you choose.
Does marketplace attribution add another fee?
No. SoundSync uses one 10% fee on SoundSync-processed sales, including marketplace-attributed sales.
Generate the licensing package. Connect your interface. Ship. belongs in one connected launch system.
Move from setup to customer access, growth, trust, and operations without rebuilding the business around disconnected services.