Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Output Compression from FCP

  • Output Compression from FCP

    Posted by Raymond Singer on January 6, 2009 at 6:43 am

    Goofy, goofy. A composer sent me a 60 second h.264 video and a 48k SFX audio track. He’s on an ancient system and composed with a QT 6 version of the film. The audio was a few frames out, which I adjusted on the timeline. Perfect. But when I spit out a compressed version – Sorenson, QT 6 compatible, QT 7, h.264, Motion JPEG any darn recipe – one of the cues is always out of synch. It’s possible all the cues are those few frames out, but it’s tough to tell and the composer isn’t here to help. So what to do? The delivery has to be an h.264, so I suppose I could, through trial and error, move the audio around until it fits just right on the compressed file, but it seems like a lot of work that shouldn’t have to be done. BTW, this happens whether I make a QT ref movie, a stand-alone QT or export from the timeline; and whether I do the compression as a QT Conversion or export the timeline or a QT ref or full version to Compressor to do the work.
    Help most gratefully appreciated. Thanks.

    Raymond Singer replied 17 years, 4 months ago 2 Members · 2 Replies
  • 2 Replies
  • Tom Brooks

    January 6, 2009 at 12:59 pm

    My first thought is to try converting that original H.264 clip into a normal video editing format (say, Uncompressed 10-bit or ProRes 422 HQ), synching that up in FCP and then exporting to the final format.

  • Raymond Singer

    January 6, 2009 at 5:55 pm

    Here’s the latest: I tried the ProRes route but alas, no-go. BUT – to synch up the audio in FCP, I had to slide the audio track 10 frames to tails. FCP played back in synch. By sliding the audio back 10 frames to heads, the compressions come out fine even though it’s out of synch on the timeline. It’s Twilight Zone time, but at least things are consistent and I can workaround the problem.

    Thanks much for your help, Tom.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy