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 12.3 pinwheels when importing Sony XDCAM files

FCP 12.3 on Mac OS 26.7 on new MBP 16 M5 Pro now pinwheels importing Sony XDCAM. I was able to import XDCAM back in June on same system but at June levels of software. Now as soon as I click on an XDCAM file using the import dialog, I get a pinwheel requiring a FORCE QUIT. I tried opening a pre-Tahoe project and using the Import dialog, to browse to other XDCAM files. Those files are not selectable and FCP Pinwheels when I close the Import dialog requiring a FORCE QUIT.


Any suggestions for fixing this?

11 replies

SOLUTION:

To their credit, the Sony has maintained FCP support for it's log and capture software (Catalyst Browse aka CTB) across the more than a decade of life the XDCAM technology has seen. Turns out there was a 0.0.1 update to the software that fixes the issue. I've been using XDCAM so long I forgot that package installs the software used by FCP to handle the XDCAM file structure. So if I had said YES to the prompt to update CTB to version 2026.1.1 from 2026.1.0, this would have been avoided.


In my defense I have been burned in the past by updates to that package ... hence the reluctance. But being a laggard burned me this time. #cantwin


EPILOG:

At this point Sony has migrated to the Free or Subscribe model and renamed Catalyst Browse. So for any XDCAM users who find this thread, you must upgrade to the V3 package of the Sony Catalyst Prepare software (here). It's safe to go in the water ... It works on Tahoe 26.7 and FCP 12.3


p.s. Drag/drop of the BPAV folder still does not successfully import XDCAM files. You must use the IMPORT dialog.

WORKAROUND:

Until FCP fixes the XDCAM support in the Import Dialog, I was able to work around the problem as follows:

1) Using the Sony CTB utility, use the EXPORT function to transcode the files to Prores

2) Import into FCP


CONS:

This workaround requires double the storage.


PROS:

You can keep working until Apple fixes the bug

Have you tried bypassing the import dialog and manually dragging the XDCAM's enclosing folder from the Finder into an event?

Drag in the entire top level folder or BPAV folder and say OK to the FCP dialog that complains there are a bunch of files it doesn't understand.

As BenB said, dragging media in will (usually) use the Import settings you've previously configured in Settings. To me, this points to an XDCAM display/decode problem in the Import window.


Report this to Apple via Final Cut Pro->Provide Final Cut Pro Feedback... or Feedback - Final Cut Pro - Apple


Thanks Terryb. What I am getting when I drag/drop the BPAV folder and say OK is a bunch of video files without audio. The audio is apparently in the BIM files and FCP merges it with the video MP4 file during XDCAM IMPORT. That processing of Sony XDCAM files happened during the Import Dialog which in FCP 12.3 now hangs FCP. It does not happen when the BPAV folder is dragged and dropped on my system.


Is it working for you on 12.3 and Tahoe?

Yes. That results in the a dialog declaring the non-video files won't be imported but the MP4 file is imported and can be edited as usual. However that bypasses the other things the import dialog does which includes copying the data off the SxS card into the Final Cut Original Media folder.


What does this indicate about the problem?

Actually, when you drag-and-drop, THAT import behavior is dictated by the options you've selected in Settings > Import. Same options as the Import Window, except it only applies to drag-and-drop imports. So you do have the same control.

Thanks. As noted in response to terryb, drag drop only brings in video. I tried drag dropping the BIM files but they are rejected by FCP. I agree this is a problem with the XDCAM support in FCP. I reported it immediately after posting here.

CORRECTION. importing via Drag/Drop, only imports the video ... so no audio. Looks like it's in the BIM files and FCP Import Dialog combined them during the import. Sigh.

Good sleuthing. Thank you for reporting your findings.