TripleYoThreat Posted April 27, 2019 Share Posted April 27, 2019 Hi Triple, Can you specify the location you mean? If you mean the cache, then the correct com.apple/audiounits etc is in the right location and the permissions are read/write, read only, read only. And I deleted that old waves file. Don't know what else I can do... Tnx! Yes the location you deleted the old waves file from. Should be ~Library/Audio/Plug-ins/Components Where ~ is root of Macintosh HD not the user home folder. Quote Link to comment Share on other sites More sharing options...
Nellis Posted April 27, 2019 Share Posted April 27, 2019 These 2: Shakepad x64.component Shakepad.component Quote Link to comment Share on other sites More sharing options...
TripleYoThreat Posted April 27, 2019 Share Posted April 27, 2019 These 2:Shakepad x64.component Shakepad.component Okay and what about /Library/Audio/Plug-ins/VST3 Quote Link to comment Share on other sites More sharing options...
Nellis Posted April 27, 2019 Share Posted April 27, 2019 The same two but then .vst Quote Link to comment Share on other sites More sharing options...
Nellis Posted April 29, 2019 Share Posted April 29, 2019 Any ideas? Tnx!! Quote Link to comment Share on other sites More sharing options...
TripleYoThreat Posted April 29, 2019 Share Posted April 29, 2019 The same two but then .vst Hey I commented yesterday! Idk where it disappeared to! But based on those files you don't even have wavves o.O What does it say when starting up and scanning? Sslchannel n stuff? Edit: I think I used an emoji so it didn't post hah Quote Link to comment Share on other sites More sharing options...
Nellis Posted April 29, 2019 Share Posted April 29, 2019 Yes I have the mercury pack. It says it will rescan 420 plug-ins everytime I need to restart logic but after about 220 Logic opens. Does this have to do with waves?? Cause it starts with scanning the waves plugins... Tnx!! Quote Link to comment Share on other sites More sharing options...
Nellis Posted May 9, 2019 Share Posted May 9, 2019 Anybody? Should there be a waveshell or some waves file in the ~Library/Audio/Plug-ins/Components folder?? Tnx!! Quote Link to comment Share on other sites More sharing options...
Solution Nellis Posted September 5, 2019 Solution Share Posted September 5, 2019 Quick update! I called Waves helpline and they helped me out in 10min and everything is back to normal!!! :) Quote Link to comment Share on other sites More sharing options...
MasterMyMix Posted September 16, 2019 Share Posted September 16, 2019 Just to follow up - the "AU Rescan" problem has been solved, and the culprit was my recent Waves 'Mercury Bundle' installation. Seems there was an extra out of date 'waveshell' in my AU folder. I had updated to 10.0 and there was still a 9.7 and a 9.6 in the AU folder. Waves tech support directed me to leave the 9.7 alone (since it's needed for compatibility) and delete the 9.6 file -- that did the trick. No more rescans! PHEW! Now if I can just figure out how to get my new Behringer X-Touch to behave.... aargh. hello i have been seating with this mess for about four months since installing Waves 10. and it annoys all the time i load LPX. do you remember the steps to sorting this out? thanks Quote Link to comment Share on other sites More sharing options...
pcd Posted April 10, 2020 Share Posted April 10, 2020 Thanks for recording all this info, folks. I just want to add that I had a consistent re-scanning problem, and your collective work helped me get to the solution. There were a bunch of extra WaveShells in the Components directory. There was a 9.7 one, which I left (thank you, MasterMyMix), and several extra for releases 10 and 11. I have upgraded, so removed the rest except for the most recent (highest-numbered) WaveShell for 11. And I'm not sure of this yet, but my Logic sessions used to freeze, or lose the playhead, if I left them alone too long. It seems this is not happening now. Quote Link to comment Share on other sites More sharing options...
caiyuuuuu Posted May 30, 2020 Share Posted May 30, 2020 Thanks so much. Change the permission of (AudioUnitCache(folder) and Cache(folder) and .cache(file)) to ((me)Read & Write, (staff)Read Only, (everyone)Read Only), solved my problem. Quote Link to comment Share on other sites More sharing options...
Dizzi45Z Posted June 21, 2020 Share Posted June 21, 2020 Thank you everyone for your advice. This was driving me nuts!!! I was able to solve it by deleting all of my older WaveShells in my Components folder that were older than 11.0. Now it doesn't scan the plug-ins anymore. Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted June 21, 2020 Share Posted June 21, 2020 Thank you everyone for your advice. This was driving me nuts!!! I was able to solve it by deleting all of my older WaveShells in my Components folder that were older than 11.0. Now it doesn't scan the plug-ins anymore. Great! Good to hear. Quote Link to comment Share on other sites More sharing options...
Marneknold Posted July 2, 2020 Share Posted July 2, 2020 Thank you everyone for your advice. This was driving me nuts!!! I was able to solve it by deleting all of my older WaveShells in my Components folder that were older than 11.0. Now it doesn't scan the plug-ins anymore. THANK YOU !!!!!!! Quote Link to comment Share on other sites More sharing options...
sahilabbaskhan Posted August 7, 2020 Share Posted August 7, 2020 I have also been encountering this problem since a while now i am running Logic 10.5.0 and my OS is MacOs Mojave. I have 32Lives running also because i do use Sylenth1 and therefore i need a 32 bit converter. Quote Link to comment Share on other sites More sharing options...
skijumptoes Posted August 7, 2020 Share Posted August 7, 2020 Sylenth1 has been 64-bit for a long long time, Just 'check for updates' in the plugins menu itself and you'll get it. Quote Link to comment Share on other sites More sharing options...
anniebarker Posted December 2, 2020 Share Posted December 2, 2020 Just to follow up - the "AU Rescan" problem has been solved, and the culprit was my recent Waves 'Mercury Bundle' installation. Seems there was an extra out of date 'waveshell' in my AU folder. I had updated to 10.0 and there was still a 9.7 and a 9.6 in the AU folder. Waves tech support directed me to leave the 9.7 alone (since it's needed for compatibility) and delete the 9.6 file -- that did the trick. No more rescans! PHEW! Now if I can just figure out how to get my new Behringer X-Touch to behave.... aargh. Thank you, this fixed it for me as well! 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.