Like so many things that need to be updated for High Sierra, the XDCAM plugin for FCP X probably needs it. Last update was 2014.

In High Sierra and FCP X 10.4, the application crashes the instant I open a folder containing XDCAM footage copied from an SxS card (using Catalyst Browser).

I'm having to use CB to export the footage to an MXF file and then importing into FCP.

Is it working for anyone?

... the XDCAM plugin for FCP X ...

Hi Les.

Are you referring to "XDCAM Transfer"? If so, I agree with you. High Sierra has pretty much "broken" it. These days, I tend to capture directly through FCP X itself (EX1R footage).

For what it's worth, I like to keep my FCP X libraries to as small a file size as possible. And I don't want to bloat them out by stuffing them full of XDCAM footage.

So, for my workflow, I set up a temporary Library which I usually call "Capture", then import the footage into FCP X. FCP X will then put QuickTime wrappers on the footage as it imports. I close that Capture Library in FCP X, then locate it in the Finder. I right-click on it and select "Show Package Contents". I then find these newly-created movie files and drag them out to a different location outside of that Library. Then I trash that (now empty) Capture Library. It takes about 10 seconds and I found it to be a much quicker workflow than using the old XDCAM Transfer. But, to each their own.

Apologies if I've misunderstood what you were saying or asking for. In that case, I'm sure someone else will chime in.

I don't mean XDCAM transfer. That was from long ago. FCP 7 days.

I copy files off the cards to the HD. Then in FCP, do Import. That is the step that wraps them into a .mov. The file is put in the library for managed libraries or in another folder you specify. The latter is the architected way to keep the libraries small and keep the video files outside the library. Until now, the wrapping into a .mov file was done internally by FCP using a plug-in provided by Sony. That no longer works in High Sierra/FCPX 10.4. During the Import, the moment you click on a folder containing the BPAV folder, FCP quits.

I went from El Capitan/FCP 10.3 to High Sierra /FCP 10.4 in one fell swoop so I don't know which is the culprit.

I import XDCam footage from a sxs card directly without any problems.
I don’t rewrap anything either or use any other software, just import straight in to FCPX. I also don’t have a problem importing XDCam footage straight from a sd card that’s in a sxs size adapter.
This is on Sony PMW 200, 300, 400 & 500 cameras and also Sony PXW 160 & 180 cameras.
Also no problem importing straight from a sd card from a Sony FS5.
This can be UDF, Fat or Ex Fat codecs, all without any problem.
I’m running the latest version of FCPX 10.4.3 and High Sierra.

There was a problem with much slower than normal import times, but this has been fixed with the recent updates to 10.4.

What camera and codec are you using?

Hmmmm. I actually tried direct from SxS card as well and the moment I click the folder containing the BPAV folder, FCP X quits. Instantly.

I am using two PMW-F3s and one EX1r. All with Sony SxS and Sony SxS-1.

In a previous thread he said he was using an old mac pro. If he upgraded it to High Sierra with FCPX 10.4 that could cause this problem. Older machines can’t run stable under the latest os.

I upgraded to a brand new 8 core nMP (2013) when I moved to High Sierra and 10.4.

That could be the issue...

As to importing directly from the sxs card, I don’t have to click on the BPAV folder or touch anything.
I put the sxs card into the reader with FCPX running and the import screen comes up automatically and I choose to import all the footage or choose which clips I want. That’s it.

So maybe it is a computer age related problem. How old/what model do you have and is it fully compatible with High Sierra?

It's a brand new Mac Pro (2013) trash can. Same thing happens on a Test user so it's not a use migration issue. The old cheese grater worked fine but was stuck at El Capitan and FCP X 10.3.

My 10.4 doesn't bring up the import screen for SxS. Just SD cards.

Your last post came in as I was writing!
Maybe start again with a complete clean install and go from there?

Top 15 Tips for Troubleshooting Final Cut Pro X (http://fcpx.tv/Pages/troubleshoot15.html)

I’ve just found this web page for trouble shooting problems.
Definitely worth checking some these...

Also, what sxs card reader are you using?
Mine needs a driver installed to work properly - again worth checking.

HAH! Thanks. I'm just now researching how to do a clean install of FCP X. For FCP 7 there was a tool called FCS remover.

It helps a lot to know it's supposed to work. Last resort is a clean OS install. Migrating users isn;t as easy as it used to be. I can see from the crash report that it;s the XDCAM plugin that's crashing. Reinstalling the plugin and deleting prefs doesn't solve.... Hmmmmm

I am using the original Sony USB SxS reader. But my workflow is top copy the the raw files to the HD using Sony's Catalyst Browser. It maintains the Sony SxS directory structure.

Have you tried removing/deleting the plug in and trying without it?
I understood XDCam is natively supported in FCPX.

Not sure how to do that...

REMOVE:
/Library/Application Support/ProApps/MIO/RADPlugins/XDCAMFormat.RADPlug

Nothing worked. I removed that MIO folder, the stuff in ~/Library and reinstalled ... no joy.

https://support.apple.com/en-us/HT202412


EDIT: I should add that IMPORT works with the SxS card reader directly. It even worked with SOME EX1r XDCAM on the HD from a year ago but not others.

Thread 6 Crashed:: MIO Mounting Thread
0 libsystem_c.dylib 0x00007fff662e2ced flockfile + 18
1 libsystem_c.dylib 0x00007fff662ea0e6 setvbuf + 69
2 com.apple.XDCAMPlugin 0x00000001263c3fca 0x1263bf000 + 20426
3 com.apple.XDCAMPlugin 0x00000001263c4260 0x1263bf000 + 21088
4 com.apple.XDCAMPlugin 0x00000001263c5dca 0x1263bf000 + 28106
5 com.apple.XDCAMPlugin 0x00000001263c73a3 0x1263bf000 + 33699
6 com.apple.XDCAMPlugin 0x00000001263c3344 0x1263bf000 + 17220
7 com.apple.XDCAMPlugin 0x00000001263c8090 0x1263bf000 + 37008
8 com.apple.XDCAMPlugin 0x00000001263c82b7 0x1263bf000 + 37559
9 com.apple.proapps.MIO 0x000000010c1d261b -[PluginLockPair volumeWithPath:error:] + 2123
10 com.apple.proapps.MIO 0x000000010c1d1bce -[PluginLockPair createVolumeForPath:error:] + 46
11 com.apple.proapps.MIO 0x000000010c1d172d -[PluginLockPair mountPath:] + 1021
12 com.apple.proapps.MIO 0x000000010c1d1af8 -[PluginLockPair scanPaths] + 392
13 com.apple.Foundation 0x00007fff404a41f8 __NSThread__start__ + 1197
14 libsystem_pthread.dylib 0x00007fff66570661 _pthread_body + 340
15 libsystem_pthread.dylib 0x00007fff6657050d _pthread_start + 377
16 libsystem_pthread.dylib 0x00007fff6656fbf9 thread_start + 13

I think it's a permissions problem from copying files across external drives. SIGH

Just leaving a breadcrumb here, definitely a permissions issue. Copying folder to internal HD of nMP does not crash FCP. Duplicating a folder on RAID still crashes.

I think I would start all over again and wipe clean the Mac and then re-install the programs...

It just so happens I returned the Mac Pro to Apple and bought a 2018 MBP. First thing I did was mount the RAID on a brand new install of FCP from the Apple store on a brand new High Sierra on a brand new MacBook Pro and .... voilå. It crashed.

My intuition from my unix days is that a recursive chgrp and chown are in order specifying the UID of the new login. But I think I'm gonna clock some time with Apple Care first.

NET: XDCAM is built into FCP X these days. It has nothing to do with Sony software. Everything works fine from SxS cards or newly created folders of footage. The problem is old footage copied to the RAID during micgration from Cheesegrater.

After an hour where the FCP Apple specialist was watching through screen sharing, they could not figure it out. Even mounting the original drive from the Cheesegrater exhibited the problem. Migrating a user from one machine to another and then renaming the user results in this kind of thing ... even tho the drive's GET INFO shows "Ignore User Permissions" is set.

All is not lost however. The work around is to copy everything to the RAID all over again. Copying the folder to the internal drive and back onto the RAID also works. ARGHHHHH 5TB of copying... at least this new MBP doesn't freeze 20 times a day like the Mac Pro.

Well it wasn't that at all. Rebuilding the drive failed and copying folders to the SSD was uneeded voodoo and did not work. THe fact it worked in the RAID Root was a boondogle.

After another 2 hours but with AppleCare level 3, we found the problem. There was a folder name containing the Mac character that (by convention) denotes "Folder" that is typed with opt-f. It's and old Mac way to name a folder something but denoting it as a folder for stuff. For example, in the applications folder, you can have an application called GoBob and a a folder to contain it's manual, license etc named GoBob ƒ.

Anyway, getting rid of the opt-f character solved the problem.