Thoughts on the 10.1.4 Update to Final Cut Pro X

Posted on by Sudd

Yesterday, Apple updated Final Cut Pro X to version 10.1.4.

Here is a summary of what’s new in version 10.1.4:

Apple also released the Pro Video Formats 2.0 software update, which provides native support for importing, editing, and exporting MXF files with Final Cut Pro X. While FCP X already supported import of MXF files from video cameras, this update extends the format support to a broader range of files and workflows.

For more information about the new MXF support, read:


Immediately after the release, my email lit up with people worrying that the limited new features in this update indicated a lack of interest by Apple in the application. Editors are an impatient bunch.

Keep in mind that this is Apple’s fifth free release in the past 12 months. The 10.1.2 update – which included significant enhancements to libraries, real-time LUT support, OS X Yosemite compatibility, ProRes 4444 XQ, and more – was less than six months ago.

Expanding on the bullet points above, the FCP X 10.1.4 release features key performance improvements including resolving an issue with automatic library backups; I’ve heard about that from a number of users. In addition, the new update introduces support for the AVC-LongG format. A relatively new format from Panasonic, AVC-LongG is part of the AVC Ultra family and provides high quality, high efficiency recording at smaller file sizes. It is being integrated into a number of Panasonic’s pro cameras and video recording devices, which are popular with broadcasters.

NOTE: AVC-LongG support is one of those features that you need if you own Panasonic gear and don’t care about in the least if you don’t.

This brings me to Apple’s Pro Video Formats 2.0 update. This provides native support for import, editing, and export of the increasingly popular Material eXchange Format (MXF). MXF is heavily used in pro video environments for editing, file delivery, and archiving. It’s specified as a delivery standard for European broadcasters, and it’s used as the audio and video packaging format for Digital Cinema Package (DCP).

While many US editors work with ProRes, the new MXF support is a significant upgrade for the video editors and facilities who work with that format. Many of these users are in Europe, where MXF is a delivery standard.

In the past, similar MXF support in FCP (Final Cut Pro 7 or Final Cut Pro X) required the purchase of expensive third-party plug-ins. MXF support is now built directly into not only Final Cut, but also Motion and Compressor and other media tools via today’s update, so editors can work seamlessly with other video products and platforms.


Our industry is evolving at an incredible pace. All of us have our own wish list for Final Cut. Mine includes better collaboration support for small groups, improved audio mixing, better integration between FCP, Motion, and Logic, and improved speed and performance for Compressor. I’m sure your list is equally long and demanding.

None of these requests will surprise Apple. They are continuing to add staff to the Final Cut team and continue to aggressively improve the product. This was “only” a release – principally bug fixes and performance improvements – with continued support for new codecs, cameras and workflows. It wasn’t intended as a major release.

There will be much more to come. Apple is not turning their back on the application, but releasing new updates and upgrades essentially every few weeks.

The recent growth of Premiere Pro and rapid development cycles from Adobe are an excellent incentive for Apple to keep pace. Competition is a wonderful thing.

Look at where we are today. Look at where we were a couple of years ago. The difference is pretty amazing.

Bookmark the permalink.

35 Responses to Thoughts on the 10.1.4 Update to Final Cut Pro X

