Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity › Forums › Apple Motion › Motion crashing even though i’ve turned off video on desktop Black Magic!

  • Motion crashing even though i’ve turned off video on desktop Black Magic!

    Posted by Lars Ege on November 10, 2005 at 9:50 pm

    Motion crashing even though i’ve turned off “video on desktop Black Magic”!
    I can’t open a new or old project…
    I use Motion 2.0.1 on a G5 2,5 GHz with Studio Pack.
    Any ideas???!
    Is there any other place than Preferences, where I can turn off “Video on Desktop”?!?!

    Thanks

    Lars.

    Mamba_admin replied 20 years, 10 months ago 5 Members · 8 Replies
  • 8 Replies
  • Jim Kanter

    November 11, 2005 at 8:33 am

    Try trashing your preferences and starting Motion again.

    I usually just rename mine by adding “old” to the start of the filename. That way if the problem is NOT the prefs file, I can easily restore my settings by changing the name back.

    Jim Kanter,
    Digital Film Institute
    http://www.dfilminst.com

  • Lars Ege

    November 11, 2005 at 11:46 am

    Thanks, but it still did not help… Then it just prompt the project settings and still dosen’t open a new project.
    I can open Motion as allways, but can’t enter Preferences, new project or old project.
    Do you have any other ideas!?

    Lars.

  • Doyle Rockwell

    November 11, 2005 at 9:54 pm

    Hey Lars,

    Trying opening the Console (found in /Applications/Utilities) and post what it says when Motion crashes. Also, post the crashed thread from the crash reporter (appears when Motion dies).

    This information should give you a hint as to what’s wrong on your system.

  • Lars Ege

    November 11, 2005 at 11:46 pm

    Well, this is what i’ve got from the Console and Crash test:

    Thanks Again!!!

    Console:

    2005-11-12 00:36:31.271 Motion[667] *** -[NSToolbarView drawsBaseline]: selector not recognized [self = 0x8d6cbc0]
    2005-11-12 00:36:31.288 Motion[667] *** -[NSToolbarView drawsBaseline]: selector not recognized [self = 0x8d6cbc0]
    2005-11-12 00:36:31.396 Motion[667] *** -[NSToolbarView drawsBaseline]: selector not recognized [self = 0x8d6cbc0]
    2005-11-12 00:36:31.396 Motion[667] *** -[NSToolbarView drawsBaseline]: selector not recognized [self = 0x8d6cbc0]
    2005-11-12 00:36:40.065 Motion[667] *** -[NSToolbarView drawsBaseline]: selector not recognized [self = 0x10153b40]
    2005-11-12 00:36:40.068 Motion[667] *** -[NSToolbarView drawsBaseline]: selector not recognized [self = 0x10153b40]
    Motion(667,0xa000ed68) malloc: *** Deallocation of a pointer not malloced: 0xbfffd5a0; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug
    Motion(667,0xa000ed68) malloc: *** Deallocation of a pointer not malloced: 0xbfffd410; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug
    2005-11-12 00:36:40.400 Motion[667] *** -[NSToolbarView drawsBaseline]: selector not recognized [self = 0x10153b40]
    2005-11-12 00:36:40.400 Motion[667] *** -[NSToolbarView drawsBaseline]: selector not recognized [self = 0x10153b40]
    2005-11-12 00:37:23.604 Motion[667] *** -[NSToolbarView drawsBaseline]: selector not recognized [self = 0xf76cf70]
    2005-11-12 00:37:23.607 Motion[667] *** -[NSToolbarView drawsBaseline]: selector not recognized [self = 0xf76cf70]
    2005-11-12 00:37:24.190 Motion[667] *** -[NSToolbarView drawsBaseline]: selector not recognized [self = 0xf76cf70]
    2005-11-12 00:37:24.191 Motion[667] *** NSTimer discarding exception ‘*** -[NSToolbarView drawsBaseline]: selector not recognized [self = 0xf76cf70]’ that raised during firing of timer with target feaa790 and selector ‘processNotifications:’
    Nov 12 00:37:25 Lars-Ege-Hansens-computer crashdump[669]: Motion crashed
    Nov 12 00:37:26 Lars-Ege-Hansens-computer crashdump[669]: crash report written to: /Users/larsegehansen/Library/Logs/CrashReporter/Motion.crash.log

    Motion Crash Log:

    ===== Oversigt starter ved offset 177346 i arkivet med l

  • David Bogie

    November 13, 2005 at 5:27 pm

    Yes, the answer is crystal clear now.

    Seriously, no one on these forums understands this stuff any more than you do, Lars. It’s deep geek, code-speak for Unix code.
    Sending the report to Apple seems like a waste of time, we know. But Specialcase asked you to post it so let’s see what he’s got to say.

    bogiesan

  • Doyle Rockwell

    November 14, 2005 at 7:03 pm

    Hey Lars,

    From what little I understand, one of the crashes in your log shows that it died when you were mousing into the toolbar. When, exactly, is Motion crashing? Precislely: what are you doing at the moment of crash? Just mousing into the toolbar shouldn’t cause a crash (of course), and the crash logs don’t look like the ones people have posted for bad installs/frameworks, so I’m at something of a loss.

  • Lars Ege

    November 14, 2005 at 7:26 pm

    Hi..
    It crashes when I try to open a new or old project and I can’t touch any of the controls in the File Browser, then it crashes to.
    Help!
    🙁

    Lars.

  • Mamba_admin

    December 1, 2005 at 9:34 am

    i would like to trash my motion prefs. where do i find them?

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy