Questions from a newbie, including programming and sample licenses.
-
The assets (samples and images) should not be released under the GPL, this license is not suitable for them. You should use a different free license such as Creative Commons but it must allow derivative works.
which includes the samples (but they're in a closed format anyway).
The format isn't closed, there just isn't an unarchiver for it (yet).
-
@iamlamprey said in Questions from a newbie, including programming and sample licenses.:
@z80 No problem, just to clarify since my first post wasn't too clear (in case anyone else reads this thread and is confused):
You CAN release a HISE plugin, even commercially (for money) without paying for a license, but you must provide everything the end-user needs to build the plugin if they so desire - that includes source code, images, and yes, samples.
So in your particular case, unless you have permission to re-distribute the samples as GPL, you'd probably want to get a license, or look for another tool to make the plugin (like SFZ) :)
Yes, SFZ may be an option, since I've worked with the SFZ format before, and there's some player for common OS.
I appreciate again your time!.
-
@MikeB said in Questions from a newbie, including programming and sample licenses.:
@iamlamprey
Sorry, I have to intervene:
HISE has no rights to the images and samples used - neither were created by HISE.
The rights to the images and samples belong to the authors and any use is subject to their permission.
Only the source code is defined by GPLv3.Christoph can only grant rights that belong to him.
ImhoThat's why the images and audio files are embedded and compiled in the source code and are therefore no longer open.
Samples of sample maps are stored in a proprietary format without headers and are therefore
only for absolute programming nerds outside of HISE.Hello.
Your response has catch my eye, and I'm wondering if you can help me a bit. First, let me explain in detail what I want to do, since I haven't explained it in full detail:
I want to preserve (for free) a home keyboard in a sampled form, for wich thing I already have the permission of the manufacturer, wich still exists, the main condition to be able to do this is that the library can't be used for commercial purpouses.
By other hand, I like the idea of people using my code, for wich I would gladly provide separately, but the samples would have copyright since they are recorded from a machine with digital copyrighted samples, if this isn't possible with HISE, I can release this library in SF2/SFZ format, my intention here is to preserve or offer a glimpse of how this keyboard sounds.
With all of this said, how do you see it? better idea to release it as a SFZ?.
-
@z80 said in Questions from a newbie, including programming and sample licenses.:
By other hand, I like the idea of people using my code, for wich I would gladly provide separately, but the samples would have copyright
Everything has copyright unless it's released into the public domain.
from a machine with digital copyrighted samples
Who owns the copyright?
if this isn't possible with HISE,
You'll need to discuss with Christoph, but make sure you are clear what rights you have to the samples.
With all of this said, how do you see it? better idea to release it as a SFZ?.
If you own the copyright, or have permission from the copyright holder then it shouldn't make a difference.
HISE has no rights to the images and samples used - neither were created by HISE.
Christoph has the right to say who can and cannot release the HISE source code in a proprietary format, and he can add any conditions to this that he wants.
However, if you're releasing it under the GNU GPL then Christoph can't place additional restrictions on your usage, but the GNU GPL does. The GPL says that the end user must be able to build the software for themselves and be able to share it and modified/derivative versions. If the software is tightly coupled to the assets and is unusable without it (like a sample library) then you need to make the assets available as well under a compatible license. However if the assets are decoupled from the software the GPL has no problem with those assets being under a different license - https://www.gnu.org/licenses/gpl-faq.html#WhatCaseIsOutputGPL.
Keep in mind that some programs, particularly video games, can have artwork/audio that is licensed separately from the underlying GPLed game.
CC-BY-SA 4.0 is explicitly compatible with the GPLv3 with the resulting combined work being governed by the GPL.
-
@d-healey said in Questions from a newbie, including programming and sample licenses.:
@z80 said in Questions from a newbie, including programming and sample licenses.:
By other hand, I like the idea of people using my code, for wich I would gladly provide separately, but the samples would have copyright
Everything has copyright unless it's released into the public domain.
from a machine with digital copyrighted samples
Who owns the copyright?
if this isn't possible with HISE,
You'll need to discuss with Christoph, but make sure you are clear what rights you have to the samples.
With all of this said, how do you see it? better idea to release it as a SFZ?.
If you own the copyright, or have permission from the copyright holder then it shouldn't make a difference.
HISE has no rights to the images and samples used - neither were created by HISE.
Christoph has the right to say who can and cannot release the HISE source code in a proprietary format, and he can add any conditions to this that he wants.
However, if you're releasing it under the GNU GPL then Christoph can't place additional restrictions on your usage, but the GNU GPL does. The GPL says that the end user must be able to build the software for themselves and be able to share it and modified/derivative versions. If the software is tightly coupled to the assets and is unusable without it (like a sample library) then you need to make the assets available as well under a compatible license. However if the assets are decoupled from the software the GPL has no problem with those assets being under a different license - https://www.gnu.org/licenses/gpl-faq.html#WhatCaseIsOutputGPL.
Keep in mind that some programs, particularly video games, can have artwork/audio that is licensed separately from the underlying GPLed game.
CC-BY-SA 4.0 is explicitly compatible with the GPLv3 with the resulting combined work being governed by the GPL.
Hello.
I think that it will be better to release this library in SFZ format , since if I release it through HISE, I may be in noncompliance with the GPL license, wich I want to respect and don't do anything that can't be wrong.
I appreciate all the responses and the time poured on this same thread, regards and thanks again.
-
@z80 said in Questions from a newbie, including programming and sample licenses.:
I think that it will be better to release this library in SFZ format
What license will you use for SFZ format?
-
@d-healey said in Questions from a newbie, including programming and sample licenses.:
@z80 said in Questions from a newbie, including programming and sample licenses.:
I think that it will be better to release this library in SFZ format
What license will you use for SFZ format?
Years ago when I checked, SFZ format did allow the distribution of SFZ and companion files for free and no royalties, but it also the same as Hise? the software license also translates to the samples? on this case, it will have copyright, but it will be a free library released under the permisson of the original manufacturer.
I think that I will have to investigate it in detail, but in the end I can also release it using the WAV format contained in several folders, it will not be as organized as a SFZ or a SF2, but well, at least people will be able to use it.
Hope that answered the question. Regards.
-
@z80 said in Questions from a newbie, including programming and sample licenses.:
SFZ format did allow the distribution of SFZ and companion files for free and no royalties,
You can use any license you want for the SFZ file, and the samples, but you still need to choose a license and you still need to own the copyright of the samples or have the permission from the copyright owner to release the samples under the license you choose.
I think that I will have to investigate it in detail, but in the end I can also release it using the WAV format contained in several folders, it will not be as organized as a SFZ or a SF2, but well, at least people will be able to use it.
Same copyright and licensing issues apply.
-
@d-healey said in Questions from a newbie, including programming and sample licenses.:
@z80 said in Questions from a newbie, including programming and sample licenses.:
SFZ format did allow the distribution of SFZ and companion files for free and no royalties,
You can use any license you want for the SFZ file, and the samples, but you still need to choose a license and you still need to own the copyright of the samples or have the permission from the copyright owner to release the samples under the license you choose.
I think that I will have to investigate it in detail, but in the end I can also release it using the WAV format contained in several folders, it will not be as organized as a SFZ or a SF2, but well, at least people will be able to use it.
Same copyright and licensing issues apply.
Many thanks for the information, I will keep it on mind.
-
If you use HISE and publish the source code then the GPL won‘t interfer with your samples. Fair usage would suggest to make them publicly available somehow, but it‘s not a legal requirement.
-
@Christoph-Hart said in Questions from a newbie, including programming and sample licenses.:
If you use HISE and publish the source code then the GPL won‘t interfer with your samples. Fair usage would suggest to make them publicly available somehow, but it‘s not a legal requirement.
I understand, I will anotate it. With all this information, I will decide what will be the best option and then I will proceed to release the library.
As I previously said, many thanks for all the users that have posted on this thread.
-
My mistake :) sorry for the misinformation
