🧵 Final Cut Pro 10.6.7 generally unreliable and buggy

latenitefilms commented 1 year ago

NOTE: If you've come here via a social media link, this thread is part of FCP Cafe's Bug Tracker.

You can learn more here: https://fcp.cafe/bugtracker/

FINAL CUT PRO 10.6.8 IS OUT NOW!

If you're currently using Final Cut Pro 10.6.6 or earlier we recommend sticking with that for the time being.

However, if you're already using Final Cut Pro 10.6.7 we recommend updating, as it resolves some issues with the Viewer going black and various crashes.

Please make sure you make a backup of your Final Cut Pro application by creating a ZIP file of it, before updating. You should also manually backup any libraries before updating.

INTRODUCTION:

There's a lot of people out there having serious problems with Final Cut Pro 10.6.7, and yet, there's others that say they haven't had any issues yet. To try and find out what's going on, the purpose of this thread is to document all the different scenarios, so we can see if there's a common cause - for example, maybe it only happens on Apple Silicon or Intel, or maybe it only happens on older versions of macOS.

Dylan Bates - The Final Cut Bro has posted a video here explaining.

DISCUSSIONS ON OTHER FORUMS/GROUPS:

TIPS TO TRY AND MAKE IT MORE STABLE:

Trash your preferences by holding down COMMAND+OPTION when you launch Final Cut Pro.
Make sure you've installed the latest Pro Video Formats 2.2.6.
If that fails, try creating a new User Account on your Mac.

If you're still having issues, please let us know in this thread, and include your macOS version and Mac specs.

WORKAROUNDS:

We recommend sticking with Final Cut Pro 10.6.5 or Final Cut Pro 10.6.6 for now. Whilst there are SOME users that are reporting that 10.6.7 is stable, there's not enough improvements in that version to take the risk.

You can manually copy and paste the older Final Cut Pro application from a backup or another machine to your Mac. Final Cut Pro is a universal app, so the same binary works on both Intel and Apple Silicon.

Inside the Final Cut Pro application bundle is your unique App Store receipt - therefore it's only recommended use share your Final Cut Pro application with machines that are using the same Apple ID, otherwise it might trigger Apple's copy protection processes.

If you don't have a copy of Final Cut Pro 10.6.5 handy, if you have an older machine running macOS Big Sur, you can download Final Cut Pro 10.6.5 on it. You can download a copy of macOS Big Sur here and install it on an external SSD.

If you're already updated a library to Final Cut Pro 10.6.7's format, Final Cut Pro will have automatically made a backup in your backups folder prior to the migration. Alternatively, you can also export out a FCPXML and import it into an older version, keeping in mind that FCPXML isn't lossless (i.e some Title parameters don't apply correctly).

BUG & CRASH TRACKER:

Below is an evolving table of known hardware/software configurations that have reported issues:

Mac	macOS Version	Reported Crashes/Bugs
MacBook Pro (16-inch, 2023)	macOS Ventura 13.4.1	YES
	macOS Ventura 13.5	YES
MacBook Pro (14-inch, 2023)	macOS Ventura 13.4.1	YES
	macOS Ventura 13.5	YES
MacBook Pro (13-inch, M2, 2022)	-	not enough data yet
MacBook Pro (16-inch, 2021)	macOS Monterey 12.6.6	YES
	macOS Ventura 13.4.1	YES
	macOS Ventura 13.5	YES
MacBook Pro (14-inch, 2021)	macOS Ventura 13.5	YES
MacBook Pro (13-inch, M1, 2020)	macOS Ventura 13.5	YES
MacBook Pro (13-inch, 2020, Two Thunderbolt 3 ports)	-	not enough data yet
MacBook Pro (13-inch, 2020, Four Thunderbolt 3 ports)	-	not enough data yet
MacBook Pro (16-inch, 2019)	-	not enough data yet
MacBook Pro (13-inch, 2019, Two Thunderbolt 3 ports)	-	not enough data yet
MacBook Pro (15-inch, 2019)	-	not enough data yet
MacBook Pro (13-inch, 2019, Four Thunderbolt 3 ports)	-	not enough data yet
MacBook Pro (15-inch, 2018)	-	not enough data yet
MacBook Pro (13-inch, 2018, Four Thunderbolt 3 ports)	-	not enough data yet
MacBook Pro (15-inch, 2017)	-	not enough data yet
MacBook Pro (13-inch, 2017, Four Thunderbolt 3 ports)	-	not enough data yet
MacBook Pro (13-inch, 2017, Two Thunderbolt 3 ports)	-	not enough data yet
-
Mac Studio (2023)	macOS Ventura 13.1	YES
	macOS Ventura 13.5	YES
Mac Studio (2022)	macOS Ventura 13.4.1	YES
	macOS Ventura 13.5	YES
-
Mac Pro (2023)	-	not enough data yet
Mac Pro (2019)	macOS Ventura 13.5	YES
-
MacBook Air (15-inch, M2, 2023)	macOS Ventura 13.5	YES
MacBook Air (M2, 2022)	macOS Ventura 13.5	YES
MacBook Air (M1, 2020)	macOS Ventura 13.5	YES
MacBook Air (Retina, 13-inch, 2020)	-	not enough data yet
MacBook Air (Retina, 13-inch, 2019)	-	not enough data yet
MacBook Air (Retina, 13-inch, 2018)	-	not enough data yet
-
MacBook (Retina, 12-inch, 2017)	-	not enough data yet
-
iMac Pro (2017)	-	not enough data yet
-
iMac (24-inch, M1, 2021)	-	not enough data yet
iMac (Retina 5K, 27-inch, 2020)	-	not enough data yet
iMac (Retina 5K, 27-inch, 2019)	-	not enough data yet
iMac (Retina 4K, 21.5-inch, 2019)	-	not enough data yet
iMac (Retina 5K, 27-inch, 2017)	macOS Ventura 13.4.1	YES
	macOS Ventura 13.5	YES
iMac (Retina 4K, 21.5-inch, 2017)	-	not enough data yet
iMac (21.5-inch, 2017)	-	not enough data yet
-
Mac mini (2023)	-	not enough data yet
Mac mini (M1, 2020)	-	not enough data yet
Mac mini (2018)	-	not enough data yet

THIRD PARTY PLUGINS:

It's important to note that since Final Cut Pro 10.6.6 Apple has dropped FxPlug3 support.

In Final Cut Pro 10.6.5 and earlier, FxPlug3 plugins ran "inside" Final Cut Pro, and a bad plugin could crash Final Cut Pro.

However, since Final Cut Pro 10.6.6, only FxPlug4 is supported, and all FxPlug4 plugins are run "out of process" - meaning they're effectively their own application, and if they crash, Final Cut Pro doesn't. Generally speaking if a FxPlug4 plugin crashes, then Final Cut Pro will just try restart it, and if it crashes 5 times or so, then it'll display the "this plugin is not responding" message. Workflow Extensions also run out of process.

What this means is that since Final Cut Pro 10.6.6, if Final Cut Pro crashes, it's NOT a third party FxPlug4 effect or a Workflow Extension - it's something in Apple's own code, and there's nothing third party developers can do about it, so there's no point emailing FxFactory, CoreMelt, MotionVFX, etc. to complain.

This is explained in more detail on FCP Cafe here.

STABLE:

Cole writes:

Just wanna put out that it auto updated for me it’s been behaving very well so far. I cranked out an 8K video today with no issues. Granted I wasn’t using plugins but I do have a decent amount installed. Need to report this to plug-in makers alongside Apple.

Noah Leon originally writes, then updates:

I've been remarkably stable, and they even fixed a bug which I had in 10.6.6. Of course, I recently did a complete wipe and reinstall of my system to clear out five years of gremlins, and I chose not to install many of my geriatric plugins, could be why.

Now my problems have started. I created h264 proxies so I could edit on the train, and I'm getting mucho stuck viewer and crashes. In Proxy-preferred mode.

Vertical Online writes:

Surprisingly stable here....✌️

MBP 16-inch M1 Max. 64GB. macOS 13.4.1 (c) w/FCP 10.6.7 - just finished a pretty substantial project and (haphazardly) upgraded mid-project to the public release of FCP. Worked fine. Phew.🤣✌️

#knockonwood #fcpx

Jeff Roy writes:

Same here. Maybe just been lucky 🤷‍♂️ If it matters: my setup is very vanilla. Only plugins are those from you, frame io, and intelligent assistance. No third party color grading or templates. No FX factory, no MotionVFX, or PFS. Only my own Motion templates … which are working.

Mac Studio M1 Max, 10/32 core config, macOS and Final Cut Pro both up to date.

I edited and exported 6 different projects today between three different libraries—an old one retrieved from the server from archive today, one that was in already progress before the update, and a quasi-new library duplicated from my new library template. The videos ranged between 40-60 min, and included old motion templates and one newly created yesterday. All custom. Basically a wide range of variables and still no issues. Maybe I just need to keep banging on it until it breaks

So far cannot reproduce. I’ve thrown everything at it in Proxy Preferred and Proxy Only. Chopped it to pieces, batch stabilized, secondary storylines, trim, insert, append, overwrite, duplicate, retime, optical flow, flow transitions, detach audio, gap clips, position tool, editing over gap clips, clip stacking, rearrange the timeline, delete clips, disable clips, merge secondary storylines, lift from storyline, copied my 4K mess into a 1080p timeline—rinse and repeat. Removed the proxy cache, restored it, moved it, re-linked it. Quit Final Cut Pro and ejected the source (network) volume, repeated above process. No multicam clips in play here. Did not forcibly remove any volumes without ejecting. Zero third party templates or plugins in use. No FX Factory installed, no Motion VFX or PFS. No CoreMelt. Only third party effect installed is NeatVideo 5 and Twixtor 7. All footage is XF-AVC from Canon C70, 4K UHD 23.98 fps.

I can’t break it. I loaded the project with every last title and generator in the app. Randomly copied and pasted them in stacks and stacks and the thing barely even dropped frames. I could even add an adjustment layer and stack that with effects and distortion. No problem.

https://www.youtube.com/watch?v=DI2ZJqwCK5E

