Activity › Forums › Apple Motion › Aaaargh, Motion quits constantly “Ozone Plug in”
-
Aaaargh, Motion quits constantly “Ozone Plug in”
Posted by Conan Stott on April 17, 2008 at 9:51 amHi all.
Is there anything I can do about this? I have done everything so far suggested to me in the apple.com forums about this… Its seems a lot of people get this problem but it also seems they have been able to fix it by removing motion and re’installing or downloading certain updates… I have all this and even resorted to fully erasing my entire hard drive and re-installing….but still every couple of minutes Motion crashes and gives me this “ozone plug in” nonesence. Has anyone got any suggestions for me??? I need to use motion for a job and its driving me insane!!! This is ridiculous, am I the only person in the entire world that has been completely defeated by this problem???
Motion has to be the most unstable programme Ive ever attempted to use…and the worst part is that Final Cut can not do some of the most basic things that you need as an editor so Motion is essential with the studio package.
Please help me if there is a way to fix this problem I really need to know.
Thank you
Best Regards
Conan.Tad Newberry replied 15 years, 5 months ago 10 Members · 14 Replies -
14 Replies
-
David Bogie
April 17, 2008 at 4:37 pmI was going to send you to apple.com.
I do not have this issue with Motion but I have others.
> Motion has to be the most unstable programme Ive ever attempted to use…and the worst
> part is that Final Cut can not do some of the most basic things that you need as an editor so
> Motion is essential with the studio package.INteresting statements, I cannot agree with a single word but I feel your pain. Since the ozone situation is not universal, screaming “bug” won’t help. Over on apple.com we started to look closely at weird hardware conflicts and obscure software conflicts. These things are impossible to diagnose by remote control. We saw a similar and equally frustrating yet totally unresolvable issue with a thread called “LiveType effects misbehavin’.”
bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
Phil Muri
April 17, 2008 at 5:57 pmHello,
I have the exact same problem– with a bit of a twist. When I launch Motion 3, the large window that pops up displaying ‘MOTION 3 UPRGARDE’ never actually disappears.
The next bizarre occurrence is the arrangement of Motion’s main window. It is offset slightly to the right, as opposed to fitting perfectly in the screen.
Lastly– and this is the real kicker… I cannot access my Library, File Browser or Inspector windows! I have tried all my custom window layouts + Motion’s default, cinema, etc. Nothing I do let’s me bring up these three windows– which, as you can imagine makes FCP a better option for motion graphics, since without the inspector, you pretty much can’t exercise any precision on parameter changes.
The only time I receive the Ozone message conflict is when, in an effort to find the windows, Motion 3 will crash.
In the past, prior to Leopard + Motion updates; occasionally the Inspector would be hidden. But with some fiddling around with layouts and re-booting, things returned to normal.
All in all, Motion is currently unusable for me without access to the Inspector window– not to mention the Library & File Browser. I was thinking of re-installing, but now am wondering if (as with the poster who began the thread) it would just be a waste of time.
The bizarre thing is… from one day to the next this problem popped-up. Not even after updating any software. Mid-project. A real nightmare.
Any takers on this problem?
Thanks,
-Phil
-
David Bogie
April 17, 2008 at 10:56 pmAll in all, Motion is currently unusable for me without access to the Inspector window– not to mention the Library & File Browser. I was thinking of re-installing, but now am wondering if (as with the poster who began the thread) it would just be a waste of time.
The bizarre thing is… from one day to the next this problem popped-up. Not even after updating any software. Mid-project. A real nightmare.
Any takers on this problem?
I don’t think a reinstall will help. Sounds more like a, gulp, preferences file issue. Did you try tossing that? Window positions, layouts, and that kind of junk are part of the .plist. However, your description also sounds like it could be graphics card issue. Lots of images going to the card form the core imaging functions of Leopard but they’re getting scrambled on their way to your monitor. All I can think of.
Like I say, I’ve got my own issues but they’re not as ruinous as yours or the OP’s and mine appear to be “simple” FxPlug handling issues..
bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
Phil Muri
April 18, 2008 at 3:36 amHey Boogie,
Thanks for your reply… What would be the exact path of the Motion pref. file. Is it in the user’s Library or just on the disk’s Library folder.
Really appreciate your guidance,
-Phil
-
Matthew Fry
April 29, 2008 at 7:54 pmi truly agree that motion is the most unstable program. i have never lost so many man hours trying to make an expensive program run like it should. i had the ozone problem as well and i know that many others have had it too. i love apple, but it is ridiculous when the can’t make a program that functions on their own OS and their own hardware! it’s not like we are custom building our own PC’s here. these are store bought macs. what really kills me is that a lot of the problems are on a $5k 8 core mac. many of these problems are very wide spread and it is time that apple starts to admit it and resolve the problems.
i reinstalled and updated motion for the 3rd time and it is no longer displaying the ozone problem but i still have one motion file that i really need, and it crashes motion everytime it opens.
ps. don’t even get me started on the problems with compressor!
-
Dan Vink
August 8, 2008 at 3:38 amI had this problem too and trashing the preferences and doing a disk permissions repair did the job for me, the preferences were in the user library.
I’m now getting the ‘ozone plugin’ problem though, i’ve installed the pro apps 08 update but still seems to crash regularly
-
Conan Stott
August 8, 2008 at 11:48 amHi Dan.
I have since discovered from some people in the local industry here and plenty more on the net that the problems with motion are in fact widespread and appear to be the norm rather than the exception. My advice to you is to plan not to use it if your project requires a lot of work outside of final cut. Use another product such as after effects for these kind of projects. On a smaller level of project Ive managed to get some use from motion ( creating DVD menus e.t.c) and I love the interface, I hope it becomes a reliable option in the future, but for projects that require a fair bit of time and complexity in a 2D motion graphics program then i’m afraid Motion would seem to be an unreliable option for now. So plan to use after effects is my advice.
Thanks
Conan.
-
Matthew Schickler
March 29, 2009 at 3:16 pmI also have this problem. In addition, I have situations where Motion will sit and “think” about things I would consider to be simple actions like switching from the timeline to the keyframe editor.
Here’s an example to illustrate how unstable and unusable this problem makes Motion:
Start with a new NTSC DV project. Create a group with some basic elements in it (e.g. a shape and a dropzone). Create a shape to use as a motion path. Add the motion path behavior to the group. Select “geometry” for motion path. When you go to drag and drop the shape to the motion path behavior drop box, software crashes with ozone plug-in failure.
Good grief. That’s not really very advanced stuff there!
Obviously, this doesn’t happen to everyone so the theory of interference from other installed programs makes sense, but is not really an acceptable excuse for a program suite that costs $1200.
I think I’m going to re-install Mac OS X and Final Cut (for the third time) and start using Time Machine so I can revert to an earlier snapshot of my system if things start going bad again……
-
Conan Stott
March 29, 2009 at 11:11 pmMy advice… Use after effects instead. I have tried everything possible to get Motion to behave (Even having the final cut suite as the only apps installed on my Mac) and the answer is quite simple… It doesn’t work. I have had many people say this as well, people who work in post and laugh about the time they thought they would try to use Motion for a project and what a mistake it was. I have had this story told by no less than 3 unconnected individuals. One for a feature he was using FCP to edit, One for a TV doco drama series that the post house he works for was making, another for his short film, and with myself having the problems it simply seems that this program does not work. So save yourself some time, don’t re-install everything ( I did that twice on advice from apple tech’s) Just use another program.
Its a pity as motion seems a good interface and I was looking forward to getting to now it at one point.
Anyhow, thats my gripe and story. Hope you work out a solution.
Regards
Conan
-
J. Tad newberry
June 9, 2009 at 6:03 amcheers…i now have the same problem, though never saw it until a few days ago. I had used Motion 2 quite a bit, then Motion 3 quite a bit when FCS2 came out. Never saw the Ozone failure before a few days ago. Since then, i have gone back to my original graphics card, which is really the only system change i have made, other than adding a few new hard drives. I’ll swap out cards again, putting in my X800 XT again which is pretty much on the verge of complete heat failure, which is why i had taken it out and gone back to my “trusty” (but slow and not-too-powerful) GeForce FX 5200
Thanks again!
J. Tad Newberry
Big Ya Productions
Power Mac G5
Dual 2 GHz
http://www.bigya.tv
Reply to this Discussion! Login or Sign Up