10.7.4 crashing motion 4

Motion 4 is crashing after osx upgrade, do I have to upgrade to Motion5?

shouldn't need to. Many people are running fcp7 and it's associated apps in Lion without a problem.
First try deleting preferences
https://discussions.apple.com/docs/DOC-2491
Here are some other troubleshooting links
https://discussions.apple.com/docs/DOC-2591

Similar Messages

Files crashing Motion on MacBook Pro

I have been using a G5 for a while with great success - I recently got a MacBookPro to use as well, with motion. I have been working on some files that have been causing the MacBook to crash almost every time when using Motion - but the exact same files wil work on the G5 without ever causing a problem.
The files are saved on an external hard drive with a firewire 800 hook up. I just upgraded to Motion 3 and cannot understand why a file will work fine onthe G5 but not on the MacBook. I have 4 gb of ram on the MacBook and 150gb harddrive. But all the files & video clips are saved on the external hard drive.
I have tried to copy the files onto the Mackbook harddrive thinking it might be a combatibility issue with the harddrive but it still causes motion to crash. I have also reinstalled Motion but it has not made a difference at all.
If anyone could offer any suggestions that would be wonderful. I bought the Macbook specifically to use moiton and fcp and it does not seem to want to work at all. Thank-you

Which updates have you installed? If you have on of the newer MacBook Pros (2.2 or 2.4 GHz) they have a new video card that causes Motion 3 to crash. This problem was fixed with an update however.

Export using Compressor crashes Motion

Motion 2.1.2
This problem seems to have surfaced out of nowhere. When using the commandshifte command to export from Motion using Compressor, Motion crashes. Every time. Was fine yesterday and have not done any software updates since. Can export directly out of Motion (but need to do a batch). Trashed Motion and Compressor prefs and repaired permissions. Compressor fires up on its own just fine.
Help?

