silly me...old version.
Meanwhile...the new version looks very nice well done Christoph
Ok, the ever thorny question. Les start out with this:
Now the first contentious statement;
Even if an authentication/authorisation system is breakable it ISNT therefore pointless to add one in.
Here's my experience. I've released Kontakt instruments for a long time, if they have no authorisation system in them then someone buys the instrument - and immediately uploads it on to a warez site. For a moderately advertised and marketed product this usually happens in about 10 days of launch and the number of sales for the product "fall off a cliff". however...
If the product has even a simplistic authentication system included(that is trivial to break for any "competent" pirate) then this "10 days to warez" doesnt happen, what you get instead is more like "100 days to warez", so it takes the intervention of a "proper" warez pirate to do some "simple" cracking, and those guys have a queue of stuff they are stealing and any (small developer, lower profile) product wont be on top of the list. When the product shows up on the warez site after 100 days then again sales suffer. But here's the point - MOST products get MOST sales in the first 3 months (90 days) so getting pirated is still bad, but not as bad.
So why all this explanation? Well Kontakt has no mechanism for storing keys/email addresses/whatever IN the saved instrument - you have to save them in an easily readable/hackable external file(well there is a way but its clunky..and not so reliable).
So what would be nice in HISE is a simple API call to hold some value INTERNALLY to the compiled VSTi/app etc. and then leave all that validation fluff to the developer.
Ok so I've cleaned a big portion of my main dev machine for HISE, so I will install VS, but - as we know from my last install, the version of VS used by the build is no longer available, so you mentioned you'd try and get it ported across the VS 2017(?). I see the new UI looks close to complete(and let me add my congratulations on that whilst I'm here..) so do you have an ETA for a "more current" and available VS dependency?
Looks like your connection to Lindon was lost, please wait while we try to reconnect.