Also eagerly waiting for the Sibelius 7 tutorial. Please do what you can to speed things up about that. Otherwise you guys are great and happy to have found you. ;)

Hi! I´m not really sure where to post this issue so forgive me if I´m all wrong here. I have a very annoying problem I hope somebody out there can help me with. I recently upgraded my OS to Mountain Lion and soon after that I installed Logic X (very cool). The thing is that now when I open up a project Logic starts scanning all my plugins everytime (even though the popup window assures this is a one-time action). Since I have quite a few plugins this procedure takes a lot of time. Also when I launch Logic 9, the same thing happens. This didn´t occure before. Why is this and more importantly - how can I escape this scanning?? I have been searching the internet of course for suggestions but haven´t found anything of value for me. Please help me out if you now anything about the matter. I would be soo greatful. =) (I have an iMac 10.8.4 with the latest Logic X, 12GB RAM, 2,93 GHz Intel Core i7)

@logicluvva Thanks for answering. Unfortunately that doesn´t help. I have "Novation 61SL MkII" keyboard with Automap v 4.5.0. I set the settings to "Use Logic 9 64Bit Plug-in Friendly Audio Units". I also disabled the plugins manually in the checkboxes (Software Setup). Still, everytime I open a project - the same timeconsuming scanning process begins. This is happening also when I launch Logic 9 aswll as Logic X. What on earth can I do more? This is the only forum I can think of... Regards Tom

Thank you for replying Christian..appreciate it. =) Well, unfortunately Logic X (and 9) still insists on making the "Scanning Audio Units" ritual on all my AU units (as I understand) everytime on start up (oddly the number of them varies from time to time. My AUs are all located as you pointed out in the HD Library>Audio>Plug-ins>Components. In Audio>Plug-ins - I also have the VST and VST3 folders with many of the same plug-ins (but with .vst and .vst3) as in Components. I guess this is as it should be... I also tried as you suggested deleting the AU cache file, without luck. I can´t understand what this can be about. It seems I´m trying everything now. I didn´t have this problem before the Logic X installation, so that must be a lead someway I guess. I also tried to change settings within my Automap...just allowing to use the 64 bit plugins to scan. I made a new "software set-up" etc. Do you have any suggestions from this point? Regards Tom

Anyone? Please help me out. This constant Sanning Audio Units procedure every startup is still going on. I am really trying everything I can come up with. Deleting cache-files and removing some plugins that might have been the cause. Still Logic insists... It is like it don´t remembers that a scanning has already been made. It seems that the problem might be then with the cache. I think it maybe might be an idea also to reinstall the "auvaltool" but I don´t really know how to do that. I´m really sad about this because I was so exited about starting to explore Logic x. Now all my projects have to be on hold. :( Does anyone have any suggestions at least to where I can turn to with this problem? There is no way Apple Logic Forum helps me out I´ve discovered... By the way...how do I re-install Logic x? Does anyone know? I thought I might try that too to be sure... I can´t just download it again from the app-store obviously. It says it is installed already of course - so do I then have to un-install somehow and download again? Don´t want to pay for it once more that´s for sure... ;) Please help me...

@Gary: You are my hero right now. Huge thanks my friend! This forum is great in so many ways - I feel I really am among the "pros" and use the site for huge amounts of self-studying. The tutorials are fantastic help-tools. Keep ´ em coming please... ;) I actually suspected this idea that you inform me about. Due to other problems I needed to unisnstall my newly installed OS Mountain Lion system "backwards" (with the awesome help from my precious timecapsule) and go back to 10.6.8 and thus loose Logic x for a while since it requires Mountain Lion as you all know. Once in the "old" system, I removed all my 32 bit plugins and put them all in a folder I named ("components - disabled") on my desktop...also VST and VST3 ones. I then deleted all suspicious plug-in components from their original places in the HD library - you could say I did a cleaning up process. I realized I simply had to "sacrifice" many of my third party plug-ins but decided I would rather do that and update/install them later on one at a time... So, I then re-installed the whole Mountain Lion OS and a bit nervously launched Logic 9. Of course Logic did it´s first Audio Scanning process as usual. But the next time I opened i, everything was clear and working as it should - without 32bit plug-ins. I updated som 32bit software to 64 and there was no problem scanning them properly just once. I then re-installed Logic x (from the app store - no double charges of course) and a bit nervously again waited for the launching to take place - but everything was all fine there to my great joy. A bit time consuming maybe, but still - this I guess is the way to go if you encounter problems like this. Not necessarily going back and reinstalling OS of course as I needed to do, but to clear your "components" folder of "suspicious" plug-ins. Later on you can install them back if you want (no 32 bit though) one at a time and check out if problems arises. ;) Once again - huge thanks for replying and helping me out! All the best, Tom

Does anyone know if it is possible and how you re-install Logic X? I have huge problems with the "Scanning Audio Units" - procedure everytime at each startup (also in 9). I have been trying to throw cache away...removing plug-ins but with no result and I´m really frustrated now. Maybe a reinstall can help in some way...the au validation tool might be corrupt or something. This problem wasn´t around before upgrading to Logic x. Please please help me if you have the slightest idea of what I can do.

Hello Rounik and thank you for replying. It turns out that this Audio Scanning problem actually does not has to do with Logic X. I had upgraded my OS to Mountain Lion just before buing Logic X and after that, my problem began. The "scanning audio units process" takes place on each start-up of a project - in Logic 9! I had to make a reinstallation of Mountain Lion OS (after having temporarly gone back to v10.6.8 via time capsule) and thus now, at the moment I don´t have Logic X installed, but will download it again as soon as my problem get fixed (I really hope it can...). Any suggestions on how I can go about this strange behaviour? What can it be? Regards Tom

Thanks alot for this. Very helpful and informative. Will be my next buy as soon as I get the cash after upgrading to Logic x. :)