How to get CPU serial number using HISE?
-
Is there a way to get the CPU serial number using HISE?
-
-
@Christoph-Hart is it possible to have access to more parameters on the system ID generation?
I'm getting system ID changes when people perform OS updates, but there seems to be ways to only use the CPU/Motherboard to generate the ID instead◆ getUniqueDeviceID() static String SystemStats::getUniqueDeviceID ( ) static This method returns a machine unique ID unaffected by storage or peripheral changes. This ID will be invalidated by changes to the motherboard and CPU on non-mobile platforms, or performing a system restore on an Android device. There are some extra caveats on iOS: The returned ID is unique to the vendor part of your 'Bundle Identifier' and is stable for all associated apps. The key is invalidated once all associated apps are uninstalled. This function can return an empty string under certain conditions, for example, If the device has not been unlocked since a restart.
-
@Christoph-Hart Will the system ID change after reinstalling the system using this method? Is there a way to bind it to the hardware ID? In this way, even if the system is reinstalled, the system ID obtained will be the same
-
@Dan-Korneff @CatABC set
JUCE_USE_BETTER_MACHINE_IDS=1
so it is more OS update resilient -
What @ustk said, the default machine ID generation is a bit less robust and will change with major OS updates, but with this preprocessor it will be a little bit more stable.
Your copy protection system must cope with the scenario that computer IDs can change though.
-
@Christoph-Hart said in How to get CPU serial number using HISE?:
Your copy protection system must cope with the scenario that computer IDs can change though.
My protection system and I are in therapy. Hopefully we can cope soon.
-
@ustk
Do I have to use this when I compile HISE, or do I use it when I compile the plug-in?Thank you
Oli -
@Oli-Ullmann Both, otherwise the ID created will not be the same during test and production.
Once you use this flag it's forever for compatibility reasons
It should be set totrue
by default imho, but I think it's for breaking old project compatibility that it'sfalse
... @Christoph-Hart ? -
@ustk
All right, that makes sense. Thanks for the info! :-)