Skip to content
SoundSyncAudio software platform

SoundSync for JUCE and Native C++

SoundSync for JUCE

Add product licensing, signed offline access, Store and My Products screens to your JUCE instrument or effect.

JUCE package choices
Access and offline grace
JUCE store example - Native interface example, not a live licensing test.

Licensing lives in the processor

The current JUCE package is a complete source integration with a processor-owned licensing runtime and editor component. Own SoundSyncJuceProcessorLicense for the processor lifetime. The editor attaches the activation UI; it must not be the only place that refreshes or enforces licensing.

Windows package targets produce VST3. Apple package targets produce VST3 and AU. These build targets are not a claim that every host or OS version has been runtime-tested.

Start the processor from a verified permission

A plugin can start from its valid signed authorization while offline, without requiring the editor to open. Online activation or validation is needed to establish or refresh the supported permission; an old unsigned cache is not a replacement.

Keep the licensing decision in the processor path and use the package upgrade guide for existing projects. Bounded grace and explicitly authorized permanent-device ownership are separate policies.

SoundSync

Integrate the current package

  1. Generate for the saved product

    Download the current Windows or Apple 0.9.3 source package. Read START_HERE_FIRST.txt, README.md, Docs/LicensingSecurity.md, and Docs/OfflineGrace.md.

  2. Add the CMake target

    Load your JUCE checkout first, enable SOUNDSYNC_BUILD_JUCE_COMPONENTS, add the package subdirectory, and link soundsync_juce.

  3. Use the licensed processor base

    Derive from SoundSyncLicensedAudioProcessor and preserve your buses, parameters, state serialization, and other processor overrides.

  4. Move your DSP callbacks

    Rename processBlock to processLicensedBlock and custom bypass callbacks to processLicensedBlockBypassed. The base owns final float, double, and bypass entry points, checking before and after DSP.

  5. Attach the editor

    Keep SoundSyncJuceEditorAttachment as the last editor member and initialize it with the editor and processor.soundSyncLicense(). It manages activation, Store/My Products, bounds, and portal closing.

  6. Test without an editor

    Exercise unauthorized startup, MIDI cleanup, sidechains, and continuing revalidation with the editor closed.

  7. Rebuild old releases

    Replacing source does not update compiled binaries. Rebuild, sign where applicable, test, and distribute the updated product.

SoundSync

JUCE package choices

Custom processor bases

If your existing processor must retain a custom base class, own SoundSyncJuceProcessorLicense for the processor lifetime and attach SoundSyncJuceDropIn to that same instance. Guard every float, double, and bypass callback before AND after DSP using audioGate()->processOutputs(buffer, midi, getTotalNumOutputChannels()); return when the guard reports locked access.

Pass the output channel count, not all inputs or sidechains. The older buffer-only guard is not suitable for arbitrary host buffers. The recommended licensed base supplies these guards without manual startup, timers, or an extra UI unlock boolean.

Keep blocking work off the audio thread

The guard reads the native access gate and clears unauthorized output. Do not make HTTP requests, read files, activate, validate, or deactivate from processBlock. The processor-owned worker performs renewal independently of editor visibility.

SoundSyncJucePublicState::mayOpenProduct is appropriate for protected controls, preset loading, and exports. A UI boolean is not a replacement for the processor audio guard.

SoundSync

Package areas

PathResponsibility
START_HERE_FIRST.txtCurrent installation and release requirements
CMakeLists.txt and modules/soundsync_juceBuild target and JUCE module integration
include/soundsync/juceProcessor, client, public-state, audio-gate, and UI interfaces
srcJUCE runtime and components
nativeJUCE package native authority and local machine state
examplesPlugin and standalone wiring references
DocsSecurity, setup, storage, lifecycle, customer access, troubleshooting, and release checks

Login, serials, and customer browsing

Customer login exchanges account credentials for a hosted customer token before activation. The runtime does not persist the account password or customer session token. The protected machine activation cache is separate from Store/My Products browsing.

Opening Store or My Products does not deactivate the machine. A portal session expiring does not by itself authorize or revoke audio; diagnose the licensing state separately.

Activation and device release

Account login and serial activation are distinct customer paths. A serial requiring ownership proof can enter the email-verification flow; an existing account should sign in rather than silently creating another identity. Saved machine credentials restore without consuming a new activation while valid.

