Registering plugin ,GUI , Demo questions.
-
I have yet to have a look at the whole registering of a plugin but for now I am thinking if I have to make any specific UI provisions for registration purposes , like a registration popup? I am putting in a lot of work on designing GUIs these days and would rather not have to add anything as an afterthought.
How do you usually deal with this both in terms of registration overall and implementing that in the gui ?
Also , how do you normally implement Demo mode ?Here are my initial thoughts.
- A user could push a switch on the GUI , and a registration popup window opens ?
- Enter key on install , which means different install for Demo and registered, not great ?
- Completely separate registration window opens when plugin first opened in DAW, with possibility of Demo mode ?
Any insight on this whole process ?
-
This post is deleted! -
For the demo you could provide the same plugin but if it's unregistered it goes silent after a certain amount of time.
-
@d-healey for your plugins ,do you provide a demos and is there a register button or how do you approach registration ?
-
@lalalandsynth My approach would be a popup that automatically shows up when opening the plugin the first time.
In this popup, two options: demo and register
Once the choice is made, close and remember in an external json
In your general setting panel (if you have one) put a "Register" button to popup the demo/registration panel again, so the user can register later.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…
-
@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…" -
for your plugins ,do you provide a demos and is there a register button or how do you approach registration ?
I do not. At the moment I'm working on a system to allow users to demo my libraries over the internet through a dedicated app.
But I offer refunds and resales anyway so there is less risk for the user to "try" one of my libraries. I've had very few refund requests.
-
@d-healey This sounds interesting! Is it an app you're developing or an existing system?
-
@ustk I'm developing the app but it incorporates several existing systems for transmitting audio, gui, and MIDI. I've got the MIDI part working, I just need to get the GUI and audio stuff working. It will also require some server side work but I'll tackle that after.
-
@d-healey Ouch... That seems to require some long nights...
Can't help pressing F5 in the forum...
-
@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:
- Checks for an authorisation file at init.
- Where there is no (or error) authorisation - mutes the plug-in and pops a panel
- 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)
- When demo mode runs: reduces the number of demo executions by 1, starts a timer and times out the plug-in after 15 mins
- On time out - Silences the plug-in and pops the auth panel again
- 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.
-
@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!
-
That is very cool stuff !
-
@d-healey I don't understand why, but it's cool
-
@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.
-
@d-healey You mean using Hise through a browser? It seems amazing!
-
@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.
-
@d-healey Oh I see! you'll quickly need a dedicated server
-
@ustk I have one :)
-
@d-healey Amazing Dave
