David Knaggs
October 13th, 2015, 06:12 PM
I updated one of my editing computers to El Capitan this morning and found that it had adversely affected a very important FCP X plug-in that I frequently use. I thought I'd pass on the simple fix that I worked out, in case it happens to others who use this particular plug-in.
I noticed that the mObject Template (mObject is a 3D plug-in by motionVFX) which was in my timeline had mostly disappeared. All that was left were some lighting effects (flares) but the majority of the content was gone. All of my other mObject templates (and I have quite a few) were similarly disabled when I checked them in the Media Browser.
Restarting the computer didn't fix it. So I quit FCP X and decided to open mObject independently.
I went to Macintosh HD > Library > Application Support > mObject > mObject and opened that.
It opened correctly and all seemed to be working fine. I quit mObject and opened FCP X. All of my mObject templates were now restored and working perfectly.
It was as though I had to "wake mObject up" as a separate action after the upgrade to El Capitan.
Other than that, the El Capitan upgrade has been very smooth.
I noticed that the mObject Template (mObject is a 3D plug-in by motionVFX) which was in my timeline had mostly disappeared. All that was left were some lighting effects (flares) but the majority of the content was gone. All of my other mObject templates (and I have quite a few) were similarly disabled when I checked them in the Media Browser.
Restarting the computer didn't fix it. So I quit FCP X and decided to open mObject independently.
I went to Macintosh HD > Library > Application Support > mObject > mObject and opened that.
It opened correctly and all seemed to be working fine. I quit mObject and opened FCP X. All of my mObject templates were now restored and working perfectly.
It was as though I had to "wake mObject up" as a separate action after the upgrade to El Capitan.
Other than that, the El Capitan upgrade has been very smooth.