Endless Crashing Makes Motion Useless

I'm attempting to use Motion to animate some vector-based characters for DVD output. However, Today Motion has been crashing endlessly, and by that I mean every five minutes or less. In specific, it crashes when I attempt to play the timeline, attempt to Render Out the timeline, or look at it the wrong way. The only way I was able to accomplish anything was by scrubbing frame by frame in the timeline with the arrow keys and animating that way. Of course, I then found out that it crashes while rendering, so that didn't really get me anywhere. This is a portion of the report I get every time:
Date/Time: 2006-01-24 15:38:11.550 -0600
OS Version: 10.4.4 (Build 8G32)
Report Version: 3
Command: Motion
Path: /Applications/Motion.app/Contents/MacOS/Motion
Parent: WindowServer [57]
Version: 2.0.1 (2.0.1)
Build Version: 5
Project Name: Motion
Source Version: 1961000
PID: 215
Thread: 6
Exception: EXCBADACCESS (0x0001)
Codes: KERNINVALIDADDRESS (0x0001) at 0x5b06061a
And here's my computer information found at the bottom of the Report:
Model: PowerMac7,2, BootROM 5.1.4f0, 2 processors, PowerPC 970 (2.2), 2 GHz, 2.5 GB
Graphics: ATI Radeon 9600 Pro, ATY,RV350, AGP, 64 MB
Memory Module: DIMM0/J11, 256 MB, DDR SDRAM, PC3200U-30330
Memory Module: DIMM1/J12, 256 MB, DDR SDRAM, PC3200U-30330
Memory Module: DIMM2/J13, 512 MB, DDR SDRAM, PC3200U-30330
Memory Module: DIMM3/J14, 512 MB, DDR SDRAM, PC3200U-30330
Memory Module: DIMM4/J41, 512 MB, DDR SDRAM, PC3200U-30330
Memory Module: DIMM5/J42, 512 MB, DDR SDRAM, PC3200U-30330
Modem: MicroDash, UCJ, V.92, 1.0F, APPLE VERSION 2.6.6
Network Service: Built-in Ethernet, Ethernet, en0
Serial ATA Device: ST3160023AS, 149.05 GB
Parallel ATA Device: PIONEER DVD-RW DVR-106D,
USB Device: Hub in Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 500 mA
USB Device: USB-PS/2 Optical Mouse, B16b02, Up to 1.5 Mb/sec, 100 mA
USB Device: Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 250 mA
USB Device: Deskjet 9800, HP, Up to 12 Mb/sec, 500 mA
If all the gibberish in between those means anything to anyone, let me know and I'll post it too. I've tried trashing my Motion Preferences, rebooting the PowerMac, and working without external video output, all to no avail. The graphics I'm animating is a cartoon character created in Illustrator and exported as 12 separate layers (each layer its own Illustrator file, since Motion treats Illustrator files as flat files). I then re-assembled my pile of character pieces in Motion like a Mr Potato Head and attempted to animate him. That's when the crashing began. If I have to deal with endless crashing another day, I'm going to revert to construction paper and in-camera stop motion.
Dual 2Ghz Powermac G5 Mac OS X (10.4.4) Motion 2.0.1

Specialcase,
Thanks for your reply. Here are the threads:
Date/Time: 2006-01-24 15:38:11.550 -0600
OS Version: 10.4.4 (Build 8G32)
Report Version: 3
Command: Motion
Path: /Applications/Motion.app/Contents/MacOS/Motion
Parent: WindowServer [57]
Version: 2.0.1 (2.0.1)
Build Version: 5
Project Name: Motion
Source Version: 1961000
PID: 215
Thread: 6
Exception: EXCBADACCESS (0x0001)
Codes: KERNINVALIDADDRESS (0x0001) at 0x5b06061a
Thread 0:
0 libSystem.B.dylib 0x9000b208 machmsgtrap + 8
1 libSystem.B.dylib 0x9000b15c mach_msg + 60
2 com.apple.CoreFoundation 0x9075d114 __CFRunLoopRun + 832
3 com.apple.CoreFoundation 0x9075ca18 CFRunLoopRunSpecific + 268
4 com.apple.HIToolbox 0x9318e1e0 RunCurrentEventLoopInMode + 264
5 com.apple.HIToolbox 0x9318d874 ReceiveNextEventCommon + 380
6 com.apple.HIToolbox 0x9318d6e0 BlockUntilNextEventMatchingListInMode + 96
7 com.apple.AppKit 0x9366b104 _DPSNextEvent + 384
8 com.apple.AppKit 0x9366adc8 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 116
9 com.apple.AppKit 0x9366730c -[NSApplication run] + 472
10 com.apple.prokit 0x95e22514 NSProApplicationMain + 288
11 com.apple.motion 0x0000ec24 0x1000 + 56356
12 com.apple.motion 0x0000d7e8 0x1000 + 51176
13 dyld 0x8fe01048 dyldstart + 60
Thread 1:
0 libSystem.B.dylib 0x9000b208 machmsgtrap + 8
1 libSystem.B.dylib 0x9000b15c mach_msg + 60
2 com.apple.CoreFoundation 0x9075d114 __CFRunLoopRun + 832
3 com.apple.CoreFoundation 0x9075ca18 CFRunLoopRunSpecific + 268
4 com.apple.CoreFoundation 0x9076be78 CFRunLoopRun + 52
5 com.apple.DVCPROHDMuxer 0x04d931ac AVS::DestroyAVCDeviceController(AVS::AVCDeviceController*) + 404
6 libSystem.B.dylib 0x9002b200 pthreadbody + 96
Thread 2:
0 libSystem.B.dylib 0x9000b208 machmsgtrap + 8
1 libSystem.B.dylib 0x9000b15c mach_msg + 60
2 com.apple.CoreFoundation 0x9075d114 __CFRunLoopRun + 832
3 com.apple.CoreFoundation 0x9075ca18 CFRunLoopRunSpecific + 268
4 com.apple.audio.CoreAudio 0x91403434 HALRunLoop::OwnThread(void*) + 264
5 com.apple.audio.CoreAudio 0x914031d4 CAPThread::Entry(CAPThread*) + 96
6 libSystem.B.dylib 0x9002b200 pthreadbody + 96
Thread 3:
0 libSystem.B.dylib 0x90053f68 semaphoretimedwait_signaltrap + 8
1 libSystem.B.dylib 0x900702c8 pthreadcond_timedwait_relativenp + 556
2 ...ple.CoreServices.CarbonCore 0x90b74e90 TSWaitOnSemaphoreCommon + 176
3 ...ickTimeComponents.component 0x8ed87564 ReadSchedulerThreadEntryPoint + 5212
4 libSystem.B.dylib 0x9002b200 pthreadbody + 96
Thread 4:
0 libSystem.B.dylib 0x9002b8a8 semaphorewait_signaltrap + 8
1 libSystem.B.dylib 0x9003001c pthreadcondwait + 488
2 Ozone 0x0129493c OZExecutionUnit::executeLoop() + 76
3 Ozone 0x0129432c OZExecutionUnit::executeLoopWrapper(void*) + 44
4 com.apple.procore.framework 0x00209f64 PCThread::startup(void*) + 36
5 libSystem.B.dylib 0x9002b200 pthreadbody + 96
Thread 5:
0 libSystem.B.dylib 0x9002b928 swtch_pri + 8
1 libSystem.B.dylib 0x9002b8f0 sched_yield + 20
2 com.apple.Helium 0x800418c4 HFAcquireExclusive + 56
3 com.apple.Helium.HCache 0x0a84d4bc HCacheFactory + 2480
4 com.apple.Helium.HCache 0x0a84d12c HCacheFactory + 1568
5 Ozone 0x0138e6b8 OZCacheManager::getHashForKey(PCHash128 const&, PCHash128*) + 104
6 Ozone 0x010491e8 OZScene::getHashForState(PCSerializerWriteStream&, OZRenderParams&) + 280
7 Ozone 0x0125d0b8 GLRenderer::render(OZScene*, OZRenderParams&) + 264
8 Ozone 0x012956b0 OZRenderUnit::processRenderInstruction(OZRenderInstruction*) + 272
9 Ozone 0x01295508 OZRenderUnit::execute() + 56
10 Ozone 0x012949f8 OZExecutionUnit::executeLoop() + 264
11 Ozone 0x0129432c OZExecutionUnit::executeLoopWrapper(void*) + 44
12 com.apple.procore.framework 0x00209f64 PCThread::startup(void*) + 36
13 libSystem.B.dylib 0x9002b200 pthreadbody + 96
Thread 6 Crashed:
0 com.apple.Helium.HCache 0x0a84d430 HCacheFactory + 2340
1 com.apple.Helium.HCache 0x0a84d12c HCacheFactory + 1568
2 Ozone 0x0138e6b8 OZCacheManager::getHashForKey(PCHash128 const&, PCHash128*) + 104
3 Ozone 0x0112e2c0 OZObjectManipulator::getHashForState(PCSerializerWriteStream&, OZRenderParams&, std::list<OZObjectManipulator*, std::allocator<OZObjectManipulator*> >&) + 464
4 Ozone 0x0104d6e8 OZSceneNode::calcHashForState(PCSerializerWriteStream&, OZRenderParams&, std::list<OZObjectManipulator*, std::allocator<OZObjectManipulator*> >&, bool) + 1160
5 Ozone 0x0112e354 OZObjectManipulator::getHashForState(PCSerializerWriteStream&, OZRenderParams&, std::list<OZObjectManipulator*, std::allocator<OZObjectManipulator*> >&) + 612
6 Ozone 0x0104d6e8 OZSceneNode::calcHashForState(PCSerializerWriteStream&, OZRenderParams&, std::list<OZObjectManipulator*, std::allocator<OZObjectManipulator*> >&, bool) + 1160
7 Ozone 0x0112e354 OZObjectManipulator::getHashForState(PCSerializerWriteStream&, OZRenderParams&, std::list<OZObjectManipulator*, std::allocator<OZObjectManipulator*> >&) + 612
8 Ozone 0x01049318 OZScene::getHashForState(PCSerializerWriteStream&, OZRenderParams&) + 584
9 Ozone 0x01294fc4 OZPrefetchUnit::execute() + 132
10 Ozone 0x012949f8 OZExecutionUnit::executeLoop() + 264
11 Ozone 0x0129432c OZExecutionUnit::executeLoopWrapper(void*) + 44
12 com.apple.procore.framework 0x00209f64 PCThread::startup(void*) + 36
13 libSystem.B.dylib 0x9002b200 pthreadbody + 96
Thread 7:
0 libSystem.B.dylib 0x9002b8a8 semaphorewait_signaltrap + 8
1 libSystem.B.dylib 0x9003001c pthreadcondwait + 488
2 Ozone 0x0129493c OZExecutionUnit::executeLoop() + 76
3 Ozone 0x0129432c OZExecutionUnit::executeLoopWrapper(void*) + 44
4 com.apple.procore.framework 0x00209f64 PCThread::startup(void*) + 36
5 libSystem.B.dylib 0x9002b200 pthreadbody + 96
Thread 8:
0 libSystem.B.dylib 0x9002b8a8 semaphorewait_signaltrap + 8
1 libSystem.B.dylib 0x9003001c pthreadcondwait + 488
2 com.apple.ColorSync 0x91550224 pthreadSemaphoreWait(t_pthreadSemaphore*) + 56
3 com.apple.ColorSync 0x9154f4c0 CMMConvTask(void*) + 40
4 libSystem.B.dylib 0x9002b200 pthreadbody + 96
Thread 9:
0 libSystem.B.dylib 0x9002b8a8 semaphorewait_signaltrap + 8
1 libSystem.B.dylib 0x9003001c pthreadcondwait + 488
2 com.apple.Foundation 0x928ed840 -[NSConditionLock lockWhenCondition:] + 68
3 com.apple.AppKit 0x93707d2c -[NSUIHeartBeat _heartBeatThread:] + 324
4 com.apple.Foundation 0x928e66d4 forkThreadForFunction + 108
5 libSystem.B.dylib 0x9002b200 pthreadbody + 96
Thread 10:
0 libSystem.B.dylib 0x90040258 machwaituntil + 8
1 libSystem.B.dylib 0x90040020 nanosleep + 384
2 libSystem.B.dylib 0x900437fc usleep + 60
3 com.apple.DesktopVideoOut 0x07face5c DVOClockGetTime + 1088
4 libSystem.B.dylib 0x9002b200 pthreadbody + 96
Thread 6 crashed with PPC Thread State 64:
srr0: 0x000000000a84d430 srr1: 0x100000000000f030 vrsave: 0x0000000000000000
cr: 0x22000284 xer: 0x0000000020000000 lr: 0x000000000a84d4f8 ctr: 0x000000008004188c
r0: 0x00000000fed1f5e2 r1: 0x00000000f03843f0 r2: 0x00000000f0384500 r3: 0x00000000f0384500
r4: 0x000000005b06061a r5: 0x0000000000000000 r6: 0x0000000000000001 r7: 0x0000000000000000
r8: 0x0000000000000000 r9: 0x00000000f51902ea r10: 0x0000000000000000 r11: 0x0000000000000000
r12: 0x000000008004188c r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
r16: 0x0000000000000000 r17: 0x0000000000000000 r18: 0x0000000040700000 r19: 0x0000000000000000
r20: 0x000000003f700000 r21: 0x0000000002269834 r22: 0x00000000f03846d0 r23: 0x0000000009de2e70
r24: 0x0000000000000001 r25: 0x0000000000000f1c r26: 0x0000000000000000 r27: 0x0000000009de2e40
r28: 0x000000005b060606 r29: 0x00000000f0384500 r30: 0x00000000000003c7 r31: 0x000000000a84d480

Similar Messages

FCP crashes using MOTION files

Hi
85-min doc mostly shot by amateur camera person, wobbly, not steady, hand held...so 75% of the shots I brought to MOTION to stabilize, then brought those into FCP timeline...only 1/3 of the way through this process and FCP crashes every 5 minutes, then takes at least 5 minutes to open up again (relaunch), my 85 min timeline now won't render, says it's out of memory (using MAC PRO 3.0 with 8GB RAM)...crashes, some MOTION files turn orange in the canvas, then beach ball , then FCP crashes...what to do?
Thanks
K

try rendering the movies out of motion, and then import them into the FCP project instead of rendering the Motion files in the timeline. Leave the motion files in the timeline, but disable them (right click on them in the timeline and deselect clip enable). That way, if you need to go back in and tweak them, you can still open the motion file from the timeline, make your changes, re-output a movie file from Motion (save as same name and it will re-link) and you'll find the workflow quite easy.

Since I upgraded to IOS5, my Smart Playlists are in a random order. Since I use it for listening to Talking Books this makes it useless. How can I control the order of a Smart Playlist?

Since I upgraded to IOS5, my Smart Playlists are in a random order. Since I use it for listening to Talking Books this makes it useless. How can I control the order of a Smart Playlist?

It may be best to recreate the folder and the smart playlists from scratch.
tt2

