Both Final Cut Pro AND DaVinci Resolve Studio crash when working with retiming!

[usagora]

For maybe a year now I've been having an ongoing, unresolved issue with Final Cut Pro, in spite of reporting it to Apple multiple times. When selecting a clip and trying to add Smooth Slo-Mo to it, it will work perfectly fine dozens of times, then suddenly I'll be trying to do it one day and Final Cut Pro will think about it for a second and then crash. Once that happens, NOTHING I can do (including recreating both the preferences and library files) will fix the issue - every subsequent clip (even in a new or separate project) will crash the app every time I try to add Smooth Slo-Mo. The ONLY solution is to restart my Mac, which is a huge PITA when I've got lots of things open.

But even after restarting, eventually the same issue will reoccur. And this happens on both my Mac Studio M4 Max (64GB ram, 16 core CPU, 40 core GPU) AND my Mac Mini M4 Pro (64GB ram, 14 core CPU, 20 core GPU), so this is definitely not a computing power issue.

So I finally decided to purchase DaVinci Resolve Studio, thinking surely it was a Final Cut Pro issue and Resolve Studio would be able to add smooth slo-mo to clips without issue. Welp, guess what? After playing with retiming on a clip and adding optical flow and changing the AI preset for it, Resolve Studio crashed. Went to open the project again - immediate crash. Tried again - crash. Can't even reopen the damn project (at least Final Cut Pro could reopen the project) - it's a total loss. Sent a report to the developer.

What in the name of all that is holy could be going on here? Do Macs just suck for AI-based retiming processing with video or what? I'm at my wit's end here.

Both my Macs and both apps are updated to the most recent public release versions.

 

[!!!]

What in the name of all that is holy could be going on here?

It would be helpful if you posted the crash logs, from ~/Library/Logs/DiagnosticReports and/or /Library/Logs/DiagnosticReports. It's possible that there are other background processes crashing as well, which is why I included the top-level Library folder as well. Sort these folders by date modified and check out the most recent ones (assuming you've just replicated a crash).

The most useful part is the backtrace, do not bother posting anything after it says Binary Images:.

 

[usagora]

It would be helpful if you posted the crash logs, from ~/Library/Logs/DiagnosticReports and/or /Library/Logs/DiagnosticReports. It's possible that there are other background processes crashing as well, which is why I included the top-level Library folder as well. Sort these folders by date modified and check out the most recent ones (assuming you've just replicated a crash).

The most useful part is the backtrace, do not bother posting anything after it says Binary Images:.

I will do this later today when I get back home - thanks!

 

[usagora]

It would be helpful if you posted the crash logs, from ~/Library/Logs/DiagnosticReports and/or /Library/Logs/DiagnosticReports. It's possible that there are other background processes crashing as well, which is why I included the top-level Library folder as well. Sort these folders by date modified and check out the most recent ones (assuming you've just replicated a crash).

The most useful part is the backtrace, do not bother posting anything after it says Binary Images:.

Final Cut Pro crash log attached.

 

[usagora]

It would be helpful if you posted the crash logs, from ~/Library/Logs/DiagnosticReports and/or /Library/Logs/DiagnosticReports. It's possible that there are other background processes crashing as well, which is why I included the top-level Library folder as well. Sort these folders by date modified and check out the most recent ones (assuming you've just replicated a crash).

The most useful part is the backtrace, do not bother posting anything after it says Binary Images:.

As for DaVinci Resolve Studio, nothing under those paths for it, but I found a log, debug report, and crash archive in the system folders for the app itself. Attached.

 

[!!!]

Interestingly, both of them seem to crash at

1   libobjc.A.dylib                     0x0000000183b0e91c objc_exception_throw + 88
2   CoreFoundation                      0x0000000183fb79dc -[__NSArrayM insertObject:atIndex:] + 1864

The FCP crash log does include AGXMetalG16X -[AGXG16XFamilyCommandBuffer encodeSignalEvent:value before the crash, which made me think it may be a driver level bug, but the Resolve crash does not.

Either they're passing in bad data, something has been corrupted, or there's an OS level issue. Since it happens with two different machines which I assume are running the same OS version, I'm likely to blame that or the source media.

It's possible that there's something slightly off about your footage, have you tried using different clips from different cameras or sources?
You could also try installing an older version of macOS on another drive/partition.

Given I have an M4 Pro and FCP, I did test Smooth Slo-Mo, and it did not crash. Though I do have Sequoia installed.

 

[usagora]

It's possible that there's something slightly off about your footage, have you tried using different clips from different cameras or sources?

Once it crashes, any subsequent attempts to apply Smooth Slo-Mo to any other source file will crash as well. It's like a switch has been flipped and the Smooth Slo-Mo feature simply doesn't work, period, until I restart macOS. And after restarting, I can go back to the original clip that it first crashed on and successfully apply Smooth Slo-Mo. So I doubt it's an issue with the source files.

Given I have an M4 Pro and FCP, I did test Smooth Slo-Mo, and it did not crash. Though I do have Sequoia installed.

Well, as indicated, I can do it without crashing too. Might even be successful 10, 15, or 20 times over days on different projects, but then all of a sudden it will cause FCP to crash over and over until I restart my Mac.

With DaVinci Resolve Studio, the specific trigger seems to be changing the Retime Process to "Optical Flow" and then adding "AI Warp Speed Metal" as the Motion Estimation setting. Once both those are done, the app will crash as soon as you attempt playback. The other Motion Estimation settings seem to apply without crashing the app.