Ok so when i launch my project in logic, this is the error i get. "audio Configuration is damaged" has anyone run into this before, it seems now then when i'm working in the project, logic tends to crash. especially whenever i go to adjust a plugin. It will just crash. Any ideas?
It seems to me that you have to check (and re-install, if needed) your audio interface driver. You can also check your system audio settings (in Audio Midi Setup utility: Applications/Utilities/Audio Midi Setup). Try using Built-in audio driver, if you use an external audio interface. If it works with Built-in driver, then you have to remove and then install audio interface driver again.
Also, make sure you use only stable plug-ins by checking your plug-ins in Preferences -> Audio Units Manager. If any of the instruments you currently use fail to validate, disable them.
Ok so even if i launch the program with the built in audio driver it still says that its damaged. I can open and work in other files with out issue but this project is somehow damaged. also i checked the audio units manager, and everything passed fine. Again the problem seems that if i click to adjust a pluging (reverb, eq, etc..) the program crashes.
Thanks you for all your suggestions, and please reply if you have any more, or need more detail. thanks.
That's weird. Maybe some files are corrupt indeed. Could you tell, did you create this project in LE8 or maybe in a previous version of Logic? Some ppl here report Logic crashing after loading a project created in Logic Pro 7, for instance.
Also, I'd recommend trying to open this project on other machine with Logic. If it crashes there, then it's not your setup, it's probably the damaged files. I am not sure though, as I've never experienced problems like this before. Try posting at other music production forums, this could help, cause there could be more experienced people, who may already know this issue and what's it caused by.
I'd also recommend to contact Apple and send them an archived project folder. Who knows, maybe it's a yet unknown bug, which has to be fixed.
