Guide
Native C++ Integration
Choose generated native enforcement or implement your own HTTP licensing runtime.
SoundSync
Native paths
| Environment | Implementation |
|---|---|
| JUCE | Processor-owned SoundSyncJuceProcessorLicense with attached editor UI and audio guards |
| HISE C++ | Native source install, patched/rebuilt HISE, native gate, and patched/rebuilt export |
| Custom C++ application | Your transport, customer proof, device identity, storage, renewal, and enforcement against the licensing API |
Keep enforcement outside UI lifetime
A closed editor must not remove licensing authority. Keep blocking network operations off audio callbacks. Test all relevant process/bypass paths and ensure protected behavior is actually gated.
Credentials and enforcement shipped in client software can be extracted or modified. Native enforcement raises the integration barrier; it is not a piracy-proof guarantee. Keep developer account tokens and partner secrets out of distributed plugins.
Separate local lock from server release
The HTTP deactivation call requires a connection and authenticated proof for the intended activation. A custom client owns its local lock and retry behavior. If it queues deactivation, retain the pending proof until the server confirms release; an HTTP timeout is not confirmation.
The maintained JUCE runtime locks locally and manages its protected deactivation state. Do not manually delete its pending proof or persistent local block. If saving intent fails, keep audio locked and resolve deactivation_storage_failed; do not claim that a pending request was saved or a slot released.