Export to Compressor using any ProRes format does not work.
If anyone would like me to upload the project I can, but it'll be a big one if I "collect media."
Bottom line, this workflow works in Compressor 3.0, 3.0.1,2 but not 3.0.3. It gets a strange pixelation that is unusable.
I cannot describe my dissatisfaction with Apple right now. My business runs on FCS2 and I have had to start this project (which is on a strict timeline.. aren't they all?) from scratch because there is no way out of this bug. The forward compatibility is another issue altogether, which irritates me beyond description.
I have noticed on these boards, that I often do some unique work and no-one experiences the "exact" same problems I encounter. I do tend to push the limits of what FCS can do, but I am not extraordinary by any means. I simply use it the way it's intended.
Exporting from Motion, using compressor, is the best way to format my graphics for my FCP timeline as I have to export many graphic sequences that need to match my FCP sequence settings. There is no reason the "export to compressor" using a custom compression ProRes preset should result in mangled motion graphics.
TO APPLE: Come the **** on. This is YOUR compression algorithm.
Please if anyone has anything to add here I'm welcome to suggestions.
Currently the only thing I can do to alleviate the problem is to roll-back to FCS/Compressor from disc and re edit my entire sequence.
**** poor. **** poor.

Motion Crashes with all exports

Greetings...
I need some serious help! I'm very frustrated because every time I try to export an animation, Motion crashes with no explanation.
My animation is simple: 30sec, standard 4:3; exporting as uncompressed 8bit with alpha channel. All other settings set to best with motion blur on.
Please help if anyone knows a simple patch.
Cheers!

Hi after several headaches, reinstalls of FCP, etc, i realized that Motion was crashing (in my case), because of 2 specific reasons (Leopard 10.5.2 with FCP with latest updates):
1. Using big or complex vector art (ais), have made crash motion (rendering too), if i set the quality to "best".
Solution: always keep the Quality in the views and render in normal mode.
2. Motion repeatedly crashed, sometimes at the start up, calling for an error in the Ozone or Lithium plugin (almost got crazy for this in a deadline).
Solution: Deactivate the previews in "timeline" and specially "layers" panel, (timeline is deactivated in preferences/appearance/timebar display set to "name", and in layers there is a little arrow in the upper right corner of the panel just uncheck "preview".)
This after several days of trial an error, after this 2 changes i went from almost every minute crashes (including render), to 1 crash at day.
I hope this work for someone else too.

Why does Motion crash when I try to remove rigged parameter?

Each time I try to remove a rigged Mask source drop well Motion crashes.
This video shows the steps I take. Will you please see if you can recreate the crash?
I've tested this on two different Mac computers (Macbook Pro with Lion and Macbook with Snow Leopard) and in both Motion 5.0.6 and 5.0.7 and it crashes everytime.
Steps
Create transition
Add image mask to Transition A
Create Rig
Add Pop Up widget
Create a new group
Rig Mask Source and Inver Mask to Pop Up
Save, Close, Quit Motion
Reopen file
In Pop Up widget right click on Mask Source and select Remove from widget.
Did it crash?

Nobody wants to purposely crash Motion? I don't blame you but it's for science!

Motion crashing EVERY time I open a particular project

I have spent a whole bunch of time working on this very involved comp in Motion. I originally built it back in January and have since shot some new stuff on green screen and have added it in. I went to scroll down my layers in the timeline and every time I do it now crashes Motion. I try to open Motion now and it opens the project. However, the moment I click on the "Timing" button to open up the timeline it crashes Motion. If I use the "Project" tab it slides open fine. I scroll down and once it reveals the lower layers it crashes Motion. I'm not sure what has happened and would really appreciate some help. It allowed me to do the work of adding in, adjusting and matting the new footage. So why now does it keep crashing? Or, does anyone know of a way that I can open the project and figure out what is causing the conflict. I have tried turning off everything possible in the Render drop down and it still crashes. Please help!

hi,
if you haven't already try turning off the preview thumbnails in the timeline and the project windows. That can cause problems sometimes. Hopefully that will allow you to be able to work on the project and isolate what layers are causing your crashes.
hth
adam

Motion 4 Crashes upon jpg import: Kern Protection Failure

Hi,
I'm just starting to use Motion 4 instead of After Effects and I keep running into a problem of it crashing, with the error of "Kern Protection Failure" and the crash seems to be related to quicktime components, but all of mine are apple components (I removed all third party components to the best of my knowledge). The crash occurs consistently every time I try to import a second jpg image. Now, this image brings up a complaint of being of too high a resolution for Motion before it crashes. The first image did that too, but did not crash. Only when I go to add another image. Any ideas? Thanks.
Error report:
Exception Type: EXCBADACCESS (SIGBUS)
Exception Codes: KERNPROTECTIONFAILURE at 0x00000000100a1000
Crashed Thread: 23
with excerpt:
Thread 23 Crashed:
0 ...ickTimeComponents.component 0x9552f6b2 vec_yuvto32BGRAOne + 346
1 ...ickTimeComponents.component 0x9553c83c getyuvMB + 378
2 ...ickTimeComponents.component 0x95547ab0 jpegdecompressClip + 4620
3 ...ickTimeComponents.component 0x95512325 JPEG_DDrawBand + 1723
4 ...ple.CoreServices.CarbonCore 0x92f0e60c CallComponentFunctionCommonWithStorage(char**, ComponentParameters*, long (*)(), unsigned long) + 54
5 ...ickTimeComponents.component 0x95512ae4 JPEG_DComponentDispatch + 114
6 ...ple.CoreServices.CarbonCore 0x92f06cb6 CallComponentDispatch + 29
7 ...ickTimeComponents.component 0x95bc8358 ImageCodecDrawBand + 43
8 ...ickTimeComponents.component 0x9550c43e BaseCodec_DecompressWorkFunction + 1002
9 ...ickTimeComponents.component 0x9550cbc0 BaseCodecDecompressCallBackCommon + 1328
10 ...ickTimeComponents.component 0x9550e88f Base_CDBandDecompress + 5438
11 ...ple.CoreServices.CarbonCore 0x92f0e60c CallComponentFunctionCommonWithStorage(char**, ComponentParameters*, long (*)(), unsigned long) + 54
12 ...ickTimeComponents.component 0x95509cff Base_CDComponentDispatch + 127
13 ...ickTimeComponents.component 0x95512b06 JPEG_DComponentDispatch + 148
14 ...ple.CoreServices.CarbonCore 0x92f06cb6 CallComponentDispatch + 29
15 com.apple.QuickTime 0x990e4a40 ImageCodecBandDecompress + 43
16 com.apple.QuickTime 0x990d2b4d DoBandedDecompress + 17559
17 com.apple.QuickTime 0x990ce4c9 ICMAction + 1177
18 com.apple.QuickTime 0x990cda1b ICMDeviceLoop + 2917
19 com.apple.QuickTime 0x990d604c DecompressSequenceFrameWhen + 714
20 com.apple.QuickTime 0x990d5d7d DecompressSequenceFrameS + 61
21 ...uickTimeImporters.component 0x9780168a importGraphicDrawInternal + 2247
22 ...uickTimeImporters.component 0x97803487 importGraphicDrawOrDecide + 1130
23 ...ple.CoreServices.CarbonCore 0x92f0e60c CallComponentFunctionCommonWithStorage(char**, ComponentParameters*, long (*)(), unsigned long) + 54
24 ...uickTimeImporters.component 0x977fff1f ImportGraphicComponentDispatch + 111
25 ...ple.CoreServices.CarbonCore 0x92f06cb6 CallComponentDispatch + 29
26 com.apple.QuickTime 0x990cb8f1 GraphicsImportDraw + 37
27 com.apple.ProMedia 0x0048f6db GI_GetFrame(PMFormatDescription const&, PCURL const&, unsigned int, PMFrameRequest&, PCBitmap*, void*) + 363
28 com.apple.ProMedia 0x00484a3b PMClip::getFrame(PCTimeValue const&, PCTimeValue const&, PMFrameRequest&, PCBitmap*) + 459
29 com.apple.ozone.framework 0x00712518 OZFootage::readRawFrame(PMLayerDescription const&, PCTimeValue const&, PCTimeValue const&, PMFrameRequest&, PGImageRefTemplate<PCBitmap>&) + 328
30 com.apple.ozone.framework 0x00712d1b OZFootage::loadBitmapHelium(OZRenderParams&, PMFrameRequest const&, PMLayerDescription const&, PCTimeValue const&, PCTimeValue const&, bool) + 1547
31 com.apple.ozone.framework 0x00714f2d OZFootage::getCachedBitmap(OZRenderParams&, PMFrameRequest const&, PMLayerDescription const&, PCTimeValue const&, PCTimeValue const&, PCHash128 const&, bool) + 877
32 com.apple.ozone.framework 0x00715ed5 OZFootage::getBitmap(OZRenderParams&, PMFrameRequest const&, PCHash128 const&) + 421
33 com.apple.ozone.framework 0x0071751f OZFootage::getTexture(OZRenderParams&, PMFrameRequest const&, PCHash128 const&) + 3055
34 com.apple.ozone.framework 0x007185ff OZFootage::getPCImage(OZRenderParams&, PMFrameRequest const&, long*) + 1551
35 com.apple.ozone.framework 0x00718c21 OZFootage::getHeliumGraph(OZRenderParams&, PMFrameRequest const&, HGRenderer*, long*, bool) + 129
36 com.apple.ozone.framework 0x007429c1 OZImageElement::getRetimedHeliumGraph(OZRenderParams&, OZFootage*, OZRenderParams&, PMFrameRequest&, HGRenderer*, long*) + 225
37 com.apple.ozone.framework 0x00743bc9 OZImageElement::getHeliumGraph(OZRenderParams&, HGRenderer*) + 233
38 com.apple.ozone.framework 0x00bbba97 OZImageNodeRender::getHelium(LiAgent&) + 871
39 com.apple.Lithium 0x01639715 LiAgent::getHelium(LiImageSource*) + 4789
40 com.apple.Lithium 0x0164b692 LiPolygonInstance::makeNode(LiClipSet const&) + 1682
41 com.apple.Lithium 0x0167c111 LiRenderInstance::collectGeode(LiGeode*, LiCollectState&) + 929
42 com.apple.Lithium 0x0167cf01 LiRenderInstance::collect3D(LiSceneObject*, LiCollectState&) + 1521
43 com.apple.Lithium 0x0167d3a8 LiRenderInstance::collect3D(LiSceneObject*, LiCollectState&) + 2712
44 com.apple.Lithium 0x0167d3a8 LiRenderInstance::collect3D(LiSceneObject*, LiCollectState&) + 2712
45 com.apple.Lithium 0x0167f4b5 LiRenderInstance::collectPolygons(LiSceneObject*, LiPtrArray<LiPolygonInstance>&) + 1509
46 com.apple.Lithium 0x0167fd35 LiRenderInstance::collect() + 949
47 com.apple.Lithium 0x0167ff91 LiRenderInstance::buildHeliumGraph(LiAgent&) + 529
48 com.apple.Lithium 0x01680a3e LiRenderInstance::getHelium(LiAgent&) + 270
49 com.apple.Lithium 0x015d6ac3 LiRenderer::getHelium(LiAgent&) + 51
...etc

Offhand, I'm gonna say that your pics are of too high a resolution, just like Motion said.
You're limited in the size of pics you can use in Motion. Because the program leverages the gfx card, you should keep picture resolutions within the boundries of your card's texture limit. Typically this is 4000px, but can be 2000px with lower-end cards. Some high-end cards have an 8k limit, but most are around 4k.
Also, your pics need to be RGB mode. Grayscale, CMYK, and other modes can crash Motion or create weird behavior.
Andy

Motion crashing upon open of certain project files (fine otherwise)

I am a fair newbie to Motion and am working through the Apple Pro training book (Motion Graphics and Effects in Final Cut Studio 2). All included project files open fine on my Mac Pro, (leading me to think the project files are fine) but crash Motion on the iMac I'm using. Projects I create from scratch open with no problem on the iMac.
Both Mac's are using the latest OS and application updates.
Below is a copy of the crash report for the crashed thread. Any ideas are gratly appreciated.
Thread: 0
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000004
Thread 0 Crashed:
0 Ozone 0x0133bcd3 -[OZTimelineViewForViewer numberOfRows] + 13
1 Ozone 0x0133b65f -[OZTimelineViewForViewer rowsInRect:] + 35
2 Ozone 0x0133b33a -[OZTimelineViewForViewer drawBackground:] + 366
3 Ozone 0x011d7706 -[OZTimelineView drawRect:] + 806
4 com.apple.AppKit 0x932f13b1 -[NSView _drawRect:clip:] + 3228
5 com.apple.AppKit 0x932f040b -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 614
6 com.apple.AppKit 0x9330236f _recursiveDisplayInRect2 + 149
7 com.apple.CoreFoundation 0x9083eb30 CFArrayApplyFunction + 307
8 com.apple.AppKit 0x932f0613 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1134
9 com.apple.AppKit 0x9330236f _recursiveDisplayInRect2 + 149
10 com.apple.CoreFoundation 0x9083eb30 CFArrayApplyFunction + 307
11 com.apple.AppKit 0x932f0613 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1134
12 com.apple.AppKit 0x9330236f _recursiveDisplayInRect2 + 149
13 com.apple.CoreFoundation 0x9083eb30 CFArrayApplyFunction + 307
14 com.apple.AppKit 0x932f0613 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1134
15 com.apple.AppKit 0x9330236f _recursiveDisplayInRect2 + 149
16 com.apple.CoreFoundation 0x9083eb30 CFArrayApplyFunction + 307
17 com.apple.AppKit 0x932f0613 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1134
18 com.apple.AppKit 0x9330236f _recursiveDisplayInRect2 + 149
19 com.apple.CoreFoundation 0x9083eb30 CFArrayApplyFunction + 307
20 com.apple.AppKit 0x932f0613 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1134
21 com.apple.AppKit 0x932ef473 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 217
22 com.apple.AppKit 0x932eeb78 -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 290
23 com.apple.prokit 0x959abd9d -[NSProWindowFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 101
24 com.apple.AppKit 0x932ee362 -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 523
25 com.apple.AppKit 0x932edc8e -[NSView displayIfNeeded] + 439
26 com.apple.AppKit 0x932eda32 -[NSWindow displayIfNeeded] + 168
27 Ozone 0x012d95af -[OZDocumentWindow displayIfNeeded] + 71
28 com.apple.AppKit 0x9333dd6c _handleWindowNeedsDisplay + 206
29 com.apple.CoreFoundation 0x9082dd6e __CFRunLoopDoObservers + 342
30 com.apple.CoreFoundation 0x9082ce10 CFRunLoopRunSpecific + 827
31 com.apple.CoreFoundation 0x9082cace CFRunLoopRunInMode + 61
32 com.apple.HIToolbox 0x92dec8d8 RunCurrentEventLoopInMode + 285
33 com.apple.HIToolbox 0x92debf19 ReceiveNextEventCommon + 184
34 com.apple.HIToolbox 0x92debe39 BlockUntilNextEventMatchingListInMode + 81
35 com.apple.AppKit 0x93272465 _DPSNextEvent + 572
36 com.apple.AppKit 0x93272056 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 137
37 com.apple.AppKit 0x9326bddb -[NSApplication run] + 512
38 com.apple.prokit 0x9598881d NSProApplicationMain + 324
39 com.apple.motion 0x00005ab8 0x1000 + 19128
40 com.apple.motion 0x0000317e 0x1000 + 8574
41 com.apple.motion 0x000030a5 0x1000 + 8357
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x0133b64a ecx: 0xa0a57184 edx: 0x00000001
edi: 0x11767570 esi: 0x117760a0 ebp: 0xbfffdab8 esp: 0xbfffda80
ss: 0x0000001f efl: 0x00010282 eip: 0x0133bcd3 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
iMac 1.83 GHz Intel Core Duo Mac OS X (10.4.10) 1.5 GB RAM
Mac Pro Mac OS X (10.4.10)
Mac Pro Mac OS X (10.4.10)

Looks like a font issue. Try this:
Create a "virgin" account from the accounts preference panel. Try opening it there.
If it crashes, try again with Console (Application -> Utilities -> Console) open and see if it outputs anything useful when it crashes.

Why are there 2-sets of IMAGE UNITS in Motion 5?

I seem to have 2-sets of Image Units in my Motion 5 library:
The first set has an icon exactly like the Filters icon; the second set has an icon exactly like the Generators icon.
I have read elsewhere online that it appears not everyone has the first set of Image Units, that perhaps it has something to do with running OS 10.7 Lion, but this has not been confirmed. I am currently running Lion, and I do have these Image Units, but they do not seem to do anything when I put them in the Timeline.
Some examples of these Image Units are: 1) Glass Distortion, 2) Glass Lozenge, 3) Copy Machine (transition)... there are 123 of these in the Image Units folder, and it looks like they might do some really cool things if I could get them to work. If I cannot get them to work then I'd like to remove them from the Motion library, if only I could figure out how to do that as well.
If I right-click on the Motion application icon and choose "Show Package Contents" these Image Units do not appear anywhere, and a Spotlight search for "Image Units" does not reveal anything significant either.
Please help me figure out 1) What is this second set of Image Units?
                                      2) If not everyone has them, how did I get mine?
                                      3) How do I get them to work?
                                      4) If they do not work, how do I remove them?
