Page 2 of 2

Re: Can I make License file for Flowstone VST like Sylenth

PostPosted: Tue Apr 11, 2017 10:18 pm
by DaveyBoy

Re: Can I make License file for Flowstone VST like Sylenth

PostPosted: Wed Apr 12, 2017 6:47 pm
by djcrazyvdj
Thank you RDGAudio for the code. :)

Re: Can I make License file for Flowstone VST like Sylenth

PostPosted: Fri Apr 14, 2017 6:16 am
by djcrazyvdj
Making a keyfile is possible by this way but my problem is every time I have to register with the keyfile. When I exit from the app/vst everything becomes demo.Asks for keyfile every time. So, in Flowstone is there any process to register key into windows memory/registry? Or make it permanent? Otherwise keyfile will be a nightmare for end user . :roll:
by,
DJ Crazy

Re: Can I make License file for Flowstone VST like Sylenth

PostPosted: Fri Apr 14, 2017 7:38 am
by nix
If you have a keyfile as a file,
ask your user to put it in the same place for different user's systems.
Like on C:
When the program runs, use 'on load' to look up the keyfile and see if it's right.

How does that sound people?

Re: Can I make License file for Flowstone VST like Sylenth

PostPosted: Fri Apr 14, 2017 7:44 am
by RJHollins
I put them in the same folder as the app or plug. There is a PRIM that can look there specifically. Load the text file when app/plug is launched.

As for the Registry ... I seem to remember an experimental PRIM or routine in one of the 'toolbox' collections back in the SM days.

Re: Can I make License file for Flowstone VST like Sylenth

PostPosted: Fri Apr 14, 2017 3:14 pm
by djcrazyvdj
Nope guys, the keyfile location same as program location not working. How to use On Load?

Re: Can I make License file for Flowstone VST like Sylenth

PostPosted: Fri Apr 14, 2017 9:49 pm
by nix
I imagine you need to trigger, then automate your registry procedure-
using the trigger that comes out of 'on load' or 'after load' whatever it's called.
So to start with, use the on load trigger for the registration dialogue.
It should pop the dialog automatically, then you will need to automate rest of the steps to enter the code

The 'plugin folder' is just perfect, will need to remember this prim