Motion 3 Freeze-up
I have a brand new macbook pro with all the trimmings and FCS2. i've just started to experiment with motion and it freezes and crashes my computer. it's happened four times tonight, but it's never happened before.
i noticed it does it when i scrub on the timeline and the keyframe editor is open, but it's happened for no reason at all a couple times, too. is motion too much to run without the laptop being plugged into a wall socket, also?
it says a whole bunch about the computer and program not being registered... and then it says this:
/XRefStm encountered but not yet supported.
"obj" not found while reading object (1397, 0).
missing or invalid cross-reference stream.
"obj" not found while reading object (1397, 0).
missing or invalid cross-reference stream.
"obj" not found while reading object (896, 0).
missing or invalid cross-reference stream.
"obj" not found while reading object (896, 0).
missing or invalid cross-reference stream.
encountered unexpected object type: 7.
Missing or invalid object number.
missing or invalid cross-reference stream.
encountered unexpected object type: 7.
Missing or invalid object number.
missing or invalid cross-reference stream.
...then it goes back to saying that the program is unregistered and that there is a problem with my comp's registration. i don't understand this. i registered the computer when i got it, and this morning, after midnight, i registered Motion 3 at my current (yet temporary) address... it reads in the console: "mDNSResponder: HostnameCallback: Error -65557 for registration..."
this would have an effect on whether or not Motion works? like i said, i used it just to play with it after i got the computer and FCS2, and it worked fine... and i even used video with jpegs in that early session. what i'm doing now is only (test) animating still images. PNG formats made in photoshop, to be exact... the program should be able to handle that, right?
the other mac programs, i.e.: FCP, DVDSP, itunes, etc... work fine and the comp is still fast as ****, but i haven't gotten the chance to look at color or cinema tools or any of the others that came in the FCS2 package... so i'm worried they'd do the same thing... is this a possibility? like i just said, i got no errors or problems from DVDsp and FCP... so i'm mystified.
BTW this is the first mac i've owned, but i've used them for years... i'm still learning... any help is appreciated.
Similar Messages
-
Motion 2 freezing my system momentarily?!
Why does Motion freeze my system just for minutes at a time? No rainbow wheel just freezes all activity except the mouse movement. I know its Motion cause it only happens when its open. FRUSTRATING!
QUADCORE 2.5 G5 Mac OS X (10.4.5)I know its Motion cause it only happens when its open. FRUSTRATING!< </div>
It's almost impossible to guess from where we're sitting.
If you're NOT getting a spinning cursor try opening Activity Monitor and see if you can get a feeling for anything that might be happening on the system. Try searching the forum for "slow down" or similar terms, we've had many threads over the months and they are all different. However, most are from folks who have a rainbow cursor.
Additional questions, did Motion ever work well? Did you install all of the resource data files?
bogiesan -
Motion 5 freezes after applying the keying filter
Why does my screen freeze (four or five yellow/green bands, curser turns to rotating ball of death) when i try to apply the keying filter in Motion 5?
What's your hardware configuration, mainly what GPU do you have?
-
motion froze on me when i was working on a blue sreen project. i force quit and restarted the computer and now motion won't launch. it starts but then freezes right dispalying the left pane. what can i do?
size and format of footage?
have you tried trashing the preference file called com.apple.motion.plist its found in (Your account)>Library>Preferences. then empty your trash? -
Motion 5 freezes macbook using oscillate
My Macbook Pro Retina (2.7 Ghz i7, 16 Gb) freezes completely using Motion. It is difficult to reproduce but it happened several times when using the Oscillate Parameter behavior on the Growth/Shrink Behavior. A restart is required. Any advice ?
Kind regards.I am a little confused on your statement about using the Oscillate behavior on the Growth/Shrink behavior. Since one can not apply a behavior to a behavior I assume you mean Motion freezes when using either behavior? I do not see that problem when I try either or both behaviors on an object. What are you applying the behaviors to? Perhaps you might delete Motion preferences or try a different object to see if that helps.
-
I have Final Cut Pro 7
When I add text (with a very slight motion at the end) ALL of the fades in the video sequence below it freeze or don't work at all.
V3 is Text
V2 has a few clips with fades
V1 is the main video
A3 Left Audio
A4 Right AudioThanks, David!
-
Motion 5 Freezes When Any Filter Is Selected
Hi there,
I recently purchased Motion 5 (running Motion 5.0.1) and everytime I select a filter or try to open a project that uses a filter the program freezes, getting stuck on the spinning beachball. It freeze is repeatable 100% of the time by simply clicking on a "filter" in the library list. Generators and particle emitters run perfectly, the issue is only with "filters" and "image units". I am running it on a 6 core Mac Pro with 17GB of RAM, a Radeon 4870 video card, and two displays. The computer is on 10.7.2. I have been running FCP X and it has not been crashing or hanging (but I haven't used it too heavily for any real work). This computer has had FCS 2 and FCS 3 installed on it. I have not had any other applications misbehaving so I don't believe it is a RAM issue. Please see the DiagnosticReports log for the freeze below. I am including only the Motion portition. Any help would be amazing and hugely helpful!
Date/Time: 2011-11-02 19:34:34 -0400
OS Version: 10.7.2 (Build 11C74)
Architecture: x86_64
Report Version: 9
Command: Motion
Path: /Applications/Motion.app/Contents/MacOS/Motion
Version: 5.0.1 (185673)
Build Version: 1
Project Name: Motion
Source Version: 185670300
App Item ID: 434290957
App External ID: 4139667
Parent: launchd [821]
PID: 2171
Event: hang
Duration: 2.05s
Steps: 20 (100ms sampling interval)
Pageins: 15
Pageouts: 0
Process: Motion [2171]
Path: /Applications/Motion.app/Contents/MacOS/Motion
Architecture: x86_64
UID: 501
Thread 0xbc71 DispatchQueue 1
User stack:
20 ??? (in Motion) [0x100002088]
20 ??? (in Motion) [0x10000560e]
20 NSProApplicationMain + 387 (in ProKit) [0x1002223c6]
20 -[NSApplication run] + 470 (in AppKit) [0x7fff8e3a462d]
20 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 135 (in AppKit) [0x7fff8e3a7cf5]
20 _DPSNextEvent + 659 (in AppKit) [0x7fff8e3a83f1]
20 BlockUntilNextEventMatchingListInMode + 62 (in HIToolbox) [0x7fff9232a4ca]
20 ReceiveNextEventCommon + 355 (in HIToolbox) [0x7fff9232a63d]
20 RunCurrentEventLoopInMode + 277 (in HIToolbox) [0x7fff923233d3]
20 CFRunLoopRunSpecific + 230 (in CoreFoundation) [0x7fff8a4f8ae6]
20 __CFRunLoopRun + 905 (in CoreFoundation) [0x7fff8a4f91a9]
20 __CFRunLoopDoSources0 + 253 (in CoreFoundation) [0x7fff8a4d23bd]
20 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17 (in CoreFoundation) [0x7fff8a4d2b51]
20 __NSThreadPerformPerform + 214 (in Foundation) [0x7fff8abc3e44]
20 -[NSObject performSelector:withObject:] + 61 (in CoreFoundation) [0x7fff8a553a1d]
20 -[QTNotificationController postNotification:] + 433 (in QTKit) [0x7fff8e1125ff]
20 releaseProxy + 128 (in QTKit) [0x7fff8e11236b]
20 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff948cd67a]
Kernel stack:
20 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0xbc87 DispatchQueue 2
User stack:
20 _dispatch_mgr_thread + 54 (in libdispatch.dylib) [0x7fff8d39e14e]
20 kevent + 10 (in libsystem_kernel.dylib) [0x7fff948cf7e6]
Kernel stack:
20 kqueue_scan + 480 (in mach_kernel) [0x5596e0]
Thread 0xbc9a
User stack:
20 thread_start + 13 (in libsystem_c.dylib) [0x7fff943b5b75]
20 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff943b28bf]
20 PCThread::startup(void*) + 18 (in ProCore) [0x100a801a4]
20 (anonymous namespace)::threadFunc(void*) + 70 (in ProGL) [0x1030596ea]
20 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x7fff948cebca]
Kernel stack:
20 lo64_unix_scall + 23 (in mach_kernel) [0x2e4977]
20 unix_syscall64 + 554 (in mach_kernel) [0x5f15fa]
20 psynch_cvwait + 1967 (in mach_kernel) [0x5c38bf]
20 ksyn_block_thread_locked + 77 (in mach_kernel) [0x5bed6d]
20 thread_block + 33 (in mach_kernel) [0x22f771]
20 thread_block_reason + 331 (in mach_kernel) [0x22f62b]
20 thread_continue + 1729 (in mach_kernel) [0x22f3a1]
20 machine_switch_context + 582 (in mach_kernel) [0x2cba26]
Thread 0xbcad
User stack:
20 thread_start + 13 (in libsystem_c.dylib) [0x7fff943b5b75]
20 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff943b28bf]
20 Thread::RunHelper(void*) + 42 (in Flexo) [0x1020f9d6a]
20 ??? (in FigProvider) [0x10bddfab8]
20 Synchronizable::Wait() + 56 (in Flexo) [0x1020f0f68]
20 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x7fff948cebca]
Kernel stack:
20 lo64_unix_scall + 23 (in mach_kernel) [0x2e4977]
20 unix_syscall64 + 554 (in mach_kernel) [0x5f15fa]
20 psynch_cvwait + 1967 (in mach_kernel) [0x5c38bf]
20 ksyn_block_thread_locked + 77 (in mach_kernel) [0x5bed6d]
20 thread_block + 33 (in mach_kernel) [0x22f771]
20 thread_block_reason + 331 (in mach_kernel) [0x22f62b]
20 thread_continue + 1729 (in mach_kernel) [0x22f3a1]
20 machine_switch_context + 582 (in mach_kernel) [0x2cba26]
Thread 0xbd57
User stack:
20 thread_start + 13 (in libsystem_c.dylib) [0x7fff943b5b75]
20 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff943b28bf]
20 listenOnDelegatePort + 418 (in QTKit) [0x7fff8e10f6f2]
20 CFRunLoopRun + 95 (in CoreFoundation) [0x7fff8a5087ff]
20 CFRunLoopRunSpecific + 230 (in CoreFoundation) [0x7fff8a4f8ae6]
20 __CFRunLoopRun + 1204 (in CoreFoundation) [0x7fff8a4f92d4]
20 __CFRunLoopServiceMachPort + 188 (in CoreFoundation) [0x7fff8a4f0b6c]
20 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff948cd67a]
Kernel stack:
20 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0xbd58
User stack:
20 thread_start + 13 (in libsystem_c.dylib) [0x7fff943b5b75]
20 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff943b28bf]
20 listenOnNotificationPort + 376 (in QTKit) [0x7fff8e10fb89]
20 CFRunLoopRun + 95 (in CoreFoundation) [0x7fff8a5087ff]
20 CFRunLoopRunSpecific + 230 (in CoreFoundation) [0x7fff8a4f8ae6]
20 __CFRunLoopRun + 1204 (in CoreFoundation) [0x7fff8a4f92d4]
20 __CFRunLoopServiceMachPort + 188 (in CoreFoundation) [0x7fff8a4f0b6c]
20 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff948cd67a]
Kernel stack:
20 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0xbd7c
User stack:
20 thread_start + 13 (in libsystem_c.dylib) [0x7fff943b5b75]
20 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff943b28bf]
20 QTCALayerRendererPendingQWorkLoop + 542 (in QTKit) [0x7fff8e1983f0]
20 CFRunLoopRun + 95 (in CoreFoundation) [0x7fff8a5087ff]
20 CFRunLoopRunSpecific + 230 (in CoreFoundation) [0x7fff8a4f8ae6]
20 __CFRunLoopRun + 1204 (in CoreFoundation) [0x7fff8a4f92d4]
20 __CFRunLoopServiceMachPort + 188 (in CoreFoundation) [0x7fff8a4f0b6c]
20 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff948cd67a]
Kernel stack:
20 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0xbe9e
User stack:
20 thread_start + 13 (in libsystem_c.dylib) [0x7fff943b5b75]
20 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff943b28bf]
20 __NSThread__main__ + 1575 (in Foundation) [0x7fff8abce776]
20 -[NSThread main] + 68 (in Foundation) [0x7fff8abce7fe]
20 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 335 (in Foundation) [0x7fff8abda0ab]
20 CFRunLoopRunSpecific + 230 (in CoreFoundation) [0x7fff8a4f8ae6]
20 __CFRunLoopRun + 1204 (in CoreFoundation) [0x7fff8a4f92d4]
20 __CFRunLoopServiceMachPort + 188 (in CoreFoundation) [0x7fff8a4f0b6c]
20 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff948cd67a]
Kernel stack:
20 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0xbea3
User stack:
20 thread_start + 13 (in libsystem_c.dylib) [0x7fff943b5b75]
20 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff943b28bf]
20 __select + 10 (in libsystem_kernel.dylib) [0x7fff948cedf2]
Kernel stack:
20 wakeup + 1024 (in mach_kernel) [0x575a00]
Thread 0xbeee
User stack:
20 thread_start + 13 (in libsystem_c.dylib) [0x7fff943b5b75]
20 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff943b28bf]
20 QTMachPortImageProviderWorkLoop + 345 (in QTKit) [0x7fff8e1d5e73]
20 CFRunLoopRun + 95 (in CoreFoundation) [0x7fff8a5087ff]
20 CFRunLoopRunSpecific + 230 (in CoreFoundation) [0x7fff8a4f8ae6]
20 __CFRunLoopRun + 1204 (in CoreFoundation) [0x7fff8a4f92d4]
20 __CFRunLoopServiceMachPort + 188 (in CoreFoundation) [0x7fff8a4f0b6c]
20 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff948cd67a]
Kernel stack:
20 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0xbeef
User stack:
20 thread_start + 13 (in libsystem_c.dylib) [0x7fff943b5b75]
20 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff943b28bf]
20 _ZL13startIOThreadPv + 148 (in CoreVideo) [0x7fff8f9c285d]
20 CVDisplayLink::runIOThread() + 710 (in CoreVideo) [0x7fff8f9c2b3c]
20 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x7fff948cebca]
Kernel stack:
20 lo64_unix_scall + 23 (in mach_kernel) [0x2e4977]
20 unix_syscall64 + 554 (in mach_kernel) [0x5f15fa]
20 psynch_cvwait + 1967 (in mach_kernel) [0x5c38bf]
20 ksyn_block_thread_locked + 77 (in mach_kernel) [0x5bed6d]
20 thread_block + 33 (in mach_kernel) [0x22f771]
20 thread_block_reason + 331 (in mach_kernel) [0x22f62b]
20 thread_continue + 1729 (in mach_kernel) [0x22f3a1]
20 machine_switch_context + 582 (in mach_kernel) [0x2cba26]
Binary Images:
0x100000000 - 0x100112fe7 com.apple.motionapp 5.0.1 (185673) <4B0F6ED6-5D91-C206-0C0F-3A45F375B1A4> /Applications/Motion.app/Contents/MacOS/Motion
0x100203000 - 0x10047cfef com.apple.prokit 7.1.1 (1511) <652BEC78-D497-3EE2-8128-B9E01AD2ADA3> /System/Library/PrivateFrameworks/ProKit.framework/Versions/A/ProKit
0x100a60000 - 0x100b3bfef com.apple.procore.framework 4.0.2 (757) <23F3B441-47FB-BB3E-D928-4B9A534154A7> /Applications/Motion.app/Contents/Frameworks/ProCore.framework/Versions/A/ProCo re
0x101f69000 - 0x102a46fef com.apple.Flexo 1.0.0 (21) <0705EC90-BAB2-5DA3-8252-D8803836B30B> /Applications/Motion.app/Contents/Frameworks/Flexo.framework/Versions/A/Flexo
0x103049000 - 0x10307dfe7 com.apple.progl.framework 1.0 (18567.3) <8B504293-53F1-F441-1648-CED174AD9673> /Applications/Motion.app/Contents/Frameworks/ProGL.framework/Versions/A/ProGL
0x10bdb3000 - 0x10bdf9fff com.apple.Fig.provider 1.0.0 (21) <C69AD40E-36E9-B00E-766B-AD02D287CB77> /Applications/Motion.app/Contents/Frameworks/Flexo.framework/Versions/A/PlugIns /MediaProviders/FigProvider.fxp/Contents/MacOS/FigProvider
0x7fff8a4c0000 - 0x7fff8a694fff com.apple.CoreFoundation 6.7.1 (635.15) <FE4A86C2-3599-3CF8-AD1A-822F1FEA820F> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff8ab74000 - 0x7fff8ae8dff7 com.apple.Foundation 6.7.1 (833.20) <D922F590-FDA6-3D89-A271-FD35E2290624> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff8d39c000 - 0x7fff8d3aafff libdispatch.dylib ??? (???) <712AAEAC-AD90-37F7-B71F-293FF8AE8723> /usr/lib/system/libdispatch.dylib
0x7fff8e0fc000 - 0x7fff8e286ff7 com.apple.QTKit 7.7.1 (2306) <A97042BD-4FD8-3556-9279-6B7742C98904> /System/Library/Frameworks/QTKit.framework/Versions/A/QTKit
0x7fff8e39f000 - 0x7fff8efa0ff7 com.apple.AppKit 6.7.2 (1138.23) <5CD2C850-4F52-3BA2-BA11-3107DFD2D23C> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x7fff8f9c1000 - 0x7fff8f9e9ff7 com.apple.CoreVideo 1.7 (70.1) <98F917B2-FB53-3EA3-B548-7E97B38309A7> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x7fff92321000 - 0x7fff92645fff com.apple.HIToolbox 1.8 (???) <A3BE7C59-52E6-3A7F-9B30-24B7DD3E95F2> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
0x7fff94364000 - 0x7fff94441fef libsystem_c.dylib ??? (???) <FF69F06E-0904-3C08-A5EF-536FAFFFDC22> /usr/lib/system/libsystem_c.dylib
0x7fff948b8000 - 0x7fff948d8fff libsystem_kernel.dylib ??? (???) <69F2F501-72D8-3B3B-8357-F4418B3E1348> /usr/lib/system/libsystem_kernel.dylibFirst of all, make sure it's in the root level of the Applications folder.
Second, I'd get rid of FCS2 for sure.
I'd first run Disk Utility and "repair" all drives.
Verify ALL of the drives on your system have at least 15% of their capacity as free space.
Use the free "Preference Manager" from Digital Rebellion to safely and properly trash yoru Motion 5 pref files.
Worse comes to worse, drag Motion 5 to the Trash, launch the App Store, go to the Purchased tab, cilck "Install" next to Motion 5. -
Motion constantly freezes computer.
Motion 3 constantly freezes my completely updated macbook pro not running leopard. Any ideas....also, when I export my graphics with animation codec with alpha channel, they constantly flicker on and off and have artificats that flicker on and off. Any suggestions?
First port of call would be to trash your prefs. Then maybe take a look at the Ozone problem thread below which goes into great detail about crashing problems.
Did you do an archive & install? This is known to be problematical with Motion.
What are you looking at your animation codec movie on? It won't play back in real time in FCP - try rendering it on a timeline.
Peter -
Motion temporarily freezes when trying to scrub the timeline
Hey guys,
Having a couple of probs... firstly when I'm working in motion and I click up the top of the timeline to scrub through the video there is a delay of about 30 seconds before my computer responds. I'm running Motion 3.0.2 on a MacBook Pro. The timeline consists of a photoshop background, a photoshop foreground and a 3 minute music track. Any help on this would be great.
Another thing that's happening and I'm not sure if they're related problems but the timeline will be playing back and then I try to click stop or anything in Motion and yet it continues to play. Same deal - about 30 seconds before I am able to control the timeline again. This also happens on my Dual 2Ghz G5.
Any help would be greatly appreciated.
Cheers,
Philcan't say that I agree that it's a graphics card limitation
You're a lucky guy to have that kind of muscle that runs on batteries. My mistake, I can see that now, thanks for clearing that up for me, won't forget it.
I'm not using my G5 to do this either - it's my MacBook Pro.
Your first post says "this" happens on both systems. Here, I shall quote it for you to save you the trouble of denying it and forcing me to call you silly names:
Same deal - about 30 seconds before I am able to control the timeline again. This also happens on my Dual 2Ghz G5.
must be something else.
Yes, silly of me to try to debug this for you when I'm here and you're there. Too bad I can't really see what you're doing, isn't it? All I can do is tell you what I know from several years of struggling with Motion and reading hundreds of threads from hundreds of Motion users whose machines neither meet their expectations nor the promises of some sales dweeb. You can read them, too, just initiate a search of the forum for "slow as snot a cold doorknob." Motion's demands on system resources are weirdly nonlinear. I've seen posts complaining about glacial behavior on a wide variety of machines that make your setup and mine look truly pathetic.
It's merely two graphics layers and a text layer (which isn't animated). The only thing I'm animating is a bouncing logo across the screen.
Hmm, that's interesting, but "merely" may mean one thing to you and quite another to your machine. I was going to ask many relevant questions about these layers of yours but, heck, you don't need to tell me anything you don't want to.
When it crashes it comes up with a message saying that it's a plugin that's causing the crash (even though I've got no 3rd party plugins installed). The problem is also intermittent.
A "crash," you say? That's dreadful. Is this new? You didn't mention a crash in your first post. Here, I'll quote it for you:
Hey guys,Having a couple of probs... firstly when I'm working in motion and I click up the top of the timeline to scrub through the video there is a delay of about 30 seconds before my computer responds. I'm running Motion 3.0.2 on a MacBook Pro. The timeline consists of a photoshop background, a photoshop foreground and a 3 minute music track. Any help on this would be great.
Another thing that's happening and I'm not sure if they're related problems but the timeline will be playing back and then I try to click stop or anything in Motion and yet it continues to play. Same deal - about 30 seconds before I am able to control the timeline again. This also happens on my Dual 2Ghz G5. Any help would be greatly appreciated.
Yep. A bit inconclusive and even you'd have to admit your explanation is clear as mud. You didn't say much at all that could actually be of any value in tracking down your problem from where I sit. but you can always start with the easy stuff. it's often a good place to start, being easy and all. Try turning off one layer at a time and see...-- oh, nevermind, I've already made that suggestion but you knew you didn't need to try it. Perceptive and shows a deep connection with your system. I bow.
I've exhausted all of my experience, Phil, and I can't write biting sarcasm like this all night, too old. So it's up to you. Make a long list of all the things you know it's not and you'll be left with what it is.
Hope you get it figured out. When you do, please let us know what it was and how you fixed it.
bogiesan -
When scrolling through the browser window quicktime file icons update nicely until they suddenly turn into small white symbols and become unavailable. From that moment it is impossible to open any item in the browser and I need to force quit the application. Any suggestion/idea?
Once in a while I also get green artifacts in the Motion main window.
I am running Motion 3 on a Quadra Mac Pro with 8GB RAM and the X1900 video card. All media on internal RAID. I checked the RAM with memtest and the Apple Hardware Test and no problems found.
Final Cut Pro does also crash often. The application disappears without the "Final Cut quit unexpectedly" message window. All other apps behave normal so far.
Anybody out there with similar problems?Hi Patrick,
here comes my FCP crash logfile. Is there anything that explains the crash?
Thank you very much for any help/advise...!
Command: Final Cut Pro
Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Parent: WindowServer [55]
Version: 6.0 (6.0)
Build Version: 2
Project Name: FCPApp
Source Version: 705022005
PID: 276
Thread: 0
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000000
Thread 0 Crashed:
0 <<00000000>> 0xffff1250 __longcopy + 80 (cpu_capabilities.h:232)
1 <<00000000>> 0xffff086e __memcpy + 206 (cpu_capabilities.h:228)
2 com.apple.procore.framework 0x0fe7c4fb PCBitmap::copy(PCBitmap const&) + 113
3 com.apple.ProMedia 0x2100bb8a QT_GetFrameMoviesTask(PMFormatDescription const&, PCURL const&, unsigned, PMFrameRequest const&, PCBitmap*, void*) + 884
4 com.apple.ProMedia 0x21001286 PMClip::getFrame(PCTimeValue const&, PCTimeValue const&, PMFrameRequest const&, PCBitmap*) + 368
5 com.apple.ProMedia 0x2100176d PMClip::guessAlphaFormat(int, PMAlphaType*, PCColor*, bool*) + 787
6 com.apple.ozone.framework 0x2011e51b OZFootage::guessAlphaFormat() + 109
7 com.apple.ozone.framework 0x20131046 OZFootage::setClip(PMClip*, bool) + 3062
8 com.apple.ozone.framework 0x20131414 OZFootage::parseElement(PCSerializerReadStream&, PCStreamElement&) + 506
9 com.apple.procore.framework 0x0fe83add PCSerializerReadStream::processElement(PCStreamElement&) + 39
10 com.apple.procore.framework 0x0fe862e7 PCXMLReadStream::endStructure(__CFXMLParser*, void*) + 67
11 com.apple.CoreFoundation 0x908689fe parseTag + 2144
12 com.apple.CoreFoundation 0x9086879a parseTag + 1532
13 com.apple.CoreFoundation 0x9086879a parseTag + 1532
14 com.apple.CoreFoundation 0x9086879a parseTag + 1532
15 com.apple.CoreFoundation 0x9086879a parseTag + 1532
16 com.apple.CoreFoundation 0x90866d7a CFXMLParserParse + 687
17 com.apple.procore.framework 0x0fe860d4 PCXMLReadStream::parse() + 22
18 com.apple.ozone.framework 0x200d282f OZDocument::open(PCURL const&) + 93
19 com.apple.ozone.framework 0x203f9147 OZXLoadDocument + 181
20 Motion 0x09d5aeed OZXLoadDocument + 83
21 com.apple.motion.component 0x09d10d31 OZQTImportComponentDispatch + 367
22 ...ple.CoreServices.CarbonCore 0x90ccecba CallComponentFunctionCommon + 1048
23 com.apple.motion.component 0x09d10c3a OZQTImportComponentDispatch + 120
24 ...ple.CoreServices.CarbonCore 0x90cce788 CallComponentDispatch + 34
25 com.apple.QuickTime 0x9439de58 MovieImportDataRef + 91
26 com.apple.motion.component 0x09d10af6 OZQTCodecComponentDispatch + 1309
27 ...ple.CoreServices.CarbonCore 0x90ccecba CallComponentFunctionCommon + 1048
28 com.apple.motion.component 0x09d10c3a OZQTImportComponentDispatch + 120
29 ...ple.CoreServices.CarbonCore 0x90cce788 CallComponentDispatch + 34
30 com.apple.QuickTime 0x943c46c8 MovieImportFile + 85
31 com.apple.QuickTime 0x943c44f0 newMovieFromFileFromComponent + 472
32 com.apple.QuickTime 0x94312c78 getNewMovieFromFileUsingImporters + 522
33 com.apple.QuickTime 0x9431280d NewMovieFromFilePriv + 1396
34 com.apple.QuickTime 0x944027cb NewMovieFromFile_priv + 52
35 com.apple.QuickTime 0x94402788 NewMovieFromFile + 61
36 ...alCutPro.Plugins.QTM Reader 0x0951ab10 PluginStart + 4614
37 ...alCutPro.Plugins.QTM Reader 0x0952af0d isNuggetFile(char const*) + 1245
38 ...alCutPro.Plugins.QTM Reader 0x0952b598 isNuggetFile(char const*) + 2920
39 ...alCutPro.Plugins.QTM Reader 0x09543b69 PluginMainEntry(long, long, KGDictInt*, void*) + 5489
40 com.apple.FinalCutPro 0x0017cdbb pKGOpenFile(KGFileRec*, unsigned long) + 171
41 ...alCutPro.Plugins.QTM Reader 0x0952d2ef isNuggetFile(char const*) + 10431
42 ...alCutPro.Plugins.QTM Reader 0x09543b96 PluginMainEntry(long, long, KGDictInt*, void*) + 5534
43 com.apple.FinalCutPro 0x0017e2b7 GetInfoFromReader(KGFileRec*, KGDictInt*, char*) + 377
44 com.apple.FinalCutPro 0x0017f5c3 pKGFileAddOrCheckImportWithKnownAlias(KGFileSpec*, char*, KGDictInt*, KGFileRec**, KGFileRec**, void*) + 865
45 com.apple.FinalCutPro 0x0017ec0f pKGFileAdd(KGFileSpec*, char*, KGDictInt*, KGFileRec**) + 57
46 ...CutPro.Plugins.Relink Media 0x0957433d PluginStart + 27373
47 ...CutPro.Plugins.Relink Media 0x0957666b PluginStart + 36379
48 ...CutPro.Plugins.Relink Media 0x09576a4b PluginStart + 37371
49 ...CutPro.Plugins.Relink Media 0x09576c84 PluginStart + 37940
50 com.apple.FinalCutPro 0x002942f5 pKGViewMessage(long, long, KGDictInt*, KGViewRecord*) + 25685
51 com.apple.FinalCutPro 0x002942f5 pKGViewMessage(long, long, KGDictInt*, KGViewRecord*) + 25685
52 com.apple.FinalCutPro 0x000c325b pKGSimpleControlMessage(long, long, KGDictInt*, KGViewRecord*) + 3423
53 com.apple.FinalCutPro 0x000c3086 pKGSimpleControlMessage(long, long, KGDictInt*, KGViewRecord*) + 2954
54 com.apple.FinalCutPro 0x0028b769 PPassMouseEvent(KGPanelRecord*, KGDictInt*, long) + 1483
55 com.apple.FinalCutPro 0x002948cf pKGPanelMessage(long, long, KGDictInt*, KGViewRecord*) + 119
56 ...CutPro.Plugins.Relink Media 0x09576ed0 PluginStart + 38528
57 com.apple.FinalCutPro 0x0028af21 pKGPanelWindowProc(long, long, KGDictInt*, void*) + 53
58 com.apple.FinalCutPro 0x0029fbc3 pKGSendWindowMessage(KGWindowRec*, long, long, KGDictInt*) + 93
59 com.apple.FinalCutPro 0x0014d624 HandleMouseDown(OpaqueEventRef*) + 3358
60 com.apple.FinalCutPro 0x0014dad1 DoEvent(OpaqueEventRef*, KGDictInt*) + 685
61 com.apple.FinalCutPro 0x003f3e71 Events(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 69
62 com.apple.HIToolbox 0x92de6537 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1093
63 com.apple.HIToolbox 0x92de5bdc SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 304
64 com.apple.HIToolbox 0x92decfbc SendEventToEventTarget + 56
65 com.apple.HIToolbox 0x92ded44f ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 1169
66 com.apple.HIToolbox 0x92de68ee DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2044
67 com.apple.HIToolbox 0x92de5bdc SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 304
68 com.apple.HIToolbox 0x92decfbc SendEventToEventTarget + 56
69 com.apple.HIToolbox 0x92e30eb3 ToolboxEventDispatcher + 81
70 com.apple.HIToolbox 0x92e30e49 HLTBEventDispatcher + 17
71 com.apple.HIToolbox 0x92ff31da _RunAppModalLoop + 120
72 com.apple.HIToolbox 0x92ff3388 RunAppModalLoopForWindow + 96
73 com.apple.FinalCutPro 0x0028bcc1 pKGDialogRun(KGPanelRecord*, unsigned char, unsigned char, KGDictInt*) + 757
74 ...CutPro.Plugins.Relink Media 0x09578203 PluginMainEntry(long, long, KGDictInt*, void*) + 1627
75 com.apple.FinalCutPro 0x0026b2c3 pKGNotifyFilesOffline(KGDictInt*, long) + 2585
76 ...FinalCutPro.Plugins.Browser 0x0909d5a2 BrowserOpenFile(KGFileRec*, unsigned char, unsigned char) + 2372
77 ...FinalCutPro.Plugins.Browser 0x090a2d20 Browser(long, long, KGDictInt*, KGFileRec*) + 9972
78 com.apple.FinalCutPro 0x001807a2 pKGDisplayFile(KGFileSpec*, char*, unsigned char, unsigned char) + 426
79 com.apple.FinalCutPro 0x00199f34 pKGPromptOpen() + 172
80 com.apple.FinalCutPro 0x0019a7a8 DefaultMenuHandler(long, long, KGDictInt*, void*) + 828
81 com.apple.FinalCutPro 0x00146fd9 HandleMenuCommand(long, unsigned char, unsigned char, unsigned char, KGErrorCode (*)(long, long, KGDictInt*, void*), void*) + 331
82 com.apple.FinalCutPro 0x001471b5 HandleCommand(long, unsigned char, unsigned char, unsigned char) + 251
83 com.apple.FinalCutPro 0x003f433e CommandProcess(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 362
84 com.apple.HIToolbox 0x92de6537 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1093
85 com.apple.HIToolbox 0x92de5bdc SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 304
86 com.apple.HIToolbox 0x92decfbc SendEventToEventTarget + 56
87 com.apple.HIToolbox 0x92e6dabd SendHICommandEvent(unsigned long, HICommand const*, unsigned long, unsigned long, unsigned char, OpaqueEventTargetRef*, OpaqueEventTargetRef*, OpaqueEventRef**) + 405
88 com.apple.HIToolbox 0x92ea18e6 ProcessHICommandWithContextAndModifiers + 60
89 com.apple.HIToolbox 0x92ea1884 SendMenuItemSelectedEvent + 128
90 com.apple.HIToolbox 0x92ea179c FinishMenuSelection(MenuData*, MenuData*, MenuResult*, MenuResult*, unsigned long, unsigned long, unsigned long, unsigned char) + 122
91 com.apple.HIToolbox 0x92e86505 MenuSelectCore(MenuData*, Point, double, unsigned long, OpaqueMenuRef**, unsigned short*) + 515
92 com.apple.HIToolbox 0x92e85fa6 MenuSelect + 100
93 com.apple.HIToolbox 0x92e85f10 StandardMenuBarEventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 104
94 com.apple.HIToolbox 0x92de6537 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1093
95 com.apple.HIToolbox 0x92de5bdc SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 304
96 com.apple.HIToolbox 0x92decfbc SendEventToEventTarget + 56
97 com.apple.HIToolbox 0x92ded9d9 ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 2587
98 com.apple.HIToolbox 0x92de68ee DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2044
99 com.apple.HIToolbox 0x92de5bdc SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 304
100 com.apple.HIToolbox 0x92decfbc SendEventToEventTarget + 56
101 com.apple.HIToolbox 0x92e30eb3 ToolboxEventDispatcher + 81
102 com.apple.HIToolbox 0x92e2f8cb RunApplicationEventLoop + 165
103 com.apple.FinalCutPro 0x00149eb4 KGMainEvent(void*) + 46
104 com.apple.FinalCutPro 0x002a381d main + 59
105 com.apple.FinalCutPro 0x00003416 _start + 216
106 com.apple.FinalCutPro 0x0000333d start + 41
Thread 1:
0 libSystem.B.dylib 0x90024c67 semaphorewait_signaltrap + 7
1 com.apple.FinalCutPro 0x0041b001 Synchronizable::Wait() + 47
2 com.apple.FinalCutPro 0x00407ff4 DisplayQueue::Run() + 702
3 com.apple.FinalCutPro 0x00444cce Thread::RunHelper(void*) + 20
4 libSystem.B.dylib 0x900245c7 pthreadbody + 84 -
I'm following a tutorial on future frame fx step by step and now just got to the part where they go to Inspector and under Timing they choose Hold....well that is not there in my version of Motion. Is it somewhere else or not there at all? Is there another way to accomplish holding a frame of one clip over another clip playing normally in Motion 2?
I know an update will solve things but I'm not there yet.I believe the Scrub filter was available in Motion 2. You should be able to use that to stop playback...
Patrick -
Motion 4 keeps freezing. Nothing else open. Changes take forever
Motion 4 is not working. Not sure if its the imac which is the biggest and newest one or if its motion which is also the newest one. Motion keeps freezing and changes take forever, mouse icon keeps thinking and nothing happens
Dude.
Grow some skin. Imagine this exchange...
Patient: I am a white male in my mid twenties and I don't often feel well.
Doctor: Oh - that's because... oh wait... I have no idea, because you provided absolutely no information.
Patient: I did provide information but you weren't listening. I don't often feel well. What part of that is so hard to get? If you don't want to bother to listen then don't respond with sarcastic comments.
Do you imagine there is one set of circumstances or a single setting that leads to performance issues in every case? Project size, duration, kind of project, content, amount of memory, render settings, disk space, media codec, etc. These are just a few of the details that we have no idea about in your case.
Patrick -
Motion 3 still freezing after after MBP Software Update 1.1
I have just started to use Motion 3 with my new Hi Rez 17" MBP and had a couple of occasions where Motion would freeze completely with the only option being to turn off the MBP and reboot it. I checked the Motion discussions and found that a lot of people had been having trouble with Intel MBP's and Motion after software update 1.0. I was pleased to hear that software update 1.1 was supposed to fix the issues and duely downloaded and installed it.
However, in the past 3 hours I have been trying to work on a motion project (a pretty simple one at that) and motion would have FROZEN AT LEAST 6 TIMES. Disappointed to say the least!
Has anyone else with a similar MBP experienced the same issues with Motion 3 after installing software update 1.1? As it is Motion is next to impossible to use and because the app is not crashing I can't even send off a report to Apple.
Cheers
PeteHi Jose,
Although we don't seem to be any closer to a fix, its good to know I'm not the 'Lone Ranger' on this issue.
A bit more info, in case somebody has any ideas. Since my post, at the suggestion from the guys I bought the MBP from I ran the Extended Hardware Test on the OSX install CD in case I might have some issues with something like the MBP's memory (I am running the full 4GB of RAM by the way). It came up completely fine.
Another thing is that I noticed today that there is a new software update available - the 'MacBook MacBook Pro Software Update 1.0'. It doesn't say in the notes that it has anything to do with any motion fixes but I found the naming convention a bit strange. Maybe this is normal but just because they stick 'MacBook' in front I would have thought Apple would have given a different version number considering MacBook Pros have already had a software update 1.0. I was wondering if I try to run software update 1.1 again whether this might have the desired effect but I think I am probably clutching at straws.
Any other feedback is greatly appreciated.
Cheers
Pete -
Clip freezes about 200 frames into motion
I have some video that I imported using Snapz pro. I can cut it up in Final Cut with no problems, but when I try to send it to motion, the clip will play the first 200 frames, give or take, and then automatically freezes.
I've tried using numerous clips, with different compressors, tried rendering and everything. Any ideas?Well, it must be doing something to the media when I send it motion--When I open the file in motion without involving FCP, it opens fine and I have no problems. But if I take the clip, import it to FCP, put it into a sequence, and say "send to motion", well then the clip will play in motion and freeze somewhere in the 200-300's. So something's happening here, and I've been looking for the answer for hours to no avail...
-
Motion freezes, Mac freezes too
making a pixelated face effect (duplicate clip, apply mask, add pix filter, hit record and follow the movement with mask), Motion keeps freezing after 2 minutes or so of effect (prog is 1hr long!), Mac freezes too except mouse movement. Cure - unplug, reboot > problem recurs.
Clip is self-contained QT from FCP, on internal RAID drive. Tried permissions repair, reboot etc, also logging in as new user - same deal. Anyone else got this trouble?If you figure 1 MB per frame times 30 frames per second times 60 seconds per minute times 60 minutes, my calculator comes to: 108,000 megabytes or 108 gigabytes - your 8 GB ram doesn't quite cut it.
You might try this tip:
http://proapptips.com/tips/article.php?story=20050312040230626
and since 5.1.2 of FCP gives you access to Motion filters, rather than blurring, you could probably use the pixelate filter...
post back,
Patrick
Maybe you are looking for
-
How do I speed up Lightroom on my new Mac Pro (2013)?
I have tried everything suggested in the forums like running imports in parallel, etc., and all my data is on the super fast built-in PCI-Express SSD of the Mac Pro. However, I have numerous speed problems with Lightroom 5.3 (latest version) when imp
-
Question about Processors???
Hi there This is just a question on the posibilities first! We have EHP3 here and using EIC. We have HR Queries going to a certain Org Unit within EIC and anyone under that Org Unit can process, but once the Web Request is converted to an Activity,
-
My iphone 5 is working VERY slow. Web pages are taking forever to open if they ever open at all. Also my Personal Hotspot tethering isn't working properly. Already have tried a hard reset and it didn't work. APPS also aren't working good. This has
-
Java retrieving SQL dbo. scripts
Hi all, I know this falls more under the SQL Database than java. I need to retrieve the Create Scripts of a database's objects. georgemc suggested that I retrieve the scripts directly from the database instead of re-generating the scripts from meta-d
-
I have a plug in error when I try to upload pictures
When I try to upload pictures from the IMAC onto websites, I received a plug in error.