Essential tools: Perian

Perian's icon is a swiss-army knife and that couldn't be a better description. It is a codec pack for QuickTime that allows you to play back a whole host of formats including AVI, DivX and 3ivX. These are PC formats that we editors get given from time to time and it is incredibly useful to have a free Mac component to view them with.

Some people have reported problems with it but I personally have experienced none so far.

The brand new version 1.1 (just came out today) features the following changes:
* Major performance improvements
* TrueAudio, MP1, and DTS audio support
* Slice-based multithreaded decoding for MPEG-1/2/H.264
* Apple H.264 now handles AVCHD/interlaced video
* Compatibility fixes for QuickTime 7.4 and Leopard
* Objective-C GC compatibility
* Fixed a crash in Toast
* Better subtitle rendering
* Subtitles play during MKV loading
* Snow support
* Miscellaneous bug fixes

Perian can be downloaded here for free.

ProKit 4.5 update

Apple has just updated ProKit to version 4.5.

ProKit, as far as I am aware, contains only UI elements such as button images for professional applications such as Final Cut Studio, Final Cut Express, Logic Studio, etc. There is unlikely to be anything exciting in it I'm afraid.

Apple's release notes are, as always, rather vague:


As always, don't update a working system unless you are experiencing a major problem that this update may fix. And when you do it, make sure to clone your drive with something like Carbon Copy Cloner first.

Update: Some people are reporting that Motion 3 instabilities with the Ozone plugin are a thing of the past with the new ProKit update.

Update 2: Others are reporting that the DVD Studio Pro menu that had disappeared is now back, while others are reporting that it causes their Logic 8 installation to crash.

I know people have been experiencing issues with Compressor windows not opening, so I would advise them to give this patch a go and see if it fixes it for them.

Recommended QuickTime and Mac OS configurations for Final Cut Pro

As the recent QuickTime 7.3 and 7.4 updates show, it is important to choose your Mac OS and QuickTime configurations carefully to match your Final Cut Pro version.

I have been developing this list of optimal configurations for a while now. It is based on my own experiences and the recommendations of others. As such, it is somewhat subjective. If your own experiences differ, feel free to let me know and I will update the page.

Note: This page is designed to give the most compatible configurations for old versions of Final Cut Pro. If you have the latest version of FCP, you should simply use the latest OS X and QuickTime versions. But don't upgrade in the middle of a project.

Final Cut Pro Version	Mac OS Version	QuickTime Version
6.0.6	10.5.8	7.6.6
6.0.5	10.5.6	7.5.5
6.0.4	10.5.5	7.5.5
6.0.3	10.4.11 / 10.5.2	7.4.5
6.0.2	10.4.11 / 10.5.1	7.3.1
5.1.4	10.4.11	7.1.6
5.0.4	10.4.11	7.1.6
4.5	10.3.9	6.5
3.0.4	10.2.8 Update 2	6.2
3.0	10.2.8 Update 2	5.0.6
2.0.2	9.2.2	5.0.1
1.2.5	9.2.2	4.1.3
1.2.1	8.6	4.1.1
1.0.1	8.6	4.0.3
1.0	8.6	4b16

Using QuickTime 7.4 with Final Cut Pro 6

I've seen a lot of questions about this lately. Some people have tried installing QuickTime 7.4 in order to fix problems they were experiencing with Final Cut Studio. There is no need to install QuickTime 7.4 on your Final Cut Pro machine as the 7.4 update does not offer any new features relevant to Final Cut. In fact, it causes a lot of incompatibilities with non-Apple software.

You should only install a QuickTime update when you are updating Final Cut Pro and the FCP update demands a later version of QuickTime. It is best not to do this in the middle of a project, and make sure you have a clone of your current system before you do so.

I understand that some people use their machines for multiple purposes and the temptation to install QuickTime 7.4 in order to get iTunes movie rentals must be great. I would advise people in this situation to at least wait for a 7.4.1 patch before upgrading. The bugs in the current release mean that such a patch is likely. Don't forget to clone your drive before you do it.

And don't install it at all unless you have the very latest version of Final Cut Pro (6.0.2) or it will break your Final Cut Pro installation.

A little update on Final Cut Pro's gamma quirks

