-
Vegas 9 renders 5.1 out of sync?
Ok. I just cannot get Vegas and FCP to play nice together. I finally decided I needed to do the 5.1 out of Vegas, and the picture out of FCP. But when I try to export the audio from Vegas, it’s out-of-sync with the original footage.
Here’s my workflow: In FCP Log and Transfer the .mts in as ProRes 422. But it doesn’t import any more than a stereo version of the 5.1, so, so far, that’s the audio.
In Vegas, import the same .mts, which does (thank god) bring in the full 5.1 audio. Now I render the audio using aif (multiple mono), 48k, 16-bit. This creates 6 discrete 5.1 audio tracks. These can then be brought back into FCP, and I checked, the sequence and the stereo audio is set to 48k, 16-bit.
So now I have the original footage in both programs, and a stereo and now 6 mono .aif versions of the 5.1 audio from the original footage.
They don’t match!
Here they are at the beginning, a couple of minutes in, and by the end of the 5 min. take:
Please tell me what i’m doing wrong.
-
6 Replies
-
Quick fix tho not a reason for why it happens… Control drag the right end frame of the outa sync tracks until they match exactly…
-
Control drag the right end frame of the outa sync tracks until they match exactly…
Can you control drag in FCP and re-time audio like Vegas can? He is working in FCP.
Please tell me what i’m doing wrong.
My first reaction was to say, “you’re using FCP, that’s what you’re doing wrong…” 😉 but I realize that it isn’t helpful. Although… why don’t you just do the whole thing in Vegas and forget FCP? It obviously doesn’t have the features you need to get this 5.1 project completed. I realize that might not be helpful either but, in general, Mac’s don’t play well with others and sometimes it’s best to just acknowledge that fact, and use the platform that has the capabilities you need.
Here is something to try. Bring the aif files back into Vegas and see if they line up with the original 5.1 audio. If they don’t, you can try the control stretch and render them out again. I really can’t explain why they didn’t match the first time because you checked that the files and project matched 48K/16bit which is what I would have said to check.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
Hi, John–
I’m not sure I understand how that help. If I do see that it isn’t the same length, wouldn’t it just render it wrongly again after I correct it? I guess, like you, I completely don’t understand what I’m doing wrong. Is there some difference between the project setting and my render job perhaps? Would that affect it?
Can I ask if you know of any program which would simply extract the audio from the .mts?
-
Well I thought it might help get the file to the correct length not knowing what caused it to be incorrect in the first place. This assumes that bringing that second render back into the project would match it up with the original 5.1. If it was still too long, then something about the render to aif is messing it up.
Hey… what if you bring the rendered aif file back into Vegas and it lines up perfect with the original 5.1 audio? This would point to a problem with FCP interpreting the aif files and not the render at all. (worth trying just to see)
~jr
http://www.johnrofrano.com
http://www.vasst.com -
Well, you got it in one.
So this is what I did. I used txmuxer to demux the .mts into an .ac3. Then I used belight/besweet to convert the .ac3 into 6 mono 16-bit .wav’s, thus successfully extracting the actual matching audio of the camera original. Then I brought all that back into FCP. And guess what — it’s out of sync by exactly the same amount.
It isn’t Vegas at all, but Apple’s lame avchd import feature. I don’t know how — yet — but it’s somehow shortening the video/audio on import.
GRRRRR!
-
Yea, it looked like you did everything correctly on the Vegas side so I kind of suspected FCP. At least now you know where to look for the answer. 😉
~jr
http://www.johnrofrano.com
http://www.vasst.com
Reply to this Discussion! Login or Sign Up