I'm still getting beach ball spinning on a lot of simple editing on Final Cut Pro 10.6.1 (latest version that many people have reported fixed their old problem).
Can anyone help diagnose if something else is going on with my machine that could be contributing? Here is the Etrecheck report attached:
Mac Pro, macOS 12.0
After FCP crashes it's best practice to delete the preferences, and is an easy thing to try first whenever there are weird problems. Apologies if you said you reset prefs in the other thread--it's too long for me to keep track of who's done what. To delete FCP prefs, hold down option and command when launching FCP and choose Delete Preferences. It will open the default Untitled library. Open the library you were working on, set the prefs back to the way you like (disable background rendering, etc.) and see if things have improved.
You have Chrome installed which is a known potential culprit for ProApp misbehavior. It installs keystone daemons which are background tasks that alway run whether or not Chrome is open and appear to interfere with the low level video subsystem. See https://chromeisbad.com for instructions on how to completely remove Chrome and the keystone daemons. Just trashing the app isn't enough. I believe the consensus here is to reinstall FCP after removing Chrome. (Drag FCP to the trash but don't empty. Go to the App Store and re-download.)
Is the Promise driver current? I'm not familiar with it but it says it's built using the 10.12 SDK which seems kinda old.
The 12TB drive is getting pretty full.
Others may chime in with advice or things they see in the report.
After FCP crashes it's best practice to delete the preferences, and is an easy thing to try first whenever there are weird problems. Apologies if you said you reset prefs in the other thread--it's too long for me to keep track of who's done what. To delete FCP prefs, hold down option and command when launching FCP and choose Delete Preferences. It will open the default Untitled library. Open the library you were working on, set the prefs back to the way you like (disable background rendering, etc.) and see if things have improved.
You have Chrome installed which is a known potential culprit for ProApp misbehavior. It installs keystone daemons which are background tasks that alway run whether or not Chrome is open and appear to interfere with the low level video subsystem. See https://chromeisbad.com for instructions on how to completely remove Chrome and the keystone daemons. Just trashing the app isn't enough. I believe the consensus here is to reinstall FCP after removing Chrome. (Drag FCP to the trash but don't empty. Go to the App Store and re-download.)
Is the Promise driver current? I'm not familiar with it but it says it's built using the 10.12 SDK which seems kinda old.
The 12TB drive is getting pretty full.
Others may chime in with advice or things they see in the report.
> Any other ideas out there?
Clean install Big Sur 11.6.1 (from a bootable USB flash installer, erase the internal SSD device as APFS). Then test FCP with no 3rd party apps, add-ons or extra peripherals. Monterey 12.0.1 reportedly still might have trouble with some external drives.
Make a bootable backup clone with CCC to an external disk first so you can easily restore.
Which drive contains your media? The large 12TB one? That is essentially full, as already noted.
Also, you have several drives, both HD and SSD connected.
I'd try disconnecting drives that are not used for editing and see how that goes.
Having several drives connected, especially HD, can slow things.
And, as suggested, trying a clean install on a separate drive to see if it shows the same problem or not can be useful.
One more thing I just isolated. My timeline had increased from 7mins to 41mins when moving to 10.6 and I couldn't figure out why (which could have also been part of the problem). I just found the clip that was causing the issue. When I replace this clip with the exact same clip from the browser my timeline goes back to 7 mins like it should. The difference between the clips is the little icon that looks like an infinity symbol. What is that? Not sure if this is related or not, but definitely a few weird things going on with my timelines since updated FCP to 10.6 (that didn't go away with 10.6.1)
UPDATE:
I think I finally found the issue so hopefully this helps someone in the future. DELETE the TIMELAPSE files from the timeline (Those that were generated in Final Cut Pro). I ended up opening a few other projects and those without Timelapse files (specifically built in FCP) were running perfectly fine. There must have been an issue when FCP updated from 10.5.4 to 10.6 and then 10.6.1 that caused some serious slow down issue in regards to rendering Timelapse files correctly. I am going to try to rebuild my Timelapse files now to see if it's isolated to prior projects that updated or if Timelapse built within FCP just aren't working well since 10.6 update. Maybe someone else can chime in that works with TL's and let me know what their experience is.
For now, I'm back on track to a useable FCP experience.
I'd start by temporarily disconnecting the HD drive that is full, and see if that helps.
You could also install a clean system on an external SSD and see how that works.
If it works fine, then a clean install should help, otherwise it will not.
Thanks for these tips. I'm willing to try anything as almost anything I do in final cut causes the beach ball (move a clip, trim, slide, revert a change, etc...) I'm about to pull my hair, especially given the hardware I'm working with.
I did delete preferences but will try again. I'll delete Chrome using the page you sent and will try reinstalling afterward.
I was wondering if promise app was causing issues. I'm running their Pegasus 32R8 server which houses my content/project file that I'm currently working in. I will update the firmware on that unit (not sure if that's what you mean vs. driver).
Open to any other tips! Thanks in advance!
Okay, I did the following:
FCP is still SLOW.. It's maybe a fraction of a second faster than before, but still seeing beachball with basic editing functions.
Any other ideas out there?
Thanks Luis and Matti.
Media is on my Pegasus Promise 32 R8 (25TB available out of 84TB). The additional drives (12TB not being used for any related. SSD's are where FCP back-ups, cache reside (1TB out of 8TB used). Do you think that's an issue?
I did a clean reinstall of Big Sur about 2 months ago, but guess I could do that again although sounds painful. I wonder if I should move all of my media to other 8TB SSD and try disconnecting the pegasus? Maybe it's a Monterey issue and not FCP as suggested (Matti).
Appreciate the suggestions...**** what a pain..
Did they work in 5.4? Sounds like the still duration changed. The infinity symbol is a sync clip. Strange to have a sync clip with timelapse in it. Not sure what you built there. Most users convert timelapse stills into video clips at the frame rate you want.
They did work in 5.4, yes.
The Sync clip (pictured) is not a Timelapse. That's a separate issue I guess. It's just a single video clip, but FCP was showing it as a Sync clip and the resulting timeline was increasing from 7 minutes to 41 minutes as a result. Which seems strange.
That is great news.
Are these timelapse composed of many still images? Or video recorded with a very low frame rate?
Luis - I think I found the issue - update below. Thx for your help!
Timelapse are composed of many still images. (which worked prior in 10.5.4)
Final Cut Pro v. 10.6.1 (Still Running Slow)- EtreCheck report included