And a longer stress test where I assembled this monstrosity (3 min). https://youtu.be/n0nQqbhXccA Every title, every generator, multiplied, stacked, combined with adjustment layers. There must be some common denominator that I don’t have. • Rosetta maybe? • I don’t have Chrome installed at all. • I’m on Apple Silicon: M1 Max Mac Studio • All Libraries are stored on my internal startup disk • Original source media is on the network, XF-AVC Canon C70. Proxies are local, h.264 full size • I have not gotten the “system not ideal for 4K” message bug. • Can confirm my Placeholder generator is broken with notes always visible. Can’t think of any other variables.

Oh yeah, and I forgot to mention that almost every video clip in there has at least one or more random effects applied to it—color, distortion, you name it. I do have a lot of RAM for Apple Silicon—64 GB. And I have the 10/32 M1 Max core config.

Don Stafford writes:

no problems at all for me

Solid as a rock for me

M1 MacStudio (base version) with latest macOS and FCP.

Jari Innanen writes:

I usually reset the prefs after each Library update. 10.6.7 working fine here.

Ventura 13.4.1 ( c) on a M1 Max 64Gt 16'' MBP

Jay Jones writes:

I am running Ventura 13.4.1(c) and 10.6.7 It is working great. Motion integrates well. Someone is feeding you buffalo chips.

Nikos Papadopoulos writes:

~~It's been working fine for me (Apple silicon, A7SIII footage (rewrapped with EditReady). No crashes or bugs (yet!).~~

Spoke too soon. Been running into black screen at the viewer, which a simple restart of FCP will 'fix'. Other than than, seems ok. Ventura 13.4.1 ( c) 64 GB M2 Max Macbook Pro 16".

Venkat Dirisala writes:

I am wedding editor, for me no issues

ventura 13.5 imac m1

Rodney Teague writes:

Haven’t had one issue

Mac Studio M2 Max and Mc Book Pro 2018 intel. Latest OS on both

Jason R. Johnston writes:

Nope. Rock solid. Latest version on a 2023 MacBook Pro 14.

13.4.1

Michael Cherry writes:

Running latest update on a 2017 MacBook Pro, no issues.

Gunnar Lindstrom writes:

It’s been solid for me! I hasn’t crash once!

Igor Mitrovic writes:

I literally have zero problems

HBartMedia writes:

Too late for me but luckily I didn’t have any problems with the recent update yet. Crossing fingers.

HaiTomVlog writes:

Too late! But I haven’t had any problems so far… 🤞🏼 I still have iMovie, so if it becomes a problem, there’s always that! 😂

Phlokk writes:

It doesn’t seem to be affecting the M1 Mac mini 2020 late edition. Just a heads up bro.

K3JRZOnTheAir writes:

No crashes here. Weird.

Yes I am. 2017 iMac. All software (macOS & FCP) is up to date also.

Sebastian Leitner writes:

Also for me (MBP 16 M1 pro 16GB 1TB) i do not feel any change from before on Ventura 13.5 and FCP 10.6.7 be it with older projects or starting fresh ones. mixed media, mostly 4K HEVC 10bit (sony, canon)

MRBIGPhoto writes:

zero issues on MacBook Pro ..Intel

MacBook Pro 16" i9 Intel 2.3Ghz, 32GB, 1TB, Ventura 13.4.1(c)

BLACK SCREEN BUG (REQUIRES MANUAL RESTART):

I'm running MacBook Pro (16-inch, 2021, Apple M1 Max, 64 GB, 8TB SSD) & macOS Monterey 12.6.6. Using a LG 5K external monitor. I've definitely had to restart FCPX quite a few times because the Viewer just goes black, and I can't bring it back to life. I had one instance where adjusting audio made the viewer strobe, also requiring a manual restart. ~~No crashes thus far~~. Trashing preferences had no impact. Annoyingly, I also lost my Destination Presets when updating to 10.6.7.
Richard Coppola writes:

Just happened again. Black screen, audio only. wtf 🤷 @AppleSupport

Knut Hake writes:

Yep. Same here. Multiple restarts. Viewer and A/v out going black.

kevinhoctor writes:

MBP 16" M1 Max 32GBmacOS Ventura 13.4.1 (c)?Final Cut Pro 10.6.7I'm having similar video playback problems. FCP freezes the video, but I can still scrub through and play audio. This started with the most recent FCP and macOS updates. I’ve deleted the library cache, created a new project and copied over the clips, and rebooted numerous times.My 4K editing and playback was smooth as silk before this morning when I upgraded. I hope a fix lands soon because this is killing my production schedule.

Jeff Richardson writes:

Yeah the black viewer screen is a PITA !!

Massimo Bianchini writes:

confermo evitate l'aggiornamento (confirm avoid the update)

BUGGY:

Jonatan writes:

Same here. Wouldn’t let me export a project with subtitles. Only after I remove them….

I did that with another Mac I have, the 16” 2019 and still didn’t work. But sure, where should I send you the file ?

Emily Lowrey writes:

I’ve been ejecting my hard drives all day thinking it’s a hard drive fault making it laggy 🫠

Nariman Gafurov writes:

Very bad friends. What they did with the final cut is unclear. when I try to move the stabilizer slider, everything freezes. The program just stopped working

Robert74 writes:

My set up: MacBook Pro 16" 2021, Apple M1 Max, 64 GB, 4 TB SSD MacOS Ventura 13.4.1 (c) FCPX 10.6.7 I noticed rather instantly with the 10.6.7 update is that the video freezes when playing or scrubbing through the timeline of a project or selecting clip ranges from the library. If I try to reopen the project after the freezing occurs I get an error message telling me 4K projects cannot be edited on my computer.

