Skip navigation

URGENT: Motion Downgrade crashes too??!!

1390 Views 18 Replies Latest reply: May 22, 2013 3:50 PM by Gustav Hoder RSS
1 2 Previous Next
zaphod42 Level 1 Level 1 (20 points)
Currently Being Moderated
Nov 13, 2012 8:46 AM

getting really desperate here!

and realizing the dependency on applications and not being able to work right now!

 

 

fortunately I finished a big project in the older version before updating to 5.0.5!

Motion 5.0.5 keeps crashing on launch ("Project Browser" windows shows up briefly)

I followed all the good advices:

- deleting ~/Library/Application Support/Motion/Layouts

- deleting ~/Library/Preferences/com.apple.motionapp.plist

- Running Pref_Man

but Motion 5.0.5 keeps crashing!!!

 

 

now it's getting really desperate:

then I tried to go back to 5.0.4 and with "Time Machine" I replaced:

 

- /Applications/Motion.app (5.0.4)

- ~/Library/Application Support/Motion

- ~/Library/Preferences/com.apple.motionapp.plist

 

 

crashes, crashes and crashes on launching!

 

 

please HELP!!!

 

 

 

 

Mac Pro running 10.8.2 (The Lion's ... my biggest mistake)

 

 

Crashed Thread:  0  Dispatch queue: com.apple.main-thread

...

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0   libsystem_kernel.dylib                  0x00007fff904b2212 __pthread_kill + 10

1   libsystem_c.dylib                       0x00007fff96f4baf4 pthread_kill + 90

2   libsystem_c.dylib                       0x00007fff96f8fdce abort + 143

3   libc++abi.dylib                         0x00007fff963fba17 abort_message + 257

4   libc++abi.dylib                         0x00007fff963f93c6 default_terminate() + 28

5   libobjc.A.dylib                         0x00007fff92799873 _objc_terminate() + 91

6   libc++.1.dylib                          0x00007fff8bda48fe std::terminate() + 20

7   libobjc.A.dylib                         0x00007fff927995de objc_terminate + 9

8   libdispatch.dylib                       0x00007fff911c70ca _dispatch_client_callout + 28

9   libdispatch.dylib                       0x00007fff911c7041 dispatch_once_f + 50

10  com.apple.motion.TextFramework          0x000000010fe3375a TXFontManager::getInstance() + 42

11  com.apple.motion.Text                   0x000000010da3d2d4 0x10da3c000 + 4820

12  com.apple.ozone.framework               0x0000000100b623b7 OZApplication::FinishInitializingPlugins() + 199

13  com.apple.ozone.framework               0x0000000100b724f3 -[OZApplicationController applicationDidFinishLaunching:] + 515

14  com.apple.CoreFoundation                0x00007fff944d647a _CFXNotificationPost + 2554

15  com.apple.Foundation                    0x00007fff8cb66846 -[NSNotificationCenter postNotificationName:object:userInfo:] + 64

16  com.apple.AppKit                        0x00007fff930f460d -[NSApplication _postDidFinishNotification] + 292

17  com.apple.AppKit                        0x00007fff930f4346 -[NSApplication _sendFinishLaunchingNotification] + 216

18  com.apple.AppKit                        0x00007fff930f1532 -[NSApplication(NSAppleEventHandling) _handleAEOpenEvent:] + 566

19  com.apple.AppKit                        0x00007fff930f112c -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 351

20  com.apple.Foundation                    0x00007fff8cb8012b -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 308

21  com.apple.Foundation                    0x00007fff8cb7ff8d _NSAppleEventManagerGenericHandler + 106

22  com.apple.AE                            0x00007fff8df8db48 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned int, unsigned char*) + 307

23  com.apple.AE                            0x00007fff8df8d9a9 dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 37

24  com.apple.AE                            0x00007fff8df8d869 aeProcessAppleEvent + 318

25  com.apple.HIToolbox                     0x00007fff94b448e9 AEProcessAppleEvent + 100

26  com.apple.AppKit                        0x00007fff930ed916 _DPSNextEvent + 1456

27  com.apple.AppKit                        0x00007fff930eced2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128

28  com.apple.AppKit                        0x00007fff930e4283 -[NSApplication run] + 517

29  com.apple.prokit                        0x00000001000e9324 NSProApplicationMain + 378

30  com.apple.motionapp                     0x000000010000270e 0x100000000 + 9998

31  com.apple.motionapp                     0x0000000100001a64 0x100000000 + 6756

  • GFXZen Level 4 Level 4 (1,320 points)
    Currently Being Moderated
    Nov 13, 2012 10:22 AM (in response to zaphod42)

    First question, does this happen with all projects or just one in particular?

     

    Next, I noticed the crash says something about text.  Have you checked for corrupted fonts? Try using font book to look for bad fonts.  (File Menu->Validate Fonts).  Try removing any corrupt or bad fonts.

  • rigreg44 Calculating status...
    Currently Being Moderated
    Nov 14, 2012 4:21 PM (in response to zaphod42)

    I have the same problem here.

    I came back to version 5.0.4 but it is now impossible to edit an effect from FCPX because all the effects has been updated to version 5.0.5.

    I hope that Apple will do something because I,m thinking too to go to AE.

  • rigreg44 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Nov 18, 2012 7:10 AM (in response to zaphod42)

    The only thing I can say here is that I upgraded to Motion 5.0.5 on my Macbook Pro and it worked. It can be a solution if you have the money.

     

    Good luck

  • GFXZen Level 4 Level 4 (1,320 points)
    Currently Being Moderated
    Nov 18, 2012 11:57 AM (in response to zaphod42)

    Zaphod42,

     

    Generally, downgrading is probably not the way to go to solve the problem.  From your initial post, I noticed you had tried a number of things, but you did not mention if you had tried re-installing the latest version.  Maybe try deleting the preferences and layouts as you previously had, and then re-install Motion 5.0.5. Also, have you tried not doing any symlinking to the content?

  • David M Brewer Level 6 Level 6 (9,180 points)
    Currently Being Moderated
    Nov 18, 2012 12:51 PM (in response to zaphod42)

    Use this free app from Digital Rebellion to remove Motion 5 from your computer:

     

    http://www.digitalrebellion.com/fcsremover/

     

    Make sure you only select Motion 5 to be removed. After that try reinstall Motion 5 from the Apple Store. Repair your disk permissions after the reinstall.

  • rigreg44 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Dec 23, 2012 1:57 PM (in response to zaphod42)

    Hi every body I got the secret of the trash.

    Go to the hidden Library/Application support/Final Cut Studio/Motion/Library put this last library in the trash and you Motion 5.0.6 will open. That worked for me

    Merry Chrismass and beleive in Santaclaus

  • rigreg44 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Dec 24, 2012 5:58 AM (in response to rigreg44)

    I have make a mistake, excuse me. I make the correction:

     

    Hi every body I got the secret of the Motion5 update crash.

    Go to the hidden Library/Application support/Final Cut Studio/Motion/Library, put this last library in the trash and your Motion 5.0.6 will open normaly. That worked for me. Thanks every body. Espacialy Zaphod42 and Jim Wanamaker.

    Merry Chrismass and beleive in Santaclaus

  • fmaggi Calculating status...
    Currently Being Moderated
    Apr 1, 2013 5:17 PM (in response to rigreg44)

    I just had the same issue with the 5.0.7 upgrade. rigreg44's solution worked for me. I spent a lot of time chasing my tail; thanks, rigreg44.

1 2 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.