Sync drift on FCP 4 23.976fps QT in PT 5.1.3

[twarren]

I've got a project shot on the Panasonic DVX100 that we posted in FCP 4 at 24p (23.98). We've exported the sequence with a TC window burn in as a QT file for use in PT 5.1.3. Also exported an OMF 2.0 file of the audio.

When we bring the file in and open it it in PT, we finding a drift of from 2 frames at 01:00:00:00 (project starts at 00:58:50:00) to about 6 or 7 frames at around 01:02:35:00.

Both the omf generated regions and the QT file are out of sync with the PT timecode and it's very difficult to tell if they are actually in sync with eachother - though my gut and eye says no.

At any rate, is this a 24fps vs 23.976 issue and is there any way to work around? I can't seem to find a 23.976 frame rate in PT.

Thanks for any help

Taylor Warren

[Noiz2]

do you have the pulldown set correctly? this sounds like the dif.

[davip]

Maybe your OMF has this problem

[twarren]

I initially wondered if it was a pulldown issue. The project in FCP is a 24p timeline and audio was brought in at 16 bit 48k from the producer's camera. The quicktime file was authored directly out of FCP so it is also 24p (really 23.976 as FCP can't do a pulldown on QT export).

Apon importing the omf file into PT I get a session running 16 bit 48k (good so far) and 24 frames per second. But none of the new regions line up with and of the frame markers in grid mode. They're about 1/4 frame off any gridline.

Also I had tried to switch pulldown modes and found that by the end all modes were off.

Session Rate

29.97 fps = session TC five frames ahead of movie burn in at end of sequence
29.97 fps with pulldown = Session TC 9 frames ahead
30 fps = Session TC 11 frames ahead
30 Fps with pullup = Session TC is 5 frames ahead
24 fps (no pulldown options) = session TC is 7 frames ahead

What I'm wondering is whether the PT 24fps is a true 24 frames per second and meant to work with film projects coming from Film Composer or (gasp) a workprint projected on a dubbing stage or if it is 24p resolved to video at 23.976. The problem I'm seeing seems far more like what I would expect from a the .1% diffence in framerate from from true 24p to 23.976. If this is the case is there a way to resolve this timing difference in DigiTranslator?

Thanks for your replies.

Taylor Warren

[Dan Pinder]

I can't say I know how to fix your problem but I can say for certain that 24fps frame rate in Pro Tools is true 24fps. Since we have to wait for PT 6.3 for 23.976, pulling down a 24fps session will effectively do the trick.

[twarren]

Thanks everyone - I figured it was probably 23.976 support but I appreciate the confirmation.

Now I'll just have to scratch the old noggin and try to figure it out or mix in (gasp)FCP.

Taylor