After that I close the application and I get an error message that is reported to Apple (the ones you get if an application crash). If I just quit the application after the freeze without trying to reopen the project I don't get the 4K message or the crash report. I can then restart the application but this will happen again within a while.

I was editing the same project before upgrading without issues. My MacBook Pro M1 Max can deal with this resolution perfectly. The MacBook Pro now also get very hot when it starts acting up. That NEVER happened before, even if editing 4K 60fps.

I have tried to change the playback view settings from better quality to better performance, but still same problems.

What is going on, I can't even work on my projects anymore. Anyone else experiencing the same issues?

Lovie Carolyn Davis writes:

I use the Samsung T7 ssd card ( recommended here) and automatically updated to the 10.6.7. Now, fcp randomly closes every 5 to 10 minutes. So I duplicate and snapshot the project. Btw, some clips were shot in 4k on my camera phone, which didn’t help either. I’m a new user whose skill set leaves much to be desired and this is aggravating. Should I uninstall and install fcp?

Brendan Quaife writes:

Yes issues with multicam editing. Fcp updated automatically (must turn that off) and now I have issues with video freezing yet can still hear audio..and crashing alot. Gah this happened mid project (a couple of days ago no problems)

brand new 2 week old macbook air with 16gig .. seemed to have come better with a software update that updated the pro video formats which seemed to have made it more stable. Note experiencing the same crashes as two days ago

Sam Plü writes:

I‘d strongly suggest to wait on updating to 13.5 if you are using FCP 10.6.7 - I did test this setup today and all clips in that library were showing a „Missing Plugin“ warning, despite no plugins applied to the clips and even source clips were going offline. Only restarting the computer would bring back the clips „Online“. Re-installing Pro Video Formats did not solve the issue. It‘a been reported to Apple without any response so far.

As I mentioned in my previous post: The latest codec update is installed. Restarting the computer temporarily brings back the clips, but they go offline shortly after again. So it‘s definitely not the missing codec support or lack thereof.

To further explain: When FCP starts, the clips are online, the missing plug-in information is only showing up after 5-10 minutes.

Allen Davis writes:

Yep. I just bought the Mac M1, and now have it freezing on me. I have to shut the program down, and restart it again, then it’s ok, for a short while. The other day I had it happen about 8 times. Bloody annoying

Julien Vidal writes:

3 days ago I opened a project and it automatically updated the files of it. Since, FCPX struggles a lot like it has never done before.

George Mercado writes:

Happens to me when I first open a project with a lot of edits . What I do is , when I open fcp, as soon as it shows the projects tab , I hurry and select a project that has the least edits so that it doesn’t crash instantly . Then I go to the project I originally came to work on.

Leon Kemper writes:

Mine did, sits at the loading bar and won't boot up

2019 1 tb hd, got it back up, used the disk utility, only thing that doesn't work still is the wireless, that's been like that for 2 years now

correction, 2017

Cameraman Steve writes:

Since I’ve updated my system, it locks up as well

Patrick Janka writes:

It's complete garbage. Trim tool doesn't work, everything is laggy

geminicenturion5961 writes:

Thank you very much for the warning, unfortunately I had already updated and have been experiencing issues in FCP. I was starting to think that there was something wrong with my Mac Studio.

mchammer5592 writes:

Man, I just got a spec’d out m2 ultra studio and I’ve been actually wondering if there was a bug in the machine itself! 😅

neutrinoradio7894 writes:

This has been a total train wreck for me. I've been on the phone with AppleCare for hours every day this week. At least next time I can come to them with the knowledge that this is a universal issue.

Dale Tristan P Sanchez writes:

I have this skimming issue. Like when I skim/scrub in timeline, usually will show all this clips in the timeline, but for some reason, freezes on one clip, But I can still hear audios. I tried to go to another project, and still not working. I have to quit FCPX (not force quit) and reopen, and it works, but its just annoying coz it dont do this before. I can't even report issue, since its it didnt "unexpectedly quit" or hanged.. Does anyone has this issue?

Germán E Vera writes:

I just want my M1 Max to handle the video edits the way it used to. It was blazing fast with the same cameras and drone I’ve been using. Now it’s stuttering Stanley!!

Peterkuk writes:

FCPX update 10.6.7 causes video freezing and restart I've been having the same issue since this update!

Everything worked fine before on my 2022 Macbook Pro M1. Now regular playback of 4k video freezes and I have to restart in order to have normal playback again.

I'm having to keep restarting FCP every 10 minutes or so to get through my edit.

Very frustrating

Bassilyok writes:

Final Cut Pro V.10.6.7 (Mac M1 Pro 1TB) is terribly slow after the latest updates, often freezes Final Cut Pro V.10.6.7 (Mac M1 Pro 1TB) is terribly slow after the latest updates, often freezes, I constantly get an unresponsive viewer window every five minutes or so. You have to restart the program frequently. Impossible to work. Mac M1 Pro starts to warm up, although this was not the case before.

Thomas Grove Carter from Trim writes:

We’ve had fairly consistent bugs with it on all machines so have reverted to 10.6.6

CRASHY:

Dylan Bates - The Final Cut Bro writes:

Worked on a pretty complex timeline all day. it crashed 16 times over my 10 hour editing session.

Hugh Chaloner writes:

I have a repeatable crash in 10.6.5 double clicking synced clips :/

Matthew O'Brien writes:

Experience crashing as well. Twice in about an hour of editing but only after I started throwing 3rd party plugins & effects at it. Stay tuned…

Brian Petersen writes:

It’s crashed on me more in the last month than ever before.

Arctic Whiteness writes:

I had a crash in 10.6.7; the first in months. At the moment when I just activated the optical flow. Apple must absolutely expand its beta tester program. (See also my others tweets about suddenly drop frames caused by stop of the four performance cores; not link with temperature)

Final Cut Pro bug? Editing multicam of three 4K 50fps video streams on a MacBookAir M2, the image get drop frames after a few minutes: curiously, it is at the exact moment when the 4 Performance M2 cores begin to stop. And it's apparently not related to temperature (65°C).

It's very strange, because it only occurs if I plug my second 4K monitor. With or without the viewer on it. I'm going to check the memory usage...

...no, it not link with any memory problem

Since then, I have just edited my mutlicam only on the MacBook Air screen, and I no longer have any drop frame. I'd like to feedback this to Apple, but I don't think I have enough elements to be useful. Did you also have this behavior with two screens?...

Matthieu Laclau writes:

I had the same bug about the viewer. But I had a more crazy one. My MacBook air M1 crashed two times when using 10.6.7. And when I mean crash, it’s suddenly a purple screen and the computer shutdown and restart.

Knut Hake writes:

I had a forced reboot too.

Ché Baker writes:

Hi all, updated today and now FCP is crashing every 30 mins or so. The viewer freezes, the app quits. Do not update to this version!!!

hi mate - 16 inch MBP 2021 pro max. 64GB ram. Os - 13.4.1 (I quit command post to make sure it wasn’t that which was conflicting - it wasn’t, app still crashing about every 40 mins or so). Trashed prefs and all the usual debugging stuff. :?)

Allan Dong writes:

It crashes very often now

I've just had my first crash - see #225.
Nguyễn Quốc Hoàng writes:

Lots of crashing sh!t in 10.6.7, I got 10 Macs and those are all behaving the same

Nicolai Hadchity writes:

Keeps crashing on me too after the update

Atlanta King writes:

I agree. It crashed while I was editing a project

Marcus Howlett writes:

Crashing 6 times a day!. Mac Studio

hey. Yes I allways update to the latest.. crashed at least 6 times yesterday as well.

Dan Paige writes:

I must have had auto update on and updated and immediately started to get a good amount of crashes. It was bearable, but annoying to say the least

Hi Chris, I am on a M1 Mac on a 14 Inch MBP with Ventura 13.4.1. I did receive notification after my Mac had auto installed that additional Pro Video Formats had been installed. I was in the middle of working on a project so using a newer version of FCP after starting the project on an earlier version could be a big part of the freezing too. Haven't tried working on a new project yet from scratch now that I am on the newer version of FCP

Arne Fauché writes:

Same here too 🤬 Every time i make an transition FCP shutes down itself. Luckly no data lost. 6 times in last 2 hours.

Luke Houghton writes:

Ye its crashed lots with me lately

Nathan Derbyshire writes:

Mine is constantly crashing too. Real pain!! I don’t know why it updated automatically, I have never had auto update on in the past and always updated manually when I knew it was ok for this reason. This new version has automatically updated in the background not impressed.

I am on a Mac Studio with M1 Max chip. On OS 13.1, I have not updated to pro video formats 2.2.6 yet. Is updating pro video likely to help?

Gummi Ibsen writes:

What is with the Bad update- I have never had FCP crash so many times as in the last few days.

John Tunkin writes:

It crashed with me too when using the voice isolation...sent a report. Had to switch the isolator off though. Now it seems to be better for some reason..so it must've been a culmination of things.

Fred T. Miller writes:

Mine crashes after about 45 minutes EVERY time. Luckily, all I have to do to "fix" it is to close out and reopen. That gets me another 45 minutes of editing time. It's frustrating, but at least that's a work-around for now. Just finished a 2-hour video with about 5,000 edits - so that was fun.

Ventura 13.4.1

macvince writes:

Glad to know that I‘m not alone! Had at least 10 crashes whilst editing my new video… So annoying.

HNeatR writes:

Bro! It crashed 4 times on me yesterday. I almost felt like I was working on Premier again 🤓

An'Darrio J. Abrams writes:

Sadly my projects updated with the 10.6.7. On both my M1 Mac and Mac Studio the program crashes every 15 minutes. At first it was just freezing on the preview pane which was ANNOYING

Joseph John Kominkiewicz writes:

I've been getting red screens for missing everything -- plugins, typefaces, etc. -- since I've upgraded from 10.6.6 to x.x.7, but I usually get those anyway so there's no way to judge what's at fault. (Everything is stored on Samba shares on an Ubuntu NAS using the latest MacOS-specific extensions in my smb.conf.) And today I relinked already ingested files, only to come back and find that they've changed from the ingested .mov files to the original .mxf files. Moreover, it crashes at least once every hour. It's okay if it crashes, because everything's been saved, but the missing files cost me hours of work and sap my motivation. I hope more and more people complain to Apple about this so that it gets fixed. Mac Studio M1 Max 64gb Ventura 13.5 Latest Pro Video codecs installed No plugins whatsoever

