Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity › Forums › Apple Final Cut Pro Legacy › FCP crashes on launch

  • Apple Final Cut Pro Legacy

    FCP crashes on launch

    Posted by Greg Nosaty on May 25, 2009 at 7:26 pm

    Yesterday Final Cut worked fine (relatively speaking).

    Today when I try to launch FCP 6.0.5 it crashes on launch with an error message that says it is caused by a Motion “ozone” plugin. All the FCP project I have tried to launch contain some kind of simple Motion text files but I don’t ever recall using a plug called Ozone. I do have the Tiffen DFX set for FCP which has a plug called Ozone but I have never used it but besides that is for FCP not Motion.

    Also I can not launch Motion project and I get a similar error message about Ozone.

    I’m re-installing Motion now to see if this corrects the problem but would like to know if anyone else have these problems or might have a solution?

    cheers, greg

    Greg Nosaty replied 16 years, 11 months ago 2 Members · 2 Replies
  • 2 Replies

  • John Fishback

    May 25, 2009 at 8:10 pm

    When FCP suddenely gets weird I trash prefs, repair permissions and run Disk Warrior.

    John

    MacPro 8-core 2.8GHz 8 GB RAM OS 10.5.5 QT7.5.5 Kona 3 Dual Cinema 23 ATI Radeon HD 3870
    ATTO ExpressSAS R380 RAID Adapter, PDE Enclosure with 8-drive 6TB RAID 5
    24″ TV-Logic Monitor
    Final Cut Studio 2 (up to date)

    Pro Tools HD w SYNC IO, Yamaha DM1000, Millennia Media HV-3C, Neumann U87, Schoeps Mk41 mics, Genelec Monitors, PrimaLT ISDN

  • Greg Nosaty

    May 25, 2009 at 11:37 pm

    Thanks for this John, but I’ve already done all that.

    I’ve narrowed the problem down to Motion files that were modified and saved last Friday. Somehow the “ozone” plugin for Motion became corrupted and also corrupted the files that were edited. once I deleted those file from my capture scratch the FCP project opened.

    After re-installing Motion I was able to open the files made on Friday and save them again to my FCP capture scratch and reconnect the media.

    The really strange thing is that I called a colleague to ask him if he had ever seen this problem before and he said it was a new one on him. Then 4 hours later one of his editors tried to open an archived Motion project and got the same error message. It’s like some spooky Y2K bug that corrupted the ozone plugin all over British Columbia!

    cheers,
    Greg Nosaty

    Cinemontage Productions Inc

Reply to this Discussion! Login or Sign Up

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy