daw ( logic ) component problem
-
In your project preferences you can set the plugin code. You should also fill in any other relevant fields, like company name, etc.
-
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 -
@d-healey
feedback from my tester friends, still the same problem. logic validates it, but does not open it. must my user install rosetta? -
@yall said in daw ( logic ) component problem:
@d-healey
must my user install rosetta?I don't know anything about rosetta sorry.
-
@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.
-
I can run my plugin without any problems on m1
-
@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?
-
xcode 10.1 could that be the problem?
Maybe, according to Apple any version from 10 should be fine, but I use 10.3
-
@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 ^^
-
@yall xcode 11 will almost certainly not work.
-
@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-healeyI'm assuming that the code you have used ISNT "Abcd" because thats not gonna work pretty much every time..
-
@Lindon it was for the example. my code is "Cebp"
-
@yall - well thats not your problem then. Looks like its the M1 situation...or the wrong version of XCode...
-
@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
-
@yall well I think Catalina is a bad idea - Mojave is a better bet.
-
@Lindon i will try mojave :)
-
@yall yes i compiled plugin on m1 and xcode 10.3
-
@arminh but how can I make my plugins compatible if I don't have a mac m1?
-
@yall you don't need m1 to build plugins for this silicon. M1 use Rosseta 2 to handle intel based apps.
-
@arminh so i don't understand my problem ... my vst works under catalina but not Bigsur. I will try again with mojave and xcode above version 10.1 to start. the notarization has been validated. I have a doubt about the id of the vst bundle which is different from that of the pkg but I see no solution at my level