Bogdan Orlic writes:

I'm really sorry but NO UPDATE for me. I tried on my other machine and #FCPX 10.6.7 would not launch. It would crash on startup, non-stop. Good think I was able to go back to 10.6.6 and for safety my laptop is running 10.6.5 @chrisatlatenite and #FinalCutCafe is keeping track.

movieguy-13 writes:

Can not export XML from fcp 10.6.7 Export stalls midway, only option is to Force Quit. Happens on my MacBook M1 and Studio M2.

Also: FCPX constantly crashes randomly when clicking/selecting

Adam Pickstone writes:

Is anyone having issues where FCPX crashes and then it says damaged timeline. For context, I am on 10.6.7 and it has happened on multiple projects and then I have to do the work I have done again as the backup was too old?

Mac Studio and everything is updated and installed

David Good writes:

Yes. Unfortunately two of our MBPs updated without us realising, so all our machines are now on this god awful version. Crashes are random and unexplainable so far, which means often a reboot fixes them. As for your specific problem, yes I've had it twice. Had to get backups both times but didn't lose anything except for the action that crashed it.

COMPRESSOR:

Steffan Andrews writes:

What did Apple do with the last update to Compressor? It's completely broken. Anyone else having issues on M1/M2/Ventura?

GUI non-responsive. Works on Intel/Monterey though.

MOTION:

Tycondaroga100 writes:

Motion is broken too! I tried setting a new project to a vertical format 1080 x 1920 and it shows almost square format but says it's 1080 x 1920.

tangierc commented 1 year ago

I upgraded. FCP 10.6.5 wouldn’t complete the upgrade of the library and wouldn't open after several attempts and force quits of the app, then the computer. Eventually the library opened and started the update process, but would repeatedly hang. Why, I don’t know. I would just watch as it has to update 112 items in the library and I don’t have 112 projects btw. Fortunately I backed up 10.6.5, that library, and the cache folder. 10.6.6 seems to have had many problems to many problems so I didn’t update and decided to wait for 10.6.7. This same library is finally working (as in opening) under 10.6.7, but it was a rough start.

Computer setup: I’m on an M2 Max MacBook Pro with 64GB of memory, clamshell mode with two monitors, but only my 34" LG Ultrwaide was plugged in at the time along with my CalDigit TS4 Thunderbolt Dock. I am using macOS Ventura 13.4.1 (c) (22F770820d)

I may go back to 10.6.5 since I have everything backed up. We'll see how things go.

Chris you're already very familiar with my library. I haven't upgraded to BRAW Toolbox 1.3.0 yet. We're at locked picture and I have everything backed up for going back to 10.6.5, so I thought 10.6.7 would be alright.

sharedscene commented 1 year ago

crash experienced while using the Text Inspector on a Title Template. the timeline is only about 30s and contains audio & a few title clips; no video. [M1 Max, 64GB] [macOS 13.5] [FCP 10.6.7]

latenitefilms commented 1 year ago

Any chance you could share the full crash log? You can find it in:

~/Library/Logs/DiagnosticReports/

You can then share the full contents as a GitHub Gist.

sharedscene commented 1 year ago

Any chance you could share the full crash log? You can find it in:

~/Library/Logs/DiagnosticReports/

You can then share the full contents as a GitHub Gist.

https://gist.github.com/sharedscene/85c21d0b441356402c9f32ca163f607a

latenitefilms commented 1 year ago

Legend, thanks!

Here's the crashed thread:

