@soundsync I'm on Gumroad at the moment but looking to switch to a better platform very soon.

Just for reference, here's your list noted for my current Gumroad setup:

a product page ✅ Gumroad checkout ✅ Gumroad customer accounts ✅ Gumroad, via Library download access ✅ Gumroad refunds and revoked access ✅ Gumroad update delivery ✅ Gumroad support emails ✅ Gumroad, if the customer emails them first “I bought this but lost the download link” ✅ Gumroad's Resend Receipt action “Where do I log in?” ✅ Gumroad Library license delivery I don't do licences currently license resets I don't do licences currently device limits I don't do licences currently “I got a new computer, can you reset my activation?” I don't do licences currently “My license is not showing up” I don't do licences currently

I'm not saying Gumroad is perfect, but if you don't do licences for plugins, then it's a very easy place to get started. Testing the waters to find out if you can find/reach an audience is easy on Gumroad.

Gumroad's real fee runs to about 16% of my revenue, which is higher than pretty much anywhere else I've looked at. But that does include unlimited email marketing, which most other platforms don't.

I'm in the process of doing comparisons with my last 12 months real revenue data between Gumroad, Moonbase, Soundsync, Fungies, Polar and direct Stripe MoR payments.

@ILIAM said in .pkgproj sharing:

Hey
Anyone has a VST vst3 au working .pkgproj for , i want to study an dmake my own builders!
thansk for sharing

I think this repository have one: https://github.com/publicsamples/Oi-Grandad
Another example from @David-Healey : https://github.com/davidhealey/sofiawoodwinds/tree/master/Packaging

But I am sure the current workshop grasped it more deeply.

@ILIAM said in .pkgproj sharing:

I have a Question too!
can we point the Pkg builder to user folder where hise outputs the Exported Components?

If file paths within the .pkgproj file are left as absolute paths (e.g., Macintosh HD/Users/username/...), the project will only work on that specific computer. Instead, the "Relative to Project" option within the Packages application should be used.

https://forum.hise.audio/topic/2250/macos-packages-issue/6

@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 Done 👍

ABSOLUTE RULES now has a MINIMAL CODE COMMENTS entry. It says to comment only what is non-obvious, contradictory, or missing from self-documenting code, to keep needed comments to one line, and to point at the forum topic or GitHub issue/PR for more context. Comments & Documentation under Code Style carries the detail with three examples. The FL Studio comment from PR 1040 and the instrument-plugin note beside the confusingly named macro in PR 1039 are listed as good comments. The multi-line host-echo paragraphs from PR 1037 are listed as too much, with the one-line-plus-reference guidance. It also bans comments that restate code, narrate control flow, mark edits, or leave investigation notes behind.

It looks a lot like UVI Falcon

@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.

new updates
https://www.knobwebstudio.com/

@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."