@dannytaurus SoundSync can currently receive information related to the product’s operation and the customer journey, including:

When the plugin is opened or connects to SoundSync Activation, validation, restoration, and deactivation activity The installed plugin version The product and license associated with the activation A hashed installation/device identifier for managing activations Interactions with SoundSync-provided areas such as activation, account, store, support, and update interfaces Timestamps showing recent validation or connection activity

This can be combined with information already created elsewhere in SoundSync, such as purchases, products owned, downloads, customer accounts, support activity, email engagement, and marketing consent.

That makes practical things possible. For example, a developer could notify customers using an outdated version, help somebody who purchased but never activated, exclude existing owners from a promotion, or create a re-engagement flow based on meaningful customer activity, cart recovery, etc, etc.

SoundSync does not inspect or collect the customer’s audio, MIDI, presets, parameter changes, DAW projects, filenames, or what they are creating. We are interested in product lifecycle events that help with licensing, updates, support, and relevant communication, not the customer’s creative activity.

We also try to keep the principle fairly simple, collect the minimum information needed for the feature, be clear about how it is used, and give developers the controls they need to handle consent and privacy properly.

Some of this varies by integration. For example, the HISE package can report plugin-open and SoundSync interface events, while licensing integrations naturally generate activation and validation events whenever they communicate with SoundSync.

@lijas90 said in Velocity layers overlapping issue:

I still get quite a noticeable jump between the different samples.

What kind of jump? Volume, tone, pitch, stereo field, something else?

Enjoy a free 30-day trial: https://www.knobwebstudio.com/

composition-1789625533424.png

@orange @David-Healey Thank you guys

@duma Try it, only you can do it :)

@dannytaurus This is super helpful thank you! It's pretty much as I understood it but this is a great way of laying it out. We're about to start proper beta testing so once that's wrapped I'll buy a HISE Indie license, already sorted the JUCE 9 EULA etc.
Thanks again!

@duma Did you extract the SDKs in the tools folder?

Hey Gang,

Quick update on SoundSync & the HISE integration I've been working on.

SoundSync is now LIVE!

This means you have two integration paths available from the developer dashboard:

1. HISE Script Package
This is the simpler drop-in version for developers who want the fastest setup inside a regular HISE project.

The include is intentionally simple:

include("SoundSync/Runtime/SoundSyncRuntime.js");

This package handles the branded activation UI, login activation, serial activation, machine validation, deactivation, Store, My Products, and customer product access using HISE Script + WebView.

2. Native C++ HISE Package
This version is for developers who are comfortable building HISE from source. It moves the more sensitive licensing/runtime layer into native C++ and keeps the HISE Script side as small as possible.

The HISE Script side is only a lightweight gate:

include("SoundSync/Scripts/SoundSyncNativeGate.js"); ssSoundSyncNativeGateStart();

The Native package includes the C++ source, HISE source patch/tools, setup instructions, and the same product/developer branding flow as the HISE Script package.

The goal with the C++ version is to make the licensing layer harder to inspect or tamper with than a script-only package, while still keeping the HISE-side integration simple.

Current package features include:

Activation by customer login or serial + email Product-specific machine activation, validation, and deactivation Server-side activation counts and serial status updates Offline grace period and cached local license state Branded activation UI with developer logo, product image, Brand Manager colors, and light/dark logo background handling In-plugin Store with catalog browsing and single product pages My Products panel with current product serial, activation info, copy serial, deactivate this machine, and owned-product access Branded storefront/account link handoff with SoundSync fallback links Test Connection flow for checking package/API setup Product-scoped generated config for each developer/product HISE Script package and Native C++ source-build package options

Both versions are generated from the SoundSync developer dashboard and are product-scoped, so developers can export a package with their own product info, branding, activation settings, storefront links, customer product access, and machine/license behavior already configured. They both include simple instructions for integration as well.

The HISE Script version is the fastest route for most developers.
The Native C++ version is the better option if you are already maintaining a custom HISE source build and want a stronger licensing boundary.

SoundSync for HISE is live now, and both package options are available from the developer product dashboard.

If you are building commercial HISE instruments or effects, you can now generate a product-scoped HISE package with activation, validation, Store, My Products, branding, and customer access already wired in.

JUCE packages are also offered for direct JUCE connection.

Feedback from the HISE community is always welcome as we keep improving the developer & customer experience.

Learn More About Soundsync

Best,

Aaron

@David-Healey Great info. Thanks!

@Christoph-Hart Great, thanks.

Where do I get a copy of the current licence? I was never sent one when I started paying.

@resonant - I think Dave's right there are not any real problems these days getting the plugin into the "system" folders on a Mac (but its been a while since I've done it as Im nearly exclusively on Tracktion these days) so caveat emptor... but every other problem (locations and content) are still there which is what the CR Setup componentry is there to resolve.

@David-Healey It seems to have fixed the panel contextual as well! 👍

@GUJIAN The errors about component missing will always happen on the first compile because the components don't exist at that point. On the second compile the errors should go away.

Also Rhapsodist isn't "fixed" yet, so expect breaking changes. Once I've stabilised it I'll make some documentation.

@Lindon

Sorry yes my typo...

Glad you weren't being charged 5% 😂

@robJ Thank You 🙏

"OK, that's it. Thank you."

@LucaL check what's in that array, I don't know without seeing the rest of your project