I’m migrating from wordpress to my hosted server, so you can find everything here at www.luminoir.com from now on. All further updates will be reflected there.
———-
Get Fast fast
Let’s get one thing straight.
Being fast does not make you a good editor.
There are certain situations in which speed is the premium, either due to deadlines, workload or budget,
but in the long run, being fast isn’t quite enough.
Bearing that in mind, speed is still an important part of your arsenal.
What gets you on your way is mastering your tools
so that you have the quickest translation of what you see in your mind
to what you execute to the cut.
This tutorial won’t cover the more obvious basics of getting faster in FCP,
I think there’s plenty out there that covers that.
Hopefully, there are enough tricks here that even the old dogs haven’t used before.
How to approach binding keyboard shortcuts (and useful non default bound keys)
There are many opposing views on keyboard shortcuts.
Everyone has a preferred configuration so there’s no point quibbling about which is right.
Some people try to get their config as similar to avid as possible.
A person that takes over the station immediately after finds this out quickly
when they try to mark clip with x and finds their in to out ripple deleted.
My preference and approach when I started on FCP was to use the default config for a while before adding my own custom keys.
There’s no pointing spending half an hour setting keyboard shortcuts for an application I hadn’t used.
I used FCP for a few weeks before starting to add commands that I used with some regularity.
Here are some commands that are not bound by FCP by default that I recommend you bind. my bound keys follow, just as a suggestion
Command
|
Action
|
| navigate tabs |
cmd shift [ cmd shift ]
(don’t click tabs any more, what a time waster!) |
Export
Export to Quicktime
Export to Compressor |
cmd e
cmd shift e
cmd opt e |
| Audio Normalization Gain |
ctrl shift g |
| fav video effect |
ctrl shift numpad
(use all 9 keys of the numpad to bind your 9 most used effects) |
| fav motion path |
ctrl opt numpad (use all 9 keys of the numpad to bind your 9 most used motion paths) |
| fav audio effect |
cmd ctrl numpad (use all 9 keys of the numpad to bind your 9 most used effects) |
| reveal in finder |
ctrl r |
| send to motion |
ctrl shift m |
| deselect |
cmd d
(cmd shift a by default but I use it often enough that I don’t want to hold 2 modifier keys to use it |
Find the find tool
The FCP find tool is one of the biggest timesavers of the software.
It’s perfect for finding the media/effect/part of timeline you need.
There’s a reason I bind my deselect key to cmd d.
The find tool searches from the selected file on the browser/effects palette/timeline.
Deselecting forces it to search from the top.
Basically it’s a rapid fire movement of holding cmd then hitting
3df for files in the timeline (See my previous article for useful applications of this)
4df for files in the browser
5df for effects in the effects palette
6df for effects in the favorites palette
This helps most if you know exactly what you are looking for.
So for gaussian blur, instead of opening the effects palette, expanding the blur folder and double clicking gaussian blur it’s
cmd 5df (open effects palette, deselect, open find dialog)
gaus (use a unique part of the full name of effect you need)
enter
the effect you want is then highlighted.
If you want the Chroma Keyer, you might put “chroma” as your search term
but this will bring up chroma key transitions first and you’ll have to scroll down.
It’s more effective to use “keyer”
Here are some phrases for commonly used effects to skip similar situations
gaus gaussian blur
keye chroma keyer
3- 3-way color corrector
flicke flicker filter
spill spill suppressor
interl interlace flicker
This, of course, varies depending on the 3rd party effects you have installed.
To get around this, you can favourite all the effects you absolutely always use
and search your favourites instead with
cmd 6df %phrase enter
Changing durations of files but retaining keyframes across new duration
We’ve all been there before.
We’ve painstaking used the motion tab to make a file move/crop/rotate on a motion path to perfection and now it needs to be 16 frames longer/shorter.
Instead of opening the motion tab and dragging keyframes around, copy the current file, extend/shorten it,
then paste motion/distort/crop attributes with the scale attribute times checkbox checked.
Changing motion effect to fit to fill without affecting sync
Whenever I had to speed effect a clip to fit to a duration, I used to create a new video layer,
move the file up, lock all others, change speed effect, unlock, move file back down, delete video layer.
Now, I’ve realized how slow that was after I starting doing it this way.
- Set playhead to start of clip
- set in point (i)
- set out point at desired NEW end of clip (after speed effect)
- go to canvas window (cmd 2)
- select in/out duration (tab)
- copy (cmd c)
- select clip
- cut (cmd x)
- go to end of sequence (end)
- paste (cmd v)
- speed effect (cmd j)
- paste (cmd v)
- enter
- cut (cmd x)
- go to in point (shift i)
- paste (cmd v)
Make Favourites your favourite tool
As mentioned earlier, I have my most used audio filters, motion paths (for resizing anamorphically stretched footage and correcting it with respect to a graphic crawler)
transitions and effects saved in my favorites. You can search them as suggested above, but what if you have a very specific set that you use all the time?
As you can see from my favorites folder I number them sequentially and bind my keyboard keys to be a modifier combination and the numpad.
This is because the # of the effect is based on creation order and I name the plugins based on that so I remember which number corresponds to which shortcut.
I create it based on frequency of use and over time it becomes second nature.
This makes all my favourite filters, motion paths a keypress away.
So I know instinctively that my motion path to fit anamorphically stretched footage into a gfx donut is ctrl opt 2 for example.
The modifiers for the filters used ctrl are for video, ctrl opt for motion path and ctrl shift for audio filters.
Autosave Duration
Hopefully, there’s been something in the article above that you’ve never used before and it has been useful to you in some way.
If you’re working faster, that means if FCP crashes 29 minutes after your last autosave and you left the autosave duration at its default value of 30 mins,
you’ve lost a lot more work that you need to do again, and that’s terribly demoralizing.
It’s slightly irritating to be interrupted every 5 minutes by an autosave
but less irritating than redoing that complicated key, secondary color correction, multicam cut from 29 minutes ago.
The Sudden Rise of FCP
July 6, 2008 · Leave a Comment
I was trained on the Avid Meridien platform and my first time using FCP was on my very first job which I took on part-time while I was in my final year at Film, Sound and Video in Ngee Ann Polytechnic.
My employer at that time had a G4 running FCP v1.2.
It was slow, unstable, crashed a lot, lacked realtime effects support and dissolves needed to be rendered.
Suffice to say, it failed to make much of an impression. It was an interesting mix of a NLE with some motion graphics capability but lacked many of features we have been spoiled with on the Avid.
In the interim, I worked on the Avid Meridien based systems and transitioned to the Adrenline when that line was EOLed. I became overly familiar with the Avid error messages to an embarrassing extent.I remember a producer quizzically looking at me when I started explaining to her about DRAGON Error messages, BUFFER OVERRUN and UNDERRUN codes.
Progress
During that time, under the auspices of Apple’s ProApps department, FCP improved. Enough for Walter Murch to decide that he could do Cold Mountain on it. Before that, Rules of Attraction, Full Frontal and The Ring had also been cut on it.
It was a necessary response from the company now that Avid had decided to migrate to Windows XP for the Adrenaline, Mojo series of Media Composer. Apple no longer had a video killer app solely available on the mac platform.
Apple had to get marketshare back somehow set that in motion by purchasing Keygrip from Macromedia and renaming it Final Cut Pro.
Apple’s G5 became the biggest dongle in the world for the new fastest growing NLE.
Avid’s regression
Avid still had a dominant installed userbase and felt no need to compete with Apple on the basis of their disruptive price point. DVXpress was deemed to be their equivalent product line, but the restriction of it’s maximum output resolution to DV25 without additional hardware meant that it’s usefulness would be restricted to the hobbyist/prosumer/budget/boutique production house.
Avid’s workflow for footage originating on tape is first class.
The media management tools, offline/online media reconnection all save us loads of time by storing it in the omf media database and enabling simple and mostly painless media management.
However, importing files to Avid, has always been a pain for the exact same reason.
Importing video files in particular is akin to pulling teeth. The files have to converted to omf media on import before they can be used.
If the current show I’m editing was done on the Avid, I would easily be converting up to 80% of my footage.
Also, the disruptive price point of FCP meant that a lot of boutique production houses were sprouting up. Final Cut Studio meant any one man operation with $2500 had the tools (not unnecessarily the skills) to compete with a production house with an Avid and graphics department.
This has resulted in the freelance editing market shifting from 80% Avid, 15% FCP, 5% others in 2002 to what seems to be a 70% FCP, 25% Avid, 5% others pie. (These numbers are obviously not scientifically gathered, it’s just me asking other freelancers the percentage of jobs they do on each platform.)
Apple’s complacency
Apple hasn’t really been pushing the boundaries of what FCP can achieve. The impression that Avid seems to have given up on competing with them for the budget/boutique user demographic seems to have left them free to their own devices. Both companies neglected to have a booth at NAB.
There are numerous bugs that have existed from the first version I used (v1.2) to this very day.
Particularly annoying are the edit to tape compression error, the keyframe editor redraw bug, inconsistent render file linkages and the fact that every point update breaks the project file.
I think the problem with FCP is that the Proapps team seems to find it cooler to add new features than fix existing bugs.
The Future
I hope Avid continues to try to compete with FCP.
Competition is necessary for innovation and I think the best work we’ve seen from both developers were when they were fighting for marketshare. It would be great if Quantel, Sony (Vegas/xpri), Media 100 got back into the mix. The key to FCP’s sudden increase in marketshare wasn’t Avid users throwing away their Meridien and Nitris Boxes. It was the multitude of new users investing in hardware/software that was no longer priced out of their reach.
This market is ever expanding and it would be a great pity, not to mention a missed opportunity, if other companies allowed Apple complete dominance of this space.
Categories: FCP · editing
Tagged: apple, avid, comment, FCP, hardware, software