Thanks so much!

1) the 2nd set of Image Units are actually Generators, which means, when applied to the canvas, you will get a Generator Pane in the inspector. You cannot add a generator Image Unit to another object and affect it's appearance as you can with a Filter Image Unit.
You can Apply Filter Image Units to Generator Image Units... LOL but not vice versa.
***STAY AWAY FROM RANDOM GENERATOR*** it does NOT belong to Motion -- it belongs to Core Image and is accessible in Quartz Composer (there are others too, in the filter image units... they will appear to do "nothing" [all of the Area XXXX filters are such]) Clicking on Random Generator has been known (and does for me as well) to crash Motion. If you want or need a random number, use the Numbers generator and click the Random checkbox. For everything else, use the wriggle behavior.
2) Everybody is supposed to have them. If they don't, something screwed up in the installation.
3) Filter Image Units will have parameters under the Filter Tab of the selected object under the heading of the Filter Name or the name you give it in the Layers palette. [Generator Image Units answered in #1]
4) You can't, and you don't want to: they belong to the System (Core Image); but for the ones that do nothing or can crash Motion, you will just have to learn to avoid them.

Motion 3 Terrible Performance On Best Hardware Supposedly

I realise that there is another topic earlier down that has been knocking this question about a bit already.
On a fairly straight forward project using FCS2 I am stuck with an unresponsive and regularly crashing Motion 3. Why is this? Apparently the updates do not work. What should I do?
Can anyone confirm that Motion 3 now works as it should on a machine of my spec? What did you do? I am reluctant to go for any updates unless someone can helpfully suggest that it works well for them.
Pleasingly, DVDSP, FC, Soundtrack, Compressor all work like a dream and really move in a lovely creatively positive manner. Motion 3 - after a short time has all the promise and easy-to-grasp beauty of a true mac product, but doesn't WORK due to freezing, crashing etc.
If only it would. I have the best (almost) laptop available. I count myself very fortunate, but why oh why will this little baby not deliver when it most counts?

