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.