Final Cut Studio Category: Digital Rebellion Blog

Speeding up Compressor

Sat, 17 Oct 2009 03:47:26 MDT

Is Compressor taking too long to encode? Here are some tips to speed it up.

Don't export directly to Compressor from Final Cut Pro

Although sending your timeline directly to Compressor may seem faster because it cuts out the step of exporting as a QuickTime movie, it is much slower overall because Compressor needs to request each frame one-by-one from Final Cut Pro instead of just reading the data out of the movie clip. It gets even slower if you're using Frame Controls or doing multi-pass encoding.

Just go to File > Export > QuickTime Movie (not QuickTime Conversion) and make sure Setting is set to Current Settings and Recompress All Frames is switched off. This ensures that the movie will not be recompressed unnecessarily.

Here's a tip - if most of your timeline is already rendered, deselect Make Movie Self-Contained. This creates a small reference movie that links to the render files on disk instead of writing the data into the file. This will be much quicker to export. If your timeline is not rendered, however, this setting is unlikely to offer any speed advantages over a self-contained movie.

Once the file is exported, drag it into Compressor and set up your batch as normal.

Only use Frame Controls where necessary

Frame Controls allow you to improve the quality of resizing, retiming and deinterlacing operations, however they should only be switched on when you are actually performing one of these operations.

In addition, you should use Better quality instead of Best, as Best is usually reserved for extreme circumstances and in most situations gives you a massive performance hit with no benefit.

Perform heaving-lifting in a separate pass to the encoding

Using Frame Controls with a multi-pass or long-GOP encoder can really slow things down because the Frame Controls processing will need to be reapplied to every frame each time it is read. Even if you're not using Frame Controls, compressing from a processor-intensive codec such as HDV or H.264 can seriously slow things down.

It makes sense, therefore, to perform all these processor-intensive operations on an intermediate movie clip (ProRes would be a suitable codec for this) and then drag in the intermediate clip and encode it to the desired format.

But there is an easier way. Job chaining is a little-used yet very powerful feature of Compressor that allows you to plug the output of one job into the input of another for additional processing.

Here's how to do it:
1. Drag your movie clip into Compressor.
2. Drag either the ProRes 422 for Interlaced Material or ProRes 422 for Progressive Material (depending on your source media) setting onto the job in the batch window.
3. Go to Job > New Job with Target Output. This will add a new job to the batch with a chain symbol to show it is linked to the job above it.
4. Drag your desired output setting onto the chained job and set up the destination as normal.
5. Submit the batch

Use a cluster

A cluster is a group of computers where each machine processes a portion of the movie simultaneously, potentially providing a massive speed boost. This service is provided by Qmaster and can be set up in the Qmaster section of System Preferences or the Apple Qadministrator utility.

You will need Qmaster set up on each computer in the cluster, and all computers should have the required codecs installed and have full access to the source media and cluster storage area.

If you have a multi-core computer, Qmaster can emulate the effects of a cluster by launching multiple copies of Compressor side-by-side to process the movie in a "virtual cluster". This can make a dramatic difference to encoding times. I wrote a tutorial on this a while back.

Conclusion

Compressor is not the fastest encoder in the world but with these tricks you can make it a lot more bearable. One important trend to note is that the simplest method isn't always the fastest - with a little extra setup beforehand you can save a significant amount of time overall.

FCPUG Amsterdam Supermeet 9-13-2009

Wed, 02 Sep 2009 01:32:29 MDT

If you're in Europe (or willing to travel), there is an FCPUG Supermeet in Amsterdam on Sunday 13th September.

As always, there's a lot of interesting stuff going on including:

Final Cut Pro co-creator Michael Wohl shows off FCP 7

Simon Walker shows how to do a Color grade in 10 mins

Jason Levine from Adobe shows how to integrate FCP and Adobe CS4 workflows

26 vendors will be showcasing their wares

The World Famous Raffle with over 43,000 Euros worth of prizes

Tickets are a steal at 15 Euros (around $20) or 10.50 Euros for students with valid ID. Doors open at 17:00 with the FCP Showcase, where attendees can meet third-party vendors and developers, and the main Supermeet lasts from 19:00-23:30.

It's being held at The Grand Hotel Krasnapolsky in Dam Square in the Netherlands. This
event is expected to be the largest gathering of Final Cut Studio users, Gurus and Digital Filmmakers in Europe during the annual IBC trade show. These shows are always well worth attending.

More details are here.

Why don't my old Preference Manager backups work on FCP 7?

Wed, 12 Aug 2009 16:40:42 MDT

One question we've been seeing a lot lately is from people who are wondering why the Preference Manager backups they previously created under Final Cut Pro 6 no longer work on Final Cut Pro 7.

There is a very simple reason for this - Final Cut Pro's main preference file is called Final Cut Pro x.0 Prefs.fcset, where x is the major version of the software. So when you updated to version 7, it created a new file called Final Cut Pro 7.0 Prefs.fcset and ignored all previous files.

So when you try to restore a backup created under Final Cut Pro 6, it will transfer the Final Cut Pro 6.0 Prefs.fcset file which will be ignored by the newer version, thereby having no apparent effect. You could just rename the file but there may well be side-effects to doing this. The solution, therefore, is to recreate your Preference Manager backups under Final Cut Pro 7.

