Import Canon C300 mkii or C500 mkii crash FCP

Since the last macOS device update I can't import Canon C300 mkii or C500 mkii footage anymore? FCP crashes instantly when I select a directory with either of those clips, even when there are not in the original card file structure.
When I drag the MXF clips directly into FCP they import fine. But when I use the import window I get the crash.

Curiously C70 works fine as before?

Send bug report to Apple but wanted to check if anybody else is seeing this?

Try resetting FCP preferences (launch FCP while holding OPT+CMD). There was formerly a bug where it would crash upon raising the import dialog if certain non-video files were in the same folder as the video files. After resetting prefs, put the camera files in a new dedicated folder with nothing else in it, then try the import dialog again.

Also make sure you are on the latest version of Apple Pro Video Formats. In current versions of MacOS that is updated via System Preferences>Software Update.

You can check your installed version of Apple Pro Video Formats by the Apple menu>About this Mac>System Report>Software>Installations, the scroll down to Pro Video Formats. On Catalina and Big Sur it is ver 2.2.1.

Thanks Joe, pref deleted several times. No change. Dragged one MXF camera file out of the card folders to the root of the drive (to test) and same result.
Have the latest pro video formats too.
I attached a crash report in case you can read these things

It just shows thread 17 crashed trying to mount the pathname. It could imply something in the volume name + pathname syntax triggered the error, such as an odd or hidden character in the volume name or filename. Or it could be some kind of permissions problem.

Can you boot to recovery mode (boot holding CMD+R) and run Disk Utility First Aid on both boot partitions?

I see ColorFinale is in memory. Are you running the latest version of that? Are you using an eGPU?

Running latest of Color Finale and no eGPU.

Will try the disk utility in recovery mode later. BUT on the same drive and with the identical type of Canon card structure folders and same XF-AVC codec specs footage from a C70 imports just fine...

I see one prior report where FCP 10.4.1 crashed on import of Canon C300 XF-AVC files -- IF they were slow motion.

You say it happens if you drag an MXF file from the camera card to "the root of the drive". What drive? Is that external or internal? Is it formatted MacOS Extended Journaled, APFS or ExFAT? What if you drag that file to your MacOS desktop and try to import from there?

Does it happen with every MXF file from the C300 II and C500 II? What if you shoot a 1 second test clip of a blank wall? Or is it only certain frame rates, certain resolutions, certain Canon codecs, etc?

Apparently there's a low-level MacOS framework called CoreMediaIO, referred to in the crash log log as "MIO". Those are implemented as system-provided plugins that run within the address space of the app, in this case FCP. For some reason it encountered an error during the FCP import dialog, possibly following the functions createVolumeForPath or volumeWithPath. That in turn caused an unhandled exception which crashed the process.

If there is an FCP 10.5.4 bug importing that codec on MacOS 11.6, I'd expect it to happen on other machines. If you can send me a small test file which reproduces the problem on your machine I can test it on several machines and different versions of FCP.

You can ZIP it and upload it here:  www.transferbigfiles.com/dropbox/joema

Thanks Joe, appreciate your effort to get to the bottom of this. Unfortunately I can't send you any clips for privacy reasons.
I will try to maybe create a few new clips with our C300 mkii and test those in the next few days. Have to get some things done first though.

Because I was wondering if there was a hiccup when offloading the cards via Hedge to an external USB drive, ex-fat format, I took one clip and moved it to the root of that drive, out of the original card structure folders. Same result, so much so that selecting that drive in the import window causes an instant crash (wish is what happens all the time: in the moment you open a folder inside the import window that contains the c500 clips FCP crashes (quits, not just a beachball), not just when selecting the clip and click import selected. So it’s not a folder problem.

I compared metadata of the C70 clips that work with the C500 clips that don't with the app Scoop, and all codec etc details are exactly the same. 
i had clips from a few weeks back from the same camera and offloaded the same way on a diff USB ex-fat drive and none had any problem to import.
Dragging the clips directly into FCP works fine, only that they are copied in their original mxf container instead of being re-wrapped into a mov container while maintaining the original codec. In fact that method is somehow better than the import window way because FCP detects the correct Canon Log settings and auto applies the LUT, which is doesn't do via the import window.

The way you, or anybody else, could test it is to take a Canon XF-AVC 10bit 4:2:2 from any camera and try to import it, with FCP and macOS all with the latest versions.

As I have not changed anything in my workflow my only guess is that there is a gremlin in FCP that was released with the latest macOS updates. 

Carsten Orlt wrote:

...The way you, or anybody else, could test it is to take a Canon XF-AVC 10bit 4:2:2 from any camera and try to import it, with FCP and macOS all with the latest versions.... 

I would be happy to do that but my team has only Sony cameras. If you could shoot 1 second of material against a blank wall, verify that clip crashes FCP, then send me that I will examine it. Since the same codec from the C70 doesn't cause the problem, you may as well also shoot the same 1 sec clip with the C70 using the same codec and also send that.

Hi Joe, finally got around to do a test with a couple of C300mkii files and this time all is good. So the only diff is that one drive is ex-fat and the one I just tested is Mac formatted.

Will keep an eye on it and probably reformat all drives to Mac format in the future to avoid this possible problem.

It really should not cause that problem but each variable increases the test matrix size. From the perspective of Apple's testing, it is likely that ExFAT is not a high priority.

ExFAT is generally OK and it's Windows compatible. However it's not a transactional file system so may be more prone to damage. It also does not support features like hard links, which FCP uses to optimize media storage in some cases.

I'm not sure if inode path resolution works on ExFAT. That is the backup method of file location FCP uses besides volume+path. It is because of inode resolution that you can rename all FCP media files on a volume, move them to different locations on that volume, relaunch FCP and it will still find the files.

Inode info: https://www.javatpoint.com/linux-inodes

Typically SD-type camera cards above 64GB are formatted ExFAT in camera; below that size is often FAT-32. So in theory the same bug or behavior should exist if importing from the SD card. If it differs between SD card vs copying the files to an ExFAT-formatted hard drive, I don't know the reason.