FCP crashing with Motion project in timeline

I have update 10.4.4 and Motion with DeckLink desktop on, works fine, but FCP 5.0.4 crashing with Motion project in timeline.
Karel
G5 DP 2GHz, 2.5 GB RAM, ATI X800 XT, AJA Io, BM DeckLink SP, Medea VideoRaid RT3 Mac OS X (10.4.4) FCP 5 Studio, Combustion 3.04, AE 6.5

Hi, Patrick
here is crash log
Command: Final Cut Pro
Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Parent: WindowServer [114]
Version: 5.0.4 (5.0.4)
Build Version: 2
Project Name: FCPApp
Source Version: 512141418
PID: 416
Thread: 0
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000054
Thread 0 Crashed:
0 com.apple.ozone.framework 0x0aed9550 fegldetach + 32
1 com.apple.ozone.framework 0x0aedbe20 context_finalize + 180
2 com.apple.ozone.framework 0x0aee9b8c fe_release + 484
3 com.apple.ozone.framework 0x0aed94e4 fecontext_glnew + 404
4 com.apple.ozone.framework 0x0aecd7d0 -[MOCIOpenGLContext initWithCGLContext:] + 84
5 com.apple.ozone.framework 0x0adcc510 OZCoreImagingEffect::getImage(OZRenderParams&) + 2208
6 com.apple.ozone.framework 0x0aa52368 OZElement::getImageWithEffects(OZRenderParams&) + 280
7 com.apple.ozone.framework 0x0aa53b40 OZElement::renderElement(OZRenderParams&) + 400
8 com.apple.ozone.framework 0x0aa53918 OZElement::render(OZRenderParams&) + 440
9 com.apple.ozone.framework 0x0aa536a8 OZElement::composite(OZRenderParams&) + 712
10 com.apple.ozone.framework 0x0aa3932c OZScene::render(OZRenderParams&) + 300
11 com.apple.ozone.framework 0x0ac5be84 GLRenderer::doSceneRender(OZScene*, OZRenderParams&) + 260
12 com.apple.ozone.framework 0x0ac5a3e8 GLRenderer::renderNormal(OZScene*, OZRenderParams&) + 72
13 com.apple.ozone.framework 0x0ac5a30c GLRenderer::render(OZScene*, OZRenderParams&) + 860
14 com.apple.ozone.framework 0x0ad64a68 OZXGetFrame + 888
15 com.apple.motion.component 0x00ad8324 dyldstubOZXGetAudio2 + 11347564
16 ...ple.CoreServices.CarbonCore 0x90b5aafc CallComponentFunctionCommon + 1044
17 com.apple.motion.component 0x00ad8d70 OZQTCodecComponentDispatch + 96
18 ...ple.CoreServices.CarbonCore 0x90b5a684 CallComponent + 260
19 ...ickTimeComponents.component 0x8f5e5484 ImageCodecDrawBand + 40
20 ...ickTimeComponents.component 0x8ee6a828 BaseCodec_DecompressWorkFunction + 1124
21 ...ple.CoreServices.CarbonCore 0x90b6d8f4 InvokeComponentMPWorkFunctionUPP + 24
22 ...ickTimeComponents.component 0x8ee68bac BaseCodecDecompressCallBackCommon + 2620
23 ...ickTimeComponents.component 0x8ee6b934 Base_CDBandDecompress + 4196
24 ...ple.CoreServices.CarbonCore 0x90b5aafc CallComponentFunctionCommon + 1044
25 ...ple.CoreServices.CarbonCore 0x90b5a684 CallComponent + 260
26 com.apple.motion.component 0x00ad8d9c OZQTCodecComponentDispatch + 140
27 ...ple.CoreServices.CarbonCore 0x90b5a684 CallComponent + 260
28 com.apple.QuickTime 0x8fad5680 ImageCodecBandDecompress + 40
29 com.apple.QuickTime 0x8fac70b8 DoBandedDecompress + 13780
30 com.apple.QuickTime 0x8fb3fb98 ICMAction_aligned + 1308
31 com.apple.QuickTime 0x8fac38e0 ICMDeviceLoop + 3456
32 com.apple.QuickTime 0x8fac9dfc DecompressSequenceFrameWhen + 860
33 ...ickTimeComponents.component 0x8eda20b4 v2m_rDecompressSequenceFrameWhen + 292
34 ...ickTimeComponents.component 0x8edaa3f8 v2m_decompressVideoFrame + 880
35 ...ickTimeComponents.component 0x8edaaefc QueueAFrame + 2580
36 ...ickTimeComponents.component 0x8edab97c v2m_doWhatTheMentorTellsUs + 1624
37 ...ickTimeComponents.component 0x8edad894 Video2MoviesTask + 2268
38 ...ple.CoreServices.CarbonCore 0x90b5ab68 CallComponentFunctionCommon + 1152
39 ...ple.CoreServices.CarbonCore 0x90b5a684 CallComponent + 260
40 com.apple.QuickTime 0x8fac05dc MediaMoviesTask + 52
41 com.apple.QuickTime 0x8fabf818 TaskMovie_priv + 3608
42 ...alCutPro.Plugins.QTM Reader 0x067a358c GetVideoFrame(KGDictInt*, MovieType**, KGSheetRec*, KGRect*, double, long, unsigned char, unsigned char, unsigned long long, unsigned char, bypassedYUVMatrixInfo*) + 3276
43 ...alCutPro.Plugins.QTM Reader 0x067a47cc FileGetVideo(KGDictInt*) + 2272
44 ...alCutPro.Plugins.QTM Reader 0x067b5c6c PluginMainEntry(long, long, KGDictInt*, void*) + 4144
45 com.apple.FinalCutPro 0x002561a4 pKGGetFileVideo(double, long, unsigned char, KGCanvasRec*, KGRect*, KGDictInt*, KGFileRec*, unsigned long long) + 1708
46 com.apple.FinalCutPro 0x00247eec pKGGetItemThumbnail(double, long, KGCanvasRec*, KGRect*, KGDictInt*, unsigned long long) + 840
47 ...Pro.Plugins.Timeline Editor 0x068610ac Draw1VideoItemThumbnail(TimelineViewRecord*, KGItemSpec*, double*, KGSheetRec*) + 1920
48 ...Pro.Plugins.Timeline Editor 0x0686a8c0 TLProcessThumbnails(TimelineViewRecord*) + 360
49 ...Pro.Plugins.Timeline Editor 0x06854670 TimelineViewMessage(long, long, KGDictInt*, KGViewRecord*) + 12300
50 com.apple.FinalCutPro 0x0015ea4c KGTimerInvoke(__EventLoopTimer*, void*) + 236
51 com.apple.CoreFoundation 0x90770aec __CFRunLoopDoTimer + 184
52 com.apple.CoreFoundation 0x9075d464 __CFRunLoopRun + 1680
53 com.apple.CoreFoundation 0x9075ca18 CFRunLoopRunSpecific + 268
54 com.apple.HIToolbox 0x9318e1e0 RunCurrentEventLoopInMode + 264
55 com.apple.HIToolbox 0x9318d874 ReceiveNextEventCommon + 380
56 com.apple.HIToolbox 0x931d2ca4 AcquireNextEventInMode + 72
57 com.apple.HIToolbox 0x931d2a94 RunApplicationEventLoop + 132
58 com.apple.FinalCutPro 0x00167598 KGMainEvent(void*) + 64
59 com.apple.FinalCutPro 0x002dde40 main + 100
60 com.apple.FinalCutPro 0x0000d83c _start + 392
61 dyld 0x8fe01048 dyldstart + 60
Thread 0 crashed with PPC Thread State 64:
srr0: 0x000000000aed9550 srr1: 0x100000000000d030 vrsave: 0x0000000000000000
cr: 0x24822204 xer: 0x0000000000000000 lr: 0x000000000aed9540 ctr: 0x000000000aed9530
r0: 0x000000000aedbe20 r1: 0x00000000bfffa6e0 r2: 0x000000000b373280 r3: 0x000000003979ade0
r4: 0x0000000000000000 r5: 0x00000000000003e8 r6: 0xffffffffffffffff r7: 0x0000000000000047
r8: 0x0000000000000008 r9: 0x0000000000000000 r10: 0x0000000000000047 r11: 0x000000000b2b012c
r12: 0x000000000aed9530 r13: 0x0000000044822222 r14: 0x0000000000000000 r15: 0x00000000bfffaa00
r16: 0x0000000039772350 r17: 0x00000000bfffa9a0 r18: 0x00000000bfffa9b0 r19: 0x00000000bfffa950
r20: 0x0000000000000000 r21: 0x000000000b28bc94 r22: 0x000000000b28bc94 r23: 0x0000000039734610
r24: 0x0000000000000002 r25: 0x0000000000000000 r26: 0x0000000031d3bc00 r27: 0x000000003979ade0
r28: 0x000000003979ade0 r29: 0x0000000000000000 r30: 0x000000003979ade0 r31: 0x000000000aed9540

