Final Cut Pro – MultiClip – Audio not syncing

[Jaqai Mickelsen]

You gave me hope John… Using streamclip I just did a test and transcoded a video at 29.97 – tried to align it with the audio (Just the single video and the single audio file) and still no dice. It acts the same way it did when the video was at 30 frames. It jumps in way after the clap in the multi clip it produced.

I’m just about to full on panic mode at this point.

[Rebecca Gillaspie]

The thing with pluraleyes is it creates new audio files when it makes the multiclip so I thought it mightwork. What a pain! Don’t panic, you’ll figure it out.

“A man is a success if he gets up in the morning and gets to bed at night, and in between he does what he wants to do.” – Bob Dylan

Rebecca Gillaspie
Producer/Editor
rgillaspie@gmail.com

[Jaqai Mickelsen]

Talked to client, at least found a work around that will work for this fire, but would still love to get a solid idea of what the heck is happening if anyone happens to see it and know the trick.

Thanks so much everyone.

[John Pale]

[Jaqai Mickelsen] “You gave me hope John… Using streamclip I just did a test and transcoded a video at 29.97 – tried to align it with the audio (Just the single video and the single audio file) and still no dice. It acts the same way it did when the video was at 30 frames. It jumps in way after the clap in the multi clip it produced.

I’m just about to full on panic mode at this point.
“

NOT STREAMCLIP! I am not suggesting you transcode anything. The conform function in Cinema Tools!

[Matt Campbell]

So does that mean this was shot 30 fps Progressive? If so, that’s what I shoot with our HVX 200 on P2. I shoot 720p30PN all the time because it downconverts nicely to NTSC 29.97 using Compressor. Do you need to conform using Cinema Tools or can you just convert with Compressor?

So, can’t he just up, down, or cross-convert the files to 1080i29.97 or whatever format he needs? NTSC, 720p60, 1080i60?

OS 10.5.5, Mac Pro 2 x 3 ghz quad-core intel xenon, 9 gb ram, with BM Intensity Pro card

[Naiche Lujan]

I had a similar but probably not exact same issue with footage from a Canon T1i SLR camera with separately recorded audio track.

Here’s the workaround I would have suggested had I read your post earlier.
1. Line up you audio track with either one of your camera angles such that it PLAYS correctly on the timeline.
2. Mute or delete the the original audio track(s) that came with that footage on the timeline.
3. Export timeline as ProRes such that you have a new video clip WITH THE PROBLEMATIC AUDIO TRACK ATTACHED.(hopefully now in sync)
4. Then put that new file along with the other camera angle into a multiclip, choosing audio from your newly created file.

It’s still a mystery why both your and my problems exist, but out of curiosity which device was used to record audio? I wonder if it could be the audio recorders are the source of the problem.

Here’s my post fyi…
https://forums.creativecow.net/thread/200/884720

Naiche

Mac Pro
Dual 2.8Ghz Quad-Core
16GB RAM
ATI Radeon 256MB
320GB 7200rpm
3TB 7200rpm Internal Software RAID0
Blackmagic Studio Card (working good so far)

[Chris Tomberlin]

Hi,

I’m having the same issue with FCP 7.01. I discovered a work around that may help you as well. If you pick your audio source and one of your cameras, merge those clips (using your in points) THEN use that merged clip and your second camera to create a multiclip the audio stays in sync. An extra step and a PITA to be sure, but it works.

Chris Tomberlin
Editor/Compositor/Owner
OutPost Pictures

[Les Arenson]

as crazy as it sounds, we’ve discovered on 7.0.1 that multiclipping 3 cameras and external audio only works when we group by OUT point. IN Point doesn’t seem to hold and audio plays out-of-sync. and of course using AUX TC is useless in FCP.

[Les Arenson]

Try OUT Point

[Guy Carmeli]

Hey guys,

I’m having the same problem on FCP 7.0.2. It does not seem to matter if I sync by IN point, OUY point or TIMECODE. Everytime the audio is 10 seconds ahead.

Has anyone found a solution yet, or is this a bug?