Something sounds wrong so do all the updates - a lot has been fixed.
If you still get a problem, reinstall Motion.
Peter

Crashing on export to H.264

I am just getting my feet wet with Motion and have suddenly started experiencing an export issue.
I am putting together some 1 and 2 second motion theme graphics for a trade show. Nothing at all fancy. Just a few basic moves using mostly imported layers of a Photoshop file.
The first few exported fine. I used H.264 compression so I could email the files to people. However the last two have crashed Motion on export. There is motion on four separate elements but only a rotate here and a fade-in there. Nothing crazy. The weird thing is that I CAN export to Apple's 4444 without crashing. I end up with a file over 100 megs but I do have a file. It gets ftp'ed instead of email but at least people can see it.
But really, why do you suppose this is happening? As you can see in my profile, I have a brand new iMac quad i7. It's not like I'm running a piece of junk here. I see no reason that it couldn't handle something so simple.
BTW I just went back to one of the "simpler" animations that DID get exported to H.264 and once again it DID export without a hitch.

well it might not fix your problem, but there are a couple of things to try. If you can export a prorez 444, then import that into compressor and export an h264. You can also try importing the motion project into fcp, drop it on a timeline and Send to compressor form there. I sometimes seem to get different results this way. The other thing to try is to copy the h264 preset you're using in compressor and to fiddle with the settings. it might be a corrupted settings file somewhere.
You might as well throw the preferences for motion and compressor away. lastly you might try turning layers off in your motion project, see if you can narrow it down to a specific item. It could be a corrupted file, or perhaps some layer becoming too big for your graphics card. You could try turning on fixed resolution for any suspect layers.
hth
adam