My iphone has been stolen, is it possible to do something to make it useless?

Hi to all
my iphone has been stolen. Do you know id it's possible to make it useless and if there is a apple database where I can add his serial number?
Thanks

Only if your carrier offers Blacklisting, so contact them. Some carriers do, some don't. Once Blacklisted(if available), the phone will not be able to be activated for service in whatever country you live in.
Report the loss to the police & your Insurance company, change all of your passwords. Apple does not maintain a database of lost/stolen products and cannot/will not help you.
If Find My Phone was setup/activated, on your phone, before it was stolen, you could login to iCloud.com & try to locate it. Requires that your phone be turned on & have an Internet connection. Otherwise, there is no way to locate your phone.

How do you make Motion templates availabe for all users for FCPX?

How do you make Motion templates availabe for all users for FCPX?

Copy your Motion Templates folder that is in your Movies folder to the movies folder of your other users.

Safari endless crash loop

Safari has gone into an endless crash loop.
Safari starts.... seems to freeze on a blank screen... then crashes.
Can't get it out of the loop.
Restarted Safari.
Tried to start from another link within another app.
Thoughts?

Solved :-)
.....cleared cookies...... fixed it.

Will an SSD make MOTION run faster?

As it says, will it run faster?
I'm currently on a god awful 5400rpm HDD :/
Motion 5 is slightly slow when rendering my projects, it exports fast and all's good. However when i want to play around with my projects it's so juttery.
Espcially when i click PLAY, it won't PLAY, it'll stutter A LOT.
Thoughts?

