XDCAM Broken on FCPX 10.4 and High Sierra

Les Wilson · July 16th, 2018, 03:28 PM

Not sure how to do that...

Les Wilson · July 16th, 2018, 03:29 PM

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

Les Wilson · July 16th, 2018, 04:30 PM

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

Les Wilson · July 16th, 2018, 06:01 PM

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

Les Wilson · July 17th, 2018, 10:22 AM

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.

Kevin Langdon · July 18th, 2018, 01:42 PM

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

Les Wilson · July 18th, 2018, 03:32 PM

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.

Les Wilson · July 21st, 2018, 06:28 AM

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.

Les Wilson · August 1st, 2018, 10:45 AM

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.

July 16th, 2018, 03:28 PM	#16
Les Wilson Inner Circle Join Date: Jan 2004 Location: Boca Raton, FL Posts: 3,014	Re: XDCAM Broken on FCPX 10.4 and High Sierra Not sure how to do that...

July 16th, 2018, 03:29 PM	#17
Les Wilson Inner Circle Join Date: Jan 2004 Location: Boca Raton, FL Posts: 3,014	Re: XDCAM Broken on FCPX 10.4 and High Sierra REMOVE: /Library/Application Support/ProApps/MIO/RADPlugins/XDCAMFormat.RADPlug

July 16th, 2018, 04:30 PM	#18
Les Wilson Inner Circle Join Date: Jan 2004 Location: Boca Raton, FL Posts: 3,014	Re: XDCAM Broken on FCPX 10.4 and High Sierra 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

July 16th, 2018, 06:01 PM	#19
Les Wilson Inner Circle Join Date: Jan 2004 Location: Boca Raton, FL Posts: 3,014	Re: XDCAM Broken on FCPX 10.4 and High Sierra I think it's a permissions problem from copying files across external drives. SIGH

July 17th, 2018, 10:22 AM	#20
Les Wilson Inner Circle Join Date: Jan 2004 Location: Boca Raton, FL Posts: 3,014	Re: XDCAM Broken on FCPX 10.4 and High Sierra 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.

July 18th, 2018, 01:42 PM	#21
Kevin Langdon Regular Crew Join Date: Jan 2013 Location: Somerset, England Posts: 120	Re: XDCAM Broken on FCPX 10.4 and High Sierra I think I would start all over again and wipe clean the Mac and then re-install the programs...

July 18th, 2018, 03:32 PM	#22
Les Wilson Inner Circle Join Date: Jan 2004 Location: Boca Raton, FL Posts: 3,014	Re: XDCAM Broken on FCPX 10.4 and High Sierra 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.

July 21st, 2018, 06:28 AM	#23
Les Wilson Inner Circle Join Date: Jan 2004 Location: Boca Raton, FL Posts: 3,014	Re: XDCAM Broken on FCPX 10.4 and High Sierra 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.

August 1st, 2018, 10:45 AM	#24
Les Wilson Inner Circle Join Date: Jan 2004 Location: Boca Raton, FL Posts: 3,014	Re: XDCAM Broken on FCPX 10.4 and High Sierra 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.