Be Careful When Reconnecting/Renaming Multiclips

When you have a multiclip already in a sequence, be aware that if one of the clips (or more) was renamed since it was edited into the Timeline, FCP can get confused and attribute TWO file names to one clip.

This will result in all manners of strangeness. For one, even though all the footage in your bin will be properly connected, a multiclip in the sequence in your timeline may still report a red bar over it, and if you hover your mouse over the red bar you'll see FCP complaining that one of the clips is offline...but it's not...it likely it just has two file names attributed to it. One of them being the old file name that's no longer available to FCP.

The solution is to 2nd click on the clip in the timeline, select Reconnect Media and then after connecting the properly named files, ignore the improperly named one(s). You should see the red render bar turn green nearly instantly.

This can happen if the files were initially named incorrectly and an editor renames them from within FCP or in the Finder late into a project's life.

iaian7's Ratio Widget

iaian7 has a pretty nifty FREE Dashboard widget to help you quickly calculate screen resolutions. You can check it out here. It even has support for iFrames already.

Beware when buying an EXT HD to replace an INT one

Xlr8yourmac.com has a brief story on what's inside an external HD case if you plan on buying one and swapping it out with the SATA drive in your laptop for more capacity, higher speeds or what have you.

It turns out that some HD manufacturers are putting their own connectors on HD's that essentially render them useless for laptop swaps. Western Digital being one of them with their 1TB Passport Essential SE USB. The drive doesn't have a SATA connector but rather a USB Mini-B (or Micro-B, I always get them confused).

Tip to use older Firewire devices under Snow Leopard

Macosxhints.com has an interesting tip on replacing a newer ktext file with an older one to get some older firewire devices to mount/work under Snow Leopard.

I haven't had any firewire devices that fail to work under Snow Leopard but this is good to know if you run into the problem.

Motion 4: May be unable to open projects

Here's a handy tip if Motion 4 refuses to open a project for you after installing Snow Leopard and FCS 09:

To address this issue, be sure Motion is not running. Then, open Terminal (located in ~/Applications/Utilities), and run the following command:

sudo touch /Applications/Motion.app

The Knowledge Base article is here.

What's Touch do? From it's Man page:

The touch utility sets the modification and access times of files to the current time of day. If the file doesn't exist, it is created with default permissions.

Apple's iFrame Announced

Apple has announced something called iFrame in a Knowledge Base article.

What's iFrame?

The iFrame Video format is designed by Apple to speed up importing and editing by keeping the content in its native recorded format while editing. Based on industry standard technologies such as H.264 and AAC audio, iFrame produces small file sizes and simplifies the process of working with Video recorded with your camera.

So it's essentially:

960x540
30fps
H.264
AAC

iMovie 8.0.5 suports it. And only two camcorders. No word on when FCP will support it.

9to5mac.com has a representational image comparing frame sizes here. Their brief article is here.

Appleinsider has a more in-depth article here.

Snow Leopard and Desktop Preview - Main

A few people (including me) have noticed quite dramatic artifacts when playing a project using Desktop Preview - Main under snow leopard. The artifacts look like quickly flickering horizontal lines which do not hold their positions when you stop and then start playback again.

I'm not sure what the exact combination of things causes the artifacts but it's something that appears for some people when under 10.6.1 but doesn't when booted from 10.5.8. Using either FCP6 or 7 doesn't seem to matter, it seems to be related to Snow Leopard.

Should People Wait to Buy FCS3?

Hardmac is reporting a rumor that one of their sources claims Final Cut Studio 3 is a "temporary/transition" version mainly released for Snow Leopard compatibility and that at NAB in 2010 (April 10th through the 15th) a more complete version will be announced.

What Model Mac Are You On?

If you're troubleshooting a Mac and aren't sure what exact model it is...so you don't know what firmware this or that needs...there's an easy way to find out not only the model designation but the type of CPU as well.

Fire up the Terminal (From the Finder hit Command + Shift + U, then T, then Command + O) and type in:

sysctl -a hw

Then hit Return.

You'll see fun info like:

hw.activecpu: 2
hw.physicalcpu: 2
hw.physicalcpu_max: 2
hw.logicalcpu: 2
hw.logicalcpu_max: 2
hw.cputype: 7
hw.cpusubtype: 4
hw.cpu64bit_capable: 1
hw.availcpu = 2
hw.machine = i386

but most importantly:

hw.model = Macmini2,1

If you want to see the exact CPU type, type in:

sysctl -a

and hit Return then look for something like:

machdep.cpu.vendor: GenuineIntel
machdep.cpu.brand_string: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz

QuickTimeMPEG2 Component vs Snow Leopard

If you install Snow Leopard and have the QuickTime Mpeg2 component installed, Snow Leopard will likely delete it. So, before you install Snow Leopard back this file up:

/System/Library/QuickTime/QuickTimeMPEG2.component

If you have already installed Snow Leopard and are now missing this file there are three things you can do to get it back:

01) Go to your Time Machine backup and restore it.

02) Head over to Apple and see if you can download it again if you bought it there under your account in Downloadables.

03) If you initially got it via Final Cut Studio then pop your FCS Install disc back in and then in the Finder hit Command + Shift + G (for Go to Folder...) and head to /Volumes/Final Cut Studio/Installer/Packages. Look for QuickTimeMPEG2.pkg and install it.

And this is curious, if you Right Click on the QuickTimeMPEG2 Component in Snow Leopard and choose Open With... you'll see the odd option KoreanIM as the default. If you try to open it with KoreanIM you'll be greeted with "Hangul cannot open files of this type."

Fun stuff.