Heya Matt,
Motion does most of its heavy lifiting with the graphics card. An SSD will technically make Motion run faster, but upgrading the gfx card will produce the best performance increase. Have you tried optimising your playback performance in the Render settings? Draft quality, quarter resolution, etc.
Hope that helps!
Jasper Thayer
Apple Certified Trainer
https://FinalCutProX.net

Vector file makes Motion crash

Hi there everyone. I have a question regarding vector files in motion. I have very small pdf file that I saved in Illustrator. I import it in to Motion 3 and turn off fixed resolution so I can see the sharp vector as it should be. Everything is fine until I go in to 3d mode and start to move the camera around. That's when I get the message "This media is too large to render at full resolution, and will be shown at a lower quality.The maximum size is 4096x4096". After that motion either crashes or everything slows down. Anybody know what is going on? If the pdf file is only 500k why should this cause any problems?

lol...alot of people had this problem before,
http://discussions.apple.com/thread.jspa?threadID=1130609&start=0&tstart=0
or use the path to shape script found here. BTY, thats quiet large for your vector file.

HT201109 Final Cut Pro 10.1 crashes with Motion 5.1 custom Scrolling text and Graphics titles

Dec 29, 2013 1:33 PM
found out why Final Cut 10.1 won't load my custom titles without crashing. When scrolling text in Motion 5.1 if you ad a graphic to scroll with the text Final Cut 10.1 will crash. If I remove the graphic in Motion and then load it into Final Cut 10.1 it will work.
So Graphics and scrolling do not work. The graphics are .jpg, .png, .tiff, .psd. I don't know how to fix it. Hopefully someone out there does.
Dave
Final Cut Pro X, OS X Mavericks (10.9.1), 2.8 GHz Intel Core i7 & 16 GB Ram
Final Cut Pro Quit Unexpectedly
Process:         Final Cut Pro [4123]
Path:            /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Identifier:      com.apple.FinalCut
Version:         10.1 (238755)
Build Info:      ProEditor-23875005025000000~5
App Item ID:     424389933
App External ID: 223682791
Code Type:       X86-64 (Native)
Parent Process: launchd [175]
Responsible:     Final Cut Pro [4123]
User ID:         501
Date/Time:       2013-12-28 12:37:04.233 -0500
OS Version:      Mac OS X 10.9.1 (13B42)
Report Version: 11
Anonymous UUID: E080EF73-4EC7-F729-7343-2C37817936C6

