Vst not working on MacOs Big Sur

[DanH]

@nesta99 The App is in Beta for @d-healey's patrons only... But he will release it for everyone soon I think?

[Sawer]

@DanH Oh great!! Got it!! So that app will codesign your vst? If I got it...

[d.healey]

@DanH said in Vst not working on MacOs Big Sur:

Haven't got my head around codesigning yet, but it is what we set in the project settings menu in HISE?

I don't think setting things in HISE will make XCode sign your apps automatically (but I could be wrong) I think you still have to go through the commandline or do some other tweaks in Xcode.

@DanH said in Vst not working on MacOs Big Sur:

But he will release it for everyone soon I think?

Some time next year once it's out of beta. Basically when it's been tested and bug fixed a bunch of times.

@nesta99 said in Vst not working on MacOs Big Sur:

So that app will codesign your vst? If I got it...

It doesn't do the codesigning, it just runs the commandline in the background to do the codesigning for you. You just need to fill in the boxes with the correct details and it will handle the technical stuff. You'll still need an Apple Developer account to notarize.

[Sawer]

@d-healey Great!! Thanks ! I think the best thing to do for now is to downgrade to Mojave..

[Lindon]

@DanH said in Vst not working on MacOs Big Sur:

@Lindon Thanks, I've got @d-healey 's app. All my plugins are working in Mojave and Catalina so far. Haven't got my head around codesigning yet, but it is what we set in the project settings menu in HISE?

No. You will have to do it for each app/plugin individually once you've compiled and tested them ready for shipping.

There are many posts here - even one where I document my process :

https://forum.hise.audio/topic/3247/notarisation-for-dummies/4

You should understand what this is for/about so I suggest you read this thread - yeah all of it:

https://www.kvraudio.com/forum/viewtopic.php?f=33&t=531663&hilit=codesign

[DanH]

@Lindon looks like the kids are taking a back seat over christmas then! :face_with_tears_of_joy: :santa_claus_light_skin_tone: (joking)

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