Protected Expansion Content
Protected Expansion Content
Signed encrypted banks, private delivery and independent ownership-aware access inside your JUCE instrument.
Deliver encrypted expansion content
Protected content packages your expansion archive into a signed, encrypted .sspc release in managed private storage. Customers receive compatible releases through their permitted library or integrated JUCE client. Keep your own expansion browser, content format and audio engine.
Private download authorization and playback authorization are different. Verify the package and the signed product/content permission in the maintained SDK. Ordinary downloaded files cannot be recalled or made securely temporary by a later account change. Do not expose the raw protected source as a normal customer download.
SoundSync
Publish an expansion archive
-
Set the product relationship
Save the required instrument relationship and product access settings. Decide whether this bank can join supported future-inclusion collections.
-
Upload the private source
In Protected expansion content choose one archive up to 512 MiB, a unique immutable revision, compatible instrument major versions and the minimum host software version.
-
Complete the upload
Follow the returned direct or multipart upload plan. Completing bytes verifies the private source; it does not publish an encrypted release.
-
Package and publish
Publish the completed protected upload to create its signed .sspc release. Review release status before publishing purchase options that require it.
-
Check delivery and playback
Test an owner, an eligible subscriber, a customer missing the required instrument, an incompatible build, offline startup and revoked access. New banks require first online authorization before offline use.
SoundSync
Connect the JUCE host in three places
-
Load on a worker
Open the protected package through the SDK loading path, not on the audio thread. Keep network, disk, cryptography, blocking locks and allocations off the real-time audio callback.
-
Retain the access handle
Attach the bank access handle to the affected sound, voice or layer. A subscription-only bank can lock without disabling another independently owned bank.
-
Preserve commercial origin
Save the bank/content identity in presets and project state so restore cannot convert commercial content into an unprotected source. Use the protected seekable stream; do not fall back to a plaintext temporary file after failed verification.
Compatibility is not another purchase
Compatible instrument majors and the minimum host version are software requirements. They do not limit a purchase to a paid major-version tier. The SDK reports missing product ownership separately from incompatible software.
Content authorization protocol 2 verifies and caches each bank permission independently. Up to 64 release references fit one server request; this is not a lifetime bank or library ceiling. The maintained client batches larger collections, normally in groups of 32.
Protected loading verifies integrity before use and as data is read. This raises the integration's enforcement strength; it is not a claim of piracy-proof software or instant remote revocation on disconnected devices.
SoundSync
Make access part of the product
SoundSync
The protected archive controls
Set the release revision and software compatibility in the product editor. This example shows the upload form, not a completed publication or a playback authorization.