Thanks Tom for the advice. I have four external hard disks, all of them formatted with Mac OS Extended Journaled. On all devices (2TB) I have more than half free space. They are connected either with Thunderbolt or USB3 cables. Different manufactures: LaCie, Toshiba, WD and Samsung. I face the same crash problem if I connect a UBS drive 16GB or a any other device to the USB ports including the Sony Video camera connected with a USB1 cable. Same problem on ALL my computers! To work properly, I have to disconnect all USB devices and work only with internal hard disks. I also tried to format the MacbookPro (erasing the partitions with a new installation) but I have the same problem. I really lost hope...

FCP7.0.3 crashing with Motion template on Snow Leopard

Have upgraded from a Leopard from the 2009 MacPro install of Final Cut Studio3 to Snow Leopard on the current Westmere hardware with the same Final Cut Studio 3 application. The Motion Templates in the FCP application are causing application crashes. Need help what could be the cause!

You may have a ProKit problem.
Consider this:
Restoring an older version of ProKit - Digital Rebellion Blog

Zzzzzrrr..... CRASH! Motion crashing!?

Ok, I JUST installed motion onto my new MBP and motion is crashing when it tries to load the main interface, BUT i dont get a notice that pops up saying that it crashed, it just closes and no Motion Quit Unexpectedly message.... What should i do???

Yes, I have all updates.... I did have final cut studio 1, now I upgraded to FCS2. And I now have the same problem only it freezes my system when trying to work with some templates.....

Endless crashes rendering with After Effects CC

System:
Windows 7 Pro 64bit (all latest updates)
16gb RAM
i5-2200k processor
GTX780 video card
Latest version of After Effects CC
To preface this, I am a novice to After Effects but fairly experienced with other video editing software such as Sony Vegas.
I have been trying to render a simple downloaded audio visualizer/react template for the last 4 days and every time I get some kind of crash. The template has a few layers and particle effects which react to an audio layer.
First it was blue screens of death, usually with the "MEMORY MANAGEMENT" blue screen error about 10-20% into the render. Of course I ran a Windows memory diagnostic, which found no problems. I'm able to use + render from Vegas and Premiere no problem also, I might add, which would seem to indicate that it is not a hardware problem. The system is stable otherwise. I have AE set to use 12gb of RAM - multiprocessing I've tried both ways, on/off. Eventually I found a user suggestion to reduce voltage to my RAM via my BIOS, which I did, and that seemed to stop the blue screen problems.
Next, I would get errors such as "A crash occurred while invoking plugin..." anywhere from 50% to 80% through the render. The exact plugin varied. All are default AE plugins, no 3rd party stuff. For example, one crash occurred with the basic hue/saturation plugin, another with glow. These do not occur ion load or on normal playback. I have tried using the secret preferences to purge every 30 frames, turned off RAM preview, etc.
It's just insane how finicky and unstable this software is. The machine is practically brand new. Very clean installation, latest graphics card drivers, etc. NO problems with any other software including video software so again I find it unlikely to be a general hardware issue. Currently I am working on reinstalling EVERYTHING on the machine with a clean W7 pro install - nothing but W7, CC, and the graphics drivers.

