Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro X Be Careful Updating FCPX!

  • Be Careful Updating FCPX!

    Posted by Ben Balser on May 23, 2023 at 6:23 pm

    FxPlug 3.0 and Rosetta for FCP plugins do NOT work with latest update! Be warned! Since I rely on mO2 a LOT, I can’t update. Thanks again Apple for updates that are really difficult for plugin makers to keep up with and thus destroy our past work! I rely on mO2 a LOT and it flat out is dead in the new update. Color me not impressed. This doesn’t happen with other NLEs.

    Ben Balser replied 1 year ago 5 Members · 10 Replies
  • 10 Replies
  • Ben Balser

    May 23, 2023 at 9:42 pm

    Motion and Compressor also got updates today, just FYI.

  • Mads Nybo jørgensen

    May 24, 2023 at 9:30 am

    Hey Ben,

    Thank you for the heads up, and for you going through the pain-barrier for the rest of us.

    It sounds like back in the old days of Apple (25+ years ago), where they updated core elements of operating system / software, without bringing software developers from 3rd party companies with them. Often it incurred delays, sometimes complete re-coding of software projects in development…


  • Craig Seeman

    May 24, 2023 at 1:57 pm

    Color Finale also sent out emails warning users not to upgrade.

  • Patrick Donegan

    June 13, 2023 at 7:00 pm

    All the plug in makers have had a chance for a few years now to update to the M1 architecture.

  • Patrick Donegan

    June 13, 2023 at 7:05 pm

    I thought that in those days Apple informed all registered developers ahead of updates.

    I remember many times seeing beta versions of the next update being available for a few months so all the developers could check there code.

  • Mads Nybo jørgensen

    June 13, 2023 at 9:04 pm

    Hey Patrick,

    Not always so, although innovative, Apple was a nightmare to work with back in the days. And, it appears, that Apple might be returning to those days.

    I recommend reading Jim Carlton’s book “Apple”, in case you haven’t already read it.
    (I am trying to give my copy away – it is print only, but free to collect).

    There is also a academic paper written which includes a paragraph on the treatment of third party developers:

    The fall of a Silicon Valley icon:
    Was Apple really Betamax redux?

    Joel West, Ph.D.
    College of Business, San José State University

    Final draft:
    December 12, 2002

    On page 15:

    “Other Factors
    Errors in Execution and Operations

    From the beginning, Apple had suffered from a dysfunctional organizational culture that hindered its execution (Moritz 1984; Malone 1999). Within the company, it was expressed by a joke: “What’s the difference between Apple and a Boy Scout troop? The Boy Scouts have adult supervision.”

    Its numerous failures to deliver major OS revisions killed its credibility and support from third-party software developers; as one executive said, “In the last few years it was impossible for any developer to work with them. We couldn’t rely on anything they said. … We were absolutely convinced they were going to die” (Kirkpatrick, 1998). In hardware, it was late to enter the laptop segment. While its PowerBook models were eventually successful, they lost momentum after a 1995 fire in one model was caused by a faulty battery.

    The company also faced a chronic mismatch of supply and demand, with too few of popular products and bloated inventories of unpopular ones. One reason was that in 1991, the head of Apple’s sales laid off five of seven demand forecasters, raising the margin of error from ±5% to
    ±50% (Carlton 1997a: 329).”

    Joel West, “The fall of a Silicon Valley icon: Was Apple really Betamax redux?”
    in Richard A. Bettis, ed., Strategy in Transition, Oxford: Blackwell, 2005, pp. 274-301.

    Hopefully Apple will listen better this time around, and work faster to help make third-party plug-ins work on FCPX.

    Adding that most of the mainstream developers have already migrated to the M1, and that my understanding is that this is mainly to do with the new Mac-OS.


  • Ben Balser

    June 19, 2023 at 8:21 pm

    I beta test for several 3rd party developers, and am a retired IT manger for software companies. I can tell you that Apple has made it more and more difficult for 3rd party developers to keep up. As for beta versions, don’t compare full apps with plugins, like apples to onions. Plugins depend on the app’s API, which for FCPX is FxPlug, which gets updated faster than many developers can keep up. As for developers using beta versions of FCPX, it is difficult, because during beta testing, bugs are found, coding is changed to fix them, and those changes can break what a developer just coded to keep up to date. It is difficult, and the lates FCPX updated FxPlug with a huge update that introduced a bunch of issues for 3rd party developers.

  • Ben Balser

    June 19, 2023 at 8:22 pm

    It’s not the M1 they have to keep up with, it’s the FxPlug API, which updates very often, and makes it difficult.

  • David Shore

    June 28, 2023 at 12:31 pm

    Right after updating to 10.6.6, all my pre-existing events and projects started hanging up 2-10 seconds on every keystroke. Apple had no answer. I managed the issue by copying and pasting the timelines into new events and projects. Someone suggested the update for iPad functionality corrupted the code.

  • Ben Balser

    June 28, 2023 at 11:34 pm

    I have found numerous bugs in the latest update of FCPX.

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