Registering plugin ,GUI , Demo questions.
-
@d-healey Oh I see! you'll quickly need a dedicated server
-
@ustk I have one :)
Libre Wave - Freedom respecting instruments and effects
My Patreon - HISE tutorials
YouTube Channel - Public HISE tutorials -
@d-healey Amazing Dave
-
Got the super simple copy protection "SSCP" working :)
Have to figure out the demo mode thingy .
In the SSCP it uses the const var GlobalMute = Synth.getMidiProcessor("GlobalMute") but I am not using midi , is there an equivalent for audio stream ?
-
@lalalandsynth replaceGHlobal Mute with a Gain FX set to -100 dB
-
Been doing an informal survey on a Audio engineer forum.
It seems that most people really HATE intermittent silence and prefer an overall time limit. A few days.
-
@lalalandsynth The question is: If they hate it, will they be more prone to purchase compared to a date limit version?
-
@ustk Indeed , other comments state that not being able to just run the plugin in a complete session is annoying , also with timed trials people said that very often they kind of forget about it and then its run out before they get to test properly.
I am not sure that annoyance is a good way to get purchases , but , good question:)
So maybe a non time limited demo with no silence that you can open/run a certain amount of times ?
-
@lalalandsynth this solution is too easy to hack ... I already do it with poorly protected demo plugins. the only solution for hise that I find good is the shutdown after 10 min for example then when buying the plugin simply provide the unprotected plugin. people who buy don't share their code.
-
@adriano said in Registering plugin ,GUI , Demo questions.:
ugin simply provide the unprotected plugin. people who buy don't shar
Do you mean shutting off the copy protection with a serial or providing another install ?
-
deactivating it does not seem possible to me but resetting the plugin to zero each time it is done in 10 seconds ....
-
@adriano said in Registering plugin ,GUI , Demo questions.:
@lalalandsynth this solution is too easy to hack ... I already do it with poorly protected demo plugins. the only solution for hise that I find good is the shutdown after 10 min for example then when buying the plugin simply provide the unprotected plugin. people who buy don't share their code.
-- but sadly they do share it - they steal a credit card, buy your product and share it...but these are the 10% who we are ignoring(see below)...
OK so my current solution is to offer limited sessions (9 at the moment) and each session will time out after 15 mins. When you start the plug-in it shows you the authorisation page - and the number of demo sessions you have left, the user can authorise or run a demo session. When the demo sessions have run out you can ONLY authorise the plug-in to run it.
Just a quick reminder here that we are NOT trying to come up with an authorisation & authentication session that will defeat serious hackers - just one to deter the casual clown, and thus remove 90% of the problems.
-
@Lindon of course you are right. the ideal would be that the "registration" file is stored on a server that would be even crazier :)
-
Xfer Serum has a 15 limit , Arturia has 20 min.
:)Having said that there is now a heated discussion about 15-20 min limitations on that engineer forum.
Basically I am defending it and everyone seems to hate it , thing is , I am not convinced that even though people say they hate it ...that it has an influence on their buying behaviour.not sure why though
-
@lalalandsynth it annoys them so they buy
