Eric Cardenas Posted February 10, 2010 Share Posted February 10, 2010 I seem to have a problem. Suddenly my AUPitch plugin stopped validating due to a Component Version mismatch??? Any one care to dig in? Quote Link to comment Share on other sites More sharing options...
n6smith Posted February 10, 2010 Share Posted February 10, 2010 Maybe a Logic cache issue as discussed in http://www.logicprohelp.com/viewtopic.php?t=53422 ? Just a thought even though this was in regards to something else relating to Logic... Also, have you tried to replace the plugin with the original from your LP9 install files? Quote Link to comment Share on other sites More sharing options...
Eric Cardenas Posted February 10, 2010 Author Share Posted February 10, 2010 Maybe a Logic cache issue as discussed in http://www.logicprohelp.com/viewtopic.php?t=53422 ? Just a thought even though this was in regards to something else relating to Logic... I'll try that. Also, have you tried to replace the plugin with the original from your LP9 install files? Hmm... isn't the AUPitch part of the OS? The problem is that I'm unable to find it. I've searched everywhere, including the System Folder but I can not find it? I thing its inside the CoreAudio plugin but I can't really locate it. Quote Link to comment Share on other sites More sharing options...
Eric Cardenas Posted February 10, 2010 Author Share Posted February 10, 2010 Maybe a Logic cache issue as discussed in http://www.logicprohelp.com/viewtopic.php?t=53422 ? Just a thought even though this was in regards to something else relating to Logic... I'll try that. Nope. Seems those caches are just for Graphics. I tried another user and it's the same thing. That means it something global. Quote Link to comment Share on other sites More sharing options...
n6smith Posted February 10, 2010 Share Posted February 10, 2010 I've found a thread relating to this issue... basically reporting the same issue as yourself. http://discussions.apple.com/thread.jspa?threadID=2319565&tstart=90 Also I noted that OS X update 10.5.6 contained the following - Core Audio and AU component version mismatch fix so maybe something went FUBAR again? Oh, and yes, aupitch is part of the OS.... Quote Link to comment Share on other sites More sharing options...
Eric Cardenas Posted February 10, 2010 Author Share Posted February 10, 2010 Ok... It seems that something was wrong with the with the resource fork. Mended the problem by replacing the CoreAudio.component with the same file in my Studio computer. Strange stuff... Quote Link to comment Share on other sites More sharing options...
n6smith Posted February 10, 2010 Share Posted February 10, 2010 Strange stuff... Very odd.. and it is not just you that has had this issue it seems... Anyhow, good to hear you found a fix at least..... Quote Link to comment Share on other sites More sharing options...
Eric Cardenas Posted February 11, 2010 Author Share Posted February 11, 2010 Odd indeed. I found a few apple discussions but none with a solution. It's kind of tricky to get the permissions right but I managed correct them with a program called BatchMod. Thanks for your help. Quote Link to comment Share on other sites More sharing options...
shrinkie1964 Posted March 5, 2010 Share Posted March 5, 2010 EricBradley, i brought this very issue up in the Apple Logic forum and got no bites. We got the exact same error output as you. Getting another CoreAudio.component file from another computer with a Logic installation without the validation issues was our solution too. This is peculiar, inasmach as the "good" and "bad" files seemed to have identical time and date stamps. At any rate, we are relieved that Logic Pro opens on my friends MacBook without the screeching warning, and that she can keep all AU plugins checked. She may never have any use for AUPitch, but that is not the point. Things should just work! 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.