Unofficial archive. This is a read-only, community-run archive of the Apple Support Community. It is not affiliated with or endorsed by Apple Inc.

FCP freezes importing second Atomos Sumo XML

Hello all,


I’m having an issue importing XML files from my Atomos Sumo into Final Cut Pro. When I import the first XML, it works without any problems. However, when I try to import a second XML, Final Cut Pro appears to start importing, but the progress bar doesn’t move. Shortly after, I get the spinning beachball and FCP stops responding.


If I force quit and relaunch FCP, the same issue happens again. The only way I’ve found to resolve it is to reboot the computer—after a restart, the XML will import successfully.


This behavior occurred on my Mac Studio, and I’m now seeing the exact same issue on a brand-new MacBook Pro M4 Pro. Because it’s happening across different machines, I’m wondering if this could be an FCP bug, an issue with the XMLs generated by the Atomos Sumo, or some kind of caching or memory-related problem.

3 replies

Are you using shared storage, like a NAS? I ask because I've found when importing XMLs into a library stored on a NAS works the first time, but then fails on subsequent imports and requires a force quit of FCP. The workaround has been to open a temporary library on the boot drive, import the XML, then copy to the library on the NAS.

I usually just copy the imported contents from the temp library into the primary one on the NAS.


Last year, joema here was very kind and examined some of my diagnostic output generated while importing XMLs into a NAS library and it appears there's some sort of file locking problem that happens. Have you tried using FCP 12? I'm not hopeful it fixes this, but there's always the possibility.

That is exactly what is happening as I have a Qnap NAS. So to confirm I just make a temp library on the local drive and run the xmls then move that temp library to the NAS or do I move the contents of the Library over to the new library.