Thai Font Causing "Ozone" Crash

I am working on a FCS project that has both a Thai and English sequence. One has a Thai narration and Thai titles and cartoons and the other has English narration and English titles and cartoons.
I did all the titles and cartoons in Motion 3.02, using some fancy text behaviours on the main titles and a simple type-on and fade out behavior on the section heading lower-third titles and cartoons. I made three animated cartoons to explain 3 complex concepts and made both Thai and English versions of all three.
I used Lucidia Grande as the font for both Thai and English. Lucidia Grand works OK for Thai in Text Editor and FCP.
For about a week, I had no problems. I embedded the motion projects directly into track v2 of the FCP timeline. Everything worked fine. The Thai fonts displayed and animated nicely and I was able to edit the motion projects by right-clicking to open in editor in the FCP timeline. Great!
Then yesterday, FCP started crashing (unexpectedly quit), whenever I scrolled along to one of the Thai titles in the Thai sequence.
I tried opening the Motion project directly from the project file. But, as soon as I tried to edit anything or play the project, Motion crashed with "problem with Ozone" message.
The English text Motion projects are all still fine. They display OK in FCP, I can open them in Motion from FCP, edit them and save them.
All the Motion projects with Thai, except one cause Motion to Crash +(Fortunately, for the complex cartoons with the Thai content, I exported a .mov file a few days ago, before Motion started crashing on the Thai font. The .mov files are OK in FCP but, of course I can not edit them. For all the other Thai font projects, I have dumped the Motion projects from FCP (had to delete the whole video track as FCP would crash if the individual projects appeared on the screen), and just used FCP's text generator to display the Thai text with a simple fade-in / fade-out.)+
There are two weird things about this problem:
One of the Thai motion projects is still OK. It only has one line of Thai text and uses the Thonburi font (maybe the Lucidia Grande font is the root of the problem?). I can open it in Motion, run it, edit it, no problems. I wanted to get into the other Motion projects and change all their Thai fonts from Lucidia Grande to Thonburi but I can not. Motion crashes before I can edit the text format.
The second weird thing is the way that Motion was working fine for many days, then the problem started occuring, out of the blue. I have installed no new software, changed no settings and done nothing different than before the problem...
I am using all the latest version of OSX and FCS and all updates have been installed.
Regards
Peter

Adam,
I did try disabling the font in the Font book but that did not help. Motion obviously does not check if a font is enabled or disabled. I was going to rename or delete the problem font but the LucidaGrande font is in System>Fonts and the OS says that I do not have enough privileges to rename or delete it, even as the admin user.
For the one remaining crashing Motion project, I bit the bullet and re-built it. Fortunately, the same project in English is working so it was just a matter of changing every text box to "Thonburi" font then "copy and paste" the Thai text in from the TextEdit file where it is kept. Didn't take too long and, at this stage, it is OK for editing and exporting.
So, I am back in business.
Just made a mental note to carefully change the font of all Thai text to a dedicated Thai font, like Thonburi, before saving a Motion project. What's strange is that my Thai-language Motion projects did work OK for quite a few days with the Font set to LucidaGrande and then Motion just started crashing...
I have never quite figured out how these Asian fonts are best handled in Mac OS X. For example, the LucidaGrande font can handle Thai characters, in some software. In MS-Word for Mac, for some strange reason known only in Redmond, Thai fonts can not display in dedicated Thai fonts like Thonburi but will display in LucidaGrande. TextEdit is fine with either Thai fonts or LucidaGrande. Motion appeared to be OK with LucidaGrande, until it started crashing yesterday.
I have also decided that, until Apple improves the stability of Motion, I wont embed Motion projects in the FCP timeline, using export .mov files instead. The biggest headache caused by this font problem was having to remove a whole track of my FCP timeline and having to rebuild it. It was the only way to stop the Motion bug crashing FCP. Took me until 2am last night to get back to where I was at 9am the previous morning...
Thanks for your help.
Regards
Peter

Motion and Compressor Gone Dead

Following a recent replacement of my internal hardrive - the previous one crashed - Motion and Compressor just wont start. I've tried changing users re-installing, trashing preferences, uninstalling, reintalling to no avail. I get the following log
Date/Time: 2006-12-19 22:20:47.612 +0100
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Compressor
Path: /Applications/Compressor.app/Contents/MacOS/Compressor
Parent: WindowServer [70]
Version: 2.0.1 (2.0.1)
PID: 473
Thread: Unknown
Link (dyld) error:
Library not loaded: /System/Library/PrivateFrameworks/Helium.framework/Versions/A/Helium
Referenced from: /Library/Frameworks/Compressor.framework/Versions/A/Frameworks/Transcoding.fram ework/Versions/A/Transcoding
Reason: image not found
and
Date/Time: 2007-02-01 02:29:53.469 +0100
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Motion
Path: /Applications/Motion.app/Contents/MacOS/Motion
Parent: WindowServer [11662]
Version: 2.0.1 (2.0.1)
PID: 11753
Thread: Unknown
Link (dyld) error:
Library not loaded: /System/Library/PrivateFrameworks/Helium.framework/Versions/A/Helium
Referenced from: /Applications/Motion.app/Contents/MacOS/../Frameworks/Ozone.framework/Versions/ A/Ozone
Reason: image not found
Please help someone out there.
Powerbook G4 17" Mac OS X (10.4.3)

Likely you need to reinstall FCS2 but first you could try this:
Here is another way without doing a complete re-install. Pay for and download Pacifist.
1. put your fc studio install dvd in the drive
2. drag the installer icon onto the pacifist icon
3. click "skip" for all the media content
You will see a list of all the install packages on the DVD
4. Select this one: "Contents of MotionGroup"
5. Click the "install" button in the upper left of the window.
6. Only the motion installer will execute and replace all the frameworks, components etc in your library.
The reason that a fresh install does not work, is that the installer assumes an "upgrade" and leaves the original files
in the various library directories alone. These files must be replaced and pacifist will save you about a day's worth of re-installs.
Then there's this:
http://docs.info.apple.com/article.html?artnum=302845

Help when opening motion

Cannot open a new project without motion opening all the previous projects, which crashes motion and won't let me close any of the files. Anyone know how to change the preferences so motion won't open the previous files used?

Hi Abhargreaves,
Thanks for visiting Apple Support Communities.
If Motion is opening past projects unexpectedly, I recommend resetting the Motion preferences as described in step 9 of this troubleshooting guide:
Motion 5: Troubleshooting basics
http://support.apple.com/kb/TS3895
Best Regards,
Jeremy

FCPX keeps on crashing when opening

I use the crash analyzer to try to find out what's going on and I get alternatively the following suspected causes :
- user interface crash
- motion effect
- Graphics card
The problem satrted yesterday. I'm currently working on a 30 minute projects and this is a total disaster. At the begining, It was crashing right after I finish my day editing. Last action was analyzing vifeo for stabilzation. Then FCPX crashed and The project would never open properly. It opens, loads, and few seconds later it crashes.
I did try to open another project and all was fine for 10 minutes so I thought my first 30 minutes project was corrupted. But from the first screen before I open it, I can export a master file so this means FCPX could read it after all.
After several manipulations, I can't access projects library anymore.
I don't know what to do next... Killing myself ?
Please, anyone, if you have an idea, I would be so gratefull.
happy new year

Ok nothing worked for now, and after replacing the event back in its original position.
what about this from DR crash ananlyzer ? Can someone interpret this "relebant line" ?
This crash appears to have been caused by a Motion Effect.
Suggested Actions
Use Housekeeper to run a Comprehensive clean.
Remove third party filters from clips, or use Plugin Manager to disable them completely.
Relevant Line
5 com.apple.Motion.effect 0x000000010a806e6d -[FFMotionEffect _makeLoadedDocReady] + 427

10.7.4 crashing motion 4

Similar Messages

Maybe you are looking for