New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crashed when exporting to ProRes #327
Comments
I'm a little suspicious about frames 19-12 which might imply the media file was changing underneath FCP during the export. But that's just a guess. Was the export to a local APFS or HFS+ disk file on a volume with plenty of space? Was it exported to a NAS location? Immediately after one of these happens, it would be interesting to use OPT+Help>Gather App Diagnostics and examine the logs. If that doesn't reveal anything, it's possible to export a more verbose FCP log using this command: sudo log show --process "Final Cut Pro" > ~/Documents/LogShowFCP.txt The text file can be large, so using BBEdit or similar is best. Look for items nearby the timestamp If that doesn't reveal anything, it's possible to extract a range of the entire MacOS log if done right Syntax to extract all events from prior 60 seconds of MacOS log to a text file. sudo log show --last 60s > ~/Documents/LogShow60s.txt Extract last 5 minutes of MacOS log (even larger): sudo log show --last 5m > ~/Documents/LogShow5m.txt If the event of interest happened before that, it's possible to give a start/end range for 'log show'. log show --start '2024-01-22 14:00:00' --end '2024-01-22 14:05:00' > ~/Documents/LogShow1400_plus5m_yesterday.txt If the log is too verbose to make sense of, it's possible in BBEdit to use "progressive exclusion",
^(?![^\n]*(exclusion_string_1|exclusion_string_2)).+$
|
Amazing! Thanks Joe! I will add all this information to the FCP Cafe Bug Tracker page! |
Apple Feedback Assistant ID: FB13545557
DESCRIBE THE BUG:
Crashed when exporting ProRes timeline.
CRASH REPORT:
Full crash report: https://gist.github.com/latenitefilms/df20eaabde8661b7ff4a6bec33988b15
SPECS:
The text was updated successfully, but these errors were encountered: