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.

Name

Email

Title

Comment

Write the displayed characters

Add Comment