![]() ![]() One person did write back to me that they were on a 2013 Trash Can so perhaps older systems on Mojave are more prone to the crash. I still want to know what the constant is for those of us having the issue though. So yeah- this dot one release was a deep one! One thing I did find was that a few people mentioned Logic hanging on plugins I am familiar with that are in fact 64bit, like Sinevibes Strobe 2. I considered the 32/64 bit thing As well and while that’s possible, Logic’s AU manager never had issue ignoring non-compatible plugs in the recent past but, maybe that’s where your “strict plugin scan” theory comes into play. Nobody seemed to have my issue but everyone had an incredibly long wait for the scan to finish experience.įor some, one plug-in was hanging up and for others, a group were and for me, it was the validation splash page for deactivated plugins living on my iLok. It’s possible- but the only constant I gleaned from all the cases I read or interacted with was that we were having different versions of a similar problem. ![]() I run Logic on a late 2017 MBP 2.9GHz i7 w 16gigs RAM running OSX.14.6. But I wanted to see if the machines affected were older (like mine.) I sympathize with them freaking out with projects due etc. I was trying to get a consensus on the Apple forum as to what machines people were using but most of them did not answer me. I finally just removed the 10.5.1 app and replaced it with the 10.5.0 and now, Logic 10.5.0 works fine on my machine. ![]() (BTW, someone on the Apple Forum said this process worked for them.) I tried that a second time and it ended just as poorly. That looked promising until Logic finally finished the scan and then. I then tried removing the cache file (Library-audio-cashes-audio unit cashe) to force Logic to re-scan. I have never seen that happen in Logic X before.)Īnyway, I tried temporarily removing all my AU plugins from the Components folder yet the Trial dialog still appeared. And the wait time between these pages was around 2-4 minutes between so, that was annoying. Even though the plugs were deactivated and in some cases, even hidden in the iLok manager, Logic still wanted to validate them. (To be clear, the validation dialog was asking to try, buy or quit whatever plugins via iLok. In my particular case Logic said it needed to scan 6 plugins (which it did not seem to do.) Instead, I kept getting validation pages for a bunch of trial plugins long deactivated on my machine. Especificaciones Prueba gratuita Comprar Requisitos del sistema macOS 12.3 o posterior 6 GB de espacio libre para la instalación mínima o 72 GB de espacio para la instalación completa con la Biblioteca de Sonidos Requisitos del sistema para Logic Remote iPad: iPadOS 14.0 o posterior iPhone: iOS 14.0 o posterior iPod touch: iOS 14. Logic basically will not start no matter how many times you try. Logic seems to want to scan the AU plug-ins but then just crashes. In short, for some Mojave users, Logic 10.5.1 crashes after a prolonged AU scan period. There's now more than a few desperate posts echoing what I went thru this morning. Well, take a peek at the Apple Logic X forum. ![]()
0 Comments
Leave a Reply. |