hello, i wanted to know if its possible to create a MBC UI without a lot of code, so with built in features mostly

@d-healey it works thank you, i made a denoiser using DSP network, i recompiled hise to create expanders nodes, and split them and added them and now i've got a cool denoiser plugin

@David-Healey Perfect, i'll search everything

thanks for helping me

@David-Healey

Yes, exactly!

I mainly wanted to confirm that this kind of approach is feasible in practice. What I’m really looking for at this stage are a few high-level hints. For example, common ways to generate a reasonably stable hardware ID and whether it’s possible for the plugin to automatically create a local authorization file after validation, like an auto sign-in.

I just need these small details before starting so I can get a clear idea of the overall architecture. Any advice or best practices would be very welcome.

@David-Healey I think there’s a misunderstanding here.

The authorization tool would not be distributed to end users.

The user would only provide their HWID, and I would generate the corresponding signed authorization key on my side and send it back to them. The plugin would then only perform local validation using the embedded public key.

These plugins are not publicly released products. They’re sold to a relatively small number of clients, which makes the likelihood of targeted cracking quite low. However, without any form of verification, the likelihood of the files simply being shared between users would be relatively high.

The goal isn’t to stop cracking in general, but to discourage casual sharing of the plugin between friends

@David-Healey The authorization tool would run locally.

The goal is to keep the whole system offline, without requiring a server-side check

We’re planning to use Ed25519 for signing, similar to what we’ve used in previous projects

We haven’t fully decided on using Ed25519 yet. Any advice or recommendations would be appreciated

@David-Healey The HWID would be generated locally, and an external tool would be used to generate the corresponding authorization token, which the plugin validates at runtime.

@David-Healey I do understand what you mean, I know that it doesn't cover every vulnerabilities and it can get cracked at any moment.

The goal of this security system is to discourage file sharing, not to provide unbreakable protection. I mean, I know its never gonna be between the hands of team R2R or some pentest pro, it is not meant to be available for purchase online that's why I want to make a security using the HWID.

Hello,

I'm currently developing plugins for my customers and I need to implement a basic licensing / verification system to prevent my plugins getting leaked.

My idea is to build a local (offline) protection system based on a Hardware ID (HWID) generated from the user's machine.

The HWID would then be cryptographically signed (or validated) and stored in a local file, allowing the plugin to auto-authorize itself on startup without requiring an online check.

I'm not asking for a full implementation, just some guidance on:
How to generate a HWID

Thanks in advance.

Hello, i'm making an eq and on the top i want to put a preset saving. And I was wondering, am I obliged to put a FloatingTilePanel with the Preset Browser, or I can do it without it

@Chazrox Thank you so much lol

Hello, im facing some convertion problems while trying to convert some dB from my band in parametriq EQ. Sometimes it works sometimes it glitches.

here's the chunk of the code:
var gainValue = Math.round(band.gain * 100) / 100;

    var band = bandValues[obj.index];
    var freqText = Math.round(band.freq) + " Hz";
    var gainValue = Math.round(band.gain * 100) / 100; 
    var gainText = (gainValue >= 0 ? "+" : "") + gainValue + " dB";
    var qValue = Math.round(band.q * 10) / 10; 
    var qText = "Q " + qValue;
    var typeText = typeNames[Math.max(0, Math.min(4, Math.round(band.type)))];