(Incidentally, I've heard a lot of people complain about scratch disk locations resetting and favorites being lost upon upgrading. FCP 7 does not read the old preferences when creating the new file so your preferences are completely reset.)

How to run Final Cut Studio 3 on a MacBook

Wed, 12 Aug 2009 16:30:30 MDT

I've been meaning to post this for a while but haven't had the chance until now. I had to be an early adopter of Final Cut Studio 3 because I develop software that interfaces with it, but I had no desire to edit on a x.0 release so I decided to install it on my MacBook solely for testing.

The only problem is that, unlike FCS 2, the FCS 3 installer refuses to continue because it requires a 128 MB graphics card. Only Motion and Color are heavy on the graphics card, so the other applications in the suite will work just fine on a lesser machine. Luckily the block is easy to work around.

Here's how I got it working on my MacBook:

1. You will need to change one of the files on the DVD. As you cannot write directly to the DVD itself, you will need to create a writable copy of the disc. Put in the Final Cut Studio DVD and open up Disk Utility (located in /Applications/Utilities).

2. Select the disc in the left-hand pane and click New Image in the toolbar.

3. Set Image Format to Read/write and Encryption to None.

4. Type a relevant filename and click Save. It will take several minutes to process.

5. Open up the disk image and ctrl-click on Install Final Cut Studio. Select Show Original.

6. A new window will appear with the FinalCutStudio.mpkg file selected. Ctrl-click on this file and select Show Package Contents.

7. Navigate to Contents/Resources and ctrl-click on the Requirements Checker bundle. Select Show Package Contents.

8. Navigate to Contents/Resources and open up minsys.plist in Property List Editor (if you have the Apple developer tools installed) or TextEdit.

9. Under the heading AELMinimumVRAM change the number from 128 to a number lower than or equal to your current video memory. I changed mine to 32. Alternatively you could change block to warn and the installer will warn you but let you continue installation.

10. Save the file, close all the folders that appeared and double-click Install Final Cut Studio on the disk image. You should now be able to install Final Cut Studio without problems.

Some of the applications in the studio also contain a minsys.plist file that will need to be modified. These applications are Final Cut Pro, Motion, Color, Soundtrack Pro and DVD Studio Pro (even though the latter apparently has no changes from FCS 2).

11. Ctrl-click on the application in question and select Show Package Contents.

12. Navigate to Contents/Resources and open minsys.plist in either Property List Editor (if you have the developer tools installed) or TextEdit.

13. Under the heading AELMinimumVRAM change the number from 128 to a number lower than or equal to your current video memory. I changed mine to 32. Alternatively you could change block to warn.

14. Color will still warn you about your screen resolution - however you can just select Never show again and continue.

That's it! You will need to repeat steps 11-14 whenever you update Final Cut Studio.

Note: Some people have suggested simply removing the Requirements Checker application but I do not advocate deleting files.

My thoughts on the new Final Cut Studio

Fri, 24 Jul 2009 09:54:23 MDT

Wow, I go away for a couple of days and Apple has a brand new version of FCS waiting for me when I get back (although I do think the fact that it is simply called Final Cut Studio and not Final Cut Studio 3 will cause confusion).

Here are my first impressions:

Architecture

This is Leopard and Intel-only, which is a little surprising because there's only a couple of months until Snow Leopard comes out, and I think many of us thought a Snow Leopard-only release in September was likely. There is no word on whether or not it takes advantage of the new features of Snow Leopard such as Grand Central Dispatch or OpenCL, nor any indication that Final Cut Pro has been rewritten in Cocoa as has been so often speculated. I noticed a lot of the screenshots in Apple's examples were taken in Tiger, suggesting that perhaps the feature list was set long before Snow Leopard was announced.

Apple claims that Final Cut Studio will not work on a device with integrated graphics - such as a MacBook or Mac Mini. However, they also say that ProRes 422 Proxy is designed for editing on a MacBook or MacBook Pro, so it would appear that Final Cut Pro can at least be used on a machine with integrated graphics, if not some of the other apps in the suite.

It's also worth noting that the minor applications in the suite only received minor updates, as indicated by their version numbers. So it is likely that the problems with Compressor have not gone away.

Blu-ray

Blu-ray burning directly in Compressor - I certainly didn't expect this. And integrating it into Compressor is significant too. Although I never really thought about it before, the majority of the DVDs I make in DVDSP are rough cuts for client approval that don't need a fancy custom menu and I never make use of any of the advanced features like scripting. I would imagine many people are in the same boat and therefore burning a basic disc in Compressor is a much faster and more efficient way to work.

It is telling though, that DVD Studio Pro did not receive a significant update for the second time running. We have been using essentially the same version for the past three years (an eternity in the technology world), and it suggests that Apple may perhaps discontinue this product in the future.

More ProRes options

Don't underestimate the importance of this. ProRes 4444 (the extra 4 refers to the alpha channel) allows you to convert footage shot with a high-end 4:4:4 camera to ProRes without sacrificing color information. With previous versions of Final Cut Studio, you would have had to leave it uncompressed (using up significantly more disk space and bandwidth), use Animation (slow) or explore a third-party codec.

The mastering possibilities are interesting too. HDCAM SR has long been the industry choice for HD mastering but it is expensive. Using ProRes 4444, you could create an HD master of equivalent quality to HDCAM SR but on a significantly cheaper LTO tape (LTO drives cost less than 1/10th of the cost of an HDCAM SR deck). LTO is the standard for data backup / archiving in the IT world and offers a number of other benefits such as potentially faster-than-realtime writing and also being format, frame size and frame rate agnostic. Of course, the receiver would have to have an LTO deck and necessary equipment.

LiveType discontinued

LiveType has long been superseded by Motion so it was only a matter of time before it was canned. In Motion 4 you can now adjust individual letters in a text object, meaning the one advantage LiveType had over Motion has now disappeared and consequently, LiveType has been discontinued. It was inevitable really.

Avid-like features

There are some nice new features to emulate Avid functionality, such as the new floating timecode display, global transitions and the ability to automatically import clips just by plugging in a drive. This is the benefit of competition.

Faster, better quality

I am a big fan of anything that makes things faster and/or improves video or audio quality. Background rendering and exporting is a huge feature and arguably should have been in Final Cut Pro 6 because they'd already laid the foundations with background SmoothCam processing.

Soundtrack Pro has a significantly redesigned architecture which improves performance and will hopefully address some of the issues I have experienced, such as working for a while on a project and then suddenly not being able to save it. It also features improved audio cleanup tools.

Faster frame control processing in Compressor gets my vote too.

RED support

The RED post workflow has always had issues and Apple has clearly developed the new Color and Cinema Tools with RED in mind. The main stumbling block in the RED workflow seems to be conforming the R3Ds once the offline edit is complete, and some third-party solutions have been created in an attempt to address this.

Now you can maintain the relationship between your original RED camera footage and your editing proxies inside a Cinema Tools database (hopefully CT creates and links the proxies automatically). You edit the proxies, export to Color and grade the original R3Ds using the data from the database to conform. This greatly simplifies things, although some would argue that native REDCODE support in the FCP timeline would be even better - perhaps when RED Rocket comes out?

Color also now supports 4K - although Apple will still be behind if the 6K Scarlet comes out this year as predicted.

Media Management

One thing people haven't commented much on is the improved media management, which has been the bane of every Final Cut Pro user at one point or another. Spotlight in Mac OS X indexes the files on your hard disk in a database and Final Cut Pro 7 uses that data to quickly reconnect the files, as opposed to querying them directly.

What this means is that FCP can reconnect files faster (so projects will presumably load a lot quicker) and hopefully be more intelligent when a file changes.

Missed opportunities

No ScriptSync (Avid) / Speech-to-Text (Premiere) - There is no way of syncing dialogue up to a script or automatically converting it to text. This means that, unless you have an assistant to transcribe it for you, you have to search through a load of footage in order to find the line of dialogue or the soundbite you are looking for.

No XML project files - Please Apple, this would make it far, far easier to seamlessly integrate Final Cut Pro with other applications.

No word on Phenomenon - Contrary to speculation, the Shake replacement codenamed Phenomenon was not included in Final Cut Studio or bundled into Motion, which begs the question of whether it will ever arrive.

Final Thoughts

There's some good stuff here - Apple has (eventually) listened to a lot of our complaints about media management, exports typing up the application, etc. But how well these work in reality will remain to be seen. I won't get my copy until next week.

But maybe it's not called Final Cut Studio 3 because there's not really anything there to justify calling it that. Although Final Cut Studio 2 also had few major features, it did at least come with a brand new application that used to cost $20k (Color). I think the new price cut reflects Apple's recognition that selling the upgrade at $499 would perhaps not be value for money, meaning future updates may not necessarily be as cheap.

Interesting Links

Official Final Cut Studio page
Fully-indexed online Final Cut Pro manual
Final Cut Studio in Depth - 66 page document from Apple detailing all the changes
Apple ProRes white paper
Apple KB: Installing content when upgrading
MacWorld review by Mike Curtis
How to Install Final Cut Studio 3
Norman Hollyn's take
In-depth review by Jan Ozer
Mike Jones compares Final Cut Pro 7 to his wishlist
Installing Final Cut Pro 6 and 7 side-by-side
Changes in FCP 7.0 XML - for developers
Studio Daily summary
More links from xlr8yourmac.com

Final Cut Pro 6.0.6 released

Tue, 23 Jun 2009 15:10:33 MDT

Apple today released Final Cut Pro 6.0.6.

The release notes name only one fix:

Improved Real-Time Playback on Certain Mac Pro and Xserve Models
Final Cut Pro 6.0.6 improves real-time playback capabilities with Mac Pro (Early 2009) models and Xserve (Early 2009) models when working with complex sequences or high-bandwidth media formats.

There are no new features, but I wasn't actually expecting any - in fact, I wasn't expecting an FCP 6.0.6 update at all. I guess this was an urgent fix.

Of course, this new update will raise questions about Final Cut Studio 3 but I am confident that it is in development. Apple's ProApp developers on the pro-apps-dev mailing list are very much alive and well, and frequently ask third-party developers what features they would like to see in future versions. Some kind of official acknowledgment and a tentative release schedule from Apple would be nice though.

The usual guidelines apply - don't update in the middle of a project, don't update for several weeks so that potential bugs and issues have a chance to show themselves, don't update if you don't need the features in this patch (it only applies to 2009 models), and make sure to clone your drive before you update.

Sign the DVD Studio Pro Blu-ray petition

Fri, 05 Jun 2009 02:24:37 MDT

AppleInsider recently had an article listing the version numbers of the applications in Final Cut Studio 3.

Although it's just a series of numbers, it is a useful indicator of just how much the applications have been updated. The most notable numbers are Color 1.5, Compressor 3.5 - indicating relatively minor changes - and DVD Studio Pro 4.2.2 - indicating virtually no changes at all.

So for those of you hoping for a major DVD Studio Pro update that supports Blu-ray burning, it looks like you're going to be disappointed once again.

There is now a petition circulating that asks Apple to reconsider its policy.

"We, the undersigned, will not buy a new version of Final Cut Studio if it is still lacking Blu-ray support."

Be sure to add your signature if you agree.

Compressor error - "You must enter a name for this batch submission"

Sun, 03 May 2009 02:31:35 MDT

Sometimes when you submit a batch, you may get the error:
"You must enter a name for this batch submission. This is the name that identifies this submission in the Batch Monitor and History window."

This error pops up when you drag items into the batch window in the wrong order. You must drag the clip in first and then drag in the settings and destinations.

There really shouldn't be a specific order for doing this but unfortunately Compressor can be very illogical at times.

Incoming network connection dialogs keep appearing

Sun, 19 Apr 2009 07:25:23 MDT

Amazingly for an OS that markets itself as secure, the firewall in OS X is not switched on by default. So if you switch it to the recommended mode, "Set access for specific services and applications", OS X will prompt you to allow or deny incoming connections.

But sometimes that dialog will not go away! Certain applications such as QmasterStatusMenu.app and Batch Monitor.app cause the dialog to pop up every 5 seconds (or every 20 seconds if you ignore it) which gets annoying very quickly.

The reason for this is that applications like QmasterStatusMenu.app and Batch Monitor.app don't communicate on the same port each time. It is constantly changing, as this log excerpt shows:

This really confuses the very basic OS X firewall.

Some people have recommended switching the firewall off but I wouldn't recommend this. There's always a trade-off between security and convenience, but this trade-off is far too big. Instead, it is much better to just obtain a more advanced firewall.

I would recommend Little Snitch for this job. It gives you infinitely more options than the default firewall, lets you see where apps are sending data, doesn't bug you too often, and most importantly, it copes with applications that constantly change ports so those annoying 5-second popups go away.

The demo gives you full functionality for 3 hours, after which you just restart the firewall again. That's a lot better than popups every 5 seconds, but if 3 hours is too often, you can buy a single license for $29.99.

Just install Little Snitch, restart the computer and switch the default OS X firewall to "Allow all incoming connections". Little Snitch then takes over - you can now use Qmaster and be safe at the same time.

3-31-09 New AppleCare articles

Tue, 31 Mar 2009 14:51:16 MDT

Here is my roundup of recent useful AppleCare docs.

Guide to Final Cut Pro Internal Tools

Wed, 11 Mar 2009 16:48:09 MDT

Did you know Final Cut Pro has a hidden menu? Just hold down Cmd + Option + Shift and click the Tools menu. You should now see a new menu item called Internal Tools.

This is a debug menu used by the developers of FCP, but it actually has some uses for us mere mortals as well. It's especially useful for plugin developers and system troubleshooters, but some features benefit all users. Here is a rundown of what's in the menu.

Adjust Windows

When you open the Audio Mixer, Frame Viewer and several other tools in the Tools menu, they open in a tabbed window called the Toolbench. This normally appears on top of the Viewer and is hidden behind it when you select the Viewer again.

The Adjust Windows menu item adjusts the window layout so the Toolbench can fit in without being obscured by other windows. If you don't have the Toolbench open when you click this item, it will leave a gap in your window layout.

Before

After

To restore the default window configuration again, press Ctrl+U.

App / Perf Info

This generates a text file containing just about everything you could ever wish to know about your FCP configuration.

Probably the most useful part is the Project / Sequence Information section. This gives various statistics about your project including the total number of clips placed in your timeline and the proportion of those clips that were unique. It will even tell you how many edits you performed per minute (don't let your boss see this!).

Log OpenGL Profile Costs

This function displays timing information about OpenGL Profiling in the Console. It will do nothing until you start profiling (see the Statistics section below), at which point it tells you how long (in ms) it took your machine to process the given frame sizes and codecs.

One thing I noticed about this is that it takes a fair while for the data to be posted to the Console - around 1-2 minutes.

Log VM Footprint

This outputs the current memory usage to the Console.

Resident refers to data in physical memory, Virtual refers to data on the disk ready to be copied into main memory as required. Note that the system often assigns more virtual memory space than it needs, so not all of that space will actually be used. So if you see a ridiculous number like 4 GB, it is not necessarily a cause for alarm.

Movie Dumpster

This one crashes Final Cut Pro for me, so I wasn't able to ascertain exactly what it does. However, Apple offers a tool called Dumpster on their developer site which gives you a large amount of technical information about a specific movie clip. I would imagine this would be similar if it worked.

Playback Meter

This will show you how your media drives are performing, and is probably the most useful tool in the menu.

If you are not using a RAID, only the audio bars will work. Everything is fine while the bar is green, but if it turns yellow or red, this is an indication that your computer cannot keep up.

Screen Size Override

This allows you to fool Final Cut Pro into thinking that you have a different-sized monitor.

Just select the desired resolution from the pull down menus and press Ctrl + U to automatically resize the windows to the new dimensions.

If you mess things up, just restart Final Cut Pro and press Ctrl + U to restore the windows to the correct position for your screen resolution.

Statistics

This displays a lot of technical information about what's going on under the hood of FCP.

For instance, select the Render check box, drag the playhead across the timeline and then click the Average button. This will average the times taken to perform the various function calls required to render the image to the screen. If your system is getting sluggish, you may find it useful to use the Averages function to see which areas are taking a long time to process.

Most of the checkboxes are self-explanatory so I won't elaborate on them here. However, I would advise selecting them one at a time otherwise you'll end up with an overflow of information.

If you want to clear the text box, click Reset. Copy copies the entire data to the clipboard and Copy Avg copies only the averages. Unset All deselects all of the checkboxes.

Both Auto Profile and RT Verify go through each item in the Browser (video clips, sequences, images, etc), playing each one four times and averaging the data. Sequences take longer because the profiler initially tests with only the V1 track enabled, and then gradually enables V2 and V3 to perform compositing tests (if such tracks exist of course).

It's worth mentioning that since it goes through everything four times, it will take a while to finish processing, depending on the size of the project. You cannot switch to another application either or the profiling will fail. I would advise creating a brand new project with short media clips and sequences. If you truly have serious bottlenecking, this will still be apparent in the shorter sequence.

All the timing information is stored inside the Profile.csv log. Although you can view this in TextEdit, it will be difficult to read because it will not be formatted correctly. A spreadsheet application, such as MS Excel or the free NeoOffice or OpenOffice packages, is recommended.

If you are experiencing poor performance, look at the timings in this file to see where the major bottlenecks are. For instance, a slow FXScript filter could be indicative of a CPU bottleneck or an inefficient script. A slow Flop operation could be indicative of a GPU bottleneck.

Auto Profile and RT Verify appear, on the surface, to perform exactly the same task. However, it is likely that Auto Profiling actually updates your RT information whereas RT Verify merely performs the test without changing anything. This is difficult to verify without official documentation though.

Most of the functions in the Internal Tools menu will be too technical for a lot of users, and so the menu will likely remain something of a novelty. But if you are troubleshooting performance issues or developing applications and plugins for FCP, it is an invaluable source of information on the inner workings of Final Cut Pro.

The only downside is that the menu must be reactivated every time you start Final Cut Pro. If anyone knows of a way to enable it permanently through a preference file, I'd love to hear about it.

Compressor error: "Unable to connect to background process"

Sat, 14 Feb 2009 12:03:41 MST

The "Unable to connect to background process" and "Unable to submit to queue" messages are common errors that unfortunately have many causes.

Before you do anything else, check that your version of Compressor is compatible with your operating system. Only the versions included with FCP 5.1.x and 6.0.x are compatible with OS X 10.5. If you have an incompatible earlier version, you will need to either upgrade Final Cut Studio or downgrade your operating system.

Try the following steps:

1. In Compressor, go to Compressor > Reset Background Processing.

2. Run Compressor Repair.

3. Trash Compressor preferences (can also be done in Compressor Repair).

4. Try these steps (use at your own risk).

Do the following if nothing else works:

5. Disable your internet / network connections.

6. Reinstall Compressor and Qmaster.

7. Perform a full erase and install of the operating system and reinstall from scratch.

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.

Why does my DVD audio level differ from the level in FCP?

Thu, 01 Jan 2009 07:29:35 MST

Have you noticed a discrepancy between the audio in your Final Cut Pro timeline and the audio of the finished DVD when using Compressor's DVD presets?

That's because the Dolby Digital 2.0 audio preset in Compressor has several functions to improve unsuitable audio, but if you have already mixed your audio they might do more harm than good in some cases. Rather than just telling you which settings to use, I'm first going to explain what these functions are designed to do because there are a lot of misconceptions about them.

Compression alters your dynamic range (the difference between the loudest and quietest sounds in a soundtrack) by compressing the level of sounds to fit within a certain range. The loudest sound in a Dolby soundtrack can be 105dB. Considering the fact that prolonged exposure to 90 dB audio can result in hearing loss, most people do not play their audio at 105dB. When you set up a Dolby decoder with a reference tone, you are telling it the volume level it should play 105dB audio at. So if this is lower than 105dB (which is likely), you will lose some of the very quiet sounds on the soundtrack. The compression presets allow you to regain these sounds by sacrificing some dynamic range in the process.

It is set to Film Standard by default but if you have already performed a mix with a moderate dynamic range, further compression is not likely to be necessary and so it is worthwhile to switch this to None.

Dialog normalization is a feature on several Dolby decoders that ensures all content plays back at the same level. The listener sets their preferred playback level and the dialogue in every DVD and TV show plays back at the same level, meaning you don't need to keep reaching for the remote in order to adjust the volume. Contrary to popular belief, it only adjusts the overall volume level when the source changes (i.e. when you begin playing the DVD or when a new TV program begins) so dynamic range is preserved throughout the movie. It does not dynamically adjust the volume as the movie is playing.

The normalization value indicates the difference between the overall level of dialog and the maximum audio peak of 0 dBFS. The default is set to -27 dBFS, which is the established level for film soundtracks. It is also the level most decoders are set to by default. If you have your decoder set to -27 dBFS and then, for example, try to play a -25 dBFS movie, the decoder will lower the overall volume by 2 dBFS so that the general dialogue level remains the same. If you do want to switch it off when compressing your audio files (if you've already leveled your sound mix for example), set it to -31 dbFS.

So if you would like your audio to be exactly how it was in Final Cut Pro, set Dialog Normalization to -31 dBFS and set Compression in the Pre-Processing tab to None. However, these functions do serve useful purposes for the end user and it is worthwhile to bear their needs in mind.

What does 2009 hold for Final Cut Studio?

Wed, 31 Dec 2008 13:50:50 MST

Now, 2008 has been a year of frustration for us editors. We've seen few Final Cut Studio updates (and some of those have broken more things than they fixed), we've seen matte displays replaced with glossy ones, we've seen no Apple at NAB 2008 and we've seen very little in the way of Mac Pro updates.

Has Apple abandoned pro users? Are they more interested in making iPods? Yes and no. Yes, of course, they will want to put a lot of resources into something that contributes strongly to their bottom line. However, I don't believe they have abandoned pro users at all.

Everything changes with Snow Leopard. Snow Leopard is Apple's way of telling us it still cares. Look at the feature list - Grand Central, OpenCL, QuickTime X, even the 2.2 gamma change - is there anything there that will benefit the average Joe Bloggs user when he's checking his email? No, this is a lean operating system designed for performance. And it's also designed to sell Mac Pros of course, and make the 8-core Mac Pro you bought a year ago worthwhile. This is an operating system designed to put the Mac back on top of the list of pro must-haves. Apple has a massive head-start on Microsoft here.

And what better way to promote Snow Leopard and the Mac than with a highly-optimized version of its flagship pro suite, Final Cut Studio.

I don't think Apple is abandoning us at all. I think they are just diverting their pro app resources into something much better. Think how the number of patches and the number of fixes has dwindled lately. Updates are rare and they only fix major issues. It makes sense that Apple would only put resources into fixing major bugs if Final Cut Studio 2 was at the end of its life.

Another thing I find interesting is that Apple is putting Shake updates in Pro Applications Updates but it is not putting Logic or Aperture updates in there. This would suggest that there may have been a merging of the Shake and Final Cut Studio teams.

And let's look back at the original launch of Final Cut Studio 2. If you remove Color from the equation, there's really not much there. Worth upgrading, sure, but no big architectural changes like FCP 4.0 to 4.5 or 4.5 to 5.0. Could it have been a version designed to tide us over until the big changes came along? Only Apple knows the answer to that question.

So here are my predictions:

1. Final Cut Studio 3 launches in 2009 to coincide with the release of Snow Leopard. I don't know how backwards-compatible it will be, it could well be Snow Leopard-only (which also means Intel-only). It will be largely rewritten to take advantage of new Snow Leopard features and hardware acceleration.

2. LiveType will be killed off and its features will merge into Motion. Motion will inherit some of the features of Shake. This will better position it to compete with After Effects. It remains to be seen whether Apple will keep the node-based interface from Shake or spin it off as a separate application. I don't think Apple will completely merge the two together as they have different target markets and different complexity levels.

3. There will be greater interoperability between Final Cut Studio applications. Color will be redesigned to better fit into the studio. Interfaces will be improved so that there is greater coherence between applications.

4. Media management will be redesigned and there will be tighter integration with Final Cut Server.

5. The current NLE fashion is to have an automatic transcription tool. I would imagine Apple would implement this too, as it has great potential, even with the inevitable inaccuracies. Imagine this with Final Cut Server - you could easily search for that elusive line of dialogue within hundreds or even thousands of media files.

Ok, some of these are predictions, some of these are wishful thinking. But I believe Apple will at least optimize FCS3 for Snow Leopard technologies, because Snow Leopard is pointless if software isn't written to support it. At the end of the day, performance is what matters most.

Other features that may not come but I'd like to see anyway:

1. Why do we have to keep exporting to XML? Why not just make the FCP project file XML?

2. Add scripting abilities to the applications in the Studio and improve their expandability. Apple can't possibly think of everything - let third party developers fill in the gaps. It might also win over some larger companies who will be able to integrate it with their other applications and databases.

3. Blu-ray - Who even knows? It might interfere with Apple's iTunes business model but either way, BD support in Adobe Encore is proving that there is a demand for it and it is possible to provide it in an authoring application despite the draconian licensing issues.

Roll on 2009!

Pro Applications Update 2008-05 is out

Wed, 17 Dec 2008 11:44:35 MST

Apple just released Pro Applications Update 2008-05. This is identical to Pro Applications Update 2008-04 except it now comes with Color 1.0.4.

The news is still hot off the press so Apple haven't gotten around to updating their release notes at this point in time, however, given the timing and the fact that only one application was modified, it is safe to say that this patch was released solely to fix the dreaded XDCAM bugs in Color 1.0.3.

If you are currently running 1.0.3 and suffering from the XDCAM bug I would advise updating to this version. If not, the Golden Rules (TM) apply as usual:
* Never update in the middle of a project.
* Don't update if you don't actually need any of the features included in the update.
* Always clone or backup your system beforehand.
* Wait for at least a week to see if there are any reported problems with the patch.
* Wait even longer if you're using third party hardware or plugins e.g. the AJA Kona card or FXFactory plugins.

Update: Changelog is now up:

XDCAM Clip Relinking Is Fixed
XDCAM EX, HD, and 422 clips now relink properly.

ISO Changes in the RED Tab Appear Correctly
Instances where the Color UI did not accurately reflect changes made to the ISO parameter in the RED tab of the Primary In room have been fixed.

Improvements to the Blur Node in the Color FX Room
Adjusting the spread parameter of the Blur node no longer causes the clip to scale up.

Possible solution to Color 1.0.3 XDCAM issues

Sun, 14 Dec 2008 02:26:08 MST

As reported earlier, the new Color 1.0.3 patch cannot seem to recognize XDCAM footage, reporting it as offline. Matt Bucy on the Apple discussions board seems to have come up with a potential fix though. It would appear that the problem is with the XDCAM codec that Sony's capture utility uses, and the problem goes away if you re-encode the video with Apple's flavor of the codec.

Matt recommends going to File > Media Manager and selecting Copy referenced media. You could also export to a QuickTime or put the files through Compressor (the latter being the least recommended option due to recompression taking place).

Let me know how well this works for you. Hopefully Apple will fix this soon.

Solving missing framework errors in Final Cut Studio

Fri, 12 Dec 2008 02:39:37 MST

If one of your Final Cut Studio applications crashes the minute you open it, chances are it's down to missing frameworks. If you click the Report button on the crash dialog, it will tell you the reason. Alternatively you can fire up the Console in /Applications/Utilities to see the message.

You'll probably see a message like this:

Dyld Error Message:
Library not loaded: /System/Library/PrivateFrameworks/BrowserKit.framework/Versions/A/BrowserKit
Referenced from: /Applications/Soundtrack Pro.app/Contents/MacOS/Soundtrack Pro
Reason: image not found

Here's how to copy that file back:

1. Firstly, if you have another machine running Final Cut Studio, it's much easier to take the file from that machine (in this case /System/Library/PrivateFrameworks/BrowserKit.framework) and copy it to the same location on the current machine.

2. If you don't have that luxury, you will need to extract it from your installation DVD. Put the disc in the drive and open up the Terminal in /Applications/Utilities.

3. Type the following:

cd /System/Library/PrivateFrameworks
sudo gunzip -c '/Volumes/Final Cut Studio/Installer/Packages/ProAppRuntime.pkg/Contents/Resources/ProAppRuntime.pax.gz' | pax -r -s ',./System/Library/PrivateFrameworks/,./,' './System/Library/PrivateFrameworks/BrowserKit.framework'

Press enter after typing cd /System/Library/PrivateFrameworks, then paste the next part as one whole line. After typing the sudo gunzip... line you may be prompted for your password.

If you are using Logic Studio, substitute Logic Studio for Final Cut Studio. If you are missing a different file, replace BrowserKit.framework with the other file's name (ProKit.framework is another common missing file).

4. If this doesn't work, replace the cd /System/Library/PrivateFrameworks line above with:

cd ~/Desktop

Then copy the same sudo gunzip... command from above. This will copy the file to your desktop. In the Finder, browse to /System/Library/PrivateFrameworks and copy the file from your desktop to that folder. You may be prompted for your password.

5. If problems still persist after copying the file, it is likely that Final Cut Studio is expecting a later version of the framework than the one on the DVD. The only solution in this case is to copy it from a machine running the same version of Final Cut Studio as you, or to uninstall Final Cut Studio and then reinstall it from the DVD and patch it to the latest version.

Color 1.0.3 reportedly breaking XDCAM footage

Thu, 11 Dec 2008 02:22:04 MST

A large number of Color 1.0.3 users are reporting that the latest version breaks XDCAM footage. Apparently their XDCAM media is listed as being offline, with no way to reconnect it. The symptoms vary - some report that 30p XDCAM works fine, others report that no XDCAM works at all. Some are saying it is an issue with 1080p clips only and that 720p is fine.

Currently no-one has managed to come up with a workaround and the only suggested course of action at this stage is to uninstall Color and reinstall version 1.0.2. As far as I'm aware, that is still available from Apple's site. If you experience problems with round-tripping from FCP you will need to uninstall the entire Studio, reinstall from the disc and then ask on some forums for the old FCP 6.0.4 update (included in Pro Applications 2008-02 I believe) because, frustratingly, Apple only posts the very latest updates on their site.

This is why it is recommended to not update in the middle of a project and to read up on the patch in some forums before updating. And to be on the safe side, clone your hard disk before you update as well. We can only hope that Apple fixes this issue soon (don't hold your breath) and in the meantime, all those experiencing issues should notify Apple so they are made aware that it is affecting a large number of their users.

Update 12/14/08: See the fix here.

11-28-08 New AppleCare articles

Fri, 28 Nov 2008 08:36:17 MST

Here are all the ProApp-related AppleCare articles from the last two weeks.

Final Cut Pro

Final Cut Pro: Creating an Easy Setup for capturing DV with 32 kHz audio - If you often need to capture DV (digital video) that has an audio sample rate of 32 kHz, you may want to create an Easy Setup in Final Cut Pro with all the necessary settings.

Final Cut Pro: Audio channel 4 may show no activity in Log and Transfer window with RED clips - When you ingest RED clips with four audio channels, the audio meter may show no activity on channel four when you preview in the Log and Transfer window.

Final Cut Pro: Restoring a DV device connection in QuickTime 7 - If you notice a loss of connectivity between Final Cut Pro or Final Cut Express and your DV camera or deck after upgrading your versions of Mac OS X and QuickTime, here's what you can do to resolve the issue.

Final Cut Server

Final Cut Server: Connecting the database to the correct local user account - Final Cut Server uses configuration data which refers to the administrative user that installed the software. This configuration data contains the User ID (UID) which is different than the username of the administrative user. There may be situations where the Final Cut Server configuration data does not match any existing UIDs of local administrative users. For proper functionality, make sure that the UID in the Final Cut Server configuration data matches the appropriate administrative user's UID.

Soundtrack

Soundtrack: About Recording Latency - Audio recorded with Soundtrack may not be in sync with existing tracks in the project. After recording an audio clip, the clip is slightly out of sync with the other tracks in the project. Typically, this occurs on computers with a single microprocessor. The latency may be more pronounced on computers with slower microprocessors.

DVD Studio Pro

DVD Studio Pro: Rules for Entering DVD@CCESS Links - The DVD@CCESS feature allows you to add additional interactivity to your DVD title when it is played on a computer. When authoring a DVD, it's important to enter the links in the correct format, or they might not work as desired.

Shake

Shake: May show version 4.1 after update to 4.1.1 on Mac OS X - The Shake 4.1.1 update affects only the QuickTime component. You may notice the Shake version number does not change across the rest of the application or its scripts.

Qmaster

Apple Qmaster: Sharing sometimes does not enable with custom shared cluster storage path - Sharing sometimes does not successfully start when you have set a custom shared cluster storage path. When you click Start Sharing in the Apple Qmaster System Preferences pane, the button dims and may not switch to Stop Sharing. If you quit System Preferences and reopen it, the Stop Sharing button may appear to be active, but the Quickcluster may not be available in Compressor.

Pro Applications Update 2008-04

Fri, 21 Nov 2008 03:31:57 MST

Yesterday Apple posted a big ProApp update containing updates for several applications.

Final Cut Pro 6.0.5

Improved High-Precision Rendering
If you render sequences using the high-precision video processing setting, make sure to update to Final Cut Pro 6.0.5 for improved reliability when rendering still images and footage in high-resolution formats.

Extended Metadata Support for the Panasonic AG-HMC150 Camcorder
Final Cut Pro 6.0.5 captures the additional metadata for footage recorded with the Panasonic AG-HMC150 professional AVCHD camcorder.

Improved Support for the Panasonic HDC-SD9 Camcorder
Final Cut Pro 6.0.5 provides enhanced precision and reliability when ingesting files from the Panasonic HDC-SD9 camcorder.

Improved Support for Metadata Imported from P2 Cards
Final Cut Pro 6.0.5 provides support for extended metadata that is captured on P2 cards.

However, one of the biggest features doesn't even come from Apple. RED have posted their Final Cut Studio Installer that adds native .R3D file support to FCP 6.0.5.

Compressor 3.0.5 and Qmaster 3.0.5

Using QuickClusters and Back to My Mac on the Same Computer
The QuickCluster feature of the Apple Qmaster distributed processing system is a simple and automated alternative to creating and configuring clusters manually. In previous versions of Compressor, enabling the Back to My Mac feature in Mac OS X v10.5 Leopard would remove any existing QuickClusters. This issue has been resolved. For more information about QuickClusters, see the Distributed Processing Setup guide.

Color 1.0.3

Improved Format Support

Color 1.0.3 provides support for XDCAM 422 media and for the RED plug-ins for Final Cut Studio.

The RED plug-in and accompanying documentation can be downloaded at http://www.red.com. For workflow suggestions and more information about this format, see HD and Broadcast Formats, available from the Final Cut Pro Help menu.

Improved Application Reliability
Overall application reliability has been improved, including in the following areas:

* Using trackers in the Geometry room
* Using the Reconform command
* Adjusting the Minimum and Maximum nodes in the Color FX room

Improved EDL Handling
Accuracy and reliability during EDL import have been improved.

Application of Display LUT Now Indicated Consistently
Color 1.0.3 consistently indicates when a display LUT has been applied to a project in the Project Settings tab of the Setup room.

Improved Handling of DPX Image Sequences
Color 1.0.3 provides improved reliability when reading and outputting the header information of DPX image sequences, including timecode, frame size, aspect ratio, and transfer code.

The Fix Headers Button Now Works Properly
The Fix Headers button, which appears in the clip bin of the Setup room when you select an image sequence, now correctly alters the header information of DPX image sequences.

Improved Handling of Interlaced Media
Interlaced clips with Pan & Scan adjustments in the Geometry room correctly render the exact range of clip media.

Tangent Control Surface Mappings Are Improved
The HSL qualifier and reset control surface mappings for the Tangent CP100 control surface have been fixed.

Shake 4.1.1

* This update addresses compatibility issues for QuickTime codecs greater than 8 bits.

I don't think anyone expected Shake updates but yes, you read that correctly. Apple later posted a knowledge base article clarifying that the fix was for the QuickTime component only so Shake itself will still display 4.1 as its version number. It's also worth noting that this only applies to people who applied for the Shake 4.1 crossgrade or purchased it after 4.1 came out - 4.0 owners will not be able to upgrade.

Pro Applications Update 2008-04 Release Notes

I know you're probably dying to install these updates but first, make note of the Golden Rules (TM):
* Never update in the middle of a project.
* Don't update if you don't actually need any of the features included in the update.
* Always clone or backup your system beforehand.
* Wait for at least a week to see if there are any reported problems with the patch.
* Wait even longer if you're using third party hardware or plugins e.g. the AJA Kona card or FXFactory plugins.

How to keep your job as an editor

Mon, 17 Nov 2008 17:32:53 MST

As an editor, there are certain technical things you can do that will, in most cases, result in instant dismissal by your employer. Here are some tips on how to avoid these pitfalls.

Black frames

We've all done it - you've got the timeline zoomed out, you drag a clip and think it snapped to the end of another clip but really it snapped to a marker or overlapping bit of audio right next to it. Consequently there'll be a gap and a flash of black when the clip is played back - which producers and audiences never fail to notice.

Before you output, put the playhead at the start of the timeline and press Shift-G. This will jump the playhead to the next gap in the timeline. If you encounter a gap, press Ctrl-G to close it. If no more gaps can be found, the playhead will jump to the end of the timeline.

Unsafe luma levels

Maximum white is higher on a computer than it is on a TV. Consequently, it is possible to set white levels beyond maximum levels for NTSC broadcast. If this happens, overmodulation can occur which means that the signal can leak to radio frequencies other than the ones assigned to the TV channel, resulting in the TV company getting into big trouble with the FCC. Not surprisingly, this trouble would come your way very quickly (that's a worst-case scenario by the way).

When I am color correcting, I always switch on the luma indication in Final Cut Pro (View > Range Check > Excess Luma). This will tell you with a warning triangle and red "zebra" lines which areas are above the recommended limit. You can then use a 3-way Color Corrector to bring down the highlights until the triangle changes into a green tick.

Then, just before my project is ready for output, I create a new sequence in Final Cut Pro and nest the old sequence inside it by dragging it from the Browser into my new timeline. I then go to Effects > Video Filters > Color Correction > Broadcast Safe to make the entire nested sequence broadcast safe.

Why do I perform this step when I already made it safe earlier? Because you can't be too careful. Maybe I thought I'd corrected each one but I'd actually missed one out by mistake. Maybe I added a last-minute clip that I forgot to correct. And if you're wondering why I nest it instead of just selecting all the clips and applying the filter to all of them, that's because I might be asked to make a last-minute change right before it goes out (in the world of broadcast TV anything is possible at the last minute). Nesting the sequence ensures that everything inside that sequence will be broadcast safe, no matter what I change later on.

It's also worth mentioning that the default settings for the Broadcast Safe filter work for the vast majority of cases. It's rare to have to modify them.

Peaking audio

Like luma levels, audio levels have a maximum limit as well. If they exceed 0 dBFS on Final Cut Pro's audio meters, they will produce an audible "crunch" noise that is very ugly to hear and will instantly distract any engaged viewers.

For broadcast work, it is recommended to have your dialogue around -12 dBFS (but not lower than -18 dBFS), with very loud sounds not exceeding -6 dBFS. Film post production tends to work with a higher dynamic range so the dialogue is normally around -18 dBFS.

The most important thing, however, is that your audio doesn't exceed 0 dBFS. To ensure this, after you've completed your mix, drag the sequence from the Browser to the Viewer, then go to Mark > Audio Peaks > Mark. This will put markers in your timeline at every point where the audio exceeds 0 dBFS. This is another of those situations where even though you've already mixed it, it's so quick and easy to check for peaks that there's no reason not to do it.

To remove the markers again, go to Mark > Audio Peaks > Clear or Mark > Markers > Delete All.

Incorrect field dominance

Here's one you probably won't spot unless you are using a broadcast monitor. This is why it's important to use a broadcast monitor or at worst, a regular TV, to view your work before output.

Interlaced video uses fields to display the image. There is a field for odd-numbered lines and a field for even-numbered lines, and they are displayed one after the other for every frame. But which one should be displayed first?

NTSC video uses the Lower (Even) field dominance, meaning it shows the even-numbered lines first. If you add a clip to your timeline that has Upper (Odd) field dominance, its fields will be reversed and the motion between those fields will be reversed, so moving objects will tend to judder as they move forwards and then backwards. PAL and HD video use the Upper (Odd) field dominance, with the exception of DV-PAL, which uses Lower (Even).

This is generally not a problem with footage acquired from an NTSC or PAL camera, as it will already have been shot with the correct field dominance. The problem usually occurs with motion graphics and visual effects sequences because they have been created in software that can create both types of footage and has to be manually told which dominance it should use.

If you have been given footage that has the wrong field dominance, first try to obtain correct footage from the person who originally supplied it. If this is not possible, go to Effects > Video Filters > Video > Shift Fields to swap the fields around.

In some cases, Final Cut Pro can get confused and think that a file with the correct dominance is incorrect, so it automatically adds a Shift Fields filter when you import it. If you suspect that the file is actually correct, first check the clip for automatically-assigned filters and remove them.

Finally, it's worth mentioning that when you drag the first clip to a new sequence, Final Cut Pro 6 will ask you to change the sequence settings to match the clip if they differ. A lot of people click Yes without thinking, but taking a moment to check whether the clip in question does actually have the correct settings will save a lot of head-scratching later on.

I hope this article has given you ideas on how to avoid these problems because in a lot of cases, mistakes aren't made through ignorance but instead lack of time, lapses in concentration, tiredness, etc. That's why most of the steps in this article are very quick and easy ways of double-checking after you've already implemented corrections. These are important aspects to keep under control so it helps to have a range of defensive measures in place. When your job could potentially be on the line, you can't double-check often enough.

11-16-08 - New AppleCare articles

Sun, 16 Nov 2008 12:20:56 MST

Apple just posted some new ProApp-related AppleCare articles.

Final Cut Pro / Express

Final Cut Pro: Choosing a Hard Disk - The disk that contains your computer's operating system is called the startup disk or boot disk. In addition to the operating system, the startup disk also stores your applications (such as Final Cut Pro), your application preferences, system settings, and documents. Because the files on the startup disk are your most critical data, maintaining the startup disk is vital. Because digital media (especially high data rate video) makes your disks work harder, you should use dedicated disks for capturing and playing back your digital video and other media files. Consider your media disks as storage units that work long, hard hours, while your startup disk keeps your system properly organized. If a disk is going to malfunction, it's better if your critical data is separate from your replaceable media files. Depending on what kind of computer you are using, you may be able to use internal and external hard disks to store your media files. Each has benefits and drawbacks.

This is a very detailed article with a lot of useful technical information about the required minimum seek times, spindle speeds, etc for Final Cut Pro. Well worth checking out.

Final Cut Express 2: How to Delete the Preference Files - Learn how to resolve issues caused by unusable preference files in Final Cut Express 2.

Final Cut Express HD 3.0: Configuration error when using with iMac G5 (iSight) and Power Mac G5 (Late 2005) - If you open Final Cut Express HD 3.0 on certain computers, you'll get a "Configuration Error" message that indicates that your computer is missing certain hardware or software, or possibly an AGP graphics card.

Final Cut Pro and Final Cut Express: Convert MP3 and AAC audio files for compatibility before importing - This document explains how to import MP3 and AAC-encoded audio files into Final Cut Pro 3, Final Cut Pro 4, and Final Cut Express.

Final Cut Express HD requires a Quartz Extreme AGP graphics card - To use Final Cut Express HD, you need a computer with an AGP graphics card that is capable of handling Quartz Extreme.

Final Cut Server

Final Cut Server: Unable to launch the specified application - In some cases the Final Cut Server client application may not open when you double-click the Final Cut Server.jnlp icon or Final Cut Server.app icon. This may happen after switching user accounts or restarting your computer from a volume other than the one you used to download the Java Web Start Final Cut Server client.

Soundtrack Pro

Soundtrack: How to Configure Digidesign Audio Devices - Learn how to use Digidesign audio devices with Apple's Soundtrack music application.

I guess they're talking about Soundtrack Pro here, not Soundtrack, as the original Soundtrack was discontinued 5 years ago.

Qmaster

Apple Qmaster: Optimizing cluster storage capacity - By default, the Apple Qmaster distributed processing system saves temporary process files in the /var/spool/qmaster directory on the cluster controller's startup disk. Computers in the cluster will access this location as needed. If you are processing large source media files that exceed the available storage space on the startup disk, you may run out of storage space on that disk.

Logic Pro / Express

Logic 8: How overlapping recordings are assigned to take folders - The Takes feature in Logic Pro/Express 8 is a powerful way to organize multiple recordings of a part in your projects. Here are some tips and explanations of what it will do in various situations.

Logic Express 8: Troubleshooting Basics - If Logic Express 8 isn't starting up properly or performing normally, try these basic troubleshooting steps to remedy the situation. Please note that these steps aren't exhaustive, and are not intended to cover any specific issue. They are fundamental, basic steps that are most effective in getting Logic Express 8 into good working order, and are the steps most often suggested by AppleCare Technical Support.

Using Compressor with multiple cores

Fri, 14 Nov 2008 07:04:18 MST

Here's a quick tip that a lot of people still don't know about. So you've just bought that shiny new Mac Pro, you finish your Final Cut Project, export to Compressor and wait.... and wait... and wait. Hang on a second, that brand-new 8-core machine is only utilizing one core!

Welcome to the world of Final Cut Studio 2, which is completely unaware of multiple cores in your system. Hopefully this will change in FCS 3 but in the meantime, here is a trick to using those cores in Compressor.

1. Go to System Preferences and open the Apple Qmaster section.

2. In the Setup tab, click Stop Sharing if Qmaster is already activated.

2. Select QuickCluster if it is not already selected.

3. Under Services, select the service marked Compressor and select the checkboxes for Share and Managed.

3. Then click Options for Selected Service.

4. Select half of the number of cores in your machine i.e. 2 for a 4-core and 4 for an 8-core (this particular machine has only 2) and click Ok.

5. If you are using Shake. Maya or have any other command-line renderer set up with Qmaster, select the Rendering item in the list and click Options for Selected Service.

6. Click the + button and add half as many Local machines as you have cores i.e. 2 for a 4-core and 4 for an 8-core, then click Ok.

7. Under the QuickCluster section, type a name for your new virtual cluster.

7. Click Start Sharing and close System Preferences.

8. In Final Cut Pro, export your sequence as a QuickTime movie. This is important. Do not choose File > Export > Compressor, as this will fail.

9. In Compressor, import the movie, set up your batch and click Submit.

10. Instead of "This machine", select the name of your new cluster in the Cluster list and click Submit. The movie clip will be processed by multiple cores in your machine.

This is called Virtual Clustering, and it is achieved by launching a new version of Compressor for every instance. This is much easier from the perspective of Compressor's programmers but it takes up more memory and is less efficient than if they were to implement true multi-core capabilities into the application.

So be aware that using this method will require considerably more memory than rendering on a single instance. Apple recommends in most cases one process for every two cores, although it all depends on the type of media you are working with and how much memory you have. If you set too many instances and don't have enough memory, your machine would slow down (or worse, crash) thus undoing the whole point of setting up the virtual clusters in the first place. Apple recommends 1 GB RAM per service but again, this depends on the media you are transcoding to.

How to reinstall Compressor and Qmaster

Tue, 11 Nov 2008 14:00:37 MST

We recently released Compressor Repair, which aims to fix some of the most common problems with Compressor - but it can't help you if you've got missing or corrupted files. Sometimes a reinstall of Compressor and Qmaster is needed (although these steps apply to any software in the Suite). Here's how to do it properly.

1. Download FCS Remover and run it.

2. Select "Compressor and Qmaster Only" as the preset.

3. Click Remove and enter your admin password.

4. Restart your machine, and when it boots up again, empty your Trash.

5. Insert your Final Cut Pro or Logic DVD (I'm using Logic here), ctrl-click on "Install Logic Studio" or "Install Final Cut Studio" and select Show Original.

6. Go into the Packages folder and run Compressor.mpkg (that's .mpkg, not .pkg).

7. When that finishes, run Qmaster.mpkg (again note the "m").

That's it! At this point, it is a good idea to update Final Cut Studio. Several users have reported that this method did not work until they had updated Compressor and Qmaster to the latest versions after reinstalling.

(Note: I've seen other people recommend Pacifist as a way of installing the files again once they've been removed. Pacifist is a great piece of software but if you make a mistake, it's possible to seriously screw things up unless you know what you're doing. I think this method is a lot safer and less susceptible to user error. However, if the above steps don't work for you, try Scott Simmons' Pacifist method here.)

Update: The article above was written for Final Cut Studio 2. To reinstall FCS 3, run the installer normally or use Pacifist (see above).

11-5-08: New AppleCare articles

Wed, 05 Nov 2008 07:07:14 MST

In the past week or so, Apple has posted several new ProApp-related articles to the Support section of its web site.

Final Cut Studio: Switch to higher performance graphics with MacBook Pro (Late 2008) - Learn how to configure the MacBook Pro (Late 2008) for better graphics performance with Final Cut Studio.

Motion: QuickTime proxies from RED sometimes import with no audio - Sometimes there may seem to be no audio when you import QuickTime proxies generated by RED cameras or by REDAlert into Motion. This may happen if you import the movie by using the Import button in the File Browser, drag the movie from the File Browser to the Canvas, or drag the movie from the Finder to the Canvas.

Final Cut Pro, Final Cut Express: Unexpected quit during AVCHD ingest - Final Cut Pro 6 or Final Cut Express 4 may sometimes quit unexpectedly when you attempt to transfer AVCHD media, if the third-party Perian QuickTime component is installed.

Final Cut Pro: "AE Effects Error: Unable to find plug-in" warning when opening some projects - You may see the warning dialog "AE Effects Error: Unable to find plug-in..." when you open certain projects in Final Cut Pro.

Motion: Higher performance graphics mode may remain active if Compressor is used to transcode Motion projects on MacBook Pro (Late 2008) - When you transcode a Motion project in Compressor on a MacBook Pro (Late 2008), your computer may stay in "Higher performance" graphics mode after the project has been transcoded. This can happen even after you change the graphics setting in the Energy Saver pane in System Preferences to "Better battery life," log out, and then log back in. The Energy Saver pane in System Preferences may report the graphics mode is "Better battery life," but it will still be in "Higher performance" mode.

DVD Studio Pro: Authoring a DVD that plays automatically without a menu - Most DVDs are created with at least one menu from which the user can select tracks, other menus, special features, and so forth. In some cases, you may wish to create a DVD that just plays its content without the need for user interaction.

Logic Pro: Using DSP powered plug-ins with systems that include nodes - Logic Pro 8 allows you to utilize the processing power of additional computers (nodes) on a Gigabit ethernet network. Most of the plug-ins native to Logic, and many third party Audio Unit plug-ins, can be processed by node computers.
Learn more about using DSP powered plug-ins (plug-ins that run from a card or externally connected device, rather than directly from the CPU) and nodes.

Pro Application Replacement Serial Numbers - A new serial number can be generated in the event that yours is missing or invalid. Apple requires a valid proof of purchase to request a replacement serial number submitted via fax or email. The following guidelines will help you to determine what is best for you.

Final Cut Pro Audio Filter Guide Part 2

Sun, 05 Oct 2008 10:12:09 MDT

This is the second part of the Final Cut Pro Audio Filter Guide. Part 1 covered the Audio Units that ship with Mac OS X and is available here. This part will cover the audio filters that ship as part of Final Cut Pro.

This guide is intended to inform Final Cut Pro users of the options available to them for fixing bad sound. It is worth mentioning at this point that this guide is intended for users of Final Cut Pro 6.

Now, one thing you may have noticed is that there are often duplicate filters such as AUBandpass (an Audio Unit) and the built-in Band Pass Filter. So which should you use? Well, for a start, bear in mind that some of those filters have the same function but different parameters. I would generally advise you to pick the built-in filters over the Audio Units whenever possible, as they tend to use up fewer system resources.

3 Band Equalizer

This allows you to take three separate bands (low, med and high) and adjust the gain up and down individually. I personally prefer AUFilter (in the Apple folder) because it gives you a bit more control and allows you to adjust 5 bands.

This is useful when you need to boost the bass of a voice or improve a flat-sounding voice.

Band Pass Filter

This will allow a range of frequencies on either side of the center frequency to pass through and reduce (attenuate) frequencies outside this range.

This is identical to the AUBandpass filter (in the Apple folder) except that instead of the bandwidth parameter, it has a mysterious one called Q. Q stands for Quality Factor and is a different way of representing the bandwidth. There are numerous articles about it on the internet that get quite technical but all you need to know is that it's the relationship between the center frequency and the bandwidth (f/b) so Q is inversely proportional to the bandwidth (i.e. when the bandwidth goes up, Q goes down by a proportional amount). It is worth noting that Q is not the bandwidth itself but it is related to it. If you want to find out the bandwidth, just divide the center frequency by Q.

If you don't understand the above explanation just play it by ear or use the AUBandpass filter.

Compressor/Limiter

The Compressor / Limiter reduces the volume of sounds above the threshold amplitude. This is a useful way of minimizing the difference between two subjects talking at different volumes or making sure that the audio fits within the limits of the playback device.

Obviously this reduces the volume of the overall audio so Preserve Volume rectifies this (although I find it is often then too loud). Attack time refers to the time it takes for the filter to decrease the volume once it has detected a frequency with an amplitude above its threshold. Release time refers to the time taken for the filter to increase the volume again once the high amplitude frequency has finished playing. Higher values allow for a smoother and less noticeable response but set them too high and the compressor won't respond quickly enough. This is something inherited from live audio mixing where you don't know what's coming next. Setting the threshold to just under your preferred limit allows time for the compressor to lower the volume in anticipation for a louder sound once the threshold is reached.

Ratio tells the compressor by how much it should reduce the volume when a sound exceeds the threshold. If the ratio is set to 2 (2:1), then a 10 dB increase in volume above the threshold will be halved to a 5 dB increase. It is worth noting that the compressor lowers the volume of sounds above the threshold but does not necessarily reduce them to a value at or below the threshold. Be aware that very loud sounds could still theoretically peak.

Finally, it is also worth mentioning that the compressor reduces the volume difference between the subject and any background noise, so background noise will be more noticeable upon boosting the audio after applying the compressor.

DC Notch

Sometimes you may experience a DC current leakage through the mic, causing noise in the recorded audio. A DC Notch filter will remove the DC offset component which you probably need a degree in audio engineering to fully understand. It has no parameters.

This is one of the lesser-used filters FCP provides.

Echo

This one obviously adds an echo. Effect Mix allows you to mix the echoing audio with the original in order to better blend it in. Effect Level controls the volume level of the echoes (but not the original audio). Brightness controls the degree that the echoes will overlap. Feedback controls how long each echo will last and delay controls the spacing between each repeat.

It is worth noting that the echoes will be abruptly cut off unless you lengthen the audio clip or fade it out.

Expander / Noise Gate

The opposite of a compressor. A compressor takes high amplitude sounds and lowers them whereas an expander takes low amplitude sounds (sounds below the threshold) and lowers them. I know it probably seems strange to lower sounds that are already quieter than the rest of the audio but this is designed to increase the dynamic range of the clip.

Threshold is the amplitude below which the expander will kick in. Ratio controls the proportion of expansion - for example with a ratio of 2 (2:1), a 3 dB fall below the threshold will be adjusted to a 6 dB fall. Attack time is the time for the volume change to be applied once it falls below the threshold. Release time is the time for the volume to return to normal once the signal goes above the threshold again.

A noise gate is a more extreme expander that will completely eliminate frequencies below the amplitude threshold. This can be achieved with high ratios (e.g. 10).

Gain

This is a simple filter that raises or lowers the volume of the audio. It is added automatically to clips when you use the Modify > Audio > Apply Normalization Gain command.

High Pass Filter

This will attenuate (reduce) low frequencies below the threshold. This is the same as a Low Shelf Filter. Use the Q slider to modify the bandwidth (width of the frequency range).

Useful for cutting out low frequency noise such as the rumbling of traffic or very low notes in a deep voice.

High Shelf Filter

This will attenuate (reduce) high frequencies above the threshold. This is the same as a Low Pass Filter. Gain allows you to adjust the volume of audio that passes through the filter.

Useful for filtering out high frequency noise such as buzzing on the soundtrack.

Hum Remover

This is similar to the Shelf / Pass filters but it has several extra parameters. Frequency, Q and Gain have been explained many times above. In order to explain what the harmonic check boxes mean, we need to delve into a little audio theory.

The fundamental frequency is the lowest frequency in a harmonic series (the Frequency value in this case). Harmonics are integer multiples of the fundamental frequency - e.g. if f=60, 2f=120, 3f=180, etc. These play at the same time as the fundamental frequency and contribute to the tone of a sound. The Hum Remover is more powerful than a Shelf / Pass filter because it allows you to remove these specific frequencies without removing any frequencies in between these. For example, if f=60 and you wanted all harmonics up to 5f removed, a Low Shelf or High Pass filter would remove ALL frequencies up to 300 Hz, potentially affecting the quality of your sound. The Hum Remover would not do this.

Despite being called Hum Remover, the use of harmonics makes it useful for other purposes such as enhancing or reducing a musical instrument on a soundtrack.

Low Pass Filter

The Low Pass Filter has the same effect as the High Shelf Filter - it will attenuate (reduce) frequencies higher than the specified frequency range, keeping lower ones intact.

Frequency refers to the center frequency and Q is a way of representing the bandwidth (the width of the frequency range).

Useful for reducing high frequency noise such as buzzing.

Low Shelf Filter

The Low Shelf Filter has the same effect as the High Pass Filter - it will attenuate (reduce) frequencies lower than the specified frequency range, keeping higher ones intact.

Useful for reducing low frequency noise such as air conditioner hums.

Notch Filter

The opposite of a Band Pass filter. Instead of only allowing frequencies within a certain range, this cuts out frequencies within a certain range.

Frequency refers to the center frequency and Q is a way of representing the bandwidth (the width of the frequency range).

Useful if you have noise of a constant frequency on your soundtrack (such as a buzzing sound).

Parametric Equalizer

This is a combination of Band Pass, Notch and Shelf filters combined into in a single filter. Frequency is the center frequency, Q is related to the bandwidth (see the explanation above) and gain allows you to boost or cut the frequencies passing through the filter.

Reverberation

This is similar to the Echo filter but considerably more sophisticated. Rather than simply repeating sounds with a delay, it allows you to mimic the characteristics of echoes within various locations. This is incredibly useful when performing ADR (Automated Dialogue Replacement) because it is highly likely that the sound booth you record the ADR in will sound nothing like the original location. This allows you to mimic the effect of sound waves bouncing off walls, with some canceling each other out and some increasing in intensity. It can also be used sparingly to improve a flat-sounding voice.

Subtlety is often the key with this filter and Effect Mix allows you to mix the reverb with the original sound to help blend it in. Effect Level controls the intensity, Brightness controls the degree that the echoes overlap and Type allows you to specify various preset locations.

It is worth mentioning that the reverberation will end abruptly unless you extend your audio clip or fade it out at the end.

Vocal DeEsser

This helps to reduce the intensity of "s" sounds, most noticeable if the actor has a lisp. The controls are similar to a compressor but it is optimized for reducing sibilant ("s") sounds. Ratio controls the amount of reduction - e.g. if the "s" sound is 6 dB and the ratio is 2, it will be reduced to 2 dB.

Emphasis controls the sensitivity of the filter and Broad Band Mode widens the bandwidth so that more frequencies around the center frequency are affected.

Vocal DePopper

Sometimes if a microphone is directly in front of an actor's mouth they will accidentally breathe into it while speaking, causing a wind-type noise to be generated. This filter aims to minimize these.

The parameters are similar to a compressor - ratio controls the ratio of reduction proportional to the intensity of the sound. Broad Band Mode widens the bandwidth so that more frequencies around the center frequency are affected.

One Final Note

These filters do a decent job of repairing troublesome audio but they are not miracle cures. Sometimes (and this is never popular with producers) it just isn't cheaper to fix it in post. Even big Hollywood movies with access to multi-million dollar sound studios re-record a lot of their audio. It is important to always think realistically.

However, I hope this two-part guide has been useful in showing you just what can be improved. I noticed a significant improvement in the sound quality of my projects once I understood more about the audio filters available to me, and I hope you'll be able to say the same.

Final Cut Pro Audio Filter Guide Part 1

Sat, 27 Sep 2008 14:31:09 MDT

In my conversations with other editors it became clear that for a lot of them (myself included), audio was a major area of weakness. They could handle editing, color correction, graphics, etc, but only knew a few ways of improving bad audio. This inspired me to create this guide to show people exactly what Final Cut Pro offers out of the box.

Filters in FCP are split into two categories - Apple Audio Units (AU) which ship with the operating system and are available to any application, and FCP-specific ones. Today I'll be giving details on the Audio Units with the FCP-specific ones coming in Part 2.

AUBandpass

The bandpass filter allows a certain range of frequencies to pass through and rejects any frequencies that are outside of that range. So if you have a person talking with rumbling traffic and high-pitched TV static in the background, you could use the bandpass filter to isolate the center frequencies of the person's voice.

AUDynamicsProcessor

This filter allows you to adjust the dynamic range of the audio (the difference between the loudest and softest sounds). Compression lowers the volume when it exceeds a certain threshold (making loud sounds quieter and therefore decreasing dynamic range). Expansion lowers the volume when it is lower than the threshold (thus making quiet sounds quieter and therefore increasing dynamic range).

Using a compressor and expander at the same time allows you to avoid overly-loud peaks while still maintaining dynamic range. The compressor will reduce the louder portions of the audio in proportion to their distance from the threshold (i.e. louder sounds will be reduced by a much larger amount), helping to even out amplitude variations. The expander will then take the quieter sounds and reduce their volume (again, proportionally), thus evening out the amplitude variation of the quieter sounds and increasing the dynamic range.

Imagine some music where you have loud crashing drums, a relatively quiet triangle and a trumpet somewhere in between. The drums are far too loud so you apply a compressor to bring them down. The drums are now a lot quieter but you've noticed that the subtlety of the triangle has been lost - it is now far too prominent. So you apply an expander to lower the volume of the triangle to an acceptable level. The AUDynamicsProcessor allows you to do this with one filter instead of two, which is a much more efficient use of system resources.

Attack time refers to the amount of time it takes for the compressor to implement a change in volume and release time is the time taken to reduce the compressor back to its original level afterwards.

There's a bit of debate over what "headroom" actually means as it's not a standard term. To the best of my knowledge, it refers to the number of dB the signal is permitted to exceed the threshold of the compressor/limiter.

The Dynamics Processor is a great way of compressing and/or expanding your audio to make sure that it fits within the audible range of your listening equipment.

AUDelay

This repeats parts of your audio. Dry/wet mix controls whether or not the repeated sounds overlap each other. 100% dry means no overlapping and 100% wet means full overlapping. Delay time is the delay before the repeat starts. Feedback controls the number of repetitions. Lowpass cutoff frequency stops certain low sounds from passing through the filter.

This filter is normally used for atmospheric effects. For more environmentally realistic results (at the cost of performance), I recommend the Reverberation filter that comes with Final Cut Pro.

AUDistortion (Leopard only)

This is a very comprehensive distortion filter offering a lot of control. I can't give much advice on the various parameters as I don't actually know what they mean and there's no documentation available. I would suggest adjusting by ear (it is probably worthwhile lowering the render quality while adjusting, and then raising it again once you're happy with the results).

AUFilter

I use this one a lot. It allows you to take 5 bands (5 ranges of frequencies) and adjust the gain up or down for each one. If a person's voice is muffled, increasing the gain on the higher frequencies can often improve this. I also sometimes use it to add bass to make a person's voice sound richer.

The bandwidth slider allows you to adjust the size of each frequency range, with the frequency sliders referring to the center of the range.

AUGraphicEQ

(image truncated for space reasons)

This is similar to the AUFilter above but the size of the frequency ranges cannot be adjusted and you can have up to 31 bands instead of just 5. This site provides a guide to common frequency ranges.

I've used this a couple of times to boost bass in a person's voice but I generally prefer AUFilter for this. It's good for removing or reducing a specific frequency range.

AUHighShelfFilter

This cuts off frequencies above the cutoff frequency, allowing lower sounds to pass through. The gain slider controls the amount that the frequencies passing through will be boosted.

Good for reducing high-frequency noise.

AUHipass

This reduces lower frequencies and allows higher ones to pass through. Resonance controls the intensification of the higher frequencies that pass through.

Good for removing low rumbling sounds such as traffic or for reducing very deep voices (I have had to do this at times).

AULowpass

Reduces (attenuates) higher frequencies and lets lower ones through, controlled by the cutoff frequency. Resonance controls the intensification of the frequencies that pass through.

Good for removing high-pitched noise.

AULowShelfFilter

Reduces frequencies lower than the cutoff frequency and lets higher ones pass through. This is similar to the AUHighPass filter above but this offers the ability to adjust the gain instead of resonance.

Good for removing low hums.

AUMultibandCompressor

This allows you to compress multiple bands (frequency ranges) individually for more control than a traditional compressor.

Pre-gain boosts the signal before it is processed which is useful if the signal is too low to be processed adequately by the compressor, and post-gain reduces the gain back to a normal level afterwards.

Crossovers 1, 2 and 3 define the point at which the previous band ends and the next one begins. Threshold refers to the amplitude level at which the compressor kicks in. Headroom, as stated above, probably gives you extra leeway above the threshold. Eq allows you to boost or lower each band.

Possible uses for the Multi Band Compressor include lowering the dynamic range of bass sounds without interfering with higher frequency sounds. This is different from the High Shelf Filter which indiscriminately cuts all bass below a certain frequency.

AUNetSend

AUNetSend is one of the most interesting filters in that it's not actually a filter. It does absolutely nothing to affect the way your audio sounds but what it does do is allow you to send audio across a network.

You need to have an application that implements audio generators. Audio editing applications such as Logic implement these. Alternatively, there is a tool called AU Lab in /Developer/Applications/Audio if you have the developer tools installed. Soundtrack Pro does not support this. Add an AUNetReceive generator to the track in your audio application, add an AUNetSend filter to your FCP audio clip and hit play in FCP. You should see "AUNetSend" pop up in the AUNetReceive configuration dialog. Select it and your track should be receiving the audio from Final Cut Pro. Note that it only appears while the timeline is playing in FCP.

In my testing, the Status parameter appeared to do absolutely nothing.

AUParametricEQ

This allows you to boost or lower the amplitude of a signal within a certain range. This is useful if for example you have a high-pitched buzzing noise in the background and you only want to eliminate that particular frequency and keep your higher sounds intact.

AUPeakLimiter

The Peak Limiter differs from a compressor in that a compressor reduces the volume of an entire track when a frequency reaches a certain level whereas the Peak Limiter reduces just that frequency. This is particularly useful if there is background noise on the track that would produce a noticeable fluctuation if the entire track were to receive a volume adjustment.

Attack and release time, as mentioned above, control the amount of time it takes for the filter to implement a change in amplitude, with longer times allowing a smoother transition. Pre-gain allows you to boost the volume before it reaches the filter in order to change the number of frequencies being affected. The limiting amount allows you to limit the amount that the filter will reduce the amplitude.

AUPitch

Adjusts the pitch of your audio, obviously. There are a LOT of controls though, and I have to admit that I don't have a clue what a Glb Trigger Thresh or a Loud Aggr K is. Effect blend blends the pitch-shifted audio with the original and is sometimes necessary to make voices sound natural. It is worth mentioning that I've gotten perfectly acceptable results by adjusting the first two parameters and not bothering with any of the others. I'd imagine that most people wouldn't have to adjust more than these.

I tried a Google search on some of these parameters but they only turned up forum threads where people were asking what on Earth they meant and no-one was able to solve their problem. If anyone does know, I'd be interested to hear from them.

This can be useful for making a male actor's voice more masculine (yes, I have had to do this!).

AURogerBeep (Leopard only)

This emulates the "roger beep" sound when someone lets go of the button on a walkie talkie. It will automatically play the sound when the audio level drops below a certain threshold for a certain amount of time (as if the person stopped speaking).

In gate threshold and in gate time refer to the time that the threshold amplitude must be maintained before the sound kicks in. Out gate threshold and out gate time refer to the amount of time that the threshold must be maintained before it ends the roger beep (adjust this if there is background noise). Roger level is the volume of the roger beep, and I think sensitivity and roger type are self-explanatory.

This is an effects filter with quite a narrow purpose so it's not something that gets used very often.

AUSampleDelay

Similar to AUDelay except that the delay time is set as a number of audio samples instead of a number of seconds.

Important:

Two of the above filters are Leopard only. If you use those filters and then transfer your project to a Tiger machine, you will receive an error message and will be unable to use those filters within the project.

Part 2 covers the filters built into FCP.

Pro Applications Update 2008-03

Sat, 20 Sep 2008 03:19:35 MDT

Don't know how I missed this. On Thursday, Apple released Pro Applications Update 2008-03 that patches both Compressor and Qmaster to 3.0.4.

Only one fix is included in the release notes but it's a big one:

Missing Clusters and Services Issue Resolved

Compressor 3.0.4 and Apple Qmaster 3.0.4, together with the Mac OS X v10.5.5 update, resolve an issue in which clusters were not visible in Compressor and Batch Monitor, and Compressor services did not appear in the Apple Qmaster pane of System Preferences.

I'm sure you know the drill by now - don't update in the middle of a project, only update if it's entirely necessary and make sure everything is backed up before you do.

This update is concerning to me for two reasons. Firstly, it requires OS X 10.5.5, completely locking Tiger users out. Presumably 2008-04 will require 2008-03 so will all patches require 10.5.5 from now on? Was 2008-02 the last Tiger-compatible patch for Final Cut Studio? There has been no official word from Apple on this.

Secondly, when you go to the download page it only lists 2008-03 as an option, with 2008-02 nowhere to be seen. How are you supposed to download Final Cut Pro 6.0.4? There's always Software Update but that's not really practical if you have a lot of machines. Apple seriously needs to rethink the way it offer patches to FCS users.

Final Cut Studio Category: Digital Rebellion Blog

Speeding up Compressor

Don't export directly to Compressor from Final Cut Pro

Only use Frame Controls where necessary

Perform heaving-lifting in a separate pass to the encoding

Use a cluster

Conclusion

FCPUG Amsterdam Supermeet 9-13-2009

Why don't my old Preference Manager backups work on FCP 7?

How to run Final Cut Studio 3 on a MacBook

My thoughts on the new Final Cut Studio

Architecture

Blu-ray

More ProRes options

LiveType discontinued

Avid-like features

Faster, better quality

RED support

Media Management

Missed opportunities

Final Thoughts

Interesting Links

Final Cut Pro 6.0.6 released

Sign the DVD Studio Pro Blu-ray petition

Compressor error - "You must enter a name for this batch submission"

Recently updated AppleCare docs - 5/1/09

Hardware

Final Cut Pro / Express

Motion

Compressor

Logic

Xsan

Misc

Incoming network connection dialogs keep appearing

3-31-09 New AppleCare articles

Hardware

Final Cut Pro

Motion

Soundtrack Pro

Logic

Xsan

Final Cut Server

Guide to Final Cut Pro Internal Tools

Adjust Windows

App / Perf Info

Log OpenGL Profile Costs

Log VM Footprint

Movie Dumpster

Playback Meter

Screen Size Override

Statistics

Compressor error: "Unable to connect to background process"

QuickTime 7.6

The Golden Rules (TM) of Updating

Why does my DVD audio level differ from the level in FCP?

What does 2009 hold for Final Cut Studio?

Pro Applications Update 2008-05 is out

Possible solution to Color 1.0.3 XDCAM issues

Solving missing framework errors in Final Cut Studio

Color 1.0.3 reportedly breaking XDCAM footage

11-28-08 New AppleCare articles

Final Cut Pro

Final Cut Server

Soundtrack

DVD Studio Pro

Shake

Qmaster

Pro Applications Update 2008-04

Final Cut Pro 6.0.5

Compressor 3.0.5 and Qmaster 3.0.5

Color 1.0.3

Shake 4.1.1

How to keep your job as an editor

Black frames

Unsafe luma levels

Peaking audio

Incorrect field dominance

11-16-08 - New AppleCare articles

Using Compressor with multiple cores

How to reinstall Compressor and Qmaster