Newer Comments →
  1. Jay says:

    These are nice, but when are they going to let us resize the inspector window to make it wider? On my 27 inch screen i need to shift my seat to read the fine print. I have asked for this in the contact apple but i will do it again. Thanks for all your wonderful articles Larry, always helpful.

  2. Todd Roberts says:

    Mankind can only dream of a time when relinking proxy files outside of the library is possible. Sigh.

  3. Jeff Orig says:

    I second the motion on improved audio editing/sound design. Right now if you do any kind of sound design in FCPX with sound effects, dialogue, music, and natural sound it turns into a crazy mess of little clips floating all over the place. You can easily have 7 layers of connected clips floating in random levels. I have tried using roles to help manage this but it doesn’t really organize it on the timeline. And compound clips don’t give me the flexibility I need during the edit. I don’t know what could be the solution here. But it is just too messy right now. Just my complaints. I have to say, I have grown quite used to FCPX and tried Premiere the other day and it felt so clunky doing a multicamera edit.

  4. I want Santa to bring me HDTV closed captioning import, export, reading and creation, FROM WITHIN FCPX. Institutional and government operations have a lot of mandates for accessibility in their program output. There HAS to be a better, “different-er” way to transcribe program audio and create closed captions for broadcast inside of FCPX, without resorting to one or more external programs and their tedious workflows. I think FCPX could steal away a lot more market share, if it can create a break thru in this prosaic, yet vital area.

    VEIL or similar embedded encoding ability from within Compressor would also be welcome. I’m always getting asked where our PSA’s or VNR’s get played: with VEIL (or something functionally like it for HDTV) and a fee paid to Neilsen, I’d have an accurate answer.

  5. Thank you for your insightful article. I see the 10.1.4 FCPX release as highly encouraging with respect to Apple’s support of the software. Adding AVC-LongG and MXF seem like strong indicators of commitment to continued development of FCPX. These new features are a major benefit to many in the broadcast media world, a user base for which FCPX design structure seems ideal.

    Like other enthusiastic users of FCPX, there are features I would like to see incorporated into the software that I’ve seen on many lists. But I’m quite happy to see stability improvements, bug fixes and media management enhancements come early.

  6. Kutaba says:

    Can i get some help please. How can i get the clips from my sony HXR-NX5U to work in FCP X. I dont know whats the best wat to import the media. Thanks inadvance.

    • Kutaba:

      First, you should check to see if your camera is supported. In your case, it is.

      Next, you want to copy the entire contents of the camera card into a NEW folder on your hard disk.

      Third, open FCP X, choose File > Import Media and navigate to the folder you just created on your hard disk.

      Select the clips you want to import and click the blue Import button in the lower right corner.



      • Kutaba says:

        Thank you larry, am using 128gb flash memory and i imported directly from it via FCP and i habd copy media selected. I had dont this before reading your adivce. Now this has takeen all my HD space, if I miport it you way donu thing there will be and difrence in size ?


      • Gordon S. says:

        In several of the replies listed above you state: “Next, you want to copy the entire contents of the camera card into a NEW folder on your hard disk.” I copy the entire content of a Canon XA10 and a Canon HF-M31 by creating a “disk image” on an external hard drive. Is creating a “disk image” a good procedure – or – would you recommend a different procedure? Have you created a tutorial video on downloading video clips from the camera to the hard drive?

        • Larry says:


          A disk image is good for archiving, but for editing, I prefer selecting the entire contents of the camera card, then dragging them into a new empty folder on my hard disk using the Finder.


  7. Carl says:

    Will applying this update to FCP Studio 7 knock out my serial number and require me to have to purchase a new serial because it sees it as a FCP X update only, or is it just a standard sort of FCP update that doesn’t mess with serials because it also fixes FCP 7?

  8. Tony Gallardo says:

    Larry, i currently have fcpx 10.1.4 installed with pro video formats also installed, on an iMac 27″, ( late 2013) running os x yosemite, 10.10.1
    i would like to know if this new pro video formats will allow me to capture the files from my mrc1 ( compact flash files m2t files)unit directly to fcpx without having to use a 3rd party transcoder like claptrap.
    Thanks for you time , as i have spent the last 2 weeks researching and reading and am unable to make this work.

  9. Dave F says:

    Hello From Las Vegas
    I am stuck and would appreciate any help that I can get. I am using the latest version of Final Cut Pro x on my iMac. I have videos taken on my Canon HF G10. I have processed the files through Wondershare and made them a .mov and a MP4 file. I can’t get Final Cut Pro to use them in a project. I do not know what I am doing wrong. Would someone direct me to where I can get help with this. I have been working on this for 2days
    Thank You
    Dave F

  10. Oksana says:

    Hi Larry,

    Thank you for all the work and your great sense of humor with which all your videos are done. 🙂
    I am not a pro video editor and I’m learning new things every day.

    It seems I’ve rushed into updating my OS with Yosemite and now, every video I make is broken (picture jumps and looks like old TV) . All the original media is good, while I edit it it’s good, but when video is rendered in final version some broken bits are suddenly appearing. I’ve tried everything. I’ve got ssd with OS and I applied all remedies you were talking about in your SSD-Yosemite problems article. So it’s trimmed.
    My FCX libraries are on other internal HD and FC is on SSD. Any suggestions for a reason it happens?
    (there is enough of space for rendering on both HDs)

    Any suggestions are welcomed, as I’m becoming more desperate with every day. 🙁

    Thank you,

    • Larry says:


      Hmmm… Well, first of all, the TRIM function is not causing this problem, I don’t think. If the original media is good, and editing is good, but final playback is bad, that would tend to rule out Trim.

      Try changing render settings using File > Project Properties. Try sharing using a different video format. See if the errors occur in the same place each time, or different places.

      I don’t know what’s causing this, yet. But one of those steps might help.


Newer Comments →

Leave a Reply

Your email address will not be published. Required fields are marked *

Larry Recommends

Final Cut Pro X 10.4

FCPX Complete

Edit smarter with Larry’s brand-new webinars, all available in our store.

Access over 1,900 on-demand video editing courses. Become a member of our Video Training Library today!


Subscribe to Larry's FREE weekly newsletter and save 10%
on your first purchase.