bigramp Posted November 15, 2018 Share Posted November 15, 2018 Hi It seems since Mojave i have to restart my computer each time i install a new plugin, otherwise Logic Pro won't catch the new one.... Is this a bug ? is there a fix ? thanks Quote Link to comment Share on other sites More sharing options...
uncleozzy Posted November 15, 2018 Share Posted November 15, 2018 I have this problem in High Sierra -- I was told it was fixed in Mojave, but it seems like maybe not. In High Sierra, at least, killing AudioComponentRegistrar before you open Logic seems to get the scan to run normally (this was suggested to me on another forum, and it did work when I tried it). So, open Terminal and run: killall -9 AudioComponentRegistrar Quote Link to comment Share on other sites More sharing options...
xgman Posted November 15, 2018 Share Posted November 15, 2018 Only certain plugs will make you log out to see the plug in LPX. Not sure what the new coding is that makes them appear without that, but there are still plenty of plugins that require a log out/in in Mojave. Quote Link to comment Share on other sites More sharing options...
kevaquarian Posted May 14, 2020 Share Posted May 14, 2020 I have this problem in High Sierra -- I was told it was fixed in Mojave, but it seems like maybe not. In High Sierra, at least, killing AudioComponentRegistrar before you open Logic seems to get the scan to run normally (this was suggested to me on another forum, and it did work when I tried it). So, open Terminal and run: killall -9 AudioComponentRegistrar Hello. I found this thread while trying to find out the location of the audio units cache in Mojave. Do you happen to know if this "component registrar" file is the new "com.apple.audiounits.cache" counterpart in Mojave? I don't see the previous cache file since installing Mojave? Thanks! Kev Quote Link to comment Share on other sites More sharing options...
des99 Posted May 14, 2020 Share Posted May 14, 2020 No, it's the process that monitors for plugin changes. A behaviour change or bug since High Sierra onwards means sometimes you either have to reboot, or restart the AudioComponentRegistrar process to notice newly installed plugins. Quote Link to comment Share on other sites More sharing options...
kevaquarian Posted May 14, 2020 Share Posted May 14, 2020 Hello again. OK - I found it - it is the same name as before - "com.apple.audiounits.cache". Must have missed it somehow, earlier - doh! So now I'm wondering what the purpose of the "componentregistrar" file is?! I've not come across this one before... Quote Link to comment Share on other sites More sharing options...
kevaquarian Posted May 14, 2020 Share Posted May 14, 2020 No, it's the process that monitors for plugin changes. A behaviour change or bug since High Sierra onwards means sometimes you either have to reboot, or restart the AudioComponentRegistrar process to notice newly installed plugins. Hi. Thanks - sorry, I was typing my previous message when your reply must have come in! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.