Thread 45 Crashed::  Dispatch queue: com.apple.flexo.playertokq.sched
0   ProGraphics                            0x10f23ec88 PGPerThreadSetCurrentContextSentry::PGPerThreadSetCurrentContextSentry() + 24
1   Ozone                                  0x113c653ec OZFxPlugSharedBase::scheduleTokens(OZRenderParams const&, std::__1::vector<std::__1::pair<CMTime, std::__1::vector<CMTime, std::__1::allocator<CMTime>>>, std::__1::allocator<std::__1::pair<CMTime, std::__1::vector<CMTime, std::__1::allocator<CMTime>>>>> const&, PMFrameRequest&, std::__1::vector<FFScheduleToken*, std::__1::allocator<FFScheduleToken*>>*) + 104
2   Ozone                                  0x113875538 OZScene::scheduleTokens(OZRenderParams const&, std::__1::vector<std::__1::pair<CMTime, std::__1::vector<CMTime, std::__1::allocator<CMTime>>>, std::__1::allocator<std::__1::pair<CMTime, std::__1::vector<CMTime, std::__1::allocator<CMTime>>>>> const&, std::__1::vector<FFScheduleToken*, std::__1::allocator<FFScheduleToken*>>*) + 528
3   MotionEffect                           0x10f35bb2c -[FFMotionEffect newEffectSpecificTokensAtTime:duration:withInputStream:context:schedInfo:downstreamPT:] + 1048
4   Flexo                                  0x107c0bf50 -[FFStreamVideoEffect newScheduleTokenAtTimeIgnoringCache:duration:context:schedInfo:downstreamPT:] + 1584
5   Flexo                                  0x107c34488 -[FFStreamVideo newScheduleTokenAtTime:duration:context:schedInfo:downstreamPT:] + 564
6   Flexo                                  0x107c0ba54 -[FFStreamVideoEffect newScheduleTokenAtTimeIgnoringCache:duration:context:schedInfo:downstreamPT:] + 308
7   Flexo                                  0x107c34488 -[FFStreamVideo newScheduleTokenAtTime:duration:context:schedInfo:downstreamPT:] + 564
8   Flexo                                  0x107c0bcbc -[FFStreamVideoEffect newScheduleTokenAtTimeIgnoringCache:duration:context:schedInfo:downstreamPT:] + 924
9   Flexo                                  0x107c34488 -[FFStreamVideo newScheduleTokenAtTime:duration:context:schedInfo:downstreamPT:] + 564
10  Flexo                                  0x108252200 -[FFAnchoredObjectSegmentedVideoStream newScheduleTokenAtTimeIgnoringCache:duration:context:schedInfo:downstreamPT:] + 256
11  Flexo                                  0x107c34488 -[FFStreamVideo newScheduleTokenAtTime:duration:context:schedInfo:downstreamPT:] + 564
12  Flexo                                  0x108484c20 -[FFMCSwitcherVideoStream newScheduleTokenAtTimeIgnoringCache:duration:context:schedInfo:downstreamPT:] + 480
13  Flexo                                  0x107c34488 -[FFStreamVideo newScheduleTokenAtTime:duration:context:schedInfo:downstreamPT:] + 564
14  Flexo                                  0x108014e5c -[FFPlayerScheduledData _scheduleInternal] + 1348
15  Flexo                                  0x1084e6f9c FFApplicationHandleExceptionThatShouldNotBeIgnoredInBlock + 20
16  Flexo                                  0x108761158 -[FFPlayerSchedTokenQueue _performScheduling] + 268
17  libdispatch.dylib                      0x1a7e2e874 _dispatch_call_block_and_release + 32
18  libdispatch.dylib                      0x1a7e30400 _dispatch_client_callout + 20
19  libdispatch.dylib                      0x1a7e37a88 _dispatch_lane_serial_drain + 668
20  libdispatch.dylib                      0x1a7e3862c _dispatch_lane_invoke + 436
21  libdispatch.dylib                      0x1a7e43244 _dispatch_workloop_worker_thread + 648
22  libsystem_pthread.dylib                0x1a7fdc074 _pthread_wqthread + 288
23  libsystem_pthread.dylib                0x1a7fdad94 start_wqthread + 8

Looks like there's an issue in the ProGraphics framework related to the number of threads.

sharedscene commented 1 year ago

another one so far today with the same heading detail for the thread: Thread 72 Crashed:: Dispatch queue: com.apple.flexo.playertokq.sched listing ProGraphics framework at the top https://gist.github.com/sharedscene/dc441c80643bdac8a8d4880263d7e715

jkominkiewicz commented 1 year ago

Hello fellow FCPers! Just wanted to share that I too have been having problems with crashing. It's usually just a minor annoyance if it crashes because everything's been saved. I hope more and more people complain to Apple about this so that it gets fixed.

The media files are stored on Samba shares on an Ubuntu NAS using the latest MacOS-specific extensions in my smb.conf.

Mac Studio M1 Max 64gb Ventura 13.5 Latest Pro Video codecs installed No plugins whatsoever

One crash log found here (some apparently weren't saved?): https://gist.github.com/jkominkiewicz/b84faa82319efe96ac82da52886bf56b

Thread 46 Crashed::  Dispatch queue: com.apple.helium.rq.gpu-ru1.vs0.gcd
0   ProGraphics                            0x110c5ec88 PGPerThreadSetCurrentContextSentry::PGPerThreadSetCurrentContextSentry() + 24
1   TextFramework                          0x112dc0ebc TXHeliumNode::preRenderGlyphsMetal(HGPage*) + 108
2   TextFramework                          0x112dc3614 TXHeliumNode::RenderPageMetal(HGPage*) + 76
3   Helium                                 0x104c96ba4 HGGPURenderer::RenderPage(HGNode*, HGPage*) + 832
4   Helium                                 0x104c96650 HGGPURenderer::ProcessOnePage(HGNode*, HGRect, HGROIsInfo&, HGFormat, HGBuffer*, bool, bool) + 720
5   Helium                                 0x104c95784 HGGPURenderer::ProcessNodeInternal(HGNode*, HGRect, HGFormat, HGBuffer*, bool, bool, bool) + 460
6   Helium                                 0x104c92f28 HGGPURenderer::GetNodeBitmap(HGNode*, HGRect, HGBuffer*, bool) + 436
7   Helium                                 0x104da76f0 HGNode::PullMetalTextures(HGPage*, int) + 400
8   Helium                                 0x104da76a4 HGNode::PullMetalTextures(HGPage*, int) + 324
9   Helium                                 0x104da76a4 HGNode::PullMetalTextures(HGPage*, int) + 324
10  Helium                                 0x104da76a4 HGNode::PullMetalTextures(HGPage*, int) + 324
11  Helium                                 0x104da76a4 HGNode::PullMetalTextures(HGPage*, int) + 324
12  Helium                                 0x104da76a4 HGNode::PullMetalTextures(HGPage*, int) + 324
13  Helium                                 0x104da76a4 HGNode::PullMetalTextures(HGPage*, int) + 324
14  Helium                                 0x104da76a4 HGNode::PullMetalTextures(HGPage*, int) + 324
15  Helium                                 0x104da76a4 HGNode::PullMetalTextures(HGPage*, int) + 324
16  Helium                                 0x104da7f08 HGNode::RenderPageMetal(HGPage*) + 76
17  Helium                                 0x104c96ba4 HGGPURenderer::RenderPage(HGNode*, HGPage*) + 832
18  Helium                                 0x104c96650 HGGPURenderer::ProcessOnePage(HGNode*, HGRect, HGROIsInfo&, HGFormat, HGBuffer*, bool, bool) + 720
19  Helium                                 0x104c95784 HGGPURenderer::ProcessNodeInternal(HGNode*, HGRect, HGFormat, HGBuffer*, bool, bool, bool) + 460
20  Helium                                 0x104c92648 HGGPURenderer::RenderTiles(HGNode*, HGRect, HGFormat, HGBitmap*, bool, bool) + 268
21  Helium                                 0x104d658f4 HGRenderer::RenderNode(HGNode*, HGRect, HGFormat, HGBitmap*) + 144
22  Helium                                 0x104d69298 HGRenderer::RenderNodes(std::__1::vector<HGRendererOutput, std::__1::allocator<HGRendererOutput>> const&, bool) + 924
23  Helium                                 0x104d68ac8 HGRenderer::RenderNode(HGRendererOutput const&, bool) + 100
24  Helium                                 0x104ca69b8 HGRenderExecUnit::ExecuteRenderGPU(HGRenderJob*) + 1216
25  libdispatch.dylib                      0x184907518 _dispatch_block_async_invoke2 + 148
26  libdispatch.dylib                      0x1848f8400 _dispatch_client_callout + 20
27  libdispatch.dylib                      0x1848ffb68 _dispatch_lane_serial_drain + 892
28  libdispatch.dylib                      0x18490062c _dispatch_lane_invoke + 436
29  libdispatch.dylib                      0x18490b244 _dispatch_workloop_worker_thread + 648
30  libsystem_pthread.dylib                0x184aa4074 _pthread_wqthread + 288
31  libsystem_pthread.dylib                0x184aa2d94 start_wqthread + 8

latenitefilms commented 1 year ago

Thanks @jkominkiewicz! That's consistent with @sharedscene's crashes too. Something is broken in Motion.

jkominkiewicz commented 1 year ago

So, since it's related to Motion, I looked to see whether I had updated to the latest version. It turns out I was one release behind since having updated to the newest FCP release. I've updated to ver. 5.6.5 and I haven't had a crash in the last half hour. Fingers crossed.

UPDATE: So, after having used it for around four hours with the updated Motion: Crashes have stopped, but I'm now getting the frozen viewer requiring a restart of FCP and the warning that my computer can't handle 4K footage.

joema4 commented 1 year ago

Here are some comments based on study of framework differences between 10.6.6 and 10.6.7, also several 10.6.7 crash logs. I used the MacOS command-line 'nm' utility to study the framework symbol differences between 10.6.6 and 10.6.7, with emphasis on the crashing call stacks people have reported.

The crash usually happens in the ProGraphics framework, which is written in C++. While much of FCP is written in Objective-C, a non-trivial amount is written in C++. The crashing method is called a 'destructor', which cleans up resources for an object being deallocated.

Doing a 'diff' on the symbols between the two versions of ProGraphics framework, there were possibly a lot of changes. In the 10.6.6 version many methods were had '.cold.1', '.cold.2', etc. suffixes. That indicates Profile-Guided Optimization had been run, which pulls out and repacks less-executed code blocks so the remaining 'hot' code blocks obtain better hit ratios on the CPU instruction cache. The fact that many of the '.cold' blocks vanished between 10.6.6 and 10.6.7 could imply the underlying source code was modified (IMO more likely), or it might mean a different profile exercise was done.

The crashing PGPerThreadSetCurrentContextSentry is one of those which changed between 10.6.6 and 10.6.7: https://photos.smugmug.com/photos/i-3Lmxhmj/0/398ab6ff/X5/i-3Lmxhmj-X5.jpg

Also the code in the 'Ozone' framework (which contains the Motion runtime engine that implements FCP effects) had lots of apparent changes. This is just speculation, but maybe some of those source code or profiling changes were related to shoe-horning FCP into iPadOS. See similar diff comparison of Ozone symbols between 10.6.6 and 10.6.7: https://photos.smugmug.com/photos/i-hKpgbrn/0/4ce40842/X5/i-hKpgbrn-X5.jpg

latenitefilms commented 1 year ago

Yes, I compared the ProGraphics framework between Final Cut Pro 10.6.6 and 10.6.7 using Hopper, and there's definitely some differences in PGPerThreadSetCurrentContextSentry. It'll be interested to see what the release notes are for the next update, but I'm assuming it'll just be "general stability improvements" or similar.

lancefrei commented 1 year ago

After update, Voice Isolation box not checkable. Freezing viewer another problem which can be temporarily fixed by trashing preferences but it recurs.

CommandPost / FCPCafe

🧵 Final Cut Pro 10.6.7 generally unreliable and buggy #223