Previous 1 2 Next 27 Replies Latest reply: Feb 11, 2013 4:38 PM by rcneveu Go to original post
  • zaphod42 Level 1 Level 1 (20 points)

    NOTHING works for me ... not even downgrading to 5.0.2.

    after spending endless hours to figure out what the **** is going on ... out of work!

    and no one to contact at Apple to get some serious support!


    what is left to do? get the competitor's product to finally work again? after all these years working with Motion? learning a new software or hoping for some kind of miracle that Motion starts up again?

  • zaphod42 Level 1 Level 1 (20 points)

    wait .... I tried an advice that I found in this forum to use a different user ... and Motion started up without crashing !?!?!!


    so there must be a conflict in my home-directory that Motion 5.0.5 keeps crashing? what could that be?

  • rcneveu Level 1 Level 1 (0 points)

    So Apple has just released udates to FCP X, Compressor, and Motion, that are bug fixes. I'm out of town and can't update till Saturday. If any of you have a chance to try out the new update (Motion 5.0.6), let me know how it works out.


    Thanks everybody!


  • Eisen Feuer Level 1 Level 1 (20 points)

    I upgraded to 5.0.6 and it crashes every time in the same way for me.  I had to Time Machine back to 5.0.4. to get it working again.

  • rcneveu Level 1 Level 1 (0 points)

    Yep, I just tried the update 5.0.6, and it crashed upon launch the same as 5.0.5. Gone back to 5.0.4.

  • dpcam1 Level 1 Level 1 (0 points)

    Hi there...I had lots of problems with FCPX and Motion after the latest updates so I did a clean install of Mountain Lion and then a reinstall of both programs. FCPX certainly behaved better. Motion had a bug to do with using dual monitors, which wasn't improved by the clean install.

  • Arthur Bell Level 1 Level 1 (120 points)

    I agree - the bug, unresolved has something to do with mulit monitors, ( so you chooes to use the other setups ' second display, etc) ) but i wonder if itis aslo related to when multiple projects being able ot be open at the same time also is at fault - as thats when it first appeared for us. 

  • Russ H Level 6 Level 6 (18,480 points)

    I noticed from your original post that you have FCS 3 on your system and wondered whether you've followed Apple's installation recommendations for having both versions on the same partition…including that part about opening M4 first and then closing.


    In my case, I've had the occasional issue with the new apps, but never anything as chronic as your situation – all the while continung to run the FCS 3 apps on the same partition. Typically, a reinstall (of the new apps) and repair permissions has been the solution to any woes.



  • dpcam1 Level 1 Level 1 (0 points)

    I'm still not convinced they've fixed the dual displays issue. It seems to me that after I put my timing pane on the second monitor, do some work, save, then close Motion, that on opening up the program later Motion hasn't retained the setting for the timing pane on the second monitior. At least the option to extend it out again is still there!!!

  • zaphod42 Level 1 Level 1 (20 points)

    after I discovered that Motion starts up normally by using a different user, I followed Jim Wanamaker's suggestions that I got in another thread to create a copy of my user folder and with this new user to start deleting files and/or folders in the ~/Library until Motion would probably start up.


    I promise this is the very last time I would go through all of this and after endless hours&hours&hours&hours spent to find that culprit .... I got him!!!

    it was a single smart font collection I created a while ago with Font-Book ... just this one particular deleted and Motion 5.0.6 started up again and seems so far useable again ... hallelujah!!!!


    so if anybody has a similar problem, start looking for a culprit here:



    start deleting one after the other either through Font-Book or in that folder to get that loved Motion back to do its job (and I hope it will stay that way!)

  • vinegarman Level 1 Level 1 (0 points)

    Is anyone still having crash prblems or have these all been resolved?

  • Arthur Bell Level 1 Level 1 (120 points)

    I am NOT experiecing this spercific problem any more. And as there been no OS or Motion updates I assume cleaning out my 'smart collecitons' ( which i see some of these Apple installs so whats the deal there?) did the trick so i appreciate that tip.


    In general our comapny is VERY releiant on Macs. We are experiencing more crashes across the board - from the apps - Motion, Adobe, to the finder, to permission problems, the lack of class they exhibited moving from Final Cut Pro to final cut toy, lack of graphics power,  lack of thunderbolt proliferation or support  etc., etc.,, that no matter what we do - A. most issues were never here, and now B. seem pretty persistant.


    The rumor I heard from inside Apple but with nothing to back this up is that Apple has steered the majority of their developer teams to iOS and they steadily abandon the 'pro apps' and the desktop as a platform in general without the vision and attention to detail they once had.


    IOS apps have their place are fun and nice quick bucks but they will never do the whole the job in the real world.


    Sorry for the digression.

  • rcneveu Level 1 Level 1 (0 points)


    Had no time to test any suggested fixes for awhile, but I now have the latest version of Moion running (5.0.6), without any crashes.


    What I did was:


    1. Trashed the .modulelayout files in: User/"Hidden" Library Folder/Application Support/Motion/Layouts,


    and in: User/"Hidden" Library Folder/Application Support/Motion/Layouts/Modified


    2. Trashed my Motion Preferences


    3. Moved all Font Collections out of: User/"Hidden" Library Folder/Font Collections, to another folder to sequester them.


    4. Ran AppStore and updated form Motion 5.0.4 to 5.0.6.


    It worked, and has for 5 days now without crashing. And I have since replaced all Font Collections to: User/"Hidded" Library Folder/Font Collections, and Motion 5.0.6 still is running without crashing.


    This leads me to believe it was the .modulelayout files. I thought I had tried that previously after reading one of the replies, but perhaps not.


    This "Hidden" Library folder can be accessed by option-clicking on the Finder Go Menu, and selecting Library.


    I hope this helps some people.





    Message was edited by: rcneveu

Previous 1 2 Next