@David-Healey ahh, no they don't
this might be the issue (I'll try)

Okay, it's working now!
Thank you!

@David-Healey I've tried with and without. In both cases the knobs are frozen.

I have a weird bug with two of my knobs (with filmstrips).
I connected them with scripting to parameters of my hardcoded master fx.

They do work, but visually they are static. Does anyone know, why this might be?

So. For everyone who is curious.
I searched a bit online and plugins not showing up in the logic list seems to be a specific logic bug with unknown reason.
(seems to have also happened to some people with big brand plugins like native instruments)

The solution that seems to work for most people (including myself) is deleting (if they exist, doesn't need to be all of them):

• user/Library/Preferences/com.apple.audio.AUHpostingService.x86-64.plist

• user/Library/Preferences/com.apple.audio.InfoHelper

• user/Library/Caches/AudioUnitCache

• user/Library/Caches/com.apple.audio.AUHostingService.x86-64

• user/Library/Caches/com.apple.audio.InfoHelper

@dannytaurus !

Sadly I needed to reach out to you with a new question.
My plugin (.component) worked once before, but is now not visible in Logic pro (again).

It is visible and validated in the list in the plugin manager, as well as by running the command "auval -a", but I cant open the plugin in Logic, it is not in the dropdown list.

Any ideas why?
Yes the PlugIn codes (2 plugins) are different to all the other plugins I use.

@David-Healey I just forgot the stage of setting the permissions with your provided code "chmod -R 755" before packaging

@David-Healey ah, i was just dumb
it worked now

@David-Healey yes
Voros Music: Blue Glockenspiel Cannot open component: -3000
thats the result

@VorosMusic okay the result says: Cannot open component: -3000

@David-Healey I'm currently rebuilding a new version of the plugin, I'll let you know, when I'm done

@Lindon the older version worked fine
, but it seems also changing the plugin code didn't do it for me.

@David-Healey

@David-Healey said in Mac (Whitebox Packages) Installer issues:

You probably need to clear the AU cache.

didn't work, but I'll take a look, what I can do. Thank you

@David-Healey Thank you so much, now its finally working.
The only issue now seems to be a weird logic thing - it says the plugin is validated, but I can't find it in the list.
Going to try to restart the Mac

@David-Healey interresting - still not working
I'm using a separate drive - should I copy the folder onto my desctop and try it there?

@David-Healey So I'm back. I signed the package manually (as you recommended) that worked, but the results are the same.
the installer is still broken

@David-Healey oh, that was my bad... I think I stopped the upload - reuploaded them (should be around 61MB)
and yes I signed it with the built in tool, maybe thats it - I'll try signing it manually tomorrow (today?)

@David-Healey yes I added the installer certificate to the package and
yes I did the whole process on this one machine.

some further information
I'm using a MacBook pro with MacOs 14.1.
and the old package preset by @David-Healey (which worked fine in the past on my last project)

I really hoped I wouldn't need any further help on this project but it seems like new issues keep to arrive.
I was able to codesign my files, package them and notarize the package, but there seem to be some issues with the package file.

The standalone version is damaged (mac says it has 0 bytes) and the .component and .vst3 files are converted into folders and logic doesn't want to open them.

ps. I think I saw another thread about the issue of .component files as folderes, but I couldn't find it again and I think the solution was codesigning?? I don't recall