Activity › Forums › Apple Motion › Motion files crash after 10.4.3 update
-
Motion files crash after 10.4.3 update
Posted by Graeme Nattress on November 1, 2005 at 3:49 pmSome old Motion2 files are now crashing Motion after the 10.4.3 update. I tried taking Motion 2.01 back to 2.0 but that didn’t help. Short of rolling the operating system back, I think I’m stuck. This happened to anyone else? Anyone care to test a Motion file on their system for me?
Graeme
– http://www.nattress.com – Film Effects and Standards Conversion for FCP
Karel Hurych replied 20 years, 6 months ago 6 Members · 13 Replies -
13 Replies
-
Keith Hill
November 1, 2005 at 4:31 pmHi Graeme,
I haven’t had a problem with Motion so far, but I won’t have an opportunity to really play with it until later this evening. I had some files that I opened that was part of a motion menu design job that I’m working on in DVDSP4. I played it back with no problems so far.
We’ll see later on when I have to work in more extensively.
Keith Hill
https://www.LightedPath.biz
Dallas, TX
Final Cut Pro 5.0.2, Motion 2.0.1, Combustion (MAC-v3.0.4), Cinema 4D r9.5, DVD StudioPro 4 (v 3.0.2); MAC G5 (v10.4.3-Tiger) 2Ghz, 1.5 RAM -
Karel Hurych
November 2, 2005 at 2:17 amI have this problem too. After installing OS 10.4.3 and Motion 2.01. Motion crash when I aply some filters.
Any ideas?
Karel -
Dan Brazil
November 2, 2005 at 11:17 amYes that is exactly what I am experiencing. I just updated to 10.4.3 and Motion 2.01 and every time I add a filter it immediately crashes. I thought this was just me given that this was the first time I have applied filters using Motion…so an auspicious start. I wonder if Apple are aware yet?
-
Graeme Nattress
November 2, 2005 at 1:33 pmThey’re very aware 🙂
No, which filters are doing the crashing? That’s the question!
Graeme
– http://www.nattress.com – Film Effects and Standards Conversion for FCP
-
Graeme Nattress
November 2, 2005 at 4:41 pmThanks. I went through and found a whole list and sent it off to apple. I gave up after a while as a lot are broken. Hopefully they can do a quick fix and get it back in action.
Graeme
– http://www.nattress.com – Film Effects and Standards Conversion for FCP
-
Jon Slagle
November 2, 2005 at 8:12 pmSame problem – I was having the “play” get stuck while editing in motion and that was getting annoying so I thought I’d just do an update and see if that might take care of it and now I can’t even get motion to open
report says:
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000054Any thoughts?
Jon Slagle
-
Karel Hurych
November 2, 2005 at 10:29 pmAfter aply filter colorize
crash report:Date/Time: 2005-11-02 23:27:39.752 +0100
OS Version: 10.4.3 (Build 8F46)
Report Version: 3Command: Motion
Path: /Applications/Motion.app/Contents/MacOS/Motion
Parent: WindowServer [71]Version: 2.0.1 (2.0.1)
Build Version: 5
Project Name: Motion
Source Version: 1961000PID: 1443
Thread: 0Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000054Thread 0 Crashed:
0 Ozone 0x014dc550 fe_gl_detach + 32
1 Ozone 0x014dee20 context_finalize + 180
2 Ozone 0x014ecb8c fe_release + 484
3 Ozone 0x014dc4e4 fe_context_gl_new + 404
4 Ozone 0x014d07d0 -[MOCIOpenGLContext initWithCGLContext:] + 84
5 Ozone 0x013cd144 OZCoreImagingEffect::OZCoreImagingEffect[unified](OZCoreImagingEffect const&, unsigned) + 276
6 Ozone 0x0175eab0 OZCoreImagingEffect_Factory::createCopy(OZFactoryBase*, unsigned) + 112
7 Ozone 0x012bd5d0 -[OZDragManager performDrop:dropInfo:] + 1520
8 Ozone 0x010ee084 -[OZLayerListController outlineView:acceptDrop:item:childIndex:] + 964
9 com.apple.AppKit 0x938e3608 -[NSOutlineView performDragOperation:] + 220
10 com.apple.AppKit 0x938becf4 NSCoreDragReceiveProc + 864
11 com.apple.HIServices 0x9180c988 DoDropMessage + 96
12 com.apple.HIServices 0x9180c8f8 SendDropMessage + 52
13 com.apple.HIServices 0x9180aff4 DragInApplication + 484
14 com.apple.HIServices 0x9180a958 DragLoop + 132
15 com.apple.HIServices 0x91809a5c CoreDragStartDragging + 200
16 com.apple.AppKit 0x938c4ab4 -[NSCoreDragManager _dragUntilMouseUp:accepted:] + 552
17 com.apple.AppKit 0x938c4330 -[NSCoreDragManager dragImage:fromWindow:at:offset:event:pasteboard:source:slideBack:] + 1120
18 com.apple.AppKit 0x938c3ebc -[NSWindow(NSDrag) dragImage:at:offset:event:pasteboard:source:slideBack:] + 136
19 com.apple.AppKit 0x938c3e20 -[NSView(NSDrag) dragImage:at:offset:event:pasteboard:source:slideBack:] + 164
20 com.apple.AppKit 0x938c711c -[NSOutlineView dragImage:at:offset:event:pasteboard:source:slideBack:] + 180
21 com.apple.AppKit 0x938c66ac -[NSTableView _doImageDragUsingRowsWithIndexes:event:pasteboard:source:slideBack:] + 576
22 com.apple.AppKit 0x9371d3c4 -[NSTableView _performDragFromMouseDown:] + 556
23 com.apple.AppKit 0x9371c470 -[NSTableView mouseDown:] + 412
24 com.apple.AppKit 0x937dc220 -[NSOutlineView mouseDown:] + 740
25 Ozone 0x01255700 -[OZLibraryOutlineView mouseDown:] + 720
26 com.apple.AppKit 0x936bc660 -[NSWindow sendEvent:] + 4616
27 com.apple.prokit 0x960cf8a8 NSProApplicationLoad + 115468
28 com.apple.AppKit 0x936656f4 -[NSApplication sendEvent:] + 4172
29 com.apple.motion 0x00010a58 0x1000 + 64088
30 com.apple.AppKit 0x9365cb30 -[NSApplication run] + 508
31 com.apple.prokit 0x960b3514 NSProApplicationMain + 288
32 com.apple.motion 0x0000ec24 0x1000 + 56356
33 com.apple.motion 0x0000d7e8 0x1000 + 51176
34 dyld 0x8fe01048 _dyld_start + 60 -
Karel Hurych
November 4, 2005 at 6:07 pmHURRA, We have the same crash report John and I saw Your profile and You have Black Magic card Declink SP as I. If You turn off BM desktop in system pref., restart and all is OK!!!!!!!!!!!!!!!
Karel -
Jon Slagle
November 4, 2005 at 6:19 pmWow! Thank you – It worked for me too!
Thankyou! Thankyou! Thankyou! Thankyou! Thankyou! Thankyou!
Jon Slagle
Reply to this Discussion! Login or Sign Up