Packages - BigSur

[d.healey]

That's correct, vst3 shows up as a folder, same on GNU/Linux. LV2 format is the same. I think .component also shows as a folder, no?

[Dan Korneff]

@d-healey said in Packages - BigSur:

I think .component also shows as a folder, no?

Not usually. The plugin that shows up as a folder is not detected by any DAW, but the plugin with vst icon is.

I also need to add that the plugins are compiling properly from HISE (they contain the icons and file type) it's only an issue after the file is delivered via Packages

[d.healey]

@dustbro Could be a permission issue. Is it only happening with the VST or also the AU?

[Dan Korneff]

@d-healey It's happening on all plugin formats :/

[d.healey]

@dustbro Are you compiling or packaging the plugins from a network shared drive?

[Dan Korneff]

@d-healey yes to both

[d.healey]

@dustbro Try it from your desktop instead. I had the same issue on MacOS.

[Dan Korneff]

@d-healey
Packages error from the desktop

Unable to copy item at path "/Users/dankorneff/Desktop/TestPlugin.vst3" because you don't have permission to create it inside the folder 'VST3'

I think you're on to something

[Dan Korneff]

Ok.. followed this guide to give Packages full disk access:
https://tombridge.com/2020/04/07/packages-in-the-catalina-era/

Unfortunately, same result after running the installer.

[d.healey]

@dustbro I just got in the habit of copying the folder from my network drive to my desktop for compiling on Mac. But if you find a proper solution do share :)

[Dan Korneff]

useful info on M1 Packages here:

https://forum.juce.com/t/using-the-packages-installer-builder-for-apple-silicon-m1-distributions/48748/17

[Fortune]

@dustbro Is there a fix for this?

I am seeing the same thing on M1 Mac / Monterey. After the installation, all pluginn versions are being installed as folders also with this message: The folder “My Plugin.component” can’t be opened because you don’t have permission to see its contents

And the DAW can't detect the plugin unfortunately.

[Dan Korneff]

@Fortune It ended up being a network permissions issue for me. I've actually ditched my M1 machine started making universal binaries with an Intel rig.

[Lindon]

@dustbro Dan, I havent tried to build universal binaries yet - but I'm sure its a request thats coming my way - is there anything specific I need to do on my (old) intel Mac?

[d.healey]

@Lindon No, assuming your Mac isn't too old it should be automatic.

[Lindon]

@d-healey automatic? what theres no switch I need to set?

[DanH]

@Lindon I think it's only Big Sur and later... what OS are you on?

[d.healey]

@Lindon As long as the arm architecture options are enabled Xcode will build a universal binary, and those options should be enabled by default when you export from HISE develop branch.

[d.healey]

@DanH I don't think the OS version is important, it's the Xcode version that matters. Xcode 12.2 is the oldest version you can use.

Building a universal macOS binary | Apple Developer Documentation

Create macOS apps and other executables that run natively on both Apple silicon and Intel-based Mac computers.

Apple Developer Documentation (developer.apple.com)

[Fortune]

@dustbro said in Packages - BigSur:

@Fortune It ended up being a network permissions issue for me. I've actually ditched my M1 machine started making universal binaries with an Intel rig.

Hmm, it looks like the Whitebox Packages has some bugs on M1 machines then. On Intel no issues but on M1, this thing happens.