Where is the logical source code for HISE to obtain machine code?

[CatABC]

Where is the source code of the logic of HISE to obtain machine code? I hope to use JS to reproduce this logic and add it to an independent client program

[Christoph Hart]

@CatABC what's machine code?

[CatABC]

@Christoph-Hart Maybe my expression is wrong. I use getSystemId() to generate machine code in HISE. I hope to reproduce the getSystemId() logic of HISE in a standalone client.

getSystemId

[d.healey]

@CatABC If you use a text editor that has the ability to search the text of all documents in a folder (and you can also do this on github) you can search the name of the function to find out how it works.

https://github.com/search?q=repo%3Achristophhart%2FHISE getSystemId&type=code

[CatABC]

@d-healey nice cool!

[Christoph Hart]

@CatABC that‘s a specific function within the JUCE framework and takes into account various properties to generate a more or less unique and stable identification id for each computer.

How would you want to run this as a independent client - you cannot deterministly create this ID for another system.

[CatABC]

@Christoph-Hart said in Where is the logical source code for HISE to obtain machine code?:

@CatABC that‘s a specific function within the JUCE framework and takes into account various properties to generate a more or less unique and stable identification id for each computer.

How would you want to run this as a independent client - you cannot deterministly create this ID for another system.

My idea is to replicate this part of HISE in the client. Before this, I successfully replicated RSA decryption using JS. But this still requires the user to provide the systemId. Now I want to put the verification step in the client operation, and use a button to automatically obtain the systemID to activate the plug-in without opening the plug-in in the DAW for operation.

[Christoph Hart]

@CatABC ah ok then just copy the c++ function from JUCE and make a simple app in C++ if that‘s what you want - I would advise against that because I personally dislike when every single plugin developer ships his own license manager.

[CatABC]

@Christoph-Hart No, my goal is to simplify the user's operation