Guide
Offline Access by Integration
Offline access is package-specific, never a universal licensing promise.
SoundSync
Current behavior
| Integration | Offline boundary |
|---|---|
| HISEScript | Configurable grace following prior valid access and an unexpired server grace state |
| Native HISE | Follow the generated native authority contract and verify the exported build |
| JUCE 0.7.3 | Signed offline grant follows saved Access period; online authorization is required without valid grace |
| Custom HTTP | Your client implements only the documented and authorized cache/grace policy |
Do not turn denial into grace
Missing entitlement, revoked credentials, expired access, refund effects, and invalid ownership are not connectivity failures. Preserve the distinction in both the UI and the processing gate.
A warm activated device, fresh installation, corrupted cache, expired grace state, and clock changes are separate release tests. A screenshot of an offline message does not establish that every offline failure has been exercised.
Hard denials are not offline failures
Offline grace is not a catch-all error handler. SERIAL_NOT_FOUND or SERIAL_REVOKED are confirmed denials, not reasons to continue with cached ownership. Device deactivation, subscription_payment_required, and an expired entitlement also require their documented access decision.
Permit grace only in an integration that supports it, after prior valid access, during a genuine connectivity failure, and before the configured expiry. JUCE 0.7.3 requires its own verified signed grant; unsigned HISEScript cache data must not unlock a JUCE startup.
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.
Signed offline access follows your product settings
Choose the grace period in product creation > Access. Successful activation or validation returns a signed grant bound to the product, activation and device. The period starts at that successful online check, not the first failed connection. The package bundles only public verification keys. Reopening the plugin or losing connectivity does not extend its signed expiry. An earlier entitlement or subscription access deadline shortens the grant.
The processor enforces access with the editor closed, including float, double and bypass processing. Confirmed revoked, refunded or deactivated access must lock the product rather than renew grace. A disconnected device learns about later server changes on reconnect or when its existing grant expires.
Regenerate the Windows or Apple source package, check manifest offlineAccess, rebuild and test your product. Existing compiled plugins are not upgraded automatically. Windows VST3 and Ableton Live 10.1.43 fixture tests cover offline playback, expiry, saved-project restart and WAV export; Apple Keychain/AU and your own product binaries require target-host testing.
offlineAccess: true describes bundled verification capability, not an active customer license or an enabled product policy. An older unsigned cache needs successful online activation or validation before offline use. After rebuilding, distribute the updated binary; replacing a ZIP in the dashboard cannot update customer installations.
Changing Access settings applies on the next successful online validation without a rebuild when the installed package already has the required public keys. A future signer change must be coordinated with replacement public keys in rebuilt clients; never add private signing material to a plugin.
SoundSync
Update an existing JUCE product
Regenerate and update JUCE
Package readiness, saved activations, offline tests, and customer distribution.
