Philip Hodgetts live conversation – the good, bad, and future of FCPX – podcast #44

by planetMitch6 Comments

Yesterday, Apple released FCPX (see our blog post) and there were emotions all over the spectrum, so we decided to quickly put together a live conversation with Philip Hodgetts who had been given a copy of FCPX the week before it was released and therefore we had someone with more experience using it than those who had just purchased it yesterday. We wanted some balanced input on the good and bad of FCPX from someone who had worked with Apple – and we got it in this 1 hour 20 minute conversation!

Redrock Micro

The podcast

For feedburner daily email readers: watch the video (note: feedburner and other email systems disable the javascript embed tags so the videos won't display.)


As we predicted, there's a whole bunch of issues to be addressed just like what happened when Apple rewrote iMovie from scratch – and eventually FCPX will be most things to everyone. But those who were expecting a miracle to happen are disappointed and I'm sorry that happened.

FCPX is a fun program and will grow into a great one.

(cover photo credit: snap from the Apple FCPX page)

Zeiss Cinema Lenses


  1. I normally really enjoy Philip Hodgett’s podcasts. But he’s such an uncompromising appologist for Apple on this issue I have to question his intentions. I understand his point that this is a version 1 app and I would be willing to give them that IF they had supported FCP7 until FCPX matured. But since they rashly discontinued support for FCP7 then this, is for all practical purposes, FCP8 and they don’t get much slack. I am not willing to wait 3 interations to see whether this software will mature into a product which supports even the most basic professional work flows. If I have to re-purchase all my plugins and tools then I am buying tools that work with Adobe PP and AE which I’m reasonably sure will have a longer lifespan.

    1. What support do you want for FCP7? It is a stable build that hasnt received any bug fixes in quite a while. Apple doesn’t offer any other support to begin with. If you are expecting Apple to continue development in the FCP7 workflow, that is like expecting TV manufacturers to keep making new models of VCRs just because people still have VHS tapes. Yes, they did jump ship and create a whole new boat, but do you really want to just stick with 32-bit software indefinitely?

      FCPX does have the MOST basic necessities for many professional workflows. Though it does lack in some features, they are not things impossible or unreasonable to add with software update.

      And what I’ve heard from many 3rd party plugin companies is the intent to offer free upgrades on any software not compatible with FCPX as is. And most are saying that they only need to make minor tweaks to make it compatible with FCPX.

      The truth is, yes the did launch it a bit prematurely, but you can run FCP7 and FCPX on the same hardware. You can assess the needs of a project and choose to open it in the new faster interface, or you may need to utilize multi-cam or some other feature not-yet supported on FCPX so you use FCP7. It’s a bit unorthodox but so was the transition from linear editing to non-linear. It’s a new tool, use it when it best suites the project, but don’t force it onto something when your existing workflow may be better suited.

      My issue with the podcast is the audio quality. I feel like I am listening to it will I have a tinfoil q-tip in my ear.

      1. FCPX or FCPiM as I am dubbing it, lacks any and all ability to function in a distributed network environment. Forcing files to be locally stored. Any professional production house with over 3 staff, uses some form of shared NAS system to transition or work jointly on projects. Most of these “Professional” users Have tens of thousands of dollars invested in networking hardware, software and knowledge base. For Apple to wholesale cut off this infrastructure is irresponsible and turns the Professional application into a one user workflow tool, useless in the real world.

        More over this “iTunes” singular storage source for your data means that sharing the footage between users is insanely cumbersome, more so with the death of FCS.
        I have spoken with vendors of Middle and High-End NAS storage solutions, and they while they are trying to find work arounds that will essentially “Fool” FCPX in allowing or duplicating the project folders, they all agree this is an killer to the professional use of the application.

        Oh and for all those clever people out there who found that Lion includes xSan and that will solve the problem allowing for shared mounted volumes…. The infrastructure and support costs of xSan are Prohibitive, each connected workstation requires a separate GigE connection (Above your local/internet connection) on an isolated switched network for connection to a metadata server (another additional system that sole use is metadata) then you need a San network switch and FiberChannel interface cards for each workstation and the Server Managing your Fiber-channel array. So thats 2 Servers, 1 Fiber-Channel Array,
        1 San Switch, 1 GigE switch and cabling all workstation for the second network, and Fiber Channel cards for all workstations. For a 3 user shop, thats about $20-25k.

        Bit like the Bush Jr. Financial plan, give everyone a “Pro” app for $300, but put them into Debt $20k. – Need to go buy more Apple stock.

  2. Pingback: Final Cut Pro X | Chris Weatherly

  3. Pingback: Every Article I Could Find on FCPX | San Diego Final Cut Pro User Group

Leave a Comment