Back to using White box...with all the problems there in....

[Dan Korneff]

@Lindon I would think that's a permissions issue. Have you seen this artice:
https://adamargyle.net/2021/02/08/dont-have-permission-to-create-a-file-in-whitebox-packages-app/

[Lindon]

@Dan-Korneff said in Back to using White box...with all the problems there in....:

@Lindon I would think that's a permissions issue. Have you seen this artice:
https://adamargyle.net/2021/02/08/dont-have-permission-to-create-a-file-in-whitebox-packages-app/

er-- right this seems to suggest its a file permission on the package creation process, assuming I get around this, by moving my plugins that are being added in to, say, the desktop, will WhiteBox just install in the system folders? Or do I have to set a flag (somewhere) for that too?

[Dan Korneff]

@Lindon This article has a much better explanation than I could come up with.
http://s.sudre.free.fr/Software/Packages/Q&A_3.html

You can select whether it's the system folder or user folder. In general, I always install files to the System Library ("/Library"), and then use a post install script to move user-specific configurations, preferences, or files for the project (AKA presets, documentation, ect...) to the User Library ("~/Library")

[d.healey]

@Lindon said in Back to using White box...with all the problems there in....:

Sorry Dave I looked and looked and couldnt find it on the Patreon site - any clues?

This one. If I remember correctly the script uses altool for the notarization, so you'll need to change that line to use the new notary tool.

Just a moment...

(www.patreon.com)

Edit: And now that I think about it I might be using the user folder, not the system folder... can't remember

[Lindon]

@d-healey said in Back to using White box...with all the problems there in....:

@Lindon said in Back to using White box...with all the problems there in....:

Sorry Dave I looked and looked and couldnt find it on the Patreon site - any clues?

This one. If I remember correctly the script uses altool for the notarization, so you'll need to change that line to use the new notary tool.

Just a moment...

(www.patreon.com)

Edit: And now that I think about it I might be using the user folder, not the system folder... can't remember

thanks - Im not troubled by the codesign or notarization steps - its the install process using Packages into ~/Library so not sure your video/script will be of a great deal of use to me...

[Lindon]

@Dan-Korneff said in Back to using White box...with all the problems there in....:

@Lindon This article has a much better explanation than I could come up with.
http://s.sudre.free.fr/Software/Packages/Q&A_3.html

You can select whether it's the system folder or user folder. In general, I always install files to the System Library ("/Library"), and then use a post install script to move user-specific configurations, preferences, or files for the project (AKA presets, documentation, ect...) to the User Library ("~/Library")

Thanks Dan - I will give this process a go.

[clevername27]

@Lindon Oh dude, if you're stay looking for info, hit me up over chat. I got that shizzle down.

[Lindon]

@Dan-Korneff okay back here again , and its still not working for me, here's what Im trying to do in teh set up:

and I build this and get:

Im running this as me nothing unusual...

[Lindon]

the only thing I see as different is when I start to define the payload then /Library doesnt have Audio/Plug-Ins/VST3 in it - so I create them, and they are seen as custom folders not as Standard Folders..

so how do I get Audio/Plug-Ins/VST3 to show up in packages?

[DanH]

@Lindon this is a permissions issue with OSX. try putting the .vst3 in the VST3 folder DAW's use and see if it works.

Otherwise the dev gave me a version that should get around this issue but I had to also add something into gatekeeper / start up options

[Lindon]

@DanH said in Back to using White box...with all the problems there in....:

@Lindon this is a permissions issue with OSX. try putting the .vst3 in the VST3 folder DAW's use and see if it works.

er thats what Im trying to do... get Packages to put the plugin in /Library/Audio/Plug-Ins/VST3

Otherwise the dev gave me a version that should get around this issue but I had to also add something into gatekeeper / start up options

[Lindon]

@Lindon ahhh.. @DanH .. now I get you ... I just moved the VST3 from the desktop into the destination folder I wanted (/Library/Audio/Plug-Ins/VST3) and rebuild the Package and it works .. well it builds at least....

[DanH]

@Lindon cool, but it won't stick it into the users VST3 folder?

[Lindon]

@DanH oh no idea, havent tried that yet - been busy trying to get it notarised...

[Dan Korneff]

@Lindon I create my packages from the Desktop as well.
Have you compared your settings to the JUCE tutorial?
https://docs.juce.com/master/tutorial_app_plugin_packaging.html

[Dan Korneff]

@Lindon also, I think it's recommended to use the latest version from git

GitHub - packagesdev/packages: Integrated Packaging Environment for OS X

Integrated Packaging Environment for OS X. Contribute to packagesdev/packages development by creating an account on GitHub.

GitHub (github.com)