Mac OS export Questions
-
@d-healey ok, I'll test it on the other Intel laptop later today
-
@ElectroBlue Ok so I just tested the AU plugin and the Standalone Mac app on my really old Intel Macbook Pro and what happened was this:
-
list item The AUi plugin worked fine without me having to do anything inside of both GarageBand and Logic Pro X
-
list item The standalone Mac app didn't launch and I got an error message from Apple saying that the app can't be opened. However, after watching a YouTube video on how to fix that in the Terminal and System settings I was able to eventually open the Mac app and then it worked just fine.
I had to open up the Terminal and type this command:
chmod +x [path to file]That actually didn't work at first because I ended up having to "show contents" of the app and then go inside the Mac OS file folder and use that in the path above.
Then I had to go into the Mac System Preferences / Security & Privacy Settings and check off that I allow apps from unknown developers. So I'm a bit confused now... when I go to distribute the app do I need to give instructions to everyone on how to do this? Or did I just compile the app incorrectly? So when you build a standalone Mac app can you just copy it or upload it somewhere to sell it as a digital download or is there some copy protection that is preventing this? I also wonder if I copied the app and then tried to open it on another M1 Mac would I run into the same issue?
-
-
@ElectroBlue Also, using the same Terminal command on my Intel iMac didn't fix it, but I noticed that in the System Preference Security and Privacy settings in Ventura ... is different ... there is no option to "Allow applications downloaded from unidentified developers" there are only two options: App Store and App Store and identified developers. So that begs the question: How do you become an "identified developer"? And that's probably why nothing works on my Intel iMac... because there is no place for me to allow applications from "unidentified developers"
-
@ElectroBlue I also just tested the VST3 plugin on my Intel iMac with Bitwig Studio and it works fine. It didn't show up as a VST3 plugin inside of Live Lite 10 for some reason but I'm not a regular Live user. I mostly use Logic Pro. I was also able to get the AU plugin to work on my Intel iMac now without issue. So the big mystery is with the standalone Mac app and how to get it to launch on any machine. I'm planning on just giving it away for free but I want to make sure it works for users and doesn't require a bunch of hurdles for them to get over before they can get permission to open it.
-
@ElectroBlue On a positive note, I discovered that the arpeggiator that I added actually syncs with whatever tempo the DAW is set to... well I actually only tested it inside of Live Lite 10 but I was super impressed that it worked! So cool! :)
-
@ElectroBlue said in Mac OS export Questions:
. So I'm a bit confused now... when I go to distribute the app do I need to give instructions to everyone on how to do this? Or did I just compile the app incorrectly? So when you build a standalone Mac app can you just copy it or upload it somewhere to sell it as a digital download or is there some copy protection that is preventing this? I also wonder if I copied the app and then tried to open it on another M1 Mac would I run into the same issue?
OK so you compiled correctly - but on MacOS there's a number of stages you need to go thru with any binary to make it work on someone else's machine .
- So your plugins need to be codesigned
- Your stand alone app needs to be codesigned and notarized.
You will need to join the Apple developer program(99 dollars/year)
You will need to generate and download and install the correct digital certificates
You will need to set up a password for altool
You will then need to execute the command line processes to codesign and notarise(as appropriate) your product set.You should read this forum topic - yes all 20+ pages of it:
-- welcome to development on the Mac, where we all end up hating Apple...
-
This post is deleted! -
@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.
-
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?
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?
