ray12

No, I haven't...I will try...and make a backup of com.apple.audiounits.cache beforehand 🤓 Thanks 👍

I can find the com.apple.audiounits.cache on my computer, but I can't find com.apple.audiounits.cache in ANY of my Time Machine backups. I just found in another forum the information that Time Machine doesn't back up User/Caches 😱 (https://discussions.apple.com/thread/2742503?page=2&sortBy=best) Can anyone confirm that Time Machine doesn't back up User/Caches? This would be a major flaw in time machine backups, considering that this is the file where my AU Plugins scans are stored. 😐

Perfect. That's what I was looking for. Luckily I have a time machine backup that I made just a couple of hours before the change (?) in behaviour. I'll try and find out if that helps. Many thanks, oscwilde! I can totally releate...I should maybe ditch some plugins as well. But it can sometimes be very addictive...a big percentage of my plugins is for doing "weired stuff" and have quite some character, almost one-trick-ponies. Therefore, if I want to have a variety of sound colors, I tend to think that I NEED all of them. 😅

Thanks for your response des99! Okay, that's what I also thought as well ...only the only thing that made me wondering: I was asked for the admin pw, when I moved the component files. The intstalling process was already a couple of months ago. Every single plugin was a clean an fresh install. After I managed everything to work ( I just don't want to go through that again...as I said it was laborious and painful) everthing was smooth until today ...before I started moving components (we are talking about 1.300+ component files) Where are AU Tool scans saved then? What file would I have to restore? I'm not comparing the plugin scanning/loading times to my old machine. I'm comparing the status of today in the morning (before moving the components) vs. now (after I tried to restore the status of today morning).

Hi, I have a proplem with a (corrupted?) file that is not loding. On my old system (OS 10.12.5) I would just move out all the compont files from the component folder to force Logic to load the file without plugins and then add the plugins back step by step to track dow the problem. That's what I did on my new machine (OS 13.4). However SOMEHOW Logic found the place where I moved them, and started re-scanning all Plugins from that temporary folder that I created. Result: Everything is messed up. When I built that system it took me ages to get all my plugins working, many times rebooting, disabling the Disable Gatekeeper, then rescanning, granting exceptions in the pricacy setting etc. To sum it up...it was painful. Luckily I have a timemachine backup. I restored "com.apple.logic.pro.cs" and "com.apple.logic10.plist" from this backup. Everything seems to be ok, except that Logic now takes way longer to start! First, there is a significant longer time of "Searching for Audio Unit Plugins" and then "Updating Information About Audio Unit Plugins". Could it be that Logic is still looking for plugins in that temporary folder that I created? What's going on? Any ideas? Any other files that I should re-store from my time machine backup?

Yes, I have 😕

There were some more hiccups, but those were more or less expected, and I could solve most of them. This one is still odd according to my understanding. The current status is: I accepted that I can't probably solve everything and that it would be better to focus the energy on recreating what is still missing in my templates (aka doesn't load properly into the new version of Logic) Nevertheless: I appreciate you help guys. Special thanks to Maestro777 for the patience and the useful input!

That helped indeed to eliminate some other problemes with the files. Thanks, Maestro777!! It is also my though that it has ti do with underlying changes between the old and new versions of Logic. On my old system I was running Logic 10.4.4 on OS 10.12.5 Maybe this was too much of a stretch to hope that everything would open smoothly.

You're totally right...I forgot to delete the AUX Channels from the project. Sorry about that. 😕

Hi Maestro777, thanks for your input. 1) unfortunately reinstalling didn't do the trick 2) when I reset all settings and start Logic again (which means Logic scans/tests all Plugins again), then Amalgame is not succesfully validated anymore. I took my quite a while to get Logic to validate all the plugins I'm using (sometimes they were recognized after I restared the computer one, on some cases they were successfully validated after I restarted the computer five time...for me there is no obvious pattern). Luckily I made a backup of "com.apple.logic10.plist" and "com.apple.logic.pro.cs" before trying "Reset all Settings except Key Command Assignments". 😉 When I put them back Amalgame is validated again, I can open it from the plugin menue...only it wont open in old projects. Just to explain why solving this issue is of importance for me: Amalgame Is not the only plugin showing this behaviour and I spent a substential amount of time creating templates for different scenario with a "ready" mix. When working under thight scheduls this is important. Recreating these templates means starting over again...

Hi des99, thanks for having a look at the file. I appreciate your time and don't want to waste it. This is so odd!! And and it makes me feel like a complete greenhorn (my first version of Logic was version 1.5😳 🙈) I have downloaded the file from the link that I posted (to make sure I didn' mix up the files that I uploaded). This is what it it looks like when I open the file: I noticed there is a backup in the Logic Project. If I revert to the backup it still looks the same: one track, one plugin (only the Audiofiles are still in the Audio Pool...for the saved version I removed them, so you won't have to deal with missing audio files). However I can see logic loading all the plugins that I removed from the session (like Neutron)... ...but there is still only one track and one plugin in the session like in the first screeshot from above (...also in my version there are also no hidden tracks). I have no Idea what's going on.

1) the plugin Manager says "successfully validated" 2) Correct, the file is for des99 (sorry for the confusion). The link should be fixed now. Best, Ray

Hey Maestro777 1) On the new sytem EVERYTHING (no exception) was a fresh install, and the Logic files were cloned to a dedicated new hard drive. 2) I made a testfile (it ist too big to attach to the post so I upladed the file to my dropbox: https://www.dropbox.com/scl/fi/avyc44xaz2iknf18dk7ak/Test-Plugin-not-found.zip?rlkey=j3dqy7leljtw62fupqgnnmnfd&dl=0 In the test file the plugin is Amalgame from ineardisplay, but the same happens also to A1TriggerGate from Alex Hilton for example.

To answer the questions: 1) The projects were originally created with an older version of Logic on an older system 2) "Won't be found" is maybe not the best description. The Plugins are available in the the plugin menu (under the same name as on the older system...because same installation file) but at the same time Logic treats then them like a plugin that is not available on the sytem: red "(!)" at the plugin slot and Logic won't load them.

Hi everyone! some plugins won't be found when I open projects from that were created on my old machine...although they are installed and have the same name (nothing like Ozone 8 vs. Ozone 9 which are separate plugins). On both machines I used the same installation files for the plugins in question (so they should have the same ID, shouldn't they?) Any ideas what is going on? thanks, Ray