Last week I made a post about Final Cut Pro modifying the gamma of clips, causing some to be too dark and some to be washed out.

The washed out issue was the most serious because it only happened upon exporting the movie, and the image looked perfectly fine in FCP. The darkening issue was less severe because it only affected the user's perception of the image in FCP and if they were not performing color correction in FCP, they would be perfectly fine.

I was just going through User Preferences, trying to help someone who was having difficulty, when I noticed a new option that I had never seen before (I don't adjust user prefs very often). In the Editing tab, there is a section marked "Imported Still / RGB Video Gamma". You can choose from Source, 1.80, 2.20, 2.22 and Custom. My research indicates that this option has been there since 6.0.0 but Apple recently renamed it in 6.0.2 to clarify that it is for RGB footage only.

1.80 refers to the default gamma of RGB footage (eg. still images and special effects codecs such as Animation). This is also the default gamma of your Mac display. 2.20 refers to the default gamma of YUV footage (eg. NTSC, PAL, ProRes, etc). Camera footage falls into this category, as do a lot of the displays on Windows machines. Gamma 2.22 is also used by Windows PCs. I would advise leaving this option on Source, so that no gamma correction will be applied to the clip itself. The only correction that will occur will be when playing back in the FCP Canvas, and not upon exporting the movie.

This setting will fix the RGB gamma issue that caused images to be washed out upon export. This does not change Final Cut Pro's handling of YUV images.

Missing codecs in QuickTime 7.4

[Time code]; has noticed that the new QuickTime 7.4 update offers you significantly fewer export options than its predecessor. At first glance, they appear to have been removed, but rest assured - they are still there and have just been hidden. To show them again, go to QuickTime in System Preferences, click on the Advanced tab and check the box marked "Show legacy encoders".

The reason for hiding them is probably to prevent end-user confusion and promote more modern formats.

Update: Apple now has a support document confirming this.

Is your Final Cut Pro sequence too dark or washed out?

This seems to be a common question. Sometimes people will create a sequence in Shake (or similar) and export to Final Cut, only to find that the image is much darker in FCP. Others have a different problem - it displays fine in FCP but appears washed out when you export it.

Final Cut Pro tends to make assumptions when it comes to gamma. If you create YUV (e.g. DV PAL, NTSC) footage, it will assume that it was created with a gamma of 2.2, which it would have been if it had been shot in a camera. Final Cut therefore lowers the gamma in order to mimic what it would look like on a broadcast monitor, resulting in a darkening of the image.

Note that the image is only dark in Final Cut Pro and if you export it, it will export with the correct gamma. However, the mistake that some people make is to brighten the image in Final Cut, leading to it being too bright upon exporting.

Applications like Shake do not make any modifications to the display of the gamma so if it looks fine in Shake, it will look fine upon exporting, no matter what Final Cut Pro is showing on the screen. This is assuming your monitor is correctly calibrated, of course.

When you import RGB elements (such as the Apple Animation codec or still images) into a YUV sequence, the opposite problem occurs. Final Cut Pro will assume they were created with a gamma of 1.8. Final Cut will then increase the gamma to 2.2 (the gamma value that FCP assumes all YUV media is created at) to compensate for this.

The image is now considered YUV, so when it plays back, Final Cut will lower the gamma again to compensate, as it does with all YUV footage. The RGB elements will be displayed on the screen at their correct gamma but when you export the sequence, the boosted gamma will be used and the exported sequence will be too bright.

The solution is to convert the files to YUV before adding them to your Final Cut Pro project. For footage, convert to Uncompressed 8-bit 4:2:2 or Uncompressed 10-bit 4:2:2 to ensure that no data will be lost in the conversion process. If the file sizes for this are too large, try a high quality lossy codec such as Apple ProRes.

For images, the easiest method is to convert them to a single-frame QuickTime file with a YUV codec such as DV NTSC. It is better to perform this task with Compressor rather than QuickTime.

How to trash preferences

If an application in Mac OS X fails to load or exhibits strange behavior, a common way of fixing the problem is to trash preferences. But what does this mean?

Application preferences such as window layouts and sizes, user-selected options, etc, are all stored in a preferences file ending in .plist. There is a different file for each application. When you delete this file ("trash" it) and fire up the relevant application, the app will notice that the file is missing and create a new one with default preferences. This can solve many issues.

Below is a table of common professional applications and where their preference files are located (note that ~ refers to the current user's Home folder):

Application	Folder	Filename
Final Cut Pro	~/Library/Preferences	com.apple.FinalCutPro.plist
Compressor	~/Library/Preferences	com.apple.compressor.Compressor.plist com.apple.Compressor.CompressorSharedService.plist
DVD Studio Pro	~/Library/Preferences	com.apple.dvdstudiopro.plist
LiveType	~/Library/Preferences	com.apple.LiveType.plist
Motion	~/Library/Preferences	com.apple.motion.plist
Shake	~/Library/Preferences	com.apple.shake.plist
Soundtrack Pro	~/Library/Preferences	com.apple.soundtrackpro.plist
Apple Color	~/Library/Preferences	com.apple.color.plist
Adobe Photoshop	~/Library/Preferences	com.adobe.Photoshop.plist
Maya 7	~/Library/Preferences	com.alias.Maya.7.0.plist
Maya 8	~/Library/Preferences	com.alias.Maya.8.0.plist
Vue 5 Infinite	~/Library/Preferences	com.e-onsoftware.vue5infinite.plist
Vue 6 Infinite	~/Library/Preferences	com.e-onsoftware.vue6infinite.plist
Boujou	/Library/Preferences	com.boujou.plist

Additional Final Cut Pro settings are stored in the ~/Library/Preferences/Final Cut Pro User Data directory. You need to trash "Final Cut Pro 6.0 Preferences" (and any previous versions), "Final Cut Pro Obj Cache" and "Final Cut Pro Prof Cache".

After deleting the files, empty the trash and fire up the application again.

Update 4/4/08:
We now have an application called Preference Manager for trashing, backing up and restoring preferences.

Capture HDV to ProRes via Firewire in Final Cut Pro 6.0.2

Chris Poisson over at Creative COW has discovered that the recently released 6.0.2 update to Final Cut now allows you to capture from HDV directly to Apple's ProRes codec via Firewire.

This provides a means of getting rid of the awful HDV codec in one step, resulting in dramatically decreased render times, improved rendering quality of footage, and more latitude in color correction due to the 4:2:2 color space (as opposed to 4:2:0). Capturing to ProRes used to require a fast Intel Mac with an accelerated capture card, or AJA's Io HD. With the new update, you can now capture on a G5 Power Mac without any additional hardware, which very much levels the playing field.

As Chris explains, however, it is not quite a perfect solution just yet. It would appear that Apple has made some compromises (half raster import for example) in order to improve capture speed on slower machines. The preview window will also be considerably behind the actual footage being captured, making it difficult to monitor on-screen (an external broadcast monitor is always recommended, if you can afford it). But if you can live with these minor setbacks, you can capture to ProRes for a fraction of the previous hardware cost.

Before you rush to upgrade though, be aware that some people have been experiencing issues with the latest patch. As always, I would recommend not installing it in the middle of a production, and have a clone or backup of your working system before you upgrade.

Final Cut Pro and Quicktime 7.3 issues

A lot of people have been experiencing issues with the latest QuickTime version. The most common issue seems to be captures stopping after 10 minutes or so, leaving behind a ridiculously large file. Other people are finding incompatibilities in third party applications that use QuickTime.

The issue seems to stem from the fact that Software Update recommends the update because it is compatible with your operating system BUT it is not compatible with less-than-current versions of Final Cut Pro. So if you have version 4 or 5, you're out of luck, and it appears to be these users that are experiencing the issues.

What a lot of people don't realize is that Final Cut Pro depends heavily on QuickTime and so any QT updates will directly affect FCP. QuickTime is not just a "feature" of the operating system. It is also worth noting that the latest version of Final Cut, 6.0.2, requires QuickTime 7.3 and will not run well without it.

This is why you should never update a machine in the middle of a production. If you are not in the middle of a production, you should wait to see if other users have issues before installing the update. It is also best to have a cloned version of your hard disk so that you can get up and running again as quickly as possible. For the latter, I would recommend Carbon Copy Cloner.

I made a post the other day about downgrading from FCP 6.0.2 to 6.0.1.