-
Importing Audio – FCP not seeing framerate correctly
I’ve had a lot of issues in the past couple years importing audio from different clients. It is usually 5.1 + 2.0 mixes from Pro Tools. They are mixed as either 23.98 or 25.
I noticed FCP doesn’t always import the audio with the correct framerate (shows green render bar in timeline). It sees 23.98 files as 25, or vice versa. I have noticed sometimes if I am in the wrong easy-setup, it can affect how this audio is imported. Other times, I am in the correct project settings, and the audio still imports incorrectly (green render bar). When it imports incorrectly, the timecode also seems off.
If I import the audio into Adobe Audition, and just do a “save as” without changing anything, the newly saved audio track will open perfectly in FCP with correct sync. It will also magically have the correct timecode to sync to.
I am thinking Pro Tools is exporting these and screwing up some metadata or something. That or FCP is crazy.
Anyone have similar problems, workarounds, solutions? Thanks.
-
6 Replies
-
No the problem is that FCP stamps a frame rate based on your default project settings NOT the current project.
As you will see by searching for Matt Lyons excellent tutorial on why this is so and how to fix a project, this is an almost daily topic here.
-
I did a search but nothing came up. Now that I search “Matt Lyon” some stuff comes up. Thanks. It’s strange because even if I set the easy setup properly, and even quit before it still doesn’t work. I just opened a blank FCP project from scratch, and the media showed up correctly. I’m not sure what’s going on, but at least I have a workaround and can troubleshoot from here.
-
My search for ‘audio sync’ brought up a few thousand posts, with about 50% bweing this very problem
https://library.creativecow.net/lyon_matt/fixing-fcp-assets/1
This is the link to Matt’s tutorial. The second half is more relevant as it describes how to correctly import audio assets to avoid the sync issue.
-
I searched “final cut audio sync 23.98 25” and I looked at a few threads but nothing I thought was relevant. Sometimes it’s about putting the right search terms. I didn’t make you reply to my thread no reason to seem so inconvenienced. I don’t post a lot and often find problems by searching. I realize there is a lot of duplicate questions. So yeah. Chill out a little.
-
[Andrew Dietz] “So yeah. Chill out a little”
Perhaps after answering the same question at least three times a week (and about three times in the past two days) you might share my frustration.
In truth I am more annoyed at Apple for making this such a difficult issue, but I do note names that never post or registered that day, popping in and re-asking this question. I am glad you have previously solved many issues by searching. The combined knowledge of many thousands of posts is a gold mine. Most of what experienced people have shared here is the result of their own initial frustrations, which they solved by searching, reading manuals, experimenting and finally asking then sharing.
Don’t be shy to answer questions that you know the answer to. Having solved this issue for many people, it seems few are willing to then take over the role of this one. So yes, good advice. I am going to chill and leave it to you or anyone else to answer this one from now on.
-
That’s a fair trade. Anyone who asks a ‘dumb’ or highly asked question should have to answer that question the next 5 times it comes up.
Reply to this Discussion! Login or Sign Up