@gryphonsegg said in HISE VST commercial license:
@d-healey hmm i wonder if the closed source license is very expensive
If I recall correctly each license is around SUPER_SECRET_NUMBER a month.
@gryphonsegg said in HISE VST commercial license:
@d-healey hmm i wonder if the closed source license is very expensive
If I recall correctly each license is around SUPER_SECRET_NUMBER a month.
@d-healey said in GPL compliant releases:
Ah I just found the confirmation
Can I put the binaries on my Internet server and put the source on a different Internet site?
Yes. Section 6(d) allows this. However, you must provide clear instructions people can follow to obtain the source, and you must take care to make sure that the source remains available for as long as you distribute the object code.
Thank You @d-healey you've been a great help !
@d-healey said in GPL compliant releases:
Once you release you project as GPL you can't undo it. You can release future versions under a proprietary license, but the GPL version will always be GPL.
To make it compliant you need to provide the HISE project folder (everything that's needed to build the binary) to anyone you have supplied the binary to, or you must do so if they request it.
The samples can be under a different license.
@d-healey understood about GPL releases and them remaining as such.
Ok so that I understand the next part correctly, If I'm selling plugins I need to make available the HISE project folder for each product in the customer download area ? This makes me compliant ?
Sorry I'm quite new to this...
Hello everyone,
I just sent email regarding commercial license, but need direction on what I have to do to be GPL compliant with my releases until I can obtain the commercial license.
Can anyone spare the time to steer me towards that goal please ?
Thank you very much.