Sorry ... I thought I had posted an update. Working with Apple Support, we discovered that the crash was due to a special character in one of the folders containing the footage. It was the character option-f which comes from an old convention back before OS X where applications installed the APP in the Applications folder as well as a folder for miscellaneous files like user manual, README, etc. The folder was the same name as the APP (so it would sort right next to it) but with an option-f added. It was basically shorthand for "Folder". I used the character to denote "Folder containing XDCAM" so my footage was separated from other files for a client or project.
Anyway, it's fine to use it in the Finder but with High Sierra, the XDCAM Plugin was crashing anytime an Import was done with a folder in the path that had that character. It could be anywhere in the path but the crash happened the moment I opened the folder containing the BPAV folder .
I didn't expect it but I have come around the the Trash Can view of desktop computing. I really like a small desktop unit separate from a RAID connected only by a small flexible cable (at the same performance of internal of course). It's no different than the backup enclosures. It also enables freedom of monitor configurations that the iMac inhibits. I think the Mac Mini coming out this fall is Apple's chance to solve the non-all-in-one desktop crisis it has. I would have waited for it had I known the disaster that awaited me with the nMP. YMMV
I saw those videos. They underscore how problematic the Apple platform is for pro users. There is no good choice. The only good news is there is still a non-windows option.
In every option, there are lots of compromises which is always the case but they seem a far greater magnitude than ever before. If you sit down and plunk down $5K to upgrade a workstation, you see the dilemna. The compromises are huge at every turn. The lack of an Apple monitor solution is the beginning.
I wanted a desktop system with separate display with an Eye to upgrade to next Mac Pro in 2020 or so. I picked up an Apple Refurb nMP 2013 but it hug and froze all the time. Ended up returning it and getting the new MBP 15. It makes for a nice video output device for editing and doing color correction. The touch bar looks interesting. TIme will tell if it holds up to desktop usage.
EPILOG: I found a few FCP editors that use them or tried them and then wished they'd waited till they came out. I picked up a Dell U3818DW 38". It's nice and easily replaces the twin HD monitors. I don't like the non-Apple experience. The monitor doesn't go black on Shutdown or sleep but instead insists on complaining about a lack of signal but eventually goes black.
It isn't very compatible with the MBP when connected via Thunderbolt 3. It prevents the system from sleeping and shutting down. Apple is researching but it's a mess. It only works using DP.
It's a Dell U3818 which is a 3840x1600 38" curved monitor. I'm not saying the problem was the display and not the fundamental D700 flaw but being manufactured so long after the problem was found and the fact it had already been returned and "Refurbished" by Apple, I was burned out trying to solve the problem. I spent a week. It basically left me with these choices:
A) Throw the dice on a "new" 5 year old Mac Pro for another $700
Suffer through the hardship of trying to get Apple to repair it
C) Return it for full refund and buy something else.
I was already in the hole $1000 for the Dell and already in love with single display equal to the old twin Cinema HD displays. iMac wasn't an option. That left MBP or Mini.
Going as far back as the G4 tower, I have always used my editing workstation for 5+ years so I choose carefully. Yesterday, I bought the 2.9 i9/32GB/1TB version to replace a 9 year old cheesegrater stuck on El Capitan. Already waited too long for a Mac Pro update that is now 2019. Plus, I never buy the version 1.0 of anything from Apple. Never. SO it was going to be a long time for a viable Mac Pro replacement.
So a week ago, I bought an Apple Refurb 8-core Mac Pro (about $1K more than a tricked out MBP) but after a week, I couldn't resolve that it froze 10-20 times a day. Best theory was the aging D700 GPUs were incompatible with modern 4K monitor etc. But nobody really could say as so few Apple techs know the nMP.
If you must buy a desktop for editing, the lack of an updated Mac Pro is problematic. Choices are 2014 Mac Mini, tricked out iMac, iMac Pro. When you read the articles about Apple's briefing on the future Mac Pro, it's clear the iMac Pro is their main offering for the "Pro" community but that a big chunk of community is actually using MBP. That's when the light went on that this model, configurable with 32GB and the i9 is a viable "desktop" in the absence of a real pro desktop Mac (I consider the iMac Pro a stop gap product) that is not an all-in-one.
So for those of us who need a desktop for use with multiple monitors, audio interfaces, raids, legacy eSata drives etc, the MBP floats to the top. It hasn't hung once and is as snappy or snappier than the 8-core nMP was (when it wasn't frozen). Time will tell.
The keyboard is junk and the aircraft carrier sized track pad a joke. But it's off to the side. The touch bar could be handy with a reach and the retina display a nice video output monitor. Plus I finally have a camera and built in mic. So there's a couple mice aspects to it over a classic desktop. Otherwise, for me, it's a very small desktop computer. YMMV
I didn't notice this thread when I posted elsewhere but as far as XDCAM 35 goes FCP 10.4 on High Sierra crashes during IMPORT when you open the folder that contains the BPAV folder. I'm assuming the culprit is Sony's FCP plugin that hasn't been updated since 2014 is the reason.
So far, the work around is to EXPORT the files using Catalyst Browser (Content Browser is deprecated and won't work on HS). The only option with CB that wraps not renders results in an MXF file.
Anyone know of another utility that will re-wrap XDCAM into .MOV?
That's interesting and hopeful Doug. Mine failed with both EX1r and F3 (XDCAM 35MBS) SxS cards.
Thanks Scott. It's July and there is still no solution. You can't import XDCAM into FCP 10.4 on High Sierra. It immediately crashes FCP.
That website has an XDCAM Drive update but in looking inside, there isn't an updated XDCAM plugin for FCP. I am interested in a place on the Sony website to report a problem but they don't seem to have one.
As a work around to using the El Capitan backup system, I use Catalyst Browse (free download) to ingest the XDCAM footage from the SxS cards onto the RAID. THen, using it's EXPORT capability, generate .MXF files. If you specify XDCAM as the "Type", it won't recompress. But it now takes twice the time to ingest and twice the about of storage.
I've done more investigation. My number one suggestion is to do the data shuffling when you have energy and focus. I was not paying attention with FCP repeatedly asked me to provide new Media and Cache locations. I thought I was needing to only do it one time when in fact, FCP was prompting me for each library. Had I been paying attention, it would have gone as planned. So here's my new recommended process for anyone gathering their data from multiple hard disks into a raid:
1) Migrate OS and User data however you choose paying attention to the files FCP keeps in your Movies folder
2) Migrate FCP Imported Clips/Cache from it's data disk to RAID
3) Copy Libraries from wherever they are to RAID
4) Open each library from the RAID
4a) Convert to 10.4 format as needed
4b) Specify FCP folders on RAID created in 2) for Media and Cache in the FCP prompt
5) Relink files for all the events in the library
6) Repeat 4-5 for each library
I discovered during my experience that there were file copy errors and FCP refused to relink to the versions on the RAID claiming they didn't match. FCP was right, the files it complained about were Import .MOV files that would not open. I think this was due to a crash during the copy. I used Carbon Copy Cloner and in reading up on it, if the file exists in the target, it won;t replace it. YMMV
I think I figured it out. It just doesn't work to copy library files. I had to:
1) boot the nMP with the Cheesegrater book drive
2) open each Cheesegrater library and point the Media/Cache to the RAID where those folders now are
3) Relink Files
4) Create a NEW LIBRARY on the Raid
5) Use FCP to copy all the files from the old library to the new one.
6) Boot using the nMP boot drive
7) Convert each library to FCP 10.4
My Cheesegrater FCP had libraries on one drive and Media/Cache on another. I used Carbon Copy Cloner to gather those folders and the library files onto a RAID on my nMP. However, launching FCP gives me the attached dialog complaining about Media/Cache folders. Setting them to the ones on the RAID doesn't satisfy the complaint and I have to Force Quit FCP. I tried recopying th eLibraries using the Finder instead of CCC but that did nothing.
Should I have done this different;y? TIA
[File Attachment: ScreenShot2018-07-09at7.26.38PM.jpg]
Hard to find serious FCP X users evaluate using the curve for editing. Does the distortion from the curve mess up getting graphics to line up or working with the horizon?
My early 2009 Mac Pro can't run 10.12 and I'm needing to run software that only runs on it. Plus I can't move to FCPX 2.4. I had wanted to wait for the new Mac Pro but that now looks like it's 2019. Not going the iMac Pro route.
So for a solid nMP configuration, my tendency would be to go for a used D700 equipped one but it's hard to make sense of all the the performance benchmarks trading off cores and graphics. I want great snappy editing and decent rendering. What configuration would you recommend for a good nMP FCPX/Motion workstation?
All my clients are 1080p edit to web. I shoot XDCAM 35MBS and GoPro.
Thanks Carsten. That does fix it at the annoyance of mixing compound clips with normal clips. Adding a transition before and after the SD clip causes all the clips to be put into a container (which I'm not up on enough to know the FCP X term for or know how to leverage them so they are just annoying). Thanks for the help.