After an arduous amount of time spent on this g0d forsaken program, I am throwing my hands up in defeat. Hehe, you have won. I have about two days left to finish a massive project, and Final Cut's insistence in stopping me is quite amusing. The beach ball. The infamous rainbow wheel, everywhere I go, I see it. Every command Z, every delete, every action, he's there. Staring at me, burning my sanity. The rendering. There is no reason in the entire world why he's deciding it's a fine time to start rendering, but he still does it. No matter what. I can't watch my project without the audio no-clipping into the backrooms and the video deciding to take a short lil' break to breathe, and then appear without a moment's notice, seconds later. These are the main issues, that have kept me in the past few days from accomplishing little to nothing.
What is the issue here? Is it that I am editing a heck ton of 4k footage on a 2018 Mac Mini with a 3ghz 6-core intel i5 processor, with 8gb of memory 2667 mhz ddr4? Or maybe, for some obscure reason, it's my graphics card providing only 1536 of MB? Or maybe it's my 4tb hard drive not being fast enough? Or maybe, it's all these random plugins I have clogging up FCPX? Whatever it is, it's causing me to go into conniptions and bury myself in 10 feet snow. Any help would be much appreciated!
(And no, I can't run a darn etrecheck because apparently it's damaged and can't be opened. Screw you, Apple and your useless antics)
For me, it was a corrupted project file, caused by crashes and a system that wasn't happy with my drive set up. Hope the same isn't happening to you because the recovery was long a painful and required a lot of re-work.
Things you can try:
1) Immediately back up your whole project, and by that I mean quit FCPX, and do a backup of everything, your project file, and all your media. Put that in a safe place and don't touch it.
2) Delete your render files. You might have something corrupted in there that's causing FCPX to beachball. support.apple.com/en-ca/guide/final-cut-pro/ver68a8c250/mac
3) If your render files are not at fault, start down the path of going backward in your edit and opening your backups. You may not know this but FCPX has had your back the whole time and been doing automatic backups for you. support.apple.com/en-ca/guide/final-cut-...a9/10.6.2/mac/11.5.1
4) Beyond that, and this is getting into more extreme and desperate territory, see if you can export a master from your existing timeline/project. Do it high-quality like ProRes 422 at least. Start a new library, a new project and import that. Yes, you'll lose the ability to access any of your edits, adjustments. You're basically baking in everything you've done at this point, BUT with 2 days to go, it might just save your project.
Just off the top of my head, but I hope it helps. I'm sure a lot of us have been there too. You're not alone in this.
Without knowing more about your version of FCP, macOS, types of storage (SSD, spinning drive, USB or Thunderbolt, etc.), I'd suggest trying a couple of things:
- Turn off background rendering in FCP preferences.
- Optimize your media, or create ProRes proxies (or both). For proxies, choose frame sizes down to 1/8 of the original 4K resolution. Before export (or color work), you could switch back to original/optimized media (Viewer menu).
These should help with the performance and responsiveness of FCP.
If you can't open/run Etrecheck, that sounds like deeper issues going on. What you're experiencing in FCP is not normal. If it were me, I'd try to get Etrecheck working and post a report here for others to see what's going on.
Some wild guesses:
FCP preferences are corrupt. Reset them.
Chrome and the system killing keystone daemons are installed. chromeisbad.com for instructions on how to completely remove all the cruft Google installs. You should reinstall FCP afterwards.
Drives are formatted to something other than HFS+ or APFS.
CleanMyMac was installed and it damaged your System.
You're running 3rd party antivirus software.
(And no, I can't run a darn etrecheck because apparently it's damaged and can't be opened.
Huzzah! It is a joyous day. I managed to get Etrecheck up and running for the first time, so that's a step in the right direction. (It for some reason previously told me that it was severely damaged. Dunno)
Here is the report: (Main problem seems to be heavy CPU usage by Final Cut and Chrome Helper, so this thing about Google messing with computers performance that I have been hearing about could be the case here possibly, search me)
Problem: Beachballing Description:
Mainly, constant rendering causing my FCPX project to go really slowly
, beachballs any time an action gets performed, (such as command Z, bl
ade tool, simple things), impossible playback with constant frame-rate
Anything that appears on this list needs immediate attention.
Heavy CPU usage - Some processes are using an unusually high amount of CPU.
These issues do not need immediate attention but they may indicate future problems or opportunities for improvement.
No Time Machine backup - Time Machine backup not found. Unsigned files - There are unsigned software files installed. These files could be old, incompatible, and cause problems. They should be reviewed. Runaway user process - A user process is using a large percentage of your CPU. Heavy I/O usage - Your system is under heavy I/O use. This will reduce your performance. Insufficient permissions - EtreCheck running under a standard user. Diagnostic information may not be available. x86-only Apps - This computer has x86-only apps might not work on future versions of the operating system. Limited drive access - More information may be available with Full Drive Access. Kernel extensions present - This computer has kernel extensions that may not work in the future. Sharing enabled - This computer has sharing services enabled that could be a security risk.
Mac mini (2018)
Mac mini Model: Macmini8,1
3 GHz 6-Core Intel Core i5 (i5-8500B) CPU: 6-core
8 GB RAM - Upgradeable
BANK 0/ChannelA-DIMM0 - 4 GB DDR4 2667
BANK 2/ChannelB-DIMM0 - 4 GB DDR4 2667
Intel UHD Graphics 630 - VRAM: 1536 MB
LG TV 3840 x 2160
macOS Monterey 12.0.1 (21A559)
Time since boot: About an hour
Gatekeeper: App Store and identified developers
System Integrity Protection: Enabled
Antivirus software: Apple
Screen sharing: Enabled
Executable: /bin/bash '/Library/Application Support/Qustodio/bin/qproxy/proxy-selector.sh'
Details: Exact match found in the legitimate list - probably OK
Follow the instructions at https::/chromeisbad.com to completely remove all Chrome related files. Just removing the app is not enough. Reboot then reinstall FCP by dragging it to the trash (don't empty it) and go to the AppStore, clicking your name at the bottom left and redownload FCP. Note that this will install the latest version available for your macOS which is FCP 10.6.2.
Also, you have a 2TB drive that's DOS formatted. If it's used with FCP you'll need to reformat as HFS+ or APFS.
While removing Chrome and reinstalling FCP is probably helpful, you still need to consider what I suggested earlier.
My suggestions will definitely have a positive effect on using FCP. In fact, you're still going to see performance issues if you don't implement some or all of what I've mentioned earlier.
Having an external disk formatted with MS-DOS FAT32 limits file sizes to 4 GB, which could cause serious issues, especially if generated files are being stored on that disk. If you are using this disk with FCP, you should re-initialize the volume with macOS Extended (Journaled) ASAP. I recommend APFS only for SSDs (APFS is optimized for use with SSD).
Also, both of your external disks are really "inadequate for purpose" when working with 4K media or on more complex projects. Those drives have a maximum bandwidth of 5 Gb/s (less in realworld usage — USB3.0 connections with a spinning disk typically have a realworld bandwidth from 85 MB/s to 120 MB/s; USB 3.2 and Thunderbolt connected disks can be much faster if they are SSDs, depending on the type of SSD). If the source media uses some variant of AVC/H.264/H.265, it stresses FCP (the computer's CPU) more than if you use ProRes (ProRes requires more storage, of course).
A "worse case" scenario with your current disk setup would be if you tried to edit unoptimized source media at 4k where you're using multicam clips with several angles. This can chew up bandwidth quite fast...
Again, to mitigate the disk I/O bandwidth issue, you should optimize media and make ProRes proxy files. You'll see a huge difference in the FCP UI's responseiveness if you make AND USE proxy files (start with 1/4 size, for example).
The other thing is to disable automatic background rendering in FCP's preferences. You can (manually) force things to render during lunch or a break. Things get rendered fully during export, anyway. You can also generate optimized media or proxy files on a per clip/file basis. This can help you reduce overall storage requirements for a project.
For color correction or complex FX work, you might want to switch from proxy to optimized files. Be sure to do this before final export so that highest quality media is rendered for export.
So, your setup may actually work fine with proxy files. Upgrading your RAM may help, as well.
Your system needs an enema beginning with ditching anything FAT32 related. I can run 4K (using proxy files if an edit gets really heavy) on a geriatic 2009 Mac Pro old soldier so there's all sorts of disjointed hardware / softwate problems with your setup.
...Final Cut's insistence in stopping me is quite amusing. The beach ball. The infamous rainbow wheel, everywhere I go, I see it. Every command Z, every delete, every action, he's there...
As already mentioned, you are running Monterey 12.0.1. There were well-reported memory leaks on that version which could cause problems like you've experienced. That version was released October 25, 2021, whereas the current version is 12.3.1, released March 31 2022. You need to upgrade to the latest version.
- Update to Monterey 12.3.1
- Update to latest FCP version
- Remove Chrome (at least temporarily while you troubleshoot this)
- Get rid of or reformat the FAT32 disk to MacOS Extended Journaled