Mac OS export Questions
-
@Lindon Thank you! Wow, what a process! Apple really makes this a painful process! I'm already an Apple Developer... I used to have several apps on the App Store a few years back, but then I got distracted with VR development for a few years. I recently renewed my Apple Developer account to start preparing for visionOS. Still waiting on Apple to update my address change ... they take forever to respond and fix things. Once they update my address in the Agreements section I have a couple apps that will likely go back online. I have noticed however, that there appears to be quite a bit of new stuff to fill out. Looks like they added a bunch of new requirements to get your apps ready. I entered my Team ID inside of HISE so I thought that it took care of all that stuff. I remember needing to have a certificate and a couple other things but I don't recall anything about notarization so that's probably a recent addition?
-
@ElectroBlue said in Mac OS export Questions:
. I entered my Team ID inside of HISE
That's just the codesigning.
Libre Wave - Freedom respecting instruments and effects
My Patreon - HISE tutorials
YouTube Channel - Public HISE tutorials -
Once you enter the team ID to code sign, you will also need to notarize the app or it won't load at all (funnily macOS treats a signed but unnotarized app as more harmful than a unsigned executable). If you do none of those things (no code signing & no notarization), then the end user has to manually allow the execution of your app, but it gives a very clear error message at least.
-
@Christoph-Hart Ahhh I see... It's all starting to make sense now what I have to do. Thank you guys for the help and support as I get up to speed.
-
@Lindon THANK YOU SO MUCH FOR POINTING ME TO THAT FORUM POST!! That post along with the help of ChatGPT propelled me to the finish line! I have now successfully complied, signed and notarized my virtual instrument. I even created the package installer! The whole code signing and notarization process is completely from hell and totally stressed me out for like two days! I can see why you guys all hate Apple! lol What a painful process that part was! However, once I finally got everything working there was a huge sense of accomplishment especially after all those issues I was dealing with on my iMac. My iMac is definitely possessed by a demon! lol Anyway, here is the link to my first virtual instrument created with HISE: https://replay11.sellfy.store/p/neon-8x/. I'm giving it away for free since it's very simple compared to other VSTs and since it's my first attempt at this. I tested the installer on both M1 mac and an old Intel Mac laptop and everything worked!
-
@ElectroBlue glad its working for you - now all you need do is wait for Apple to change the rules (AGAIN!) - and you have to relearn all this from the start - usually in a sort-of 6 month cycle for them.... hey ho...:-)
-
@Lindon Ugh! Typical Apple. Yeah that's really annoying, but that will actually motivate me to build more before that happens!
-
@ElectroBlue Also you need a HISE license if you haven't got one already, and a JUCE license.
-
@d-healey how do I get a license? Is it needed to distribute a free instrument or only if I plan to sell it?
-
@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?
https://docs.hise.audio/introduction/index.html#licensing
Both JUCE and HISE licenses are required for any proprietary release, it doesn't matter if you charge for it or not.
-
@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?
-
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
