Catalina has been released...
-
@orange I only release 64bit anyway so that part isn't an issue. Glad to know I can just carry on as I have been (with the additional notarization crap)
-
@orange - I think the answer to this part of Dave question is: "maybe"
"And if I build one on Mojave will it work on Catalina?"
-
Just to be sure - if I don't have an Apple Developer ID, Hise-based instruments won't work on Catalina until I sign them?
-
@tomekslesicki For now, it is working. But acording to Apple you need to sign everything. And non-signed plugins won't work anymore in the next updates.
So I suggest signing your plugins if you don't want your users return back and say "hey my plugin doesn't work anymore".
-
Thanks @orange !
-
So I imagine that we need to sign Hise as well right?
Is there no issues, I mean, with many devs signing the same app?Interesting thread:
https://forum.juce.com/t/confusion-on-catalina-notarization-hardened-run-time-no-changes-needed-after-all/35850/5 -
Maize Sampler recently signed/notarized its main application so the plugins created with it are Catalina ready. How do I make sure my Hise Sampler made plugins are compatible with Catalina? Is there a step by step guide on how to do it?
-
@orange said in Catalina has been released...:
For plugins, you only need to sign them digitally with Apple Developer ID ($99/year). Actually, you can't notarize plugins. But if you don't sign the plugins, they won't load in the DAW. (mabe they can work in Catalina first release, but not for the further updates). By the way I don't know if Maize Sampler is digitally signing plugins or not while exporting.
It is now with the new version. How do I sign my Hise Sampler plugins?
-
@SampleScience Here is the guide for signing and notarization ;) : https://www.kvraudio.com/forum/viewtopic.php?t=531663
develop Branch / XCode 13.1
macOS Monterey / M1 Max -
Did You Guys Tried This With Hise
Please Take A Look At This Article, And Skip To The End, Where It Says
https://support.apple.com/en-us/HT202491How to open an app that hasn’t been notarized or is from an unidentified developer -
@orange said in Catalina has been released...:
@SampleScience Here is the guide for signing and notarization ;) : https://www.kvraudio.com/forum/viewtopic.php?t=531663
This looks great, thank you! I guess that the process can be applied to Hise Sampler made plugins too. Hopefully, it is.
-
@SampleScience plugins (no matter how they are built) dont need to be notorized, just codesigned.
HISE Development for hire.
www.channelrobot.com -
@Lindon Mate
Can You Do A Tutorial Or Some Step By Steps Guides?
Thanks -
@Natanr many many people have already pointed at the tutorial:
https://www.kvraudio.com/forum/viewtopic.php?f=33&t=531663&sid=bce341acccb7bc5b7138ab6bba3f3574
-
@Lindon to codesign i also need Apple Dev Account yes?
-
@arminh yes. You need an apple Dev ID and password. You need to code sign all your plug-ins and notarize your installers.
HISE Development for hire.
www.channelrobot.com -
@Lindon I don't remember... Is it mandatory to make the whole process with Catalina or is it doable in a previous OS? (I don't want to update my main working station right now but just the MacBook) Lazy to search today :)
-
@ustk I'm no expert but my understanding is that you dont need to be on Catalina at any point in the process, just you need to code sign/notarize as required so your work will run on Catalina.
-
Does anyone know if plugins made for Catalina (signed) will work with previous versions of macOS? If so, how far in previous versions will it work? I see that Audio Damage supports 10.9 Mavericks or newer and I wonder how they are knowing it for sure.
-
In our plugins, I've just tested down to the Mavericks too. The plugins were signed and installer was notarized in Mojave and they work down to Mavericks.
Also probably, they should work down to a couple of level older versions too.
develop Branch / XCode 13.1
macOS Monterey / M1 Max
