Reel 2010

July 26th, 2010

A collection of shots over the last two years.
Read the rest of this entry »

Final Cut Pro and the Dvorak Keyboard Layout

December 1st, 2008

In order to improve my elitist computing, I have adopted the Dvorak Keyboard Layout.

I can’t say that my typing speed has increased, but it feels smoother. Actually, the worst part is trying to use QWERTY again, after the conversion: changing an offending layout over to DVORAK isn’t the issue, it’s just embarrassing having to type so slowly in front of others! It’s a real blow to my elitist computing skills. I am always silently preparing my defence against the didn’t-you-learn-to-type accusation, which most people are too polite to issue.

Final Cut Pro 5 (and 6), however, is the one app that has caused me a modicum of irritation. For keyboard shortcuts, most applications simply use your newly re-mapped layout. FCP, however, does not. And although FCP does let you customize your keyboard layout, there are two issues.

  1. There are millions of keyboard shortcuts that have to be manually changed.
  2. Some keys are permanently assigned.

For example, aside from the missing existence of a preset DVORAK layout, trying moving the ‘copy’ shortcut from the old QWERTY ‘C’ (now DVORAK ‘J’) to its new location and you get this error:

What?! “It cannot be re-assigned”! Can anyone explain why FCP developers would prohibit specific shortcut re-assignments?

Thankfully, Cody over at stolen films found a workaround via TOOLS > BUTTON LIST. Read his comment below.

So for all you DVORAK FCP users out there in my imaginary elitist video editing circle, here is my best attempt at a DVORAK layout that matches key for key (using Cody’s workaround) the old world QWERTY’s, all zipped up:

Default – US Dvorak

Three Swim Day

September 13th, 2007

[ Javascript required to view QuickTime movie, please turn it on and refresh this page ]

During our annual family holiday in Tofino this last July, Mischa, Michael and I caught three great swims in some local fresh water.

I used Google Earth for the fly-in intro. Not wanting to shell out for the $400 pro version, I used a screen capture tool called Capture Me when Copernicus continued to crash. With a very slow frame rate in the resulting captured video, I had to increase the speed of the clip in FCP by 200% to eliminate the stutter.

I also tried out the image stabilizer filter in FCP which worked fairly successfully, I thought considering some of the crazy camera shake on the full zoom shots.

Audio mix-down was straightforward. Up-converted to 720p 30 form NTSC DV. Eventually, I’ll be able to use these HD renders.