Catalina has been released...
-
@d-healey said in Catalina has been released...:
@SampleScience I have MacOS, Windows 10, and Linux Mint, all installed on my Mac Mini :)
Impressive! :) This is something I should do, it would be much more intelligent than using multiple computers like I'm doing now.
-
@SampleScience This is the guide I followed - https://robpickering.com/triple-boot-macbook-pro-macos-windows-10-linux/
Use Linux Mint 17.3 (or equivalent Ubuntu version) for max compatibility.
-
@d-healey said in Catalina has been released...:
@SampleScience I have MacOS, Windows 10, and Linux Mint, all installed on my Mac Mini :)
Bad Ass
Always Wondering What Kind Of Mindset You Have Sir
Big Fan Of You Since Kontakt 5 " How To Lock Your Script Editor " LOL
-
@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
I went through the thread and found that the signing of Maize made plugins doesn't work because: "the code-signing does not longer allow references to other files within the .component file". The way Maize Sampler works is by loading mse files found within the plugin. This means that I'll either have to move completely to Hise or cease to release macOS compatible plugins.
Another problem: I found their signing process slow and cumbersome considering I have close to 50 plugins in my catalog. lol Just thinking about it is painful. lol
-
@Lindon said in Catalina has been released...:
@SampleScience plugins (no matter how they are built) dont need to be notorized, just codesigned.
I thought you were right but on KVR I've read this: "When it’s signed it seems to run fine first. But when I upload it and download it again, it will not run anymore. I’ve read somewhere in the documentation that all software needs to be notarized. They specifically mention plugins too." (quote by e-phonic: https://www.kvraudio.com/forum/viewtopic.php?f=33&t=531663&start=45 ).
So I guess that plugins, in order to work on Catalina, need to be both notarized and signed.
-
@SampleScience said in Catalina has been released...:
So I guess that plugins, in order to work on Catalina, need to be both notarized and signed.
This begins to cause doubt in my head because both cases (notarized and not notarized) have "solid" arguments here and there...
In case of a doubt, it usually seems that going for most the secure solution seems to be the most the secure solution... -
@ustk except as far as I read you cant notarize a plug-in. You can only notarize its installer or zip file
HISE Development for hire.
www.channelrobot.com -
@Lindon ah, we technically can't... So where does the error @SampleScience mentionned above come from
-
@ustk many many misunderstandings(myself included)
"The notary service generates a ticket for the top-level file that you specify, as well as each nested file. For example, if you submit a disk image that contains a signed installer package with an app bundle inside, the notarization service generates tickets for the disk image, installer package, and app bundle."
-
It's the zip file that you need to notarized, at least that's what I understood from reading the whole KVR thread. :P
In any case, for the moment I'm out. I'm just fed up by the whole situation and I'll probably go Windows only for my upcoming plugins. This way, I'll do what I like, which is to create plugins. Solving endless problems created by Apple has never been part of the plan for me.
-
Just don‘t care about catalina ;)
People know by now how to bypass the notarization error...
-
@Christoph-Hart said in Catalina has been released...:
Just don‘t care about catalina ;)
People know by now how to bypass the notarization error...
I wish it was the case for my customers, but I got so many emails that I'm really tired of the whole situation now.
