Skip to content
SoundSyncAudio software platform

Guide

Regenerate and Update a JUCE Package

Upgrade JUCE plugins to 0.9.3 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

JUCE package choices

JUCE package choices

SoundSync

Upgrade without losing customer access

  1. Save the Access policy

    Open the saved product > Access. For bounded access choose grace up to 90 days, or zero/disabled for online authorization; explicit signed permanent-device ownership is a different mode. Keep the existing product and machine identity; do not create a replacement product merely to upgrade.

  2. Regenerate for each target

    Download a current Windows or Apple 0.9.3 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.

  3. Check package readiness

    In manifest.json confirm packageVersion 0.9.3 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.

  4. 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.

  5. Refresh existing activation online

    Allow a successful online activation or validation to obtain the signed authorization for the selected policy: offline_lease for bounded grace, or explicitly authorized product_authorization and content_authorization for permanent-device ownership. 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.

  6. 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.

  7. 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

CheckMeaning
manifest.json offlineAccess: trueTrusted verification keys are bundled. It does not itself grant customer access. Bounded grace follows Access settings; explicit permanent-device grants have their own signed policy.
manifest.json offlineAccess: falseThe 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 in bounded-grace modeThe 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 for bounded graceThe 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

Integration and recovery

JUCE package

Processor, editor, configuration, and package API.

Offline troubleshooting

Expired grants, missing keys, storage, and clock recovery.

Licensing API

Signed grant response fields and authorization.

Native account login with two-factor authentication

The updated JUCE 0.9.3 and HISE Native C++ 0.5.2 sources support the customer account two-factor challenge. Regenerate the complete package, replace the matching sources and rebuild the plugin; an older installed binary does not acquire this behavior from a documentation or server update.

Sign in with the customer email and password. If two-factor authentication is enabled, the account form changes to Authenticator or recovery code. Enter a current authenticator code or an unused recovery code and choose Verify code. A challenge is not a customer session, entitlement or device activation; the plugin remains locked until verified account login and product/device activation succeed.

An invalid code can be retried. An expired challenge requires signing in again. The challenge lasts up to ten minutes and is kept only in the running native client, not the activation cache, logs or public state. Account passwords, two-factor codes and account session tokens are not saved in the license cache. Do not disable two-factor protection to integrate a plugin.

Activation feedback and protected Windows recovery

JUCE 0.9.3 improves activation progress, failure feedback and retries for serial and account activation. On Windows, a damaged product cache can recover after fresh successful online authorization, and a damaged device-identity copy can be restored from its valid protected backup.

Conflicting identities and unreadable deactivation markers remain locked and require support. Do not delete activation proof or deactivation markers to bypass them. Regenerate the matching source package and rebuild your plugin to include the update. The selected Access grace period, signed-grant expiry and local deactivation block still apply; this recovery does not create offline permission.

Protected banks without a lifetime bank-count ceiling

JUCE 0.9.3 uses content authorization protocol 2 for configured purchase-option products. It removes the previous 64-release lifetime ceiling. Subscription access follows the developer's published inclusions, including all current and future eligible banks when that is the offered plan.

Keep your own expansion browser, content format and audio engine. The same three integration connections remain: load protected content on your loading worker, retain its access handle on the affected sound or voice, and preserve its commercial origin in saved state. The SDK automatically batches requests and caches each signed bank permission independently. The 64-release maximum applies to one server request, not the total library or active banks.

Explicit permanent-device purchases keep their permanent instrument and purchased-content rights. Subscription permissions retain their signed offline grace and expiry. A newly published bank needs its first online authorization before offline use. Regenerate and rebuild with matching package headers and binaries; existing protected archives do not need repackaging. Older binaries retain their original behavior.

SoundSync

Add messaging without changing licensing

JUCE Plugin Notices

Independent companion and binary upgrade requirements.

SoundSync

Include the complete 0.9.3 update

  1. Keep the product identity

    Use the existing product and machine identity. Preserve valid activation proof and deactivation markers; do not create a replacement product to update the SDK.

  2. Match all package parts

    Regenerate the complete target package with its configuration, source, headers and native libraries. Read Docs/ProductOwnership.md and Docs/ProtectedContent.md as well as OfflineGrace.md and LicensingSecurity.md. Do not mix versions.

  3. Keep compatibility separate

    Set the real software version for bank compatibility. Same-product ownership no longer uses paid major-version gates; separately sold products still need their own rights.

  4. Test the relevant offline modes

    Test the selected bounded Access grace, earlier subscription/trial expiry and explicit permanent-device ownership independently. Verify new-bank first online authorization and immediate local deactivation.

  5. Test host recovery

    Check Windows protected-cache recovery and legitimate macOS Keychain approval in each supported host. Do not delete keys, identities or deactivation markers to bypass an error.

  6. Ship rebuilt binaries

    Rebuild, sign/notarize where appropriate, test each format/OS and distribute the new plugin. A downloaded ZIP or server update does not replace installed customer binaries.

SoundSync

Start with the product package controls

Download the package for the intended product, then follow the upgrade guide, rebuild and distribute your plugin. This screenshot identifies the controls; it does not certify a package version.

JUCE package choices

Require the authorization for the selected offline mode

Bounded grace requires a valid signed offline_lease with its product, activation, device and deadline checks. Explicit permanent-device ownership instead uses signed product_authorization and any required content_authorization verified by the matching protocol-2 SDK. A missing offline_lease alone is not a failure for that explicitly authorized ownership mode.

A device credential renews authorized access online; it is not itself offline playback permission. Pending enrollment, an unsigned cached date and a successful catalog read cannot substitute for a verified grant. Package regeneration still requires integrating, rebuilding and distributing the matching plugin; changing an API URL does not update installed binaries.