Newbie questions about HISE...?
-
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! :)
