HISE Logo Forum
    • Categories
    • Register
    • Login

    Mac OS export Questions

    Scheduled Pinned Locked Moved General Questions
    61 Posts 4 Posters 5.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • E
      ElectroBlue @d.healey
      last edited by

      @d-healey how do I get a license? Is it needed to distribute a free instrument or only if I plan to sell it?

      d.healeyD 1 Reply Last reply Reply Quote 0
      • d.healeyD
        d.healey @ElectroBlue
        last edited by

        @ElectroBlue said in Mac OS export Questions:

        @d-healey how do I get a license? Is it needed to distribute a free instrument or only if I plan to sell it?

        Link Preview Image
        HISE | Docs

        favicon

        (docs.hise.audio)

        Both JUCE and HISE licenses are required for any proprietary release, it doesn't matter if you charge for it or not.

        Libre Wave - Freedom respecting instruments and effects
        My Patreon - HISE tutorials
        YouTube Channel - Public HISE tutorials

        E 1 Reply Last reply Reply Quote 0
        • E
          ElectroBlue @d.healey
          last edited by

          @d-healey Ok, I'm confused. What constitutes a "proprietary" release? Also, I clicked on your link and read it and then clicked on the GNPLv3 link.. and read a bunch more, but couldn't find any instructions on how exactly do release the source? I'm not familiar with this process and I've never really used any kind of source control software. Is this about like uploading my HISE project folder to something like Github?

          d.healeyD 1 Reply Last reply Reply Quote 0
          • d.healeyD
            d.healey @ElectroBlue
            last edited by

            @ElectroBlue

            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).

            Libre Wave - Freedom respecting instruments and effects
            My Patreon - HISE tutorials
            YouTube Channel - Public HISE tutorials

            E 2 Replies Last reply Reply Quote 0
            • E
              ElectroBlue @d.healey
              last edited by

              @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?

              E 1 Reply Last reply Reply Quote 0
              • E
                ElectroBlue @ElectroBlue
                last edited by

                @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.

                Christoph HartC 1 Reply Last reply Reply Quote 0
                • E
                  ElectroBlue @d.healey
                  last edited by

                  @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.

                  d.healeyD 1 Reply Last reply Reply Quote 0
                  • Christoph HartC
                    Christoph Hart @ElectroBlue
                    last edited by

                    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.

                    E 1 Reply Last reply Reply Quote 0
                    • d.healeyD
                      d.healey @ElectroBlue
                      last edited by

                      @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.

                      Libre Wave - Freedom respecting instruments and effects
                      My Patreon - HISE tutorials
                      YouTube Channel - Public HISE tutorials

                      E 1 Reply Last reply Reply Quote 0
                      • E
                        ElectroBlue @Christoph Hart
                        last edited by

                        @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.

                        1 Reply Last reply Reply Quote 0
                        • E
                          ElectroBlue @d.healey
                          last edited by

                          @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?

                          d.healeyD 1 Reply Last reply Reply Quote 0
                          • d.healeyD
                            d.healey @ElectroBlue
                            last edited by d.healey

                            @ElectroBlue

                            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

                            Christoph HartC 1 Reply Last reply Reply Quote 0
                            • Christoph HartC
                              Christoph Hart @d.healey
                              last edited by

                              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 .gitignore is 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.

                              1 Reply Last reply Reply Quote 0
                              • First post
                                Last post

                              16

                              Online

                              1.7k

                              Users

                              11.8k

                              Topics

                              102.4k

                              Posts