Hi Pier31, Welcome to the fcp.co forums
Given that you are attempting to restore your FCP project from a Data Recovery Software app, there are all sorts of potential problems. IMHO, it is very rare for such recovered files to fully function, but YMMV.
Also the type of computer plays a big part. If it has a T2 chip in it will make full recovery difficult or impossible. No data inside the T2 is recoverable AFAIK. Not at all sure if T2 data would affect FCP or not??
Even without a T2 chip, data recovery may provide the files, but there is a tremendous amount of backend file management, links, and hidden IDs that often do not re-link so you may end up with the files without functionality. Data is stored in many parts of computer and any corruption in recovery file would result in crashes of FCP.
A crash report is your best friend here. There are lots of threads about crash reporter, and how to read the report like here… www.fcp.co/forum/4-final-cut-pro-x-fcpx/...2-imac-2017-64gb-ram
Or this one where Joema has linked to some great resources on crashes… www.fcp.co/forum/4-final-cut-pro-x-fcpx/...-mac-os-kernel-crash
EtreCheck is a free tool that helps to analyze your computer and read crash reports… etrecheck.com
You can post your EtreCheck report and someone here may be able to help.
You might try to open a Final Cut backup version from your Movies Folder.
You can open the FCP bundle "Show Contents" and then you check your media clips. Often, your media files may be intact, but lost are edits, plug-ins effects etc… due to recovery corruption or incompleteness.
FCP can(will) crash if the app cannot link to required data or resources, so if the recovery file is not a total one to one bit recovery, any bad process/link in the FCP will cause an signal abort process and FCP will crash.
If your Data Recovery Files are corrupted, media recovery would at least allow you to rebuild the project by starting over on the edit:(
Pier31 wrote: ...had to recover data from a Final cut Pro project from a hard drive using professional recovery software..After that, I tried to open the project, but Final Cut Pro was trying to open it crashes. In your opinion, what are the causes? I use Final Cut Pro version 10.5.4
This implies the data wasn't fully recovered and either the media is damaged or (more likely) the SQL relational database files comprising the project and library are damaged.
The key thing is whether you have any FCP auto-backups of the libraries themselves. By default those are in /Movies/Final Cut Backups. If the system drive crashed, you might have those on a Time Machine backup. Each of those is a compressed auto backup of each library, made periodically by FCP. They contain no media, cache, or render files -- just the edits in a series of SQLite databases, so are quite small.
As VidGreg said, another key step is evaluate whether the media files are intact and can be played outside of FCP. Those files might be external, ie imported with "leave files in place" or they might be media files within the library.
If you have a copy of the library bundle, you can look inside it in Finder via right-click>Show Package Contents, then go to EventName>Original Media. Either the media files will be there or symlinks to the files. Unfortunately if the referenced media is not present, Finder will not show you the resolved link location. Without starting FCP and loading the library, the only way I know to show this is using terminal, go inside the library to the original media folder and use the command "ln -l". That will show where the symlinks are pointing.
If the library would just open, you could try to export a library or event XML, then load that into a fresh library. But that would likely require many of the same software code paths as displaying a timeline. So if the library data is damaged, that may not work.
There is logic in FCP that in some cases will detect the library is damaged then open it in read-only mode. It displays a prominent message when that happens. The fact FCP crashes trying to open the library implies the library itself is damaged more severely.