Activity › Forums › Apple Motion › Motion2 won’t boot
-
Motion2 won’t boot
Posted by Bill Depalma on January 13, 2007 at 4:07 amI need some help, I can’t get Motion2 (2.1.2, really) to boot anymore. Just started out of the blue. Never have had a problem in the past. I am using an intel mac pro 2.66, ati1900, 6g of ram.
When I attempt to open the app I get the opening screen for a few seconds and then nothing, screen goes away and nothing has happened. I have disabled all the fonts except for system fonts.
Not sure what else to try. I have reloaded the software several times, nothing. Any ideas?
thanks
BillIamsoclever replied 19 years, 3 months ago 6 Members · 7 Replies -
7 Replies
-
Jim Kanter
January 13, 2007 at 9:19 pm -
Bill Depalma
January 14, 2007 at 5:43 amJim
I’m looking and I cannot locate a preferences file for motion, assumed it was in the library
where else might it be
thanks
Bill -
Bill Depalma
January 14, 2007 at 4:53 pmI reinstalled Motion but no change, still won’t boot
Here is the crash log from Console if that helps::===== Sunday, January 14, 2007 11:49:23 AM US/Eastern =====
NOTE: ignoring this component:
Discovered 26 component = 0x61baa64 type = sinp subt = fwpa manu = appl flags = 0NOTE: ignoring this component:
Discovered 26 component = 0x61baaae type = clok subt = fwcy manu = appl flags = 02007-01-14 11:49:27.866 Motion[257] An uncaught exception was raised
2007-01-14 11:49:27.866 Motion[257] *** -[NSURL initFileURLWithPath:]: nil string parameter
2007-01-14 11:49:27.866 Motion[257] *** Uncaught exception:*** -[NSURL initFileURLWithPath:]: nil string parameter
Jan 14 11:49:28 Bill crashdump[258]: Motion crashed
Jan 14 11:49:28 Bill crashdump[258]: crash report written to: /Users/BillD/Library/Logs/CrashReporter/Motion.crash.log
thanks
Bill
-
Peter Berdovsky
January 19, 2007 at 12:44 pmI have the same exact problem, but I have just finished installing Motion 2.0 on my mac book pro, went through the tutorials, started the program (made a new file), it took a few seconds to load all the windows – then everything just disappears! It’s so frustrating… I was really looking forward to using this software. What should I do?
-
Gabriele De simone
January 19, 2007 at 3:50 pmWell in your case, you shouldn’t be using Motion 2.0 on a MacBook Pro. You should be using Motion 2.1.2, which you get with the Final Cut Studio 5.1 Universal, and one more round of automatic software updates.
The fact that Motion 2.0 even launches on your system is a testament to how good Rosetta (the PowerPC emulation layer) is 🙂
Gabe
Noise Industries, LLC -
Kaz Miley
February 5, 2007 at 1:07 amI’m unsure if you’ve discovered the answer to this – I have experienced the same problem.
I had a G5 and installed Motion fine. Bought the new macbook pro and motion won’t boot – I get the welcome screen, then choose anything and it loads, shows me the interface for 1/2 second and then crashes out. I’ve got the Motion 2 software but have downloaded upgrades to the most recent version. I really need to work this problem out as I have people interested in Motion work and this is what I got a lot of work through last year!
I was really surprised that my super duper macbook pro was not able to run an older (not THAT old!) version of Motion.
help!
-
Iamsoclever
February 13, 2007 at 4:50 amI’m running Motion 2.1.2 on a MacBook Pro. It was working fine until today – all of a sudden it doesn’t respond at all when I try to “Save” or “Export.” If I close my project, it brings up the dialogue “Do you want to save your changes before closing?” so I hit save but then Motion quits unexpectedly. Here’s the log from my console:
2007-02-12 23:46:03.997 Motion[448] Can’t open input server /Library/InputManagers/Smart Crash Reports.bundle
2007-02-12 23:46:35.078 Motion[448] *** -[NSNavSegmentSwitchControl cellAtRow:column:]: selector not recognized [self = 0xb6fb990]
2007-02-12 23:46:35.156 Motion[448] *** -[NSNavSegmentSwitchControl cellAtRow:column:]: selector not recognized [self = 0xb6fb990]
Reply to this Discussion! Login or Sign Up