Something I have been curious about ever since someone asked me to work on building a custom pluggo for them…
If I were to distribute a pluggo I have made, is there a way to "protect" it so that it cannot be copied freely? Does the authorizing function need to be built into the plugin using max? or is it done with something else?
On Jan 9, 2006, at 9:57 AM, Simone Ghetti wrote:
> If I were to distribute a pluggo I have made, is there a way to
> "protect" it so that it cannot be copied freely? Does the
> authorizing function need to be built into the plugin using max? or
> is it done with something else?
There are a variety of ways you could try to do this.
One idea that comes to mind is that you have a coll object read a
secret file somewhere and see if it contains a special key. If it
does, then it opens a gate~ object for your plug-in to make sound.
They key could be an encoded version of the boot drive or MAC address
or something. This will certainly be hackable, but it will probably
serve its purpose for the average person who just needs to be
reminded gently that your plug-in isn’t free.
Thanks for the responses… I think I have some idea of how this might work now…
C74 RSS Feed | © Copyright Cycling '74