Final Cut Pro X Ingest Bug — And A Solution

An Image Of A Movie Set Clapboard, The Graphic For Apple's Final Cut Pro X Software

When trying to ingest video clips from the SD card I use in my Canon XA-10, I ran across an irritating Final Cut Pro X ingest bug. Here is what happens:

When I attempt to ingest clips from the SD card File > Import > Files would be the normal command. However, this just leads you to a grayed out directory on the SD card. So, even though I’m not importing from a camera, I selectFile > Import From Camera. No problem, the clips show up in the Camera Import window. However, if you create a new event and try to ingest, this is the error you get:


ErrorMessage Final Cut Pro X Ingest Bug — And A Solution


No storage location set

Cannot start ingest because there is no storage location set. Please set one under Storage in Preferences and try again.

The problem with this is that there isn’t a “Storage” preference in FCPX. You would think it would be under the Import preference panel, but it isn’t:


Final Cut Pro X Import Dialog Box

~ Click To Enlarge ~


And it isn’t under the Editing or Playback preference panels either.

The solution? Don’t try to ingest into a new event. Create a new event first (or ingest to an existing one) and then ingest into it. Voila, clips ingested.

Any other bugs in FCPX that you know of that need fixing?

Final Cut Pro X Ingest Bug.

This entry was posted in Technical, Videos.


  1. Ori Danziger January 11, 2014 at 11:53 am #

    Hi there, first thank you and second it didn’t work for me not with an existing event, not with a new one I have just created before importing

    • Jon Witsell January 11, 2014 at 11:03 pm #

      Hi Ori,

      Hmm, that’s strange. Have you downloaded the latest FCPX update? I am in Laos and don’t have a fast enough connection to get it. I was wondering if that might fix the ingest bug. Have you tried deleting FCPX preferences? I’ve not tried this yet, but you might see if it helps:

      Let me know how you fix the problem!


  2. Mark January 16, 2014 at 4:32 am #

    I have the same problem. Unfortunately this didn’t work

    • Jon Witsell January 17, 2014 at 12:23 am #

      Hi Mark,

      That’s strange. I just ran through the process and it did work. What version of OSX and FCPX are you using?


Post a Comment

Your email is never published nor shared. Required fields are marked *