[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.

[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.

[Jaqai Mickelsen]

What is odd is that the audio does sync up if I put everything in a time line manually…with the same inpoints.

V1 – camera 1
V2 – camera 2
A1/A2 – audio

That works. It’s the moment I try to put the three of them in that pesky multiclip does the sky fall. And again, hoping to hold onto multiclip so when they take the selects that still have access to both cameras.

[Jaqai Mickelsen]

Yes, we shot HD on cameras (Not sure which they were to be honest, they Canon SLRs that capture HD with H.264.) The audio isn’t coming from the camera but from a completely independent dat recorder.

[Jaqai Mickelsen]

Hi thanks for your reply – I did that with just one audio clip thinking maybe it was off sync because the audio was 48 and the video’s audio was 44.1. I was trying to get everything exactly the same in an effort to chase down the culprit.

But, you are right – it made no difference. 48 khz vs 44.1 khz = same results for the problem here. I still have the original 48 khz file so will likely revert back.

[Jaqai Mickelsen]

Thanks, but getting it to align isn’t really my issue – We shot with a clapper board, so I have great reference points for syncing. My issue seems to be that FCP won’t play nice with this audio in a multiclip – and I can’t for the life of me figure out why.

It’s ignoring where the inpoint is – but if I monkey around with the inpoint I can get it to sync manually, so the inpoint is having some kind of impact. It’s gotta be something silly right? Some setting/transcoding tweak somewhere?

[Jaqai Mickelsen]

Ok. I realize I’m responding to a post that is from the dark ages…but still, here I am.

I’m dealing with the same issue. I come from “premiere land” and am still getting acclimated to FCP. This “fit to fill” hint worked perfectly for me in FCP 6.

But there seems to be a catch. While it works just fine when I’m previewing it within FCP, once I export the video using quicktime conversion – the “fit to fill” footage is exported as black. I tried exporting a it a few different times trying a few different settings and the results were all the same. Black video.

Any thoughts? I did a google search on this and didn’t find much.

[Jaqai Mickelsen]

Ah. Maybe “looking” at quicktime.com before posting on creative cow would be in order, eh? I see right there a little radio button for Tiger.

How about a round of applause….

[Jaqai Mickelsen]

For Leopard? I should have pointed out I’m still on Tiger. Does that update also apply here?

[Jaqai Mickelsen]

Ok – it gets worse. I’m new on this Mac, and I of course updated QT thinking “well, it wants me to update, and Mac would never betray me like Windows has..”

Well, it did. I’m getting that render error – (right at 10 minutes) but here is why I’m freaked out. I went backwards to the old quicktime (using directions I found on another site using Pacifist) …and I’m still getting that render error despite the fact that in the “About Quicktime” area it’s saying 7.31.

Any additional ideas? (Again, I’m still pretty green when it comes to Mac. I’m a long time Windows user.) I’m already “buying time” with the boss…