Doug Metz
246
Apple Final Cut Pro X Coins
314
COW Coins
16
Storage & Archiving Coins
4
Solve Coins
Forum Replies Created
-
Hey Scott,
Installation guide for 6.2 on macOS:
To change directory in Terminal, for this install specifically, type “cd /usr/local/bin/“ – don’t type the quotes, hit Enter to execute.
Then you can list the contents with “ls” (no quotes) and Enter to verify the executable is in place.
The Bad CPU error makes me think the tool is looking for an Intel CPU and your machine is Apple Silicon, but that’s just a guess.
Their install guide also says the 6.2 tool supports “MAC 10.12 to 11.5 – Standalone drives only” so it may be that the later Big Sur updates break something that triggers this error.
One last thing – I noticed in your post that you’ve got an underscore in the command name, but the online install guide only shows that underscore in the name of the installer (not the name of the command).
-
Alrighty. Give this a try, Tim:
https://drive.google.com/file/d/1sXaSHEvqTtLPrrTAA7-ozxCU6aA8pABT/view?usp=sharing
-
Hey Tim,
It’s been interesting so far. I’ve attached a FCP Library file with the first batch of timelines, plus an Event with just the footage (keywords = bins) which I exported after removing all the sequences.
Crack it open and see what you can relink vs. what can’t / doesn’t. I’ll pause the translations until we confirm you can actually relink your media.
I agree that it is totally bananas not having a translation tool outside of FCP7!
-
Hey Tim!
I’m able to open the project and individual timelines just fine. There are 3 ‘EDIT’ bins, each with 70+ themes, and some of those themes have subs too. It seems there was a main EDIT folder to start, and over time it was duplicated a couple of times, though I’m not sure what’s different between them.
When possible, I export XML of the entire project at once. With this one, unfortunately, export repeatedly fails due to ‘critical XML error’. I’ve tried thinning things down to get a bulk export, but anything other than a single timeline produces the error. That said, I am able to export individual timeline XML and am in the process of exporting the latest timeline from each theme bin.
Once I’ve got those out, I’ll convert and bring them into a FCPX library and see what’s what.
-
Glad I could help, Nick.
-
Could very well be. I modified the above by removing the Brightness filter from the clone layer, and instead applied the Extrusion filter to the clone (extruding the original text layer caused unwanted clipping of the extrusion). Filters / Stylize / Extrude
-
You can replicate this in Motion:
– basic text layer
– apply Stroke filter (Library / Filters / Border / Stroke)
– create clone layer of the text, place directly below
– add Brightness filter to clone layer, shift clone position to wherever you want your drop, adjust brightness to dim shadow color/stroke
Could easily be made into a plugin, btw.
-
Sure, Tim!
I don’t need the media, just the project file(s). I’ve had really good success with small/medium-sized projects, but the bigger ones haven’t been quite as consistent. Won’t really know until I open it and see.
@ Eric Santiago – Good luck! I’ve got an OWC SSD on a PCI card for my boot disk, and a 3-disk RAID internal. I don’t put it on the network, and only boot it when needed. It’s been a really solid cheese grater for me going on 15 years.
-
You’ll need to start with a standard project, and bring your 360 footage into that. Set your output dimensions/frame rate when you create the project, don’t use Automatic Settings.
-
This situation is exactly why I purchased EditReady long ago. First, re-wrap card media, then import in-place. This extra step will retain metadata / TC for everything downstream.
I realize that doesn’t help in this situation, and it would be much more helpful if FCP could simply read the non-standard TC ref, but I don’t see that happening.
