Final Cut Pro version 10.6 extremely slow!!!

I have a 2015 MacPro (then tricked out to the max with 2 G RAM for video. 10.6 says you need the very minimum of at least 4 G but even more is preferable. 10.6.1 the same. Check on “Requirements for 10.6.1” and see if your machine complies. Those whose machines do and had these problems report that 10.6.1 fixes things. My old silver horse needs to be sent off to the glue factory:-)

Is there

@photowinz, start a new thread (this one is getting long with parallel conversations) and include an Etrecheck report. Use the "Additional text" button below and paste the entire report into the pane. The report will give the hivemind here a chance to help you diagnose why your system isn't working well. There are so many potential reasons, like updating the macOS in place year after year rather than doing a clean install, using an app "cleaner" that actually damages the ProApps, installing Chrome and its problematic keystone daemons which break the system's video toolbox... The list goes on but we can't help you figure it out without more system info, which is what the Etrecheck report does.

Update to 12.1.

Please post an Etrecheck report from https://etrecheck.com, which will provide information about what might be going on. Give the application Full Disk Access in Privacy System Preferences, and use the "Additional text" button at the bottom of the reply box to paste the copied report. 

Are you using third party plugins? Which ones?

Please post an Etrecheck report from https://etrecheck.com, which will provide information about what might be going on. Give the application Full Disk Access in Privacy System Preferences, and use the "Additional text" button at the bottom of the reply box to paste the copied report. 

Update to 10.6.1.

MoonMike wrote:

Hi, Tom! Yes, glad there are data-only backups. However, my issue is that my media rides with the Library and not on a linked folder. This is because some 90% of my media is AVCHD, and at the time it made sense, on importing, to copy those files to my Library, since I couldn't put my hands on the AVCHD footage as individual files.

If I had to do it all over, I'd import the AVCHD files and then, right away, convert them to Optimized ProRes files, which I could then put on a linkable folder and not copied to the Library And then I'd delete the AVCHD. Too late now, as I have some 32 hours of AVCHD.

So for me, having the data-only backups in 10.5.4 is of no use, since the media is copied — and therefore also updated to 10.6 — to my Library.

The media itself is not changed, just the library structure.

You can either:

a) Open (slowly) the library in 10.6, choose a location outside the library and consolidate;

or

b) With FCP not running, open the package contents, and make a Finder copy of the media folders inside the library to some external location

Then you can open a backup library or an exported xml in 10.5.4 and relink the media.

A few things of note in your report:

You are running 11.6; if you want to stay in Big Sur, you should probably update to 11.6.2.

There are several crashes and applications hanging. Is the Wacom driver fully up to date?

Also I see that you are using Paragon software, which is meant to handle NTFS formatted drives.

That is fine, but they should not be used for FCP libraries or for exporting. Use Mac OS Extended or APFS.

I had a few issues with Monterey 12.0.1, but 12.1 seems quite stable.

Of course, always make a full backup or three before upgrading your OS.

I usually do a clean install and then migrate only the user accounts, and reinstall the applications separately.

Even though your system is pretty lean, but because you are having issues, it may be worth doing that.

Many show-stopping problems reported here with 10.6. I suggest you re-install 10.5.4 from your backup.

I have the latest M1 Max 16" MBP. 32RAM 32 GPU cores.

FCP 10.6.1 seemed to have fixed all of my performance issues I was experiencing.

There’s something else going on with the system. The EtreCheck report would be helpful.

It seems to be related to the new MacOs Monterey. Same video loads fast on Big Sur (5 seconds), but it takes almost 5 minutes to load on Monterey. Hopefully Apple will address this issue in the next Monterey patch.

Same problem here. Horrendously slow to load, audio wave-forms take minutes to draw after every cut, and hard-crashing after adjusting audio levels and zooming-out of the timeline.

Deleting all 3rd party effects and transitions from Final Cut helped reduce the number of crashes, but the problems still exist.

Using an 2019 iMac w/Intel, and cant go 5 minutes without FCP 10.6 crashing.. I have seen (many) reports on other forums that it's happening just as much on M1 as Intel.

**Please everyone be sure to report this issue to the Final Cut team! Complaining about it here is no guarantee that the FCP team will hear about how many people are having this issue... You can report it directly to the FCP team here: https://www.apple.com/feedback/finalcutpro.html

I am running a brand new 16" M1 Max - 1Tb - 32gb Unified Memory. I have the same issue as others have described when launching. I also had this issue on my 2016 MBP.

Here are some observations I've made:

• The M1 Max cut the load time in about half or less of my 2016. So the raw horsepower does seem to help.
• Once things are loaded, for the most part things are snappy, but occasionally it will feel the need to "load" an event when I click on it and it will then take the 30-240 seconds.
• When watching Activity monitor during this time, the system is not taxed at all when FCPX is just "Loading...."
• In Activity Monitor, Final Cut Pro Process says "Not responding..." when it is stuck at the loading screen.
• I spend TONS of time removing/updating/reinstalling plugins, and If I load a blank project it opens instantly. So therefore, the plugins just existing does not cause the problem.
• I also created a new library and copied all of the events over and created a blank Project. If I keep all of the event collapsed and then close FCPX and reopen, it loads fast "most" of the time. But then if you expand an event or click into one, you get the slow loading event.
• It is slow in a similar time frame for a 3gb project vs a 96gb project. So size doesn't appear to matter.

That's it for my observations thus far. I agree with the 10.6 being the likely culprit.

Sorry to burst the bubble of all those hoping that their new M1 Max laptop will save the day.. it helps, but doesn't totally save it.