@bendurso said in Creating an Offline Authentication Method?:

@Lindon said in Creating an Offline Authentication Method?:

Thank you! I’m working on implementing something similar based on this post.

Do I first need to create a set number of licenses (e.g., 4000) and then encrypt them all? Or is there a way to create a pattern that meets specific criteria, as you mentioned, without creating each string?

How do I encrypt all the strings? I assume it's with encryptWithRSA, but how should be done?

Well when I use this method I wrote a HISE application that:

allows me to enter a public and a private key and a project name allows me to define my characters and positions generates a user entered number of strings that comply with 2 above encodes these strings using the private key, tests they all decode correctly Writes the encoded strings to a text file Records the project data into a recallable json file....

I suggest you do the same....

@Lindon Ok. 🤭

@ccbl

That's correct

@griffinboy Ok

@Christoph-Hart Okay. I understand. monolith is my friend.

@Sampletekk In Inno Setup, the commoncf64 directory constant is used for 64-bit Common Files folder. So the below is the example for VST3 & AAX folder installation with Inno Setup.

Source: FolderPath\YOUR_PLUGIN.vst3; DestDir: "{commoncf64}\VST3\"; Components: VST364; Flags: ignoreversion Source: FolderPath\YOUR_PLUGIN.aaxplugin\*.*; DestDir: {commoncf64}\Avid\Audio\Plug-Ins\YOUR_PLUGIN.aaxplugin\; Components: aax_64; Flags: ignoreversion recursesubdirs createallsubdirs

@DanH Thank you so much! I owe you a beer or a coffee! 😊 ;)

@d-healey ah ok strange.

Thankyou for your help as I now have it working properly and selecting the correct samplemaps.

I've also got the expansion load working in daw as well so I can progress with my project which is great news.

Thanks again, your help is always invaluable

bumpity bump

@xander You need to export (compile) separately on each OS you want to use.

For AAX you need to sign up for an AVID developer account, and you'll also need a PACE account and iLok for signing your plugins. You'll need to compile the AAX SDK on each OS before you can use it.

@ustk That was quick! Really nice work 🧙 🧙

@d-healey awesome, thank you

@d-healey thank you

@d-healey aaaaa... great. thank you.

@d-healey ok. Thank you

@Gab Unfortunately I don't think it has anything to do with IPP, as it lags with both IPP on and off.

@d-healey Yeah, I looked carefully and it is indeed.😹

@Lindon said in I don't really understand this pairing system for HISE MIDI note on and note off messages:

@VirtualVirgin print the Event ID and see if they match...

So here it is with the Event ID:

Screenshot 2024-11-09 at 11.30.56 AM.png

As you can see, the hung note (the last 60 on the list) is not closing the note on 60 that just preceded it.

So I would assume that HISE is trying to match the event ID of the note off to a note on before making it "available" or "active".

I just don't understand this method or the point of it.

Why is it trying to close notes that are already closed?
In the type of MIDI engineering I am used to, if a note off occurs after a note on of the same channel and note number, it closes that note, end of story. No other special conditions needed.

Is there some way to turn this Event ID matching system off for the note messages?
I would like that last note off 60 to close the previous note on, no matter the Event ID.

I know this may muddy the waters a bit...but ive actually never code signed my VST3/AU...only my AAX because its required...Ive only ever codesigned the .PKG when I was using those and the Standalone app(via apple's signing/ notarizing in Xcode) now I have a custom installer that I built and I only have to codesign/Notirize it via Xcode(not via the terminal) and I dont worry about the cosigning any of the individual binaries...and all my plugins run just fine for my users...