Jeff Kirkland
Forum Replies Created
-
Import the clips into an event. Use the info panel to set the metadata for the clip angle if it’s not already done. If the angles are continuous clips, then you can add a marker at roughly the same spot at the start each angle to give FCPX a hint about where to start. That will speed things up a lot but for the most part, it’s pretty quick anyway.
Select all the clips to be synced and get FCPX to create the multiclip. FCPX will do the rest.
Once the multiclip sync is done, open the clip in the angle editor and rearrange the clips into whatever order you want them to be in. Occasionally, if the audio on an angle was really bad, I’ve had to tweak things a little in the angle editor, and very occasionally I’ve had to sync the angles one at a time using the drop down inside the angle editor itself but that’s pretty rare.
That’s all there is to it.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
On import, FCPX will force you to optimise non-native files, leaves you the option of optimising non-ProPes “native” files, and will (should) leave ProRes alone because it’s already optimised and just import it.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
Missed that.
It usually pays to keep your OSX version and FCPX version in sync so as to avoid any potential weird stuff happening… you should ideally be running FCPX 10.1 on a Mavericks system, or maybe Yosemite for the later 10.1.x versions.
So, in addition to my list of diagnostic steps above, insert “is this the latest version of FCPX?” as the first question to ask.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
I have no idea why it’s crashing for you but my thoughts are…
1. Try letting FCPX create the multi clip and see what happens. pluraleyes is great but fcpx’s internal sync is just as good and maybe there’s an issue with the multicam pluraleyes is generating.
2. Maybe your install of FCPX is broken. Try reinstalling it and see if that helps.
3. when you say the screen disappears, what is happening exactly? Are we talking FCPX crashing or the whole of OSX going away?
Anyway, it’s hard to remotely diagnose individual crashes but the general procedure (in order of pain level) would be a) trash preferences, b)log in as different user and try it there to see if it’s something corrupted in your user folder, c) remove/disable/stop using any third party apps and plugins that might relate to the crash, and d) delete FCPX, reboot, reinstall FCPX.
If none of those work then your problem is either OSX or hardware related.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
Even if you do import and create optimised media, fcpx will give you info on the original media, not the optimised media. Optimising media on import isn’t replacing the media you import, it’s creating an optimised copy that FCPX substitutes for the original when editing. Essentially it’s creating a full-sized Prores proxy for your h.264 clips under the hood, but on the surface will continue to treat it as the h.264 original.
If you look at the info panel, you should see that while it reports the clip as h.264, and further down the panel it will show if you have an optimised and/or proxy version available. FCPX will use the optimised/proxy version first, if it’s available, and then use the original of there isn’t an optimised version.
You have two copies in your browser because instead of just letting FCPX do its thing, you went to the optimised media folder and imported the footage again. And no, don’t delete the original media unless you want a potential mess on your hands later when it comes to archiving the project.
The FCPX user manual explains all this fairly well and, from memory, Ripple Training spend quite a bit of time on how FCPX handles media importing in their training videos. Both are worth checking out if you haven’t quite got your head around what’s happening at the file import stage.
I personally use an app like Editready to convert all my media to ProRes before I import it to FCPX but only because I prefer to manage and organise my media manually in the Ffinder rather than letting FCPX do it.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
FCPX is working fine for me with El Capitan. There can be some minor graphics glitches but nothing that will stop you using the app. As Jeremy mentioned, this version of FCPX doesn’t specifically take advantage of any of the new technology on OS X but it does benefit from El Capitan just being a faster, more efficient platform.
It’s only anecdotal on my part, but I definitely feel that FCPX is running faster under El Capitan.
Having said all that, my recommendation is always to wait until there’s a post El Capitan release of FCPX before updating. I was just in a position where I had to do a clean install anyway, so I decided to give El Capitan a try.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
Once the file has been sent to Compressor, from within Compressor choose “Create Blu-ray” as the preset. Choose the folder, not the two presets inside it. The last action of that preset is to bring up the same Blu-ray creation dialog you’d see in FCPX.
That last step is actually set up as the action at the end of the job. In the Job panel on the right you can set “When done…” to “Create Blu-ray” if you want to set up a preset like that by hand. (or I think you could, I’ve only ever used and tweaked the original preset).
Happy holidays…
Jeff KJeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
I think FCPX is playing at being broken. I use compound clips the way you are (if I’m falling what you’re doing properly) and I’ve never had an issue. Have you tried the basics like resetting the preferences, copying things to a new library, or reinstalling FCPX?
I know that’s the equivalent of a tech support guy telling you to turn the computer off and on again but, from my experience at least, what you’re describing isn’t normal so you’ve got to start with the simple fixes and work on up from there.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
From personal experience, H.264 is pretty much your only choice for near universal file delivery. This brings delivery size down to down to something that will fit on a USB thumb drive.
If you are determined to give them a full copy of the MOV master file (which 90% of Windows users won’t be able to play), then buy a small harddrive and give it to them on that.
In terms of the hard drive format, I use Paragon NTFS so I can read/write NTFS formatted drives. I just ask the client if they want Mac or PC.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
No worries, happy to help.
There’s another option in the same panel that lets you tell it whether or not to rename clips, and if so what to. From memory, the default is to use the original clip name.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland
