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.

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

@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

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

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

@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

I also added a LineSpacing and LetterSpacing to the Markdown renderer so I can style it to match my plugin.

https://github.com/christophhart/HISE/pull/1008

@Christoph-Hart That is just way too convenient ! 😲

@lalalandsynth ahh yup. 👍

Update: Claude-generated gist here of the suggested patch: https://gist.github.com/weavermedia/3fc4a419920fcda8de389a89d7aec68d

You're trying to build the Faust build without having installed Faust. Select another Scheme to build that doesn't include Faust (or use the hise-cli for setting this all up).

@ustk Just the ever-tightening security of OS vendors. Privacy is a selling point now, as is anti-machine-fingerprinting.

A user account authentication system, via the browser, feels much more lightweight, predictable and more transparent to the user.

Now that I've reverted to using the hr1 system I ran into this issue again.

I have a library that is going to be about 20GB compressed and when I send out an update to my users that changes only the data (hxi) I don't want them to have to redownload the entire 20GB all over again.

So I worked with Claude to implement a split archive solution.

The default behaviour is the current behaviour, bundle everything together into one set of hr files - works for expansions and regular plugins as before. I did change the default split size to 2GB as that seems to me to make sense.

Then there are two new options:

Split Data From Samples: This will put the data into its own .hr1 file with the suffix _data. The samples will then be bundled into .hr2, .hr3, etc. as needed. If the user only needs the data (because they installed the samples previously) then they just download and extract the .hr1. As it extracts it will still check for the next archive as before but will fail silently if its not there. However if one of the other archives is missing it will report an error as expected - I also improved the error message so instead of just saying Read Error, it tells the user which archive is missing. Data Only Update: This just compresses the data into an .hr1 archive and assumes the samples haven't changed and have already been compressed using the split option.

With the mod matrix system each connection can have a intensity and you should also be able to set it programmatically without the matrix floating tile using the API.

For targets that dont expose a mod chain you can just define a UI knob and give it a matrixTargetId. You‘ll loose the precision of the real mods but if it‘s acceptable then fine.

The modwheel could also be a global source modulator using a control modulator.