FCP to Compressor problems

loganwang

New member
I just upgraded to a new 17" MacBook Pro from a 15" Pro that was two years old. In the past, I've been able to open Compressor and jump back and forth from FCP to Compressor, sending a number of sequences one at a time before finally submitting the entire batch. With my new computer, FCP "does not respond" and I have to Force Quit if I try to jump back into FCP after loading a sequence into Compressor. Any thoughts on why this is happening? I've had so many problems with Compressor in my life - you'd think Apple could create a better program to go with FCP.
 
never use the Export via Compressor option... export to QT Movie and bring that into Compressor manually.
 
I always make a different folder for the sequences that I export together. I select them all in this folder and then send it to Compressor. This way you don't have to go back and forward, because that causes a lot of problems.

The export to QT Movie is another option, but I always wondered how much detail you loose by making it a Quicktime Movie first? Actually the export to Quicktime Movie is the only option for me now the make use of all the 8 cores with Compressor. As the direct export to compressor doesn't work with that.
 
I've always gone straight to Compressor and never had any problems. Upon upgrading to FCP 6.0.6, I'm now both unable to go back and forth between Compressor and FCP, and it's taking unreasonably long to export a single file.

I need to backup entire tapes as h.264s with timecode stamps, so exporting as QT movies first adds a huge amount of time. I've always had great success with my method of compressing multiple sequences from FCP at once in the past...

Any insight as to what is causing these problems?
 
When you use Export using Compressor, FCP will get locked for as long as Compressor is encoding. FCP will be busy sending frames to Compressor and you won't able to edit anything else in the process until Compressor is finished, which could take a long time.

As was stated above, export to standalone files first, then run Compressor in the background. This will free up FCP and you can do something in the process (though probably nothing very intensive since you'll be encoding the background). This workflow tends to be more reliable (less freezing of the apps, etc.).

Yes, technically this process can result in slight quality differences since you are exporting to an intermediate stage first. How much would depend on the intermediate and the output codec you are aiming for. As long as the intermediate stage is of better quality than your output then you shouldn't have any major quality issues. For example. ProRes as intermediate going to H.264, DV50 going to MPEG2, etc.
 
you don't even need to export anything... go to your capture scratch folder and bring your master clips into compressor.
 
Back
Top