The Ozone Plug-in Error
I ran into this recurring problem recently which, in turn, spurred my semi-annual hunt for information on what it means and how to make it go away.
My search ended when I realized the problem was simply an animated vector graphic that was just too large for my video card to handle. I solved the issue by baking the animation into a movie clip then re-importing it into Motion.
For future reference, and anyone else looking for answers, here are the articles I found to be the most helpful — ordered by helpfulness.
SO I HAVE TO DELETE FINAL CUT PRO.. AND RE DOWNLOAD IT AGAIN.. WILL IT WORK.. SO I HAVE TO MAKE THE FILES 72 DPI FOR IT TO WORK PROPERLY ON MOTION?
My search ended when I realized the problem was simply an animated vector graphic that was just too large for my video card to handle. I solved the issue by baking the animation into a movie clip then re-importing it into Motion.
WHERE DO YOU BAKE THE ANIMATION INTO A MOVIE BEFORE RE-IMPORTING IT INTO MOTION?
THANKS FOR THE HELP.. BECAUSE THIS HAS HAPPENED TO ME TWO TIMES..
Hi. I’m not sure what you’re asking in your first comment. I didn’t mention anything about uninstalling Final Cut Pro. I would recommend that any images you’re working with be at 72dpi, or somewhere thereabout.
To “bake” your animation simply export a movie right from within Motion. Choose File > Export and pick the export settings that you need. When it’s finished exporting you can either reimport that file into your project (and disable all of the layers you just “baked”) or create a new project file and continue building on it from there.
Does that help?
Also, UR CAPS R ON.