HISE VST commercial license
-
@d-healey can you explain the difference to me?
-
If you release your plugin under the GNU GPL license then you must provide the user with your project folder so that they have access to the source code. And you must follow the rules of the GNU GPL - https://www.gnu.org/licenses/gpl-3.0.en.html
If you release a close source/proprietary plugin then you don't have to provide the source code to the end user.
The price you charge (or don't charge) for your plugin does not factor into it.
-
@d-healey hmm i wonder if the closed source license is very expensive
-
@gryphonsegg I don't know, you'd need to discuss it with Christoph. You'll also need a JUCE license for proprietary projects, you can view their pricing here - https://juce.com/get-juce/
-
@d-healey can you possibly give me his email to ask him about the license?
-
@gryphonsegg It's at the link i posted above
-
@d-healey there is no email for him at any of those links. Unless I missed it, which link? I checked them all.
-
-
@Dan-Korneff that link just goes to the hise home page ;)
-
@gryphonsegg you'll have to message @Christoph-Hart or wait for him to comment here
-
@gryphonsegg the email address is : info@hise.audio
Found on the HISE website :) -
@iamlamprey that's a little counter intuitive... but at the bottom of the home page:
-
@Dan-Korneff I wrote to this email but still no answer...
-
@gryphonsegg sorry, slipped through, you should have got a reply now...
-
@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.
-
@Plugworx I've changed your post to hide the number. I don't want to post that publicly for various reasons.
