Notarisation for dummies
-
@nesta99 Here it is. The instructions are just a few posts above. This is with installers. I think the process is a bit different if you do it without installers.
-
Hello everyone. After code sign the plugin I'm still not able to open my plugin on Logic Pro. I have the latest version of logic on a Monterey OS. Is it required to notarise the plugin before making it work o a daw?
Thanks
-
@nesta99 said in Notarisation for dummies:
Is it required to notarise the plugin before making it work o a daw?
In Logic almost certainly, other DAWs might be more tolerant.
-
@d-healey Thanks so much. Another question: I'm having an issue with dealing with the packaging, most precisely on the destination folder:
As shown in the picture above I wasn't able to place the .component in the Audio/Plugins/Component folder.
Now when the end user will install the product, the .component fill will be place in the wrong place, making it complicated.
Any solution? -
@nesta99 Are you using Whitebox Packages?
-
@d-healey
This:
-
@nesta99 Yep, you need to setup your install paths in there.
-
@nesta99 said in Notarisation for dummies:
Hello everyone. After code sign the plugin I'm still not able to open my plugin on Logic Pro. I have the latest version of logic on a Monterey OS. Is it required to notarise the plugin before making it work o a daw?
Thanks
I have NEVER had to notarize any plugin anywhere - codesign - yes but notarize no, I strongly suspect its not that its not notarized, have you run auval against your compiled component plugin?
-
@d-healey Ok, thanks.
How can I Kindly do it, pretty new to whitebox? -
@lindon To be honest, I dont know what auval is and since I never remember to use it, then no.
-
@nesta99 said in Notarisation for dummies:
@d-healey Ok, thanks.
How can I Kindly do it, pretty new to whitebox?The documentation is probably the best resource - http://s.sudre.free.fr/Software/documentation/Packages/en_2017/index.html
-
-
@d-healey So based on my understanding , on the path section, I just need to put this /Library/Audio/Plugins/Components , right?
-
@nesta99 said in Notarisation for dummies:
I just need to put this /Library/Audio/Plugins/Components , right?
No idea, I haven't used it for over a year. Just try it and see, and then share your wisdom.
-
@nesta99 said in Notarisation for dummies:
@lindon To be honest, I dont know what auval is and since I never remember to use it, then no.
run auval everytime on every AU plugin:
-
@lindon Yeah true. Plugin not signed yet. I tried but not working ...
It says : "no identity found" . Any Idea? -
@nesta99 said in Notarisation for dummies:
@lindon Yeah true. Plugin not signed yet. I tried but not working ...
It says : "no identity found" . Any Idea?sounds like you dont have the plugin ID set up correctly.. (as a guess)
-
@lindon Ok thanks. Not finding anything specific related to this, neither a solution to this problem. Any idea? I got all the certificates in my keychain with their keys password.
-
@nesta99 I think @Lindon is talking about the Plugin ID in the HISE settings. I believe there is the Bundle Identifer (for Mac purposes) and the Plugin ID (which is usually 4 letters like Abcd). Make sure you have both setup correctly.
-
@trillbilly @Lindon Ok, it's getting more intricate than expected.
In any case, I've finally managed to codesign the plugin, the problem was related to my certificate.
Now, the problem is that, Logic Pro doesn't see my plugin..
I really can't understand the issue now. At least, Logic Pro should see it, even if the plugin couldn't be validated by auvatool. But the plugin doesn't show up!
Any Idea?
