If I had the option to upgrade the laptop to Mojave and 10.5 I would do it in a minute.Ĭlick to expand.Hi BEAT16, i tried both of your posts. I only have one Abberant plugin and it is ShapeShifter. And I hate it for everything other than mixing. My Pro is like this, it can only run Logic 10.4. These machines need a graphics card upgrade in many cases, before they can be updated to Mojave. If they are not coded to run on High Seirra the main difference between it and Mojave are "METAL" support. I am wondering if it has something to do with Aberrant's GUIs actually. Logic Plugin Manager will just not see it. I have had to, so I know it's possible but it's a pretty remote occurrence. You should never need to code sign a purchased piece of software. It's more like keep them, move them out of the way, and then Add Them Back one at a time.Īlso, when you purchase something it should already be signed. Your approach is much easier than having to re-download everything. You can also just move the entire folder and rename a new one so it replaces the older one. You just move them out of the folder, because they are not system kinds of files like. (I don't really know or care why)īatChmod: on MacOS you do not need to remove plugins. Once in a great while Permissions Reset will fix something which BatChmod does not fix. I would use BatChmod, not Permissions Reset in almost every case. Try using OSX Validate All AU's utility to force validation of the ones which are not showing up. I really hope someone on this forum can provide some help to solve my problem. I tried to search for my problem on other websites. It seems to be a global Macos problem, because the plugins also don't run in other DAWs. I also have some new Mac systems in my studio - but this is my homestudio setup and its still very important for me. Im using an older Macbook Pro End 2013 - still on MacOS Sierra 10.12.6 - Logic Pro X 10.4.4 - I don't want to upgrade this system because there are some older plugins which im still using - which won't run on new systems. So i won't be able to use the older still working plugins too. Because i'm afraid that it will kill every single plugin. The only thing i did't not try was to delete the plugin cache and do a complete rescan of all my plugins. I tried a "Permissions Reset" on severeal. I tried to install the plugins in SafeMode. I tried it with disabled SIP via the csrutil command. In Steinberg Wavelab 9.5 the newly installed plugins don't show up either. In Logic Pro 9 i'm getting the same error. But if i try to rescan a working plugin, i get the same error and the plugin is unusable. VALIDATING AUDIO UNIT: 'aufx' - 'SCii' - 'Abrn'įATAL ERROR: OpenAComponent: result: -1,0xFFFFFFFFĮvery single plugin has the same error message "-1,0xFFFFFFFF" and "couldn’t be opened".Īll my other plugins which are installed for years now - running perfectly. Validating Audio Unit SketchCassette II by Aberrant DSP:Ĭopyright 2003-2013, Apple Inc. If i try to "reset & rescan" a plugin for example SketchCassette II - i am getting the following message: Unfortunately every single of those plugins had the exact same error message in Logic's Plugin Manager "couldn't be opened". Installed them and tried to use them within Logic Pro X. I've just purchased some new plugins at Pluginboutique. I've never had an error like this before. I got a strange problem in Logic Pro X / Logic 9 and also in Steinberg Wavelab.
0 Comments
Leave a Reply. |