Final Cut Pro X - Error... "Incompatible Audio Units Found"

Hi,

I have this exact same problem. I kind of tracked it down (well, the cause, not the solution) to the Automap client AU that is needed to use Novation's Automap with my Remote Zero SL controller.

For me, temporarily moving the Automap plugin out of ~/Library/Audio/Plugins/Components (to somewhere safe) was enough to get FCP working normally again. Unfortunately this is far from a solution as once I put the Automap plugin back where it should be, the problem with FCP comes back. I can see that while booting, FCP keeps invoking the AU validation tool for all the plugins that Automap is trying to map to. There's obviously some incompatibility going on. I'm running Mountain Lion (10.8.2) and the latest build of FCP (which I'm not about to boot to find the version number....for the reasons above 😟 )

I use Automap for audio work all the time. To have to 'disable' it in this rather crude way every time I need to boot FCP is no good at all.

Be interesing if you have the same plugin installed.

Cheers,

Neil

Yeap same problem here running on a deadline and have automap 4.4 FCPX 10.5 on OSX 10.7.4

loaded an adui plug to a track no response loaded it again and crash ive had to go in delete the video that has the plugs on it with scrub turned off no i have to re create the edit, very painful. Clearly its the Third Party plug/wrapper problem. Im going to ununstal auto map till i finish this project. my only solution

Stu

I too have the same problem: Automap 4.5.0 and FCP X 10.0.6. I have no reason to suspect that the slight nuisance has actually produced any real problems. FCPX just crashes on its own without any help from a third party:-) No, seriously, my project does suffer from crashes and other problems (long loading times, of up to 40 minutes when the diskhappens to become selected in the events browser) but it has become too monstuously large to still be practical (1,5 TB of video in 40+ events and 20+ projects). Again, I have no idea whether or not the Automap issue actually contributes to the problems. I would therefore be interested in any subsequent posts in this thread. Thanks. Happy Editing to you all. H.J. Lirb

Time to archive some projects methinks!!!

Load times are a bit of an issue. 7 looked like it was quicker?

Archiving projects would certainly be a good idea. Unfortunately, I am editing a project which is the collaborative effort of a host of volunteers who made hundreds of shots spread across events that need to be kept available throughout the editing process. So, yes, we are pushing the application past reasonable limits. Still, the project is good fun.

As an experienced editor (Media100, FCP4-7, Premiere Pro), I would have been happier to have been able to continue along the FCP7 path. FCPX is not my cup of tea, apparently, even though, by now, I have become rather familiar with the application. FCP7 was quicker, more stable (yes) and gave me infinitely better control. Or at least a much better "sense of control" so as not to offend any supporters or fans of the new application. So that's just my personal opinion.

But I must admit that it is impressive to see how easy and enjoyable Apple has made it for even absolute beginners in video editing to put something decent together without much explanation or training. I have seen this with a few of the volunteers I am working with on this project. FCPX certainly has its merits, therefore, but you are absolutely right in your comment. We must try to keep our active (and actually mounted) "Final Cut Projects" and "Final Cut Events" folders small, setting aside those which do not necessarily have to be available in separate "parking" folders. For the next project (in general language, not FCPX jargon), I will bear this in mind myself. Cheers.

Best Regards, Huib