Specific project in library leads to sudden FCP application quit

[Jeremy Garchow]

Did you try opening a backup?

File > Open Library > From Backup

[Grant Peacock]

Thanks Jeremy,

I apologize : I neglected to mention in my post that the behaviour is identical when going back to a version that is 2 days prior to the date of the issue occurring.

This leads me to suspect that there’s damage occurring to each project as it is opened inside FCP. What makes this so confusing is that the errant behaviour has survived both OS and FCP upgrades – 10.4 -> 10.4.2 (not to mention moving from external to internal SSD drive, just to eliminate that uncertainty as well).

I wish that there was a way to save a project as a discrete file external to the FCP ecosystem, but I’m pretty sure those options don’t exist in FCP X. It may be time to call it a day and restart the project.

Grant.

Grant Peacock
Washington DC
GPI TV LLC

http://www.gpi.tv

[Jeremy Garchow]

This may be a corrupt motion template, or busted media link.

Is the media inside or outside of the library?

You can always export an FCPXML if you can have the library open for long enough.

[Grant Peacock]

Thanks again Jeremy. By only selecting the project in Browser, and not loading it to the Timeline, I was able to export the FCPXML file. (FCP apparently will not crash until I load the project file to the Timeline)

Now, would the next step be to establish a new library, and reimport media, then reimport the XML file into this?

I don’t think this is relevant, but my Finder level architecture/strategy for each new Library in FCP is to first establish a Finder-based folder inside Movies (name of folder matches Library yet to be created). Inside the folder, I create subfolders : cache, media, output, source. After opening FCP and creating a new library, I position the Library inside that top level folder (and alongside the subfolders), and modify Storage Settings so that cache and media are pointing to these relevant subfolders. I do not change the default locations for Backups or Motion Templates.

I don’t know if there’s anything in that strategy that might have contributed to an issue, as this has worked well throughout my time with FCP X in it’s various iterations.

Grant.

Grant Peacock
Washington DC
GPI TV LLC

http://www.gpi.tv

[Jeremy Garchow]

I would download the free XFX and load the XML in to it.

See if it returns any false values: https://www.spherico.com/filmtools/X-Files/X-FXHandler/

[Grant Peacock]

Thanks again Jeremy. The reimported XML file did produce a warning dialogue, but it’s basically machine code. I did also delete generated event files, but after quitting and restarting machine, and re-rendering, nothing has changed.

I’ve decided that the way to go is : new library, reimport, and rebuild the edit from scratch.

This has been an elusive problem, and it might not be one with a solution.

Grant.

Grant Peacock
Washington DC
GPI TV LLC

http://www.gpi.tv