daw ( logic ) component problem

[yall]

Hello, after weeks and weeks of waiting for a reaction from apple, I finally got to notarize my vst instruments. everything went successfully.
I therefore send my vst to a friend equipped with the latest mac M1 bigsure.
he opens his daw (logic), and logic finally recognizes my vst as validated.
the problem is that it does not appear in the instrument list when you want to load one into your project. it is present and valid in the plugin manager.
What can be the problem? I sent him a PKG signed with 1.vst and 1.component (both are signed and the pkg notarize and staple).
i am with the last scriptnode branch of christoph.
little recap, notarization ok (yes I'm happy to say it ^^), logic recognizes but cannot open it because it is totally absent from the list of instruments.
thank you;)

[d.healey]

@yall Did you set the plugin code?

[yall]

@d-healey how to do this please? I simply exported and followed the notarization procedures

[d.healey]

In your project preferences you can set the plugin code. You should also fill in any other relevant fields, like company name, etc.

[yall]

I just realized that I was missing a "in my command line to staple my pkg.
the problem must come from there.
yes I used to do all the steps during a new project. Abcd, name, website ...... I thought it was another code system I'm not sure ^^ but in the end everything was fine. I await the return of my beta tester. thanks @d-healey

[yall]

@d-healey
feedback from my tester friends, still the same problem. logic validates it, but does not open it. must my user install rosetta?

[d.healey]

@yall said in daw ( logic ) component problem:

@d-healey
must my user install rosetta?

I don't know anything about rosetta sorry.

[yall]

@d-healey OK thanks anyway. I will wait to see if someone has managed to run their vsts on the new m1 processors without any problem.

[arminh]

I can run my plugin without any problems on m1

[yall]

@arminh you compiled it with the mac which has the m1? i have osx high sierra and xcode 10.1 could that be the problem?

[d.healey]

@yall

xcode 10.1 could that be the problem?

Maybe, according to Apple any version from 10 should be fine, but I use 10.3

[yall]

@d-healey I'm going to create a publication with mojave and x code 11. we'll see. but it is boring. I always have weird things happening to me ^^

[d.healey]

@yall xcode 11 will almost certainly not work.

[Lindon]

@yall said in daw ( logic ) component problem:

I just realized that I was missing a "in my command line to staple my pkg.
the problem must come from there.
yes I used to do all the steps during a new project. Abcd, name, website ...... I thought it was another code system I'm not sure ^^ but in the end everything was fine. I await the return of my beta tester. thanks @d-healey

I'm assuming that the code you have used ISNT "Abcd" because thats not gonna work pretty much every time..

[yall]

@Lindon it was for the example. my code is "Cebp"

[Lindon]

@yall - well thats not your problem then. Looks like its the M1 situation...or the wrong version of XCode...

[yall]

@Lindon I will try an update to catalina and x code which works. Could the problem be that ipp is activated and the M1 does not want this? I try to eliminate the hypotheses because mrs vst of course work the other macs

[Lindon]

@yall well I think Catalina is a bad idea - Mojave is a better bet.

[yall]

@Lindon i will try mojave

[arminh]

@yall yes i compiled plugin on m1 and xcode 10.3