Time Problem with Mac Compressor 3.0.4 for FCP

[Daniel Low]

“I exported from FCP to Quicktime using video only — include chapter markers options and then used an AIFF audio file exported from FCP. Everything worked perfectly in DVD SP.

It only took a few minutes to create the QT file and 30-40 minutes for the Compressor run.

Apparently Compressor speaks QT very fluently because everything went like clockwork— no slow downs and a fast pace to completion”

I’m glad it worked (please ‘Rate my Post’ if you want to!)

You are still making like harder than it should be. Just export using the quicktime method and deselect ‘Make self contained’ Once in compressor, use the AC3 encoder for your audio.

Another thing to remember is that Quicktime IS the Mac OS. Quicktime is so very much part of the whole operating system that saying something like “Compressor speaks QT very fluently” just doesn’t make sense.
At the very heart of FCP, compressor, DVDSP, Motion, iTunes iMovie, iLife and every other media aware relies on Quicktime. All these apps are built around Quicktime. Quicktime is the man-servant, butler, translator, heavy-lifter, all round good guy etc. Quicktime is one for the reasons why using a Mac is so good and also why when things go wrong they can be so frustrating.

QuickTime rocks! 😉 Nothing else on the market comes within a million miles of the capabilities of Quickime. (and I remember testing the very first version!)

__________________________________________________________________
Please post back saying what solved your problem. It could help others, and saying ‘thanks’ is free!

[Redford Givens]

Apparently Compressor speaks QT very fluently because everything went like clockwork— no slow downs and a fast pace to completion”

Another thing to remember is that Quicktime IS the Mac OS. Quicktime is so very much part of the whole operating system that saying something like “Compressor speaks QT very fluently” just doesn’t make sense.

Then why does Compressor go into slow motion when receiving directly from FCP.

I’m no computer expert, but I’ve got a feeling that this problem stems from a flaw in the way FCP and Compressor count frames when they communicate.

Counting errors in FCP are probably responsible when you get timecode breaks while capturing long clips with resulting sound sync problems. Capturing requires precise frame counts etc. Ditto for sending a project to Compressor.

If these errors only occur when FCP is directly in the mix, it becomes a prime suspect. I would suggest that the programmers take a long hard look at how FCP and Compressor count frames and keep the timecode in order.

This is my hunch.

At the very heart of FCP, compressor, DVDSP, Motion, iTunes iMovie, iLife and every other media aware relies on Quicktime. All these apps are built around Quicktime. Quicktime is the man-servant, butler, translator, heavy-lifter, all round good guy etc.

Then these problems are even more mysterious. Apparently FCP or Compressor is not fluent in ALL QT dialects.

Quicktime is one for the reasons why using a Mac is so good and also why when things go wrong they can be so frustrating.

QuickTime rocks! 😉 Nothing else on the market comes within a million miles of the capabilities of Quickime. (and I remember testing the very first version!)

I’m a Mac fan for life. These problems pale in comparison to the brain damaging, ego destroying, production killing, unsolvable problems that happen to PC users.

So far I’ve never encountered a problem on a Mac that wasn’t resolved in short order.

Kill all robots

Redford Givens