HELP! FCPX 10.2.2 Crashes After Publishing Motion 4 Title with Motion 5

Question

Level 3

673 points

HELP! FCPX 10.2.2 Crashes After Publishing Motion 4 Title with Motion 5

In Motion 5, I opened a Motion 4 title that I had created.
Clicked the Play button and everything looked and worked fine.
Then went to the menu File/Publish Template.
Filed out all information, but as soon as I clicked on "Publish as Final Cut Generator", the Publish button is was disabled.
Uncheck "Publish as Final Cut Generator" and Publish button became enable, so I clicked on the Publish button.
Went to launch FCPX and after about 5 seconds, FCPX crashes.
Repeated launching of FCPX result in always crashing.
Used Digital Rebellion's Crash Analyzer and it tells me that the crash appears to caused by a Motion Effect and refers to the line "2 com.apple.Motion.effect 0x000000010bf5126b __33+[FFMotionEffect registerEffects]_block_invoke + 334"
Ran the Housekeeping procedure, and deleted the template I published from the "~/Movies/Motion Templates" folder.
Tried launching FCPX and still crashes with same error reported by Crash Analyzer.

I have exhausted every methods I can think of to fix this problem, but at this point, FCPX is completely dead.

Is there some other location that the effect may be hiding, or pref file that I can delete to get FCPX working again.

I have attached a link to the full crash report in hopes that it will give someone a clue as to how I can fix the problem.

https://dl.dropboxusercontent.com/u/651698/FCP%20X%20Crash%2020151004.txt

Any help or suggestions would be greatly appreciated.

TIA

iMax 27" late 2009

Mac OS X 10.10.5

Quad G5 2.5 GHz, 4 GB RAM, 1.5 TB HDD, Mac OS X (10.5.8), iLife '09, iWork '09, Final Cut Studio2, DROBO 6TB

Posted on Oct 5, 2015 3:58 AM

Reply

Answer 1

Gary Sumlak Author

Level 3

673 points

Oct 11, 2015 12:30 PM in response to Gary Sumlak

I was hoping someone would have had some input, but alas.

I got FCPX working by deleting the project libraries, and then one at a time bringing them back from backups to figure out which library was the problem one.

Reinforces the axiom, "Before any change or edit... backup, backup, backup!!!"

Reply

Answer 2

fox_m

Level 6

13,354 points

Oct 11, 2015 5:19 PM in response to Gary Sumlak

There were several Filters available in Motion 4 that have been deprecated in Motion 5. If your project used one of these filters (like: Droste, Primatte RT, Displace, and a few others I no longer remember) that could cause problems for FCPX. If you knew the problem to begin with, all you needed to do was MOVE the offending generator out of your Movies > Motion Templates > Generators > [category] folder and restarted FCPX... you would have gotten a missing media marker where the generator existed and you could safely delete it from the timeline. Deleting project libraries was overkill.

In 99% of cases, you should be able to publish older Motion projects as Generator projects for FCPX without incident. I've converted a good many of the old templates for FCP Studio (Motion 4) for FCPX without incident. Aside from the deprecated filters, the other quick killer is setting up a project with a Font that might be corrupt. So, in determining what the root problem might have been for the crash, consider fonts along with everything else. Use Font Book to validate all your fonts from time to time. Avoid fonts with any issues even if they pass validation. Set up "generic"/neutral fonts (known validated fonts) for templates and allow the end user to select their own font for use with the template.

Reply

Answer 3

Gary Sumlak Author

Level 3

673 points

Oct 11, 2015 5:30 PM in response to fox_m

Thanks for the reply.

Del

fox_m wrote:

all you needed to do was MOVE the offending generator out of your Movies > Motion Templates > Generators > [category] folder and restarted FCPX...

First thing I tried. Sorry for not including that in the original post. As the new template was the only template in the Motion Templates folder, I deleted the entire folder. FCPX still crashed. It was not until I deleted the project that I was able to launch FCPX again. But I will add your suggestion to my trouble shooting list in the future.

Thanks

Gary

Reply