Logic Pro X loads Plugins everytime I start up

[BassMake]

Hello,

I have a big problem with Logic. Every-time I want to start up logic it starts with scanning all the plugins. It takes over 15 minutes to load all the 1100 plugins which isn't really convenient in my workflow. It just look like it won't cache all the plugins to only load them whenever there is a new/updated plugin. Ive tried to look everywhere to find a solution but can't really find anything related to this topic.

Is there someone who please can help me?

[Ed A.]

1100 plugins, huh?

[BDeep]

I’m afraid I don’t have the answer to that question, but, I’m sure it would improve your workflow and solve the scanning if you cut down your plugins with about 90%

Seriously, for all I know Logic just does that. Ironically despite the fact that OS X does in fact keep a cache of the AUs.

[W23]

I had the same problem a while back. I just copied and pasted the thread here because it was easier than explaining it

W23 wrote: ↑
I just bought and downloaded Logic over the weekend, and am wondering if there is any way to stop Logic from scanning every single one of my 3rd Party AU plugins (all 132 of them) at start up. It does it at every single time, and it's getting to be a tiny bit annoying. It wants to turn on my Waves NX head tracking utility at start up too. Nice gesture, I guess but, I would really like to be the one who decides when to run Waves NX


I've heard of this behavior before. It was usually either a permissions issue related to the AudioUnits cache or some old Waves waveshells not scanning correctly, so Logic gets stuck in a loop rescannning them on every launch. I would check the caches folder:

~/Library/Caches/AudioUnitCache

There should be a decently sized com.apple.audiounits.cache file in there. If there isn't or it's 0kb, then maybe something is preventing it from being written. Try deleting the whole AudioUnitCache folder and let Logic recreate it. Maybe that will fix it. Also check ~/Library/Audio/Plug-Ins/Components to see if there are multiple waveshells present, which can sometimes clash with each other. Over the years I've had to run the Waves AU reg utility to fix issues with their plugins. It used to be found in the Applications/Waves/Waveshells folder.

[sprnva]

If it doesn't scan your plugins at launch how is it going to find any new or updated ones?

All DAWs have to do this. Unless you meant validating.

[surferman]

My logic pro doesn't scan everytime I open. Only when I install new plugins. If you are constantly installing plugs, which with 1100 maybe you are, then that is why. Test by opening logic then closing and then reopen. It should scan for plugs and only load the ones listed for the current project.

You can control how many plugins are loaded by the plugin manager. Go to Logic Pro>Preferences>Plug-in Manager. You uncheck any plugins you don't want to load.

[Bombadil]

Logic will slightly hesitate when loading on my computer. 'Updating Info on plugins' or something like that. It's only for about 2 seconds, max. Then again, I don't have 1,100 plugins.

[Deep Purple]

Usually a problem with an application not saving its settings is that it can't create a cache. It might be due to permissions on the cache, or you might need to delete the cache completely and see if it saves after a reboot and starting Logic again.

If this doesn't fix it, you could try repairing permissions on your Mac

[W23]

As noted above, the same happened to me. I had 6 waveshell folders for who knows what reason in my components folder. I deleted all but the 2 most recent waveshells, and the problem was solved. I also deleted the Audio Unit Cache folder just to be sure

[BassMake]

I had the same problem a while back. I just copied and pasted the thread here because it was easier than explaining it

W23 wrote: ↑
I just bought and downloaded Logic over the weekend, and am wondering if there is any way to stop Logic from scanning every single one of my 3rd Party AU plugins (all 132 of them) at start up. It does it at every single time, and it's getting to be a tiny bit annoying. It wants to turn on my Waves NX head tracking utility at start up too. Nice gesture, I guess but, I would really like to be the one who decides when to run Waves NX


I've heard of this behavior before. It was usually either a permissions issue related to the AudioUnits cache or some old Waves waveshells not scanning correctly, so Logic gets stuck in a loop rescannning them on every launch. I would check the caches folder:

~/Library/Caches/AudioUnitCache

There should be a decently sized com.apple.audiounits.cache file in there. If there isn't or it's 0kb, then maybe something is preventing it from being written. Try deleting the whole AudioUnitCache folder and let Logic recreate it. Maybe that will fix it. Also check ~/Library/Audio/Plug-Ins/Components to see if there are multiple waveshells present, which can sometimes clash with each other. Over the years I've had to run the Waves AU reg utility to fix issues with their plugins. It used to be found in the Applications/Waves/Waveshells folder.

Awesome! it worked deleted 9 old wavesshells aswell as writing new permissions with batchmod. now it seems to work as it should be. Im very thankfull

[TSS]

I have a few plugins that are always still scanned every time Logic starts, been bugging me for a while so I will try this!

[Winstontaneous]

I have a few plugins that are always still scanned every time Logic starts, been bugging me for a while so I will try this!

Me too. I have no Waves plugs, but Logic re-scans the same 12 or 14 plugins at every startup.

[Bombadil]

I just bought 2 Waves plugins. Now, when booting Logic, it hesitates for a few seconds, wth the spinning beachball, before It runs the scanning and loading process. Not sure what I think about that.