Final Cut Pro X - Not Enough Disk Space Available to Process Clips

This message has been haunting my workflow for the last few weeks on this project and I've watched as FCP gets slower and buggier with each passing day. Most annoying of all is that all of my drives have plenty of space (over 100GB). I even deleted the renders and proxy files and it still gives me this message!


Today I can't even move clips on the timeline without it pinwheeling and i'm hoping it's all stemming from this one issue.



Posted on Feb 11, 2022 3:41 PM

Reply
Question marked as Top-ranking reply

Posted on Feb 12, 2022 1:56 PM

Does FCP have Full Disk Access enabled in System Preferences?


Did you try resetting FCP Prefs? Hold option and command while launching FCP and choose Delete Preferences. It will open the default Untitled library. Re-open the library you were working on, set the preferences back to the way you like them (disable background rendering, reset Import to Leave Files in Place, etc.) and see if the issue has been resolved.


Did you dismount and disconnect the ExFAT drive?


If you still have issues, post an https://etrecheck.com report after giving it Full Disk Access. Use the "Additional text" button below in your reply to paste the report.

Similar questions

20 replies
Question marked as Top-ranking reply

Feb 12, 2022 1:56 PM in response to Beanst_lk

Does FCP have Full Disk Access enabled in System Preferences?


Did you try resetting FCP Prefs? Hold option and command while launching FCP and choose Delete Preferences. It will open the default Untitled library. Re-open the library you were working on, set the preferences back to the way you like them (disable background rendering, reset Import to Leave Files in Place, etc.) and see if the issue has been resolved.


Did you dismount and disconnect the ExFAT drive?


If you still have issues, post an https://etrecheck.com report after giving it Full Disk Access. Use the "Additional text" button below in your reply to paste the report.

Feb 12, 2022 2:24 PM in response to Beanst_lk

Chrome and its keystone daemons are installed. Chrome breaks the video toolbox and the daemons are known causes of ProApps problems. To completely remove, follow the instructions at https://chromeisbad.com and then you'll need to reinstall FCP.


Do you have 3rd party plugins and are they up-to-date? There are some popular ones that are not yet compatible with M1.


Full Disk Access in System Preferences->Security & Privacy->Privacy

Feb 12, 2022 2:34 PM in response to Beanst_lk

If there are no problems with fresh library, then I'd look at some sort of corruption in the problem library or project. You can open the problem project's timeline, select all, copy, then paste it into a new, blank project in the freshly created library. This sometimes clears odd corruption issues. It's also possible some media has become corrupt.

Feb 12, 2022 3:52 PM in response to terryb

FIX: I made a new Multicam File. So the majority of the work that I've done in this project was on a Multicam File and I was resisting making a new one since its all manually synced. I found I'm able to copy each angle individually and paste them to the new multicam file but then I just have to sync each line individually or move them to the timecode they start at on the other Multicam. Idk if i'm making more work for myself than I need to but the files are all working now.


I would like to ask if you know any way for me to make the waveforms render quicker? Since I'm manually syncing, most of my work is based on being able to see the waveforms and even though everything else is working smoothly now the waveforms are still taking a long time to render and then have to re-render every time I zoom in or out of the timeline.

Feb 12, 2022 5:28 PM in response to Beanst_lk

Did you try copying the bad project contents into a new project?


I don't know what your timeline looks like but if it's primarily the multicam, I think you could copy the edited bad multicam and paste into your new timeline lined up above the good multicam. Disable the bad multicam and just advance to each edit in the bad multicam and make an edit to match in the good multicam. Basically the bad multicam is just acting as a guide.


If that doesn't work, there might be a geeky way to recover your multicam cuts by editing an exported XML. I haven't tried it so this is conjecture, but I think you'd export an XML of the bad project and an XML of a simple project containing only the good multicam. The open both XMLs in a text editor and note the reference to the good mulitcam. In the bad project XML, change the bad multicam references to the good multicam. Then import the edited XML.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Final Cut Pro X - Not Enough Disk Space Available to Process Clips

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.