Deactivation locks locally immediately and persists the intent before contacting the server. Only confirmed server deactivation proves the device slot was released. Transient renewal failures retry with backoff; a confirmed denial or deactivation does not silently reactivate.

SoundSync

Access and offline grace

Place Store and My Products where they fit

The editor attachment provides packaged launchers. Custom controls can call openStore(), openMyProducts(), and closeStorefront(), or use createStoreButton() and createMyProductsButton() with the supported style settings. Hide built-in navigation when providing your own controls; do not duplicate account or catalog logic.

The renewal worker remains processor-owned and independent of the editor. Its validation interval is clamped to 5 through 120 seconds; renewal cannot be disabled. Optional licenseProcessingChanged callbacks run on the audio thread and must be realtime-safe.

Release checks

Test fresh startup, saved credentials, unavailable network, expired/revoked access, device limits, deactivation, multiple instances, float/double/bypass processing, and editor-closed operation. Check product ID and branding after regeneration.

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.

This guide describes the current implementation and package instructions. Source review does not certify every host, operating system, provider delivery, or payment lifecycle. Test the exact build and environment you intend to release.

SoundSync

JUCE package status in the developer workspace

Developers can review package readiness, product licensing setup, credentials, and connection state before integrating the JUCE package into a plugin or standalone app.

JUCE package choices

SoundSync

JUCE login activation

The JUCE login screen shows the activation-required state, product identity, customer account path, and connection test access inside a native-styled plugin UI.

JUCE login example - Native interface example, not a live licensing test.

SoundSync

JUCE serial validation

The JUCE serial screen shows serial activation with a customer email field, final validation action, and the same product-scoped access decision used by the package.

JUCE serial example - Native interface example, not a live licensing test.

SoundSync

JUCE Store

The JUCE Store screen shows available products, product cards, and customer navigation inside the plugin storefront surface.

SoundSync

JUCE product detail

The JUCE product detail screen shows product artwork, product information, and the customer action to view or buy through the connected storefront.

JUCE detail example - Native interface example, not a live licensing test.

SoundSync

JUCE My Products

The JUCE My Products screen shows sanitized customer identity, owned products, serial state, and device deactivation actions after login.

JUCE library example - Native interface example, not a live licensing test.

Ship offline verification with the processor

JUCE 0.9.3 verifies product- and device-bound offline permissions with bundled public keys. Bounded grace uses the period selected in Access after a successful online activation or validation, up to 90 days and capped by earlier access expiry. Reopening the editor is not a renewal.

Explicit permanent-device ownership uses its own signed authorization. A confirmed denial or local deactivation locks the product; a disconnected client cannot learn about a later server revocation instantly.

Regenerate the package for the intended Windows or Apple target, rebuild, test in your supported hosts and distribute the updated plugin. Keep private signing material out of the client.

Inspect manifest.json: offlineAccess: true means the package includes verification capability, not that this customer owns the product. An older unsigned cache must complete online authorization first. Grace starts at the successful check, not the first failed connection. A signer rotation needs replacement public keys in a rebuilt release.

SoundSync

Offline access during the grace period

JUCE offline example - Native interface example, not a live licensing test.

SoundSync

Update an existing JUCE product

Regenerate and update JUCE

Package readiness, saved activations, offline tests, and customer distribution.

Account security and product access stay separate

JUCE 0.9.3 and HISE Native C++ 0.5.2 account login can request an authenticator or recovery code when the customer has enabled two-factor authentication. Completing account sign-in still requires an entitlement and device activation for the selected product. Use the current package sources and rebuild existing plugins; a sign-in challenge does not create offline permission. See the package update and account-security guides for the required versions.

SoundSync

Add messaging without changing licensing

JUCE Plugin Notices

Independent companion and binary upgrade requirements.

Resolve each owned instrument and bank independently

The JUCE client combines the valid grants for the instrument and its protected content. Ending one subscription must not remove a bank the customer owns through an independent purchase; owning a bank does not itself grant its required instrument.

Verify the matching signed product and content authorizations in the processor. Store and My Products present the customer journey, but a catalog entry or visible download button is not audio-unlock authority.

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

Own products and protected banks

JUCE ownership

Independent grants, required instruments and software compatibility.

Protected-content integration

Private publication and three host connections.