2 Replies Latest reply: Feb 20, 2014 4:52 PM by chappa-ai
chappa-ai Level 1 Level 1

Motion 5 has just crashed for the 3rd time this evening, either by inept Apple code writers, taxing the application's upper limits, or a combination of both.  For each crash, nothing special was occurring - simply zooming in or out of the canvas, then the application terminates.  I'm currently at 2000 frames for a series of sequential effects.  Due to their being sequential, I'm wondering if maybe instead I should break them down into smaller segments to be exported separately to FCPX for compositing.


Edit:  Make that 4 crashes.  Simply turning off the Outline on a shape after posting this question caused yet another crash.  And I paid money for this application....

MacBook Pro, OS X Mavericks (10.9.1)
  • jeremy_v Community Specialists Community Specialists

    Hi chappa-ai,


    Thanks for visiting Apple Support Communities.


    If Motion 5 is quitting unexpectedly, the steps in this article can help with troubleshooting the application. I recommend starting with step 2:


    Motion 5: Troubleshooting basics



    Best Regards,



  • chappa-ai Level 1 Level 1

    Thanks, but I'm already on OS X 10.9.1 (was pre-requisite for downloading from the Apps Store), have 8 GB of RAM, have a supported AMD Radeon HD 6490M graphics card with 256 MB of RAM, and 391.66 GB of free disk space.  The system should be more than capable of handling the small project I'm working on.  Motion 5 is the latest version (5.1), just downloaded from the Apps Store last weekend.  Everything else on that list is either already up to date or isn't applicable (not being used).  The crashes stopped after I reduced the size of my project file, but now I get to composite separate Motion-created effects in FCPX instead of simply importing one movie clip.  I really don't get how a project with only 2000 frames (small, in my opinion) with limited behaviors and filters can so easily bring an alleged sophisticated application so quickly to its knees.