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.

@David-Healey That was my next step using the MIDI Monitor in Cubase to read incoming MIDI data from Dorico. I had started out working directly in HISE and researching the documentation. I will respond with what I see...

@Orvillain said in Why I'm not making a Windows installer (nor code-signing):

Interesting, I wasn't aware of that. More details would be lovely! Private message if you need to :-)

https://forum.hise.audio/topic/14949/why-i-m-not-making-a-windows-installer-nor-code-signing/13?_=1785506496174

@David-Healey nope, I'll need to work on the details with Tobias when I'm back from vacation.

@lijas90 your installer needs to create/write to the Link file in the %APPDATA% folder with the path to your samples. so on Windows this is LinkWindows, on MacOS its LinkOSX.

As an aside putting samples in the %APPDATA% folder system, as you are doing, is generally a bad idea, esp. for Windows users who often have small C; drives (where the %APPDATA folder resides) as thus there is not enough room for the sample set. Better to ask the end user where they want to keep their samples during the install.

@lalalandsynth its all brand new to me. Just passing along the info. Im sure there's a fix.

@griffinboy Thanks for this. Put a link to part 1 at the top.

@Chazrox yea similar to cosmos but cross platform at least win and linux it have a nice pixeldrain feature for sharing uploading user generated samples etc

@lalalandsynth I use a font unless I need to manipulate in some way that is easier outside of HISE. For example my company logo I use a vector.

@ustk Sweet , thanks !

@musicayciencia globals are used when you need to share data between script processors - although David correctly suggests that this should be the last tool you pick for that as there are way better ways for cross-module communication by now. The callback of a single script processor share all the variables declared in the onInit callback.

Now about the non-deterministic issue: if you compile that script it won't cause an error, as the JS compiler cannot know whether the variable setGlobalVariable is a function that can be called - it might get assigned to something callable at some point so it stays put and doesn't complain. However when you play a note, then it's time to call this variable and that's where HISE realises that you can't execute the (empty) variable.

var callableAtSecondTime = undefined; function onNoteOn() { callableAtSecondTime(); } function onNoteOff() { callableAtSecondTime = function() { Console.print("Now I work"); }; }

This script will throw an error when you press the first note, but the first note off will then assign a function to the variable so subsequent notes will not raise the error but call the function. That example looks weird, but it's one of the more powerful features of JS (and HiseScript) to be able to reassign function slots to different functions like this so you can implement dynamic logic more easily.

@39oririn

go to :

https://github.com/christophhart/hise-cli

and follow the instructions there...

@dannytaurus thank you so much my friend! 😁🙏🏻

so cool my friend!

@griffinboy @lalalandsynth @Chazrox @ulrik @Oli-Ullmann @scottmire thanks everyone! 🤙🏼 😎

@David-Healey Yours always seems to be more generally useful than mine though 😂

This one is pretty niche but I'll likely be using single column preset browsers in most of my plugins, so it's really useful for me.

@digi @lalalandsynth lol I included the 'Control Token' feature so you can mess around with it and see if its something we should keep. See at the bottom of every 'ARC' layer there is a 'Token Control' toggle. Toggle that one and you can choose between controlling the arc with either a 'GlobalCable' or by connecting it to the components native 'Mod' values. In theory it should work, but I suck at wiring up the mod matrix so I could use some help testing this out. I would not use the GlobalCable mode just yet. I think I have to nail down some of the Hise code gen for this part. Try the 'Native' mode and hook up the knob to a mod source in HISE. I got it to "WORK" as much as seeing the mod source value move the arc knob properly but I still dont know how this will do in actual use case. Lmk what you guys think about that one. 🙏

@ustk Can you please give it a go if you have a minute? I know you're pretty well versed in using modValues.

(at the bottom of each ARC layer properties)
Screenshot 2026-07-27 at 4.40.12 PM.png

@blush It's listed under the PathTypes section here: https://docs.hise.dev/ui-components/floating-tiles/plugin/draggablefilterpanel.html

https://docs.hise.dev/images/custom/filterpathtypes.png