So I’m off for a week, doing production sound on Adrian Langley’s latest project… a ghost story starring former Law and Order: SVU star Adam Beach. I’ll try and post details here as often as possible… here’s hoping the hotel has internet access!
This is another bug, which can cause issues when trying to layback audio from your audio DAW into FCP. FCP bases audio pullup/down on it’s CAPTURE settings, NOT it’s sequence settings.
FCP Capture Settings at 29.97
True 24fps Sequence
What does this mean? If you are working on a TRUE 24fps project (not 24p, 23.976, or 23.98) such as animation, AND your capture settings are set to 29.97 or 23.98, then FCP will pull UP (convert the sample rate), and the file will drift out of sync. Conversely, if you are in PAL land and your capture settings are 25 and you are working on a 29.97, or 23.98 sequence, FCP will pull DOWN the audio, and again it will drift out of sync.
Audio nicely in Sync in PT
Audio Pulled out of Sync in FCP
Notice the redline above the sequence in the pic above? That’s a dead giveaway that FCP is sample rate converting. Use the NO RT function in the sequence menu to check. The workaround solution is the save the audio as an Audio Only Quicktime Movie at the correct frame rate, and import THAT into FCP.
Here’s the Youtube version of the theatrical Ad Trailer for the series Rollbots on YTV (which I mixed/ sound supervised). Music by Serge Cote, Sound Editing by Jordan Bell, Mix and Sound Design by yours truly.
I’ve added a new category and menu item to the site -”Sound Advice”. Sorry about the bad pun, but I really couldn’t think of a better one! In here I’ll put solutions I’ve found for Filmmakers and Sound People about everything from workflow issues, to known bugs in software. My first post below, is on the (in)famous 23.976 OMF problem in FCP. More to come…
A known bug in Final Cut Pro is that OMF’s of 23.976fps (or 23.98 as it’s sometimes called) sequences, report as 24fps sequences when loading into ProTools or other Audio DAW’s.
23.976 OMF Opened in ProTools
This is simply a misreporting of the frame rate by Final Cut Pro. The session IS indeed at 23.976, and changing the timeline to 23.976 will fix them problem.
Notice the Audio is off the Frame line
As always when changing any sync session, sync should be checked. This is easiest when a “two-pop” (a SINGLE frame of bars and tone, exactly 2 seconds before picture start) is included with the OMF.