Soundsync: HISE Ecosystem | UPDATE: WE ARE LIVE!

[soundsync]

@Sifres Thanks for the words!

Yes, for sure, the competition is building. I love it! The motivation is real.

MoR is on the list as well as a couple more big updates that will be implemented in the coming weeks.

Im open to adding anything that developers will find useful! Just let me know and I'll get it taken care of.

Thanks again.

Aaron

[David Healey]

@soundsync said in Soundsync Beta: HISE Ecosystem | UPDATE: Serial Validation + Storefront Package and Security.:

Simply enter your project UI size and generate the package.

You might be able to remove this step if you can make use of Content.getInterfaceSize() in your package.

[soundsync]

@David-Healey How did this get missed? Updating it now!

[dannytaurus]

@soundsync It should also support dynamic sizes. Some plugins have keyboards you can show/hide, which change the plugin height.

[David Healey]

@soundsync said in Soundsync Beta: HISE Ecosystem | UPDATE: Serial Validation + Storefront Package and Security.:

How did this get missed?

You were using the wrong AI, you need DaveGPT :p

[soundsync]

@David-Healey I have a position open when you're available lol

[dannytaurus]

@David-Healey In a conversation with ChatGPT today, it said to me

Your mockup surprised me—I expected to dislike it. I don't.

AI is getting cheekier!

[soundsync]

@dannytaurus YES! Im adding this now as well. Didnt even cross my mind.

[soundsync]

UPDATE: Auto-Detect + Dynamic GUI Sizing

When you download the HISE package, you will not be required to enter the GUI size anymore as it is auto-detected directly in your project. Thanks @David-Healey

Also, the complete HISE package is dynamic and will change dimension based on changing GUI elements (like an expandable keyboard or effect section). Thanks @dannytaurus

For example: Customer didn't pay for their subscription, grace period ends, they are using plugin now with the keyboard extended. The plugin will pause, popup the activation webview, and the webview overlay will still block the entire plugin, not just the original size.

[soundsync]

UPDATE: Native-Authoritative C++ Licensing Bridge

SoundSync HISE package is rebuilt so the UI stays in WebView/HiseScript, but the licensing authority is now native C++. The WebView only collects user actions and renders safe public state. C++ handles activation, validation, restore, protected storage, device identity, offline grace, deactivation, and the final mayOpenProduct access result. HISE copy protection then reads that native result.

It’s not a pure C++ UI replacement. It’s a hybrid: WebView for branded UX, C++ for licensing authority. That seems to fit HISE better because WebView is still the easiest way to keep product branding, storefront, My Products, and login flows flexible, while C++ owns the trusted licensing path.

@Lindon thanks for the suggestion.

[Edwards]

@soundsync Sounds like a useful workflow for HISE developers, especially having licensing, delivery, and customer management tied together. I’d be interested to see how the activation flow handles offline use in practice.

[soundsync]

@Edwards said in Soundsync Beta: HISE Ecosystem | UPDATE: Native-Authoritative C++ Licensing Bridge:

Sounds like a useful workflow for HISE developers, especially having licensing, delivery, and customer management tied together. I’d be interested to see how the activation flow handles offline use in practice.

Good question! The current flow is online for first activation because the plugin needs to verify the license/serial/customer account against SoundSync and bind that activation to the user’s machine.
After that, the plugin keeps a local activation state so the product can continue opening without calling home every launch. If the server is unavailable, the plugin can enter an offline grace state instead of immediately locking the user out.
The intended behavior is:

• First activation requires internet.
• Normal launches restore from local activation data.
• Periodic validation refreshes the license state when online.
• If offline, the plugin can continue working during the configured grace window.
• If the license is refunded, revoked, deactivated, expired, or outside grace, the plugin returns to the activation screen.
• Developers can choose how strict the grace period should be for their product.

So the goal is not “phone home every time or fail,” but also not “activate once and trust forever.” It sits in the middle: friendly to real users who are offline, but still gives developers control over revocations, device limits, offline grace and subscription/license state.

[dannytaurus]

@soundsync You might consider a challenge/response system for offline activation.

Some users genuinely do have air gapped studio computers.

[soundsync]

@dannytaurus Great idea. I'll add this to the HISE/JUCE package updates.

Thanks!

[soundsync]

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