Maintain, optimize and troubleshoot your NLE
Professional cloud workflow platform
Simplified media management

Workarounds for the QuickTime 7.4 rendering issues in After Effects

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.
Posted by Jon Chappell on Jan 24 2008 to QuickTime, Visual Effects, Apple
Permalink

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.
Posted by Jon Chappell on Jan 23 2008 to Apple, Final Cut Studio, QuickTime
Permalink

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.
Posted by Jon Chappell on Jan 18 2008 to Apple, QuickTime, Final Cut Studio
Permalink

QuickTime 7.4 causes issues with After Effects

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.
Posted by Jon Chappell on Jan 17 2008 to QuickTime, Apple, Visual Effects
Permalink

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.
Posted by Jon Chappell on Dec 23 2007 to Analysis, Final Cut Studio, QuickTime
Permalink