Guide
Regenerate and Update a JUCE Package
Upgrade JUCE plugins to 0.7.1 signed offline grace: save Access settings, regenerate, rebuild, validate online, test, and redistribute.
A package update is a plugin release
SoundSync provides the updated source package; it does not replace a compiled plugin already installed on a customer computer. Existing 0.7.0 binaries retain their original behavior. Regenerate the package, integrate it into your product, rebuild, and distribute the new binary.
Keep your DSP, editor customization, build configuration, and existing release recoverable. Compare package-owned files before replacement rather than overwriting your own product code.
SoundSync
Upgrade without losing customer access
-
Save the Access policy
Open the saved product > Access. Choose offline grace up to 90 days, or zero/disabled for online authorization. Keep the existing product and machine identity; do not create a replacement product merely to upgrade.
-
Regenerate for each target
Download a current Windows or Apple 0.7.1 source package for that product. Read START_HERE_FIRST.txt, README.md, Docs/LicensingSecurity.md, and Docs/OfflineGrace.md. Do not reuse another product configuration.
-
Check package readiness
In manifest.json confirm packageVersion 0.7.1 and offlineAccess: true for an offline-capable build. Keep the generated public verification keys in SoundSyncJuceEmbeddedConfig.h and its matching configuration. Never add a signing private key or pluginSecret.
-
Integrate and rebuild
Use SoundSyncLicensedAudioProcessor, or the documented processor-owned custom-base integration. Preserve before AND after DSP guards for float, double and bypass callbacks. Rebuild, sign/notarize where applicable, and confirm the host loads the new binary.
-
Refresh existing activation online
Allow a successful online activation or validation to obtain a signed offline_lease. An older unsigned cache is not offline authorization. Reuse valid saved machine credentials where supported; do not delete activations or consume a new device slot merely to obtain a grant.
-
Test the grace deadline
Disconnect after successful validation and check saved-project restart, editor-closed processing, exact expiry, zero/disabled grace, and earlier entitlement/subscription deadlines. Reconnecting refreshes grace only after successful validation.
-
Distribute the tested build
Publish the rebuilt plugin and customer update instructions. Test each supported OS, format and host with your actual product; generating a ZIP is not a substitute for release testing.
SoundSync
Package capability is not customer authorization
| Check | Meaning |
|---|---|
| manifest.json offlineAccess: true | Trusted verification keys are bundled. It does not enable grace for a product configured with zero/disabled grace or grant access to an unactivated customer. |
| manifest.json offlineAccess: false | The package lacks offline verification capability. Online authorization may still work. Contact SoundSync to resolve signing readiness, then regenerate and rebuild before advertising offline support. |
| A positive Access period | The server applies that saved period on successful activation/validation, capped by earlier access deadlines. Time begins at that success, not the first network failure. |
| A verified, unexpired offline_lease | The signed grant authorizes this product, activation and device until its deadline. A cached date or successful Test Connection cannot replace it. |
Settings and key changes reach clients differently
An Access policy change is applied after successful online validation on that machine; it does not require a rebuild when the installed package already supports the current signing keys. A disconnected client retains its previously issued deadline until expiry or reconnection. Confirmed denial or deactivation must lock access rather than restart grace.
Signing keys are managed by SoundSync. A future signer change must be coordinated so replacement public keys reach rebuilt clients before the new signer is used. Regenerating alone does not update deployed binaries; an unknown signing key cannot be repaired by editing cached dates or embedding private signing material.
SoundSync