daw ( logic ) component 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
-
I come back here to try to understand. I therefore uploaded my mac to mojave. and xcode 10.3. l exports of my plugin are going successfully. .vst3 .vst. component I sign my plugin.ok I sign my pkg. okay I notarize the pkg. okay I receive the apple validation email ... ok I staple the pkg. okay I check the notarization ok the plugin is detected as validated in "logic". my beta tester cannot find my plugin in his list. Really, I do not understand. apple m1 bigsure so i tried it another way. notarize only the pkg, it doesn't work. notarize a .zip which contains the pkg. it still does not work. sending the .au or .vst3 file directly does not work. to tell the truth, at this stage I have no idea what to do.
-
@yall Have they tried any other DAW?
-
@d-healey yes ableton also. but still the same.
-
-
@d-healey I just read that. so i would have to export with xcode 12 to be able to output an any mac version?
-
so i would have to export with xcode 12 to be able to output an any mac version?
Why Xcode 12?
-
@d-healey I just read that the universal binary export function was only available from xcode12.2. afterwards I read a little stupidly because I have the brain broken down. I am already happy to have accomplished my notarization
