License GPL!
-
Hello
I am new to development with the GPL License and would like to learn more.
I'm about to release an EQ with this license.I would like to know what I need to give the public exactly!
And how do I give it, I have to put it in the VST folder that the client download?
-
Everything you need to know - https://www.gnu.org/licenses/gpl-3.0.en.html
You must provide the source code.
-
Hi Alex,
just put the project folder on a public GitHub repository, put the link to it below your download link and you're set. You might want to not include the
Binariesfolder as the temporary build files get pretty large. The most convenient way is to just addBinaries/to the.gitignorefile in your repo BEFORE you push anything there and it just will ignore this directory without further efforts.Finding the right VST directory is a bit hard, and if you only distribute one plugin file, you might as well just distribute a .zip file and let the user's extract it to their location manually.
-
Do I need to include my GUI (Made with affinity designer) and my WAV Impulse?
-
You need to include anything that is required to build and use your plugin, so you definitely include the image files and impulse responses. You don't need to upload the .afdesign file though, just the .PNG images is enough obviously.
I am not a lawyer, but the assets don't have to inherit the GPL license, so you can still have the copyright on them, but they must be available.
-
Even with GPL you still have copyright
-
@christoph-hart said in License GPL!:
You need to include anything that is required to build and use your plugin, so you definitely include the image files and impulse responses. You don't need to upload the .afdesign file though, just the .PNG images is enough obviously.
I am not a lawyer, but the assets don't have to inherit the GPL license, so you can still have the copyright on them, but they must be available.
The wording of the GPL only refers to "source code" and thus I believe any non source code elements have their own copyright and are not subject to the license.
Also I am not a Lawyer but I was just reading the GPL with a few business/legal minded friends to better undersand the nature of what I must do going forward with HISE and JUCE.
As a small startup company with limited revenue the idea of releasing the source code for any derived plugin from HISE in order to sell it doesn't bother me, and of course am willing to pay for a commercial closed source license as soon as we are generating some proper revenue.
For that matter I believe that my initial reciprocal value in working with HISE and providing my source will be in the ways I extend and fix the source.
I am wondering if there is any more information on the closed source license option for HISE available?
-
@macromachines a commercial license with HISE is probably affordable, even to a startup company.
-
@dustbro I'm sure it could be affordable, but I try not to make assumptions.
I also haven't tested the waters of the insanely competitive and over-saturated-heavily-pirated VST instrument market yet, so I am not entirely certain of what the profitability is..
HISE is also lacking a few features that I will likely need to implement myself to realize my designs, so I think providing something like time stretching looping back into the HISE source ecosystem, or even maybe even some higher quality DSP effects would be an equivalent or potentially even more valuable means of reciprocity in realizing a first project than whatever the cost of the license may be, considering I made about 6 or so grand on a license of some of my time stretching DSP assembly code to a botique guitar pedal ..
I have also evaluated things like audioweaver which is a set of matlab DSP objects for high performance embedded DSP and thought "Oh this could be a cool way to do rapid development of effects hardware".. and then I called up to get a license pricing and it was $15,000 plus a dollar per unit because his tool was mainly used by car and home stereo systems to do eq filters and reverbs that have budgets where that price is nothing (but damn though.. I could write a fricken biquad bank myself in assembly.. its not that complicated). QT costs $450 a month for a closed source license.. the range of license pricing can be rather varied.
-
We‘ll definitely come to terms here. If you manage to contribute a working time stretching algorithm, I am more than happy to talk about exhanging licenses to use each other‘s work.
But apart from that the default licensing scheme for HISE is rather fair and if you‘re just want to go the GPL route to keep the startup investments down, there are smarter solutions. Write me an email then we discuss the terms.
