Registering plugin ,GUI , Demo questions.

[Lindon]

@lalalandsynth said in Registering plugin ,GUI , Demo questions.:

@ustk Yep, that makes sense . I guess I am looking for a way to not have to do anything specific on the gui itself to be able to register.
And this might be the method "If the user choses the demo mode, you can also keep the panel to show up at each launch, this way you don't need a button in a setting section…"

So the authorisation system I use works like this:

1. Checks for an authorisation file at init.
2. Where there is no (or error) authorisation - mutes the plug-in and pops a panel
3. Offers the ability to authorise the plug-in (create an auth file with your supplied code) or run in demo mode, also shows the number of demo mode instantiations are still available (a max of 10)
4. When demo mode runs: reduces the number of demo executions by 1, starts a timer and times out the plug-in after 15 mins
5. On time out - Silences the plug-in and pops the auth panel again
6. When there are no more demo instantiations left it just pops the auth panel with no other option but to authorize.

It uses a "plain" panel and a set of labels + two button graphics (Authorise and Run Demo). So very little UI work to do.

[d.healey]

@ustk said in Registering plugin ,GUI , Demo questions.:

@d-healey Ouch... That seems to require some long nights...

I'm getting there.

HISE remote control in a browser with audio is now possible. Just have to put it all together!

[lalalandsynth]

That is very cool stuff !

[ustk]

@d-healey I don't understand why, but it's cool

[d.healey]

@ustk I'll tell you why :) It means you can control HISE running on my computer through your web browser. Once I put it all together this will be a perfect way for users to demo the full version of a library.

[ustk]

@d-healey You mean using Hise through a browser? It seems amazing!

[d.healey]

@ustk Yeah, except instead of HISE it will be the standalone version of my plugin. It's not running in the browser, it's running on my computer but you can see it and control it as if it's in the browser. It's very similar to VNC except it's just a single window instead of the whole desktop. The tool I'm using is called Xpra, but it doesn't support MIDI, so I'm making a custom client to handle the MIDI stuff.

[ustk]

@d-healey Oh I see! you'll quickly need a dedicated server

[d.healey]

@ustk I have one :)

[ustk]

@d-healey Amazing Dave

[lalalandsynth]

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 ?

[Lindon]

@lalalandsynth replaceGHlobal Mute with a Gain FX set to -100 dB

[lalalandsynth]

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.

[ustk]

@lalalandsynth The question is: If they hate it, will they be more prone to purchase compared to a date limit version?

[lalalandsynth]

@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 ?

[adriano]

@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.

[lalalandsynth]

@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 ?

[adriano]

deactivating it does not seem possible to me but resetting the plugin to zero each time it is done in 10 seconds ....

[Lindon]

@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.

[yall]

@Lindon of course you are right. the ideal would be that the "registration" file is stored on a server that would be even crazier :)