Can I make License file for Flowstone VST like Sylenth

[djcrazyvdj]

I would like to know is it possible in Flowstone to create my own License file to register Flowstone VST ?? I would like to make my own License file (like Sylenth or Reveal Sound Spire) to register my own exported VST. When the end user will put the license it will become a full featured VST, otherwise it will make White noise(Flowstone Default Demo VST).



Cheers!!
Craizon

[Spogg]

Interesting question!

My quick and dirty solution would be to make an export from a schematic with the intermittent noise generator in place (a full export not a demo) and the noise generator part could then be disabled by entering a pre-determined string. This would mean you'd have to modify the source schematic for every plugin you sold so as to keep them all unique.
In addition your exported plugin would need to read the license code after loading so you didn't have to enter it every time you run it. It would probably be easier to make it so the licence code file was in the same location as the VST. In this case you could just copy and paste the unlock file to be with the plugin and not have to type in the unlock code.

Maybe a Ruby expert could come up with a better solution that could parse an input string to check if it has the appropriate credentials, like only certain characters are looked at and the others are random etc.

This question also makes me wonder if FS can read and write to the registry, which I believe it cannot.

I'll be interested to see what others come up with for this question...

Cheers

Spogg

[rdgaudio]

Interesting....

[DaveyBoy]

Found this in my archive:

key file.fsm

(1.03 KiB) Downloaded 1811 times

I don't know who the original author is but it looks promising!

[djcrazyvdj]

Thank you DaveyBoy.. I will try and will be back with the result.

[tulamide]

Yes you can, using Ruby. You have to read more on the subject, it isn't easy.
https://en.wikipedia.org/wiki/Public-key_cryptography

[djcrazyvdj]

Hello DaveyBoy, I am working with your KeyFile.fsm this is perfect for one particular product. But the real problem comes if I use it for more products. Lets say I have three products, If an end user gets one product they will activate the other products very easily. How can I fix this issue?

[DaveyBoy]

Hi djcrazyvdj

It's not my schematic, I don't know who created it. It came from the old Synthmaker forum Archive, (I think Spogg posted a link to it on here).

Maybe one of the more experienced and knowledgeable guys on here could help you with this

[djcrazyvdj]

Okay, I hope so.
Thankyou DaveyBoy for the KeyFile. The old Synthmaker forum Archive is no more.Thanks for sharing it here. The given keyfile has snatched my night's sleep.

[rdgaudio]

Yes you can generate license for more than one products. If you have three different products you can use "m", "u" and "p"
In the 'Generate Keyfile' you will find a code like this----

Code: Select all

output [@str].pack('m')

Change it to.....

Code: Select all

output [@str].pack('u')

or

Code: Select all

output [@str].pack('p')

Make sure to change the 'get from file (match = 1)' >decode ruby code. Otherwise the code will not work.

Code: Select all

output @str.unpack('m')[0]

change it to...

Code: Select all

output @str.unpack('u')[0]

or

Code: Select all

output @str.unpack('p')[0]

I hope this will help you DJ Crazy.
Thanks DaveyBoy for sharing the Old Synthmaker's forum file. Synthmaker forum is no more (I think,because every time Synthmaker forum is redirected to the FS Home page)..If any old but gold files are shared anyway it will be very beneficial for our new members.
Cheers!!
Rudra Ghosh