OK, I've totally wiped my system and reinstalled with very little luck. Here is the full list of specs/info as per the FAQ.
After Effects version: 13.0.2.3, 2014.0.2 release (After Effects CC)
Have I installed recent updates: Yes
What OS: Windows 7 Home Premium 64bit. Version 6.1 (Build 7601: SP 1)
Error messages: Currently my system alternates between "MEMORY MANAGEMENT" BSODs, and a series of errors to the effect of "Crash occurred while invoking effect plugin" followed by a series of native AE plugins in my project, such as radial wipe, glow, hue/saturation, etc
What was I doing when problem occurred: In all cases, simply leaving a freshly-rebooted system to render in peace with no other applications open and caps lock ON
Has this ever worked before: I managed to render the project once, somehow, with no errors. I have not changed any settings, hardware, or software since then.
Computer hardware: CPU is i5-2500k @ 3.3ghz 4 cores, 16gb Corsair XMS2 RAM, GTX780 graphics card with LATEST DRIVERS, 20" LED monitor connected via HDMI, USB wireless LAN adapter, USB mouse, PS/2 keyboard, no other peripherals or hardware. OS + AE installed on a FRESH 250gb Samsung SSD. One other HD in the system (500gb normal HD)
Graphics driver version: GeForce 344.11 release date 9/8/2014, version 344.11
Third party i/o hardware: No
Source footage: You can download the exact template I'm using here. http://impactsoundworks.com/work/AudReactV2.rar
QuickTime installed: Yes version 7.7.5 (1680.95.13)
What other software am I running: While using After Effects, nothing except the Adobe CC application, Geforce control panel, and Samsung Magician for my SSD. No firewall no antivirus.
Third-party effects / codecs: None. This occurs with a 100% completely fresh installation of Windows 7 (with all windows updates) and AE CC, with no additions
OpenGL Features in AE: Not sure how to check.
RAM preview, final output?: The problem happens when rendering. Though if I try to play back the projects in real time, after about 5 seconds it says my RAM is maxed out @ 16gb
Using render multiple frames simultaneously? Happens with this feature on AND off, makes no difference.
Ray-traced 3D render: Not sure
Render settings: Occurs with H.264 AND uncompressed AVI, both set to 1920x1080 resolution, 8bit depth, 48khz audio, 24 fps
Please note for clarity, these problems were occurring on my previous installation of Windows with the same machine. So, I put in a 100% new hard drive, installed Windows 100% fresh, with nothing but Adobe CC and the same problems still happened. I then installed Premiere and Sony Vegas. I have been able to use and render from these with NO PROBLEMS at all.
I'm at my wit's end here...

What if a thief unchecks the Find My Mac box in iCloud? Doesn't that make it useless?

Maybe I'm totally missing this, but if a thief grabs my macbook and quickly unchecks the Find My Mac box in the iCloud settings, doesn't that render it useless? I wasn't able to find a way to put a security setting on that section of preferences.

Requiring a passcode to turn off wouldn't be much use. Every electronic device needs a hardware reset function in case the software crashes badly.
So, even if you could prevent the power off in software (by requiring a passcode), you'd only need to perform a hardware reset to bypass it.

Encore CS4 Crashing On Motion Menu Render

Working with a blu-ray project that has a total of 19 motion menus. While attempting to render motion menus, the program crashes and takes me to a crash report screen. I get no error message; just a crash and report screen.
The crash seems random in terms of when it occurs during the render process, so I cannot seem to narrow it down to a particular menu or file. This crash occures both when building the project as well as when I try and render the menus through File>Render>Motion Menus.
I can find very little on the cause online, thus am attempting to post here in hopes that someone can share with me some answer as to how to fix this issue quickly.
Thanks!
Computer Specs:
64-bit Windows 7 Home Premium
3.2GHz AMD Phenom II X4 955 Black Ed Quad-Core Processor
Corsair Vengeance 16GB PC12800 DDR3 RAM - 1600MHz
PCI-E GeForce 9500 GT 1GB 128-bit DDR2

Some other reading and help tips
Odd Errors http://forums.adobe.com/thread/670174?tstart=0
For CS4 you must update the Roxio component http://forums.adobe.com/thread/400484?tstart=0
More on Encore and Roxio http://forums.adobe.com/thread/528582?tstart=0 or direct to
http://kb.roxio.com/search.aspx?URL=/content/kb/General%20Information/000070GN&PARAMS
As well as the below, right click the Encore icon and select Run as Administrator... which is NOT the same thing as running the computer with the Administrator account... and which fixes several "odd" problems
Run as Administrator http://forums.adobe.com/thread/771202?tstart=0
Long File Names or odd characters cause problems
Read http://forums.adobe.com/thread/588273
And #4 http://forums.adobe.com/thread/666558?tstart=0
And This Message Thread http://forums.adobe.com/thread/665641?tstart=0

Endless Crashing Makes Motion Useless

Similar Messages

Maybe you are looking for