QuickTime Category: Digital Rebellion Blog

Aperture changes in Compressor 3.5

Sat, 24 Apr 2010 12:22:38 MDT

Have you noticed that movies compressed with Compressor 3.5 have a slightly different frame size when viewed in QuickTime Player?

Compressor 3.5 gives all QuickTime movies a Clean aperture by default (previous versions of Compressor set the aperture to None). This means that, although the actual frame size of the movie hasn't changed, when playing back, QuickTime scales and crops the movie to account for the non-square pixel aspect ratio of various video formats such as DV.

This has confused a lot of people because videos encoded with Compressor 3.5 are displayed differently to those encoded with Compressor 3.0. Although it is easy enough to change this within QuickTime Player, it needs to be done on a per-movie basis.

Luckily, Apple included an option in Compressor 3.5.2 (in the Pro Applications 2010-01 update) to switch this off. Just upgrade to Compressor 3.5.2 and deselect Add clean aperture information in the Encoder tab.

WWDC 2009 Summary

Mon, 08 Jun 2009 15:37:37 MDT

The WWDC Philnote ended a few minutes ago. If I were to sum it up in one sentence, it would be "one step forward, two steps back".

15" MacBook Pro

Apple announced a new 15" MacBook Pro with a built-in battery like its 17" sibling. This results in dramatically improved battery life, performance and reliability at the expense of a battery you cannot replace. To me this is not a problem at all but to some it will be a dealbreaker.

It also has an improved display with a 60% greater color gamut, allowing it to display a much greater range of colors. It's much faster, with up to a 3.06GHz Core 2 Duo CPU and up to 8GB of RAM, with a 500 GB hard disk or 256 GB SSD. It's also cheaper, starting at $1699 for the base model.

However, much like its previous notebook offerings, Apple gives with one hand and takes with the other. In a move that makes me question how in touch Apple is with its pro users, they have replaced the ExpressCard slot with an SD card slot. So that means no more native SxS support - you'll need to fork out for a USB adapter. And expect a drop in transfer speed over USB too.

Removing the ExpressCard slot drastically reduces the flexibility of the laptop. They've replaced a versatile port with one that has few uses (at least for video professionals). It also means we will not be able to connect eSATA devices or monitoring / conversion devices such as the Matrox MXO2 to MacBook Pros, drastically reducing their usefulness. This is a ridiculous decision for Apple to make on a device with "Pro" in the title.

Sure, you can get around this issue by buying a 17" MacBook Pro but I feel an ExpressCard slot should come as standard and not require you to buy a bigger, heavier and more expensive machine just for that feature.

Another aspect that is sure to irk ProApp users is the base model. Although it is good that Apple has reduced its price, it only features onboard graphics, unlike all the others which feature onboard and discrete graphics. This makes it unsuitable for applications like Motion and makes me question how future-proof this machine will be when Snow Leopard with OpenCL comes out. I think a machine with "Pro" in the title should be appropriately-specced to run Apple's professional applications.

13" MacBook Pro

Speaking of which, Apple rebranded the aluminum unibody MacBooks as the 13" MacBook Pro. Although the specifications are similar to the base 15" model and will therefore also result in limited ProApp usage and questionable OpenCL performance in Snow Leopard, I don't have a problem with that because this is something that was never there in the first place - this is not something Apple has taken away from us.

There's also some good news - Apple seems to have paid attention to the protests over the lack of FireWire ports in the previous generation and has now restored a single FireWire 800 port. The models are available up to 2.53 GHz with up to 8 GB RAM, an SD slot and a GeForce 9400M. The high-end 13" model is identical to the base 15" model in specification, which reiterates my opinion that the base 15" model is underpowered.

MacBook Air

Like the others, the MacBook Air has received a speed bump. It's also had a huge price cut and there is now only a few hundred dollars difference between the regular hard disk and SSD versions.

Snow Leopard

Apple demoed a few features but as the main changes were under the hood, these will probably be explored in more detail during the rest of the week.

Worthy of note:

Snow Leopard takes up around 6 GB less space than Leopard
"Fewer wait cursors"
Exposé is built into the dock - click and hold on a Dock icon and the app's windows will zoom out
Browser plugins are put in a separate process so that they do not crash the browser when they fail (it's unclear whether browsers other than Safari will be able to take advantage of this)
QuickTime X has been rebuilt from scratch, is hardware accelerated, has built-in ColorSync support and can stream data from any HTTP server (unfortunately more detailed information was not given)
QuickTime X has a minimal UI - it's very similar to QuickLook. Simple editing and uploading to popular video sharing sites built-in (essentially QuickTime Pro for free).
All system apps run in 64-bit
Grand Central allows developers to manage threads to make multi-threading more efficient

The biggest Snow Leopard announcement is that Snow Leopard will cost $129 retail like all the rest but only $29 if you are upgrading from Leopard. Yes, you read that correctly. It comes out in September, a month before Windows 7.

Safari 4

Safari 4 is out today and is available for download for Mac OS X 10.5.7. and Windows. This was one of my favorite announcements of the day - why? Because it makes Safari 4 the first shipping browser to pass Acid3 and support many new HTML5 web features.

One notable feature is video and audio tags. These allow you to play supported video and audio content directly in the browser without the need for Flash, Silverlight or other technologies. Plugins are always slower and more resource-hungry than native support for a particular feature, and open standards are always preferable. See this page for an HTML5 video that plays directly in your browser without Flash.

These changes have also made it across to MobileSafari, and it means Flash on the iPhone is even less likely than before (not a bad thing).

iPhone 3GS

It is a new iPhone but the name is very similar to the previous iPhone 3G, probably because no external differences were made to the phone or perhaps because it is still on the 3G network. It is considerably faster, features a 3MP digital camera, can record video, has a magnetometer (compass), 7.2Mbps HSDPA (faster 3G connection), voice operation, available in 16 and 32 GB on June 19th. The iPhone 3G has been reduced today to $99 and will continue to be sold once the new phone is out.

Tethering is not supported by AT&T and MMS will only work on the AT&T network at the end of summer (other networks do not have this handicap). Even Apple seemed fed up with AT&T's general incompetence, making frequent jokes at AT&T's expense.

One other notable feature is called Find My iPhone. Mobile Me users can log in and locate their lost iPhone on a map, send messages to it or make it emit a sound so that it can be located (even if it is on silent). If the phone has been stolen, you can remotely wipe your personal data from it. This is a pretty nice feature.

Final Cut Studio 3

This was missing in action, leading us to wonder when it will be released. Will it be released in conjunction with Snow Leopard - who knows? All I know is that Avid and Adobe CS4 have edged ahead and are looking mighty tempting, and Nuke is looking like a great replacement for Shake. When it comes to making your living, you can't wait around forever for software that you don't know anything about in terms of new features and may not even end up being released. You have to buy what you need when you need it - Apple needs to realize this.

So in conclusion, there's some great stuff there for consumers but professional users appear to have been sidelined once again.

QuickTime 7.6

Thu, 22 Jan 2009 05:37:24 MST

As I'm sure you are already aware, QuickTime 7.6 was released yesterday. Unlike a lot of recent releases that were provided solely for compatibility with new iTunes versions, this one has a lot of things that can benefit pro users.

First, let's look at the change list:

Video:

* Improves single-pass H.264 encoding quality
* Increases the playback reliability of Motion JPEG media

Audio:

* Improves AAC encoding fidelity
* Audio tracks from MPEG video files now export consistently

Almost all of the main features improve exporting, and so it only benefits Pro App users and people who purchased QuickTime Pro. Furthermore, they all improve quality and performance in one way or another.

But Apple never details every single change made in detail. Discrete Cosine discovered that QT 7.6 can now demux MPEG-1 audio, meaning you can convert an MPEG-1 file to another format and the resulting file will have both video and audio.

Meanwhile, on ProLost, Stu Maschwitz discovered that QT 7.6 fixes clipping issues on footage imported from the Canon 5D MK II. However, as he notes, this could drastically change the look of an existing project if you update in the middle of it.

So in all, this looks like a pretty good update for Pro App users. However, the update has only been out for a day which doesn't leave much scope for discovering potential problems. If you look at the ProLost link above, some commenters are already complaining about slow playback performance with some codecs.

The Golden Rules (TM) of Updating

As always, the Golden Rules (TM) apply:
1. Never update in the middle of a project.
2. Only update if this update fixes a problem you have been experiencing (i.e. don't install it if you don't use these codecs).
3. If you do decide to update, give it a couple of weeks for any significant issues to surface that would affect your workflow.
4. Make a clone or backup of your system drive before you install.

Here are the download links:
QuickTime 7.6 for Leopard
QuickTime 7.6 for Tiger

Important Update!
MacFixIt is reporting many problems with this update. It would seem Apple has made significant changes under the hood that are causing compatibility issues with everything from the Finder to third party codecs - even to video games. The MacFixIt page lists several workarounds.

My advice is to avoid this like the plague until Apple releases 7.6.1 or third party developers update their software to be compatible.

Perian 1.1.1 released

Tue, 30 Sep 2008 00:49:04 MDT

Perian, the free QuickTime codec pack, was just updated to v1.1.1. It allows you to play back more obscure media in QuickTime such as Flash FLV, DivX, 3ivx and MKV.

Changes:
* H.264 in AVI fixed
* Some anamorphic AVI files are now supported
* Performance problems due to PIC fixed with Xcode 3.1
* Incorrect frame skipping on H.264 intra frames fixed
* Better character set detection
* The update checker is now much more polite
* Several parsing and rendering bugs with subtitles fixed
* Player freezing while loading subtitles with embedded fonts fixed
* Audio fixed for some older MKV files with AAC/FLAC
* Strange values in MKV chapters or video sizes are handled better
* Initial support for SAMI subtitles added
* Worked around a QuickTime bug (#5770288) causing frames to be lost during export
* New codecs: DosBox ZMBV, VP6+Alpha, Nellymoser ASAO
* FFmpeg: Crashing on PPC G3 fixed
* Fraps decoding artifacts fixed

Perian can be downloaded for free from Perian.org.

[via TUAW]

QuickTime 7.5.5 released

Tue, 09 Sep 2008 18:22:20 MDT

Apple today released QuickTime 7.5.5 to coincide with iTunes 8, FrontRow and various other patches released today. The update is required for the latest iTunes update and also fixes vulnerabilities from maliciously-crafted movies and images. If you just use your machine for editing, this patch is not necessary. If you are likely to be using iTunes 8 or doing a lot of web surfing on your FCP machine (it's ideally best to avoid using your FCP machine for other purposes) I would advise waiting around for at least a week for any issues to surface.

As always, only update if it is absolutely necessary, NEVER update in the middle of a project unless there is a serious problem preventing you from completing the project, and always clone your disk before updating so that you have an exact copy of your original configuration to revert back to.

QuickTime 7.5.5 for Leopard
QuickTime 7.5.5 for Tiger

Apple releases ProRes codecs for non-FCP machines

Sat, 30 Aug 2008 09:53:56 MDT

A couple of days ago, Apple released Apple ProRes QuickTime Decoder 1.0 for Mac and Apple ProRes QuickTime Decoder 1.0 for Windows. This allows Windows users and Mac users without Final Cut Pro 6 installed on their machines to view ProRes-encoded files. This is great because in my experience, there are very few options when it comes to sending high-quality files to Windows machines and it should aid adoption of the ProRes format.

It should be noted, however, that you still need Final Cut Pro 6 in order to write ProRes files.

P.S. Sorry for the lack of updates but I haven't had internet access in about a month, which sucks big time.

QuickTime 7.5 released

Mon, 09 Jun 2008 23:54:29 MDT

"QuickTime 7.5 improves application compatibility and addresses security issues."

The timing suggests it is related to the recent iPhone announcements so I doubt this patch does much for ProApp users.

I have heard reports of crashes, choppiness and missing audio although of course your mileage may vary. It is always better to sit on updates for a while to check for problems before installing. I would not advise installing this one though because it probably won't offer ProApp users anything new.

And remember the Golden Rules - never update in the middle of a project and always have a clone.

Edit: This update points directly to the QuickTime site rather than a specific file on the server. This makes me think that Apple will no longer be keeping old versions around so make sure to back this up.

Why does QuickTime report a different resolution?

Sun, 13 Apr 2008 03:02:01 MDT

Ever wondered why QuickTime reports a completely different resolution to the one you exported at?

Welcome to the world of non-square pixels. NTSC and PAL use rectangular pixels to fill up space on the screen and save transmission bandwidth, which was more of an issue when the standards were invented. Computer monitors use square pixels and so QuickTime has to squeeze one side of the image in order to prevent it looking stretched. This is purely for display and the file is not modified.

The pixel aspect ratio of NTSC footage is 0.889 meaning 720 x 0.889 = 640 so it is displayed at 640x480. For PAL it is 1.067 so 720 x 1.067 = 768 and it is displayed at 768x576.

QuickTime also has some options for controlling how the movie is displayed. Open up your movie, go to Window > Show Movie Properties and click on the Presentation tab.

You will see an option marked "Conform aperture to:" with the following options:

Classic - Classic is identical to having the conform aperture setting switched off.

Clean - Scales the image to compensate for the pixel aspect ratio and crops it to mimic the overscan on a broadcast monitor.

Production - Scales the image to compensate for the pixel aspect ratio but does not crop the image.

Encoded Pixels - No modification is made to the footage. Note the stretching caused by non-square pixels.

This is one of the many reasons why a broadcast monitor is essential.

QuickTime 7.4.5 released

Thu, 03 Apr 2008 00:17:01 MDT

Apple just released QuickTime 7.4.5 to coincide with the release of iTunes 7.6.2 and Front Row 2.1.3. The coincidence of these releases suggests that the QT update specifically affects those applications and offers no specific benefits to Final Cut Studio. If you have a working system, DON'T install it!

On the other hand, if your system is not working, you have nothing to lose. I'd advise cloning your system beforehand though, as a non-working system could potentially be made even worse by this update.

Here are the links... use at your peril!
QuickTime 7.4.5 for Panther
QuickTime 7.4.5 for Tiger
QuickTime 7.4.5 for Leopard

I have also updated our list of QuickTime downloads.

Using Pacifist to downgrade QuickTime

Fri, 15 Feb 2008 10:00:27 MST

Since I often need to use this information for reference, I am posting a guide here. As you may already be aware, certain versions of QuickTime can cause havoc with Final Cut Pro and other professional applications like After Effects. For example, many users of FCP 4.5 HD have been unable to capture long clips after installing QuickTime 7.3 and up.

Apple does not offer a means of uninstalling a rogue version of QuickTime so the solution is rather "hacky". It will solve the problem but for best results, you are recommended to perform a full Erase and Install to reinstall Mac OS X.

Also, don't perform this process unless it is absolutely necessary.

1. Download Pacifist.

2. Check which version of QuickTime works best with your software.

3. Download the version of QuickTime you wish to downgrade to.

4. Start up Pacifist and drag the QuickTime package onto the Pacifist logo in the main window.

5. A new window will pop up. Use the disclosure triangles to select the following two directories:
System/Library/Components
System/Library/QuickTime

It might be worth backing up the existing /System/Library/Components and /System/Library/QuickTime directories on your hard disk before performing this.

6. Now click Install up the top.

7. You will get this message, click Install and then type in your admin password:

8. It will spend a minute or so extracting and verifying files then this message will appear:

Click "Don't ask again for this installation" and then hit Replace.

9. When it finishes, restart your machine. If you go to QuickTime Player, it will still say the version number of the old version but if you open Final Cut Pro, it will now work as it did previously.

Full credit for this tip goes to Fred Turner.

Edit 2/17/08: Fixed a couple of errors.

Update 11/16/08: Erik Smith sent me another solution to the issue, although I would definitely say try it at your own risk.

List of QuickTime downloads

Fri, 15 Feb 2008 09:12:28 MST

Are you looking for a non-current version of QuickTime to ensure compatibility with old software? Look no further.

QuickTime 7:
QuickTime 7.6 for Leopard
QuickTime 7.6 for Tiger
QuickTime 7.5.5 (Leopard)
QuickTime 7.5.5 (Tiger)
QuickTime 7.5 (Leopard)
QuickTime 7.5 (Tiger)
QuickTime 7.5 (Panther)
QuickTime 7.4.5 (Leopard)
QuickTime 7.4.5 (Tiger)
QuickTime 7.4.5 (Panther)
QuickTime 7.4.1 (Leopard)
QuickTime 7.4.1 (Tiger)
QuickTime 7.4.1 (Panther)
QuickTime 7.4 (Leopard)
QuickTime 7.4 (Tiger)
QuickTime 7.4 (Panther)
QuickTime 7.3.1 (Leopard)
QuickTime 7.3.1 (Tiger)
QuickTime 7.3.1 (Panther)
QuickTime 7.2
QuickTime 7.1.6

QuickTime 6:
QuickTime 6.5.3
QuickTime 6.5.2
QuickTime 6.5.2 reinstaller for QuickTime 7.0.1
QuickTime 6.4 reinstaller
QuickTime 6.3.1
QuickTime 6.3 reinstaller
QuickTime 6.0.3

QuickTime 5:
QuickTime 5.0.5

QuickTime 4:
QuickTime 4.1.2
QuickTime 4.0.3

Unfortunately Apple's site does not offer versions below 4, but I doubt many video editors out there are using a machine old enough to require QuickTime 3.

QuickTime 7.4.1

Wed, 06 Feb 2008 16:42:03 MST

Apple today released an update to QuickTime, to bring it up to version 7.4.1. This update "addresses security issues and improves compatibility with third-party applications".

The big question everyone is asking is: does it fix the dreaded After Effects 10 minute rendering bug? Initial testing would indicate yes.

As always, if it ain't broke, don't fix it. And definitely don't install it if you have a Final Cut Pro version lower than 6.0.2.

QuickTime 7.4.1 for Leopard
QuickTime 7.4.1 for Tiger
QuickTime 7.4.1 for Panther

Update: Macworld claims that an Apple spokesperson confirmed to them that this fixes the After Effects issue.

Update 2/7/08: Adobe confirms this.

Recommended QuickTime and Mac OS configurations for Final Cut Pro

Fri, 25 Jan 2008 08:15:29 MST

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

Workarounds for the QuickTime 7.4 rendering issues in After Effects

Thu, 24 Jan 2008 01:37:55 MST

I have heard claims that it is caused by DRM and I have heard claims that it is just a case of adjusting a preference.

The preference in question is the "Show legacy encoders" option. Unfortunately I can't test this out myself as I don't have the CS3 version of AE and I wouldn't really want to install QT 7.4 even if I did. However, people are reporting that adjusting this preference makes no difference. I would imagine that this is correct, as the option simply shows and hides encoders in the QuickTime menus.

This problem only affects sequences longer than 9:59 (I have also heard 9:57 but it doesn't make much difference) in length. If you are exporting sequences shorter than this, you will not be affected.

The bug only affects QuickTime exports. A workaround is to export to an image sequence (I recommend TIFFs). Final Cut Pro doesn't work well with image sequences and it will really slow down your timeline, so I recommend then converting the images to a movie in QuickTime.

To do this, fire up QuickTime and go to File > Open Image Sequence. Choose the first frame of the sequence and click Open. Select your desired frame rate and click Ok.

You now have two options: you can go to File > Save As and save it as a self-contained movie or the second option is to go to File > Export and choose an export format. The former will make no changes to the quality of the images and the second one will recompress it to a given format (such as DV). The latter option is recommended if you are placing it in a Final Cut Pro sequence, as it will not require rendering if you match the sequence settings.

This workaround can be applied to any application that is having difficulties with the latest QuickTime update.

Using QuickTime 7.4 with Final Cut Pro 6

Wed, 23 Jan 2008 11:46:57 MST

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.

Missing codecs in QuickTime 7.4

Fri, 18 Jan 2008 00:50:28 MST

[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.

QuickTime 7.4 causes issues with After Effects

Thu, 17 Jan 2008 10:07:15 MST

After some users found problems with QuickTime 7.3, some are reporting issues with 7.4 as well.

The QT 7.3 update broke non-current versions of Final Cut Pro, causing log and capture dropouts among other things. If you were hoping the latest update fixes the problems caused by the previous patch, I'm afraid you are out of luck. You will need to downgrade to QT 7.2.

Additionally, After Effects users are reporting that version 7.4 is causing rendering issues for them. They are finding that AE will stop rendering after exactly 10 minutes with the message "After Effects error: opening movie - you do not have permission to open this file (-54)". The only solution so far is to downgrade back to QT 7.2 or 7.3.1 or wait for Adobe or Apple to issue a patch. Windows users have been reporting these issues as well, and the issue seems to affect widespread versions of AE.

There is a post on Apple's support boards that gives a way of "hacking" QuickTime back to 7.2 by installing 7.3 or 7.4 and then copying over the old 7.2 files. This is a quick and dirty way of doing it but I would not advise it. Final Cut Pro is a professional and complex application and for best results, I recommend backing up your files and performing a complete Erase and Install. This creates the most stable environment for running the software. You do not want it to fail at an important moment, particularly if you make your living from using it. Remember not to reinstall QuickTime 7.4 again afterwards!

Always remember the Golden Rule: Don't install updates on a production machine unless you have a way of quickly getting everything back to normal (such as a clone), and DEFINITELY don't install anything in the middle of a project.

Update: Some After Effects users are coping by rendering out their sequences in 10 minute segments, putting them together in Final Cut Pro and then exporting them as one movie clip. Obviously this significantly increases the total rendering time and you should make allowances for the extra time burden.

Update #2: Apparently, this issue also affects Cinema 4D and is related to an update in QuickTime's Digital Rights Management (DRM) code. Presumably this is a conflict with code designed to prevent people from copying or distributing iTunes-rented movies.

Final Cut Pro and Quicktime 7.3 issues

Sun, 23 Dec 2007 02:48:35 MST

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.