| Fixing The Ozone Problem |
 |
 |
 |
| Written by Administrator | |
| Wednesday, 23 January 2008 03:28 | |
 Motion has been plagued by crashing giving reports that an "Ozone Plugin" was to blame. Here we look at a solution to the problem. There are some things that really ruin your day and having the 'Ozone' problem with one of my templates was definitely one of them. I had followed all the advice from the Apple discussion board saying to install or reinstall OS, ProApps Support, Motion, delete compressor etc - all with no fix!Now here's the science bit:- Ozone is the main internal framework for Motion so there is no surprise that this gets flagged up more than once when there is a problem. What makes life difficult is the fact that there are different crash reasons that will still give the same crash report. A bit like two people blaming their car won't start because of the engine when one has a flat battery and one has run out of petrol. The problems that can be cured by a reinstall (and this should be the first port of call for a fix) have been well documented on the Apple discussion forums Here. Unfortunately I had tried all of those with no luck and believe me hours in front of a computer inserting disks is not my idea of a fun friday night. Worse still was for me it was all a red herring. How did I solve my problem? Simple, by substituting vector media (a PDF) in my Motion project for a same sized PNG file. It looks like Motion cannot render a vector file greater than the graphics card texture limit which depending on your system is 2K, 4K or 8K. My project had this image growing large but most of it offscreen. As soon as I had replaced the graphic the problem never reappeared. What a relief! OK, so you think you've never had the Ozone problem? Well try THIS PROJECT as I bet you within a few minutes it will crash your system, I've yet to come across a machine running 3.0.2 that it will work on. Just as a disclaimer, this wont' harm your system or make you any more liable to crashes :) I hope this helps as I have spent many hours trying to get round this problem. |
More...
Comments (3)
 ...
written by Charles Wren on January 27, 2008 Hi, Upgraded to leopard only to find all my adobe software did not work. Upgraded adobe, as I thought FCP 4.5 was working OK on leopard. Of course that turnes out not to be ture. Upgraded the RAM, the card and purchased studio2. It crashes constantly in FCP, LiveType and motion. Wish I could just get my 2K back and go back to 4.5 and my old adobe software. I work at a large university and am asked constantly by students "Apple/FCP" or "PC/Avid"? From here on out I will nudge them in the direction of PC Avid. FCP aint working for me dawg! Hold on a sec
written by Mark Rezyka on December 24, 2008 Your solution sounds great - but I have no vector files (unless straight text qualifies) in my Motion project. But I keep getting the "ozone plugin " message. If your solution means; don't use text - that kind of defeats the whole point of the software, don't you think? Mark - text is fine, just avoid scaling vector artwork beyond your texture limit. Follow the link on tha Apple board for more possible fixes what else can cause it?
written by Ben Jennings on February 27, 2009 I'm a student in a TV Production class using Motion 3 for 3D graphics and animation. I've drawn 3 rings in motion and, using keyframes, set them to rotate to create kind of an "atom orbital" look around a piece of text. It's really a killer animation, but each of the rings has an effect on them to colorize them, then blur them into 3d, which gives them a cloudy 3d look. The rings are only 200 or 300 px in diameter, but all these properties often gives me the Ozone crash. Almost to the extent that I'm saving every third change or so so that i don't lose work. There's no way I'm exceeding my machine's capabilities, but it keeps crashing... ??? Write comment
|
|
| Last Updated on Monday, 01 March 2010 12:42 |
Show/hide comments
Show/hide comment form
