Newbie questions about HISE...?
-
Just looking at HISE and it seems interesting.
Have a couple of newbie questions:- Is it allowable to create a commercial product with HISE?
- Are there any third party programs that will help me get the best out of HISE and make things easier, - for example, is there a GUI designer with some good stock graphics that could make the interface look attractive?
thanks,,
-
- Is it allowable to create a commercial product with HISE?
Of course! HISE is licensed under the GNU GPL so you are free to use it as you wish. However I think what you are asking is can you create proprietary (closed source) commercial plugins - the answer is also yes, but you will need to arrange a license agreement with the developer of HISE @Christoph-Hart
- Are there any third party programs that will help me get the best out of HISE and make things easier, - for example, is there a GUI designer with some good stock graphics that could make the interface look attractive?
HISE includes a built in interface designer with stock widgets. If you think they're attractive or not is up to you :p If you're handy with graphic design then gimp\inkscape\knobman\blender\etc. Pretty much any graphic design application can be used for some part of creating your interface. Another option (that I use a lot) is to hire a pro designer.
-
but you will need to arrange a license agreement with the developer of HISE >@Christoph-Hart
Hmm, that sounds like it might ultimately involve some expense. I wonder if he has a website or something that tells you how much a license with him might cost and what the license details are so I could have a better idea of costs?
Also, I gather that people share code sometimes. E.g. if I wanted to add a Saturation knob and someone say, "here's some code of mine you can use" then might add, "you can use it, but non-commercially..." I suppose that happens?
I actually dont mind paying for stuff, but just would like to have more information. -
@Ian_SAfc I believe the license is a % of sales, so no upfront fee - but I could be totally wrong.
I haven't seen anyone share code that couldn't be used commercially, although I've seen a lot posted without a specific license. Usually if it's on the forum it's public domain but you can ask the person who posted it to be 100% sure.
Most of the code in my github repo is GNU GPL - so you can use it commercially but not in a proprietary plugin - and I also post lots of trivial snippets which are public domain and can be used in any context.
-
Hi @Ian_SAfc
First, if you want information on the licensing scheme, you should ask Christoph directly (via the chat on the top right for instance, Christoph is quite busy always improving this marvellous platform, so be patient)
But to give a clue, I think there's no need to make expenses before selling your product (except outside of Hise if you hire someone of course), but this is Christoph's domain...People are always sharing code here, and this is why Hise is so great! Now, there is sharing and sharing... If you struggle with your code, you'll always find someone to help you.
But if you want "ready to paste" code, this is not the best way to proceed... But for all that is necessary at first, (GUI implementation, modules connexion and other basics things), you'll already find plenty of information on this forum. There are not so many people here, but so many topics has already been treated, just use the search bar ;)Also, there are some marvellous script (@d-healey did incredible things here) that you can use, but they are often under GNU GPL license, so read the script comments first, or ask the author if you want to use them in the peace of mind.
-
sorry @d-healey for cross posting...
-
@d-healey said in Newbie questions about HISE...?:
@Ian_SAfc I believe the license is a % of sales, so no upfront fee - but I could be totally wrong.
Thats a good system.
Most of the code in my github repo is GNU GPL - so you can use it commercially but not in a proprietary plugin - and I also post lots of trivial snippets which are public domain and can be used in any context.
Thats good of you.
I know what proprietary means, but I am not sure I understand your meaning in terms of "commercial" vs "proprietary " in this context.
If I release a "commercial" product, it has my name on it. Its closed etc. -
@Ian_SAfc Proprietary means closed source. Commercial means you sell it for money. There are millions of commercial apps and plugins that are free software (i.e. open source). Putting your name on it might come under trademark law which is a different matter.
-
Commercial under the GNU GPL means you can sell, it's free for you regarding Hise Audio, but you must make your source code available for customers
Proprietary means you pay fee to Hise Audio, so your product is closed, you don't have to share your source code
-
Oh ok, I see now.
So in theory I could make a sample library (e.g. sample a piano), and sell that without putting my name on, and that would be "commercial".
I would then make the code public that creates the plugin.
But at the same time, I would not have to make the piano WAV samples public.And proprietary means, I put my name on the piano sample library, and dont make the code available.
-
That's exact, in both cases the samples are your creation thus belong to you only
For the name, I have no idea... But I don't see why you couldn't put your name on a commercial license, you're still the guy who did it... But I might be wrong... -
@Ian_SAfc You can put your name on it either way. In fact I think it's in the GNU GPL that you have to make it clear that your version is your version and if someone else makes a version they have to make it clear that it's not the same as yours :)
If you're making a virtual instrument that can't function without its samples then these must also be made available. So a synth has no audio files so no issue, but a sample library does have audio files so these have to be released under an "open license" too. Christoph says they should be released under the GPL but I don't agree with him ;) because the GPL stipulates that source code must be available and audio files don't have source code, and all derivative works must be released under the same license - you can't expect people who use your virtual instrument to release their compositions under the GNU GPL, doesn't make sense. So I release mine under a Creative Commons license.
-
If you're making a virtual instrument that can't function without its samples then these must also be made available.
Oh, ... so I would have to make the samples available in this case.
-
Well it appears I am wrong about the samples... I still don't really understand that. Because samples are a piece of art by themselves.
What I will say here is purely my opinion, but if someone wants the code in order to make his own version of the plugin/sampler, I would say ok do it using my code, but make your own samples...Can't help pressing F5 in the forum...
-
If you make a free and open plugin that streams music, it doesn't make the music free, so I don't understand this part...
-
@ustk The rules are specific to HISE not your code. So if you provide code to someone you can dictate the rules for your code. But if someone wants to release a GNU GPL plugin made with HISE (which of course contains Christoph's code) then you have to do it by his rules.
@Ian_SAfc You don't need to make source code or samples public. You only need to provide them to the people who purchase from you. So if I bought your GNU GPL sample library you must give me the samples, and if I want the source code you must provide it as well.
It would be very handy if there was a page somewhere that spelt all this out because everyone (quite rightly) asks about it... @Christoph-Hart ;)
-
@d-healey Thanks, you made it clear David!
You're right, some documentation on this would be very very helpful...
Under the new 5 points democratic vote system, I vote for you David!
-
@ustk said in Newbie questions about HISE...?:
@d-healey Thanks, you made it clear David!
You're right, some documentation on this would be very very helpful...
Under the new 5 points democratic vote system, I vote for you David!
I vote for that too! :)
