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

@David-Healey said in Opening plugin UI disables active automation in Ableton Live:

@Lindon Christoph said in another thread that he's currently busy with a theatre project but will get to the PRs soon.

https://forum.hise.audio/topic/15026/au-component-version-is-always-0-in-exported-plugins-xcode-exporter-misses-versionashex/8?_=1788803845075

yes I know I read it- Im just tagging this one as one I think needs to be included - of course Christoph is entitled to tell me to F'k right off with my view of what is important or not :-)

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.

@ustk Yeah, good idea. I asked Claude if the version reports as an invalid number, or just as 0.0.0.

The AU plist has AudioComponents.version = 0. Pluginval decoded that as v0.0.0. JUCE’s decoder explicitly formats the packed integer 0 as 0.0.0.

0.0.0 is valid as a semantic version, but AU metadata uses a packed UInt32, not a SemVer string.

In practice, hosts treat raw value 0 as “version unset.” Logic therefore labels it invalid, while pluginval merely displays the decoded value.

For 0.0.30, the AU field should contain integer 30. The bundle’s separate CFBundleVersion can remain the string 0.0.30.

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

@dannytaurus said in No-argument sort() is a no-op on strings - bug?:

So you think the docs are wrong, rather than it being a bug?

Could be either

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

@Lindon so as a work around you can create a Faust based FX and drop it into a Hardcoded Fx slot, heres the faust code for a simple FM FX (as provided by Gemini):

import("stdfaust.lib"); // Modulator Controls modFreq = hslider("Mod Frequency [unit:Hz]", 100, 10, 2000, 0.1); modOctave = hslider("Mod Octave Offset", 0, -3, 3, 1); modDepth = hslider("Mod Depth", 0.2, 0, 1, 0.001); // Calculate the effective modulator frequency using the octave offset effFreq = modFreq * ba.semi2ratio(modOctave * 12); // Modulator oscillator (sine wave oscillating between -1 and 1) modulator = os.osc(effFreq); // Convert depth to a delay modulation amplitude (in samples) // A small maximum delay (e.g., 2ms) keeps the FM effect tight and clean maxDelayMs = 2; maxDelaySamples = ma.SR * (maxDelayMs / 1000); delayMod = (modulator * modDepth + 1) * (maxDelaySamples / 2); // Apply Phase/Frequency Modulation using a fractional delay line fmEffect(x) = de.fdelay(maxDelaySamples, delayMod, x); // Process stereo or mono input process = _,_ : fmEffect, fmEffect;

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

@David-Healey Oh, you mean like this? 😂

CleanShot 2026-08-29 at 13.12.10@2x.png

Claude says:

It's painting the warning in the wrong tab, and it's a false positive from conservative metadata.

The metadata classifies every sendRepaintMessage variant as unsafe wholesale; a finer classification ("warning: fine to call, just don't do it per-sample") would be more accurate.

The two points are: (1) ApiDiagnostic needs the callback id so the editor can place the marker in the right tab, and (2) sendRepaintMessage's callScope should probably be "warning" rather than "unsafe".

Glad I don't use the HISE script editor anymore. That would confuse the hell out of me! 😜

Update:

All 20 discount codes have been claimed. I've been recieving great feedback on the app so far. I want to keep the good vibes going!

I've opened up 10 more promo code slots! Get it while its hot! Don't forget to join the discord. 🙏

Add this to your cart:

https://roxdesignersuite.com/products/rox-designer-suite

Enter promo code: "LAFOUTLOUD" at checkout.

ENJOY!

If you've already grabbed a copy for yourself are enjoying it, share this code with a friend that might need it! 🙏 ⚡
Have a great day!

Rox

Join The Discord:
https://discord.gg/GV2vHAdX9

@dannytaurus agreed about Claude, has become unusable in my opinion, deep dives and minutes of ruminations for simple questions, eats tokens like crazy.

I use cursor for everything now.