Mac OS export Questions
-
Proprietary = closed source. If you release under the GNU GPL (open source) you are required to give a copy of the source code to anyone who you give a copy of the binary to. You don't have to make your source code public, but of course anyone who receives a copy could do.
For a HISE project the source code is basically your HISE project folder, but you only need to include stuff for building the binary, so don't include the samples, binaries, or pooled resources folders (there might be some others you can omit too).
-
@d-healey Oh I see. Thanks for the explanation. I'll have to do that then. How do most others do this? Just ZIP up my HISE project folder (omitting the items you listed) and then include that ZIP file along with my PKG file as a digital download? Won't users be confused as to what that is? I'm guessing I'd probably have to also include a .txt file explaining what it is?
-
@ElectroBlue Or could I just include a .txt file with a link to download the source ZIP if they want it? This way they don't get confused and open that ZIP file first wondering where the instrument is.
-
@d-healey Does your HISE master class ever go on sale? I'm interested in taking it, but I'm in the US so its more expensive for me to purchase it.
-
The rule is that you need to offer the source code to anyone that you provide a binary. How you do this is up to you and any of the options you mention would work.
That being said I highly recommend start using git (for other reasons than being compliant to GPL, it's just software development best practice) and then just make a public repo that you put a link on your website.
-
@ElectroBlue said in Mac OS export Questions:
@d-healey Does your HISE master class ever go on sale? I'm interested in taking it, but I'm in the US so its more expensive for me to purchase it.
The Hackspace one? I don't know I'm not in charge of the pricing there. I did post a discount code on Patreon a while back. If you're a patron you get 15% off.
-
@Christoph-Hart Got it. Thanks for the clarification. The main reason I haven't really used Git is because my Unity and Unreal projects are always like 50 gb or 100gb or more and I could never upload that amount of data to Git.
-
@d-healey Music Hackspace: This course: https://musichackspace.org/product/creating-virtual-and-sample-based-vst-au-plug-in-instruments-with-hise/
Is that the same as the link you just provided or is that a different course? -
The main reason I haven't really used Git is because my Unity and Unreal projects are always like 50 gb or 100gb or more and I could never upload that amount of data to Git.
Don't confuse git with github.
Is that the same as the link you just provided or is that a different course?
That's the one. My link is to the discount code on Patreon.
Libre Wave - Freedom respecting instruments and effects
My Patreon - HISE tutorials
YouTube Channel - Public HISE tutorials -
The main reason I haven't really used Git is because my Unity and Unreal projects are always like 50 gb or 100gb or more and I could never upload that amount of data to Git.
That's what
.gitignoreis for - just exclude the folders with big assets and you're fine. In HISE you need to add the Binaries, Samples and PooledResources folder to the ignore file too.
