Notarisation for dummies

[A Former User]

@orange That's a great explanation, Thank You!

[trillbilly]

All hail @orange

[trillbilly]

@orange Ive gotten to waiting for the email. Ill post update after.

UPDATE: Success. Thanks again!

[Fortune]

@orange Thnx for this epic information! All of the required information is here. You're awesome

@Christoph-Hart could you add this information to the Hise Documentation, please? I will be so helpful for the newbies.

[d.healey]

@fortune said in Notarisation for dummies:

could you add this information to the Hise Documentation, please?

HISE | HISE | Contribute to the HISE Docs

How to contribute to this documentation.

(docs.hise.audio)

[trillbilly]

@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.

[Sawer]

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

[d.healey]

@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.

[Sawer]

@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?

[d.healey]

@nesta99 Are you using Whitebox Packages?

[Sawer]

@d-healey
This:

[d.healey]

@nesta99 Yep, you need to setup your install paths in there.

[Lindon]

@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?

[Sawer]

@d-healey Ok, thanks.
How can I Kindly do it, pretty new to whitebox?

[Sawer]

@lindon To be honest, I dont know what auval is and since I never remember to use it, then no.

[d.healey]

@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

[Sawer]

@d-healey said in Notarisation for dummies:

Packages User Guide

(s.sudre.free.fr)

Thanks man.

[Sawer]

@d-healey So based on my understanding , on the path section, I just need to put this /Library/Audio/Plugins/Components , right?

[d.healey]

@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.

[Lindon]

@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:

Audio Unit Development Fundamentals

Explains how to use Core Audio frameworks and the Core Audio SDK to create audio units.

(developer.apple.com)