Edit-Tools support
Send a clear description of what happened, the macOS and Final Cut Pro versions you are using, and whether the issue happened before or after importing the exported project. CoreTrim requires Final Cut Pro because it is a Final Cut Pro workflow extension. Include CoreTrim diagnostics whenever possible.
CoreTrim
For CoreTrim, include the project name, source export mode, your Final Cut Pro version, whether the issue happened before or after importing the exported project, and any source names that look wrong.
Contact CoreTrim supportCoreTrim problem reports
Diagnostics help us see the project structure, CoreTrim settings, source decisions, export result, and logs. They usually make a support request much faster to solve.
If the issue happened after an export, keep the exported media folder and project export exactly where CoreTrim created them until support has reviewed the diagnostics.
Use Help > Report a Problem in CoreTrim. CoreTrim saves a Diagnostics folder inside each export folder; send the folder from the export that had the problem.
Include the source export mode, the project name, what you expected, what actually happened, and whether Final Cut Pro imported the exported project successfully.
Send the complete Diagnostics folder with your email. Do not remove files from it; the original project data, exported project data, settings, logs, and decision summaries work together.
Start with the Diagnostics folder. If a media file is needed, support will ask for the smallest specific source that reproduces the issue.
Import the exported CoreTrim project into Final Cut Pro, confirm it is online, read the export report, and check for skipped sources. Skipped sources remain linked to their original files.