Made a plugin - Github and GPLv3
-
I made a Saturation fx plugin and want to confirm I've followed HISE's policy for the GPLv3 open source license. I didn't do any scripting. I'm a noob with HISE and Github.
Download link for Simple Saturation Plugin (VST3 Windows 64-bit) https://drive.google.com/file/d/1PIqBFSdY5E8GrktDCJwt9pFvSS4lFFgY/view?usp=sharing
^ If anyone can test it to see if it works it would be much appreciated!
Thank you,
Cool WAV
-
Bump, do I need to include the GPLv3 license disclaimer anywhere else on Github or project folder?
-
@coolwav Yes you must use GPLv3 and make your HISE project available to anybody who you distribute the binary to.
-
@d-healey Right I understand, I want to make sure that I have included the GPLV3 license in all of the correct locations. I put it in several places on the Github repository and am including a txt file with the download link I share. Is there anywhere else I need to put it?
Github Repository
https://github.com/coolwav/Simple-Saturation-PluginZip file - VST3 + txt file with GPLv3 open source license
https://drive.google.com/file/d/1Y6l9Ffn0NRHOfNLPCsGBnONVo-Y-od1y/view?usp=sharing -
@coolwav You need to put your HISE project on github so that someone else can come along, download the project, and build it just the same as you did.
-
@d-healey Ok thank you, the project file is uploaded there and I left my email address on the readme in case any files are missing
-
@coolwav Here's an example of one of my projects - https://github.com/davidhealey/sofiawoodwinds
-
@d-healey Right on thanks this seems like something I should add, replacing Libre Wave with Cool WAV "If you wish to fork this project or reuse it in your own virtual instrument you must remove the Libre Wave name and trademark and make it clear that your project is separate so that it won't be confused with this project. This includes using different names/imagery for your project as approriate."
