HISE Commercial Licence
-
Hi everyone, I've wrote an email to @Christoph-Hart to know more about commercial licence, but I haven't recived any response.
How much does a commercial license cost?Best,
F. -
Sorry, overlooked that mail. I've responded to your PM.
-
@Christoph-Hart +1 to know the price ;-)
-
@pelle I don't understand it. Why do we call it a commercial license? After all, even GPl3 can be commercially applied - or not? Isn't it more accurate to call it a license for closed code?
-
@Robert-Puza it's a commercial licence because you are paying for it. If you use any licence other than the GPL (even another open source licence) then you need a commercial licence.
Libre Wave - Freedom respecting instruments and effects
My Patreon - HISE tutorials
YouTube Channel - Public HISE tutorials -
For most commercial projects a proprietary license is the most viable option because it permits the confidentiality of the source code. The HISE commercial license is a company-wide license that allows you to release as many proprietary projects as you want as long as your license subscription is active.
That's called dual licensing. You have two options:
- Use GPL3
- Don't use GPL3 because you want a proprietary product. Then you need to acquire a separate license from all copyright holders of the source code that you're using - that would be JUCE and us.
The fact that you can do that does not mean that anybody else can take your GPL3 code, buy a HISE license and sell it because then they would be violating your copyright (you could of course offer a dual licensing for your plugin too if you want people to resell it, but that's not part of the GPL then anymore).
-
@Christoph-Hart The topic of license is very difficult for me to understand. The way I see it is that it would be effective if I had a person in the team who understands it. I'm a sound designer and I don't understand the licensing and marketing topic. So I can't sell musical instruments under GPL3? Or is it unethical? I would never copyright my setup of your software. That is unethical for me. But selling the product under the same license as Hise is not a good idea?
-
@Robert-Puza How can I use my talent to produce a quality instrument without knowledge of the law? I need a team.
-
@Robert-Puza I want to work under GPL3. According to GPL3 free means free in the use of the software, not free in the price. Or not?
-
@Robert-Puza you have copyright automatically when you write something, you don't need to register it.
Yes you can sell anything you make under the GPL.
-
@d-healey Ok. Thank you
-
@Robert-Puza Yeah, if you want to publish your project under the GPL license, just go for it:
- Download HISE & JUCE
- Build your project
- When you publish the project, publish the source code of your project (usually the HISE project folder) & make the samples somewhat accessible so that people can actually use it.
No team of lawyers required.
-
-
I don't understand that. After all, what we create is a Hise setting. Is that automatically subject to copyright? Mi own presset? I don't understand it. After all, if you change the setting by 1 mm, it is no longer my setting. Or not?
-
@Robert-Puza said in HISE Commercial Licence:
After all, what we create is a Hise setting.
Not sure what you mean. When you build an instrument in HISE and compile it you are creating a piece of software based the things you've implemented in your HISE project. The combination of modules, sample maps, scripts, etc. is all your unique work.
You can think of like writing a document in a text editor and exporting it as a PDF.
-
@d-healey Exactly. But if the combination of modules, etc. change it by 0.000001 mm and it's not mine anymore. Or not?
-
This post is deleted! -
@Robert-Puza said in HISE Commercial Licence:
Exactly. But if the combination of modules, etc. change it by 0.000001 mm and it's not mine anymore. Or not?
If you change a line of code then I guess (I'm no lawyer) you can claim a copyright on that change, but it doesn't affect the rest of the code.
-
@d-healey Okay. I don't understand programming at all and I don't know the code language. So forgive me for possibly stupid questions
I always respect copyright. I'm just saying that the copyright on my own preset of existing software (open source) is funny.
-
@Robert-Puza e.g. I will design and implement the reverb control in my instrument. and the user will get the copyright for setting the reverb that I enabled? I designed it so that only a small part of the reverb control is available. so that from the sound designer's point of view the user cannot mess up my settings. And he will get the copyright for setting the algorithm that I compiled because the creator of Hise gave me a tool for it? it's funny
