Vst not working on MacOs Big Sur

[Inreachent]

All My Plugins Work

[d.healey]

I have a customer who is having an issue running one of my codesigned/notarized plugins in Logic 10.6.1 on an M1 system running Big Sur. He's saying the plugin doesn't show up in Logic's plugin list. Any ideas?

[Lindon]

@d-healey is the plugin coed unique? (FILE>Preferences>Project>Plugin Code)Logic is the only DAW I know of that insists every plugin has a unique ID.

[d.healey]

@Lindon It's unique among my plugins...

[d.healey]

Oh it's working now, must have been user error ;)

[yall]

@d-healey how did you manage to make a .componant work in logic with mac m1? for my part it is impossible, only the .vst works, when you speak of unique code that does it mean?

[d.healey]

@yall

how did you manage to make a .componant work in logic with mac m1?

I don't know if my customer is using the AU or the VST.

unique code that does it mean?

Each plugin needs a unique code that you set in the project properties: File >> Preferences.

[yall]

@d-healey yes the Abcd code .. each plugin has its own code like Bght for example ... it does not seem to me that logical load the .vst c is for what I ask. j had sent notarized plugins to a mac m1 logic user but not found in logic. I had read on forums and somewhere on another apple developer forum than the. component must be extracted with the universal binary option of xcode. but this option is only available on xcode 12 it seems to me so I gave up. what version of xcode do you have? damn mac m1 ^^

[d.healey]

@yall I think I'm using 10.3

[yall]

@d-healey ok so we have the same system. do you know the manipulation that your user has to do to make it work? I can conclude that this story of compiling with the universal binary option is ultimately useless

[d.healey]

@yall He didn't say that he did anything special, he just restarted Logic and the plugin showed up.