24p OMF from FCP

i just got a film delivered at 24p. the editor and director are certain that their projects were done at 23.98 and the footage was digitized this way from the Deck. the QT is telling me 23.98. but the DIGI TRanslator tells me the OMF is 24. when i import the OMF, the 2 pop is at 01:00:06:00 for reel 01. when i leave the session at 24, the 2 pop is not on the grid. when i change the session setup to 23.976, the 2 pop is smack dab on 6 seconds. all of of my other HD stuff canme from AVIDS. their OMF's came in at 23.976. any reason why DIGITRANSLATOR thinksn that this FCP OMF is 24? i beleive he is using normal pulldown mode in FCP. thanks!

Because it is from FCP? Dunno.

hi richard! i am guessing that it does have something to do with FCP -- that it is somehow less robust. but i dunno either. i just watched the reel down at 23.976 and everything is in sync.

Had the same problem recently. Damn FCP. I slid the audio till the 2 pop matched up with video, checked the tail pop and it was in. My pic was off a tape that was NTSC 29.97ND diged in on a Aurora Igniter LT. I thought it was out because of the video transfer. Who knows. Can you imagine, an entire post facility based in FCP. They are building a mix room based on Logic. I can hardly wait...

I haven't tried a 23.98 export from FCP but I have tried 23.98 as well as 24 frame (24p) exports from Avids and they open up properly in Pro Tools. In other words, DigiTranslator and Pro Tools see both 23.98 or 24 frame OMF's properly. Does FCP do AAF exports? If so, you may want to try that too. Jon Connolly Digidesign Product Specialist

hi john, well, i know what you are saying. i get 23.98 OMF's from AVID's and they translate fine. FCP seems the culprit here. or, perhaps it is editor error. but i doubt it. i dunno if FCP does AAF. he has FCP 5 and i only have 4.5. but i will check that to see what i can see. thanks!

Got off on a rant there...sorry. More to the point, the OMF from FCP supposedly was 23.98, but showed up in digitranslator as 24. Its probably FCP. And there was a point. Despite the omf coming intoPT out of sync, I was able to shift it into sync and it did not drift.

no worries, charles! i was picking up what you were puttin' down! i see how things are going, pretty soon it won't be logic, but garage band rooms, and they'll wonder why they can't get their rig to chase LTC properly, or resolve to tri-level sunc WC. and i did get your point about once you fixed it, you were fine. once i changed my timeline, i was fine. no sliding, nothing. it is just puzzling. and, ah korse, ya want every thing ship shape when you do these things. i wanna make sure that the HD layback and Dolby PM goes off in sync, without a hitch! ..so, i thought maybe someone knew of this and could explain it, or maybe, the editor needs to recheck his settings.

I found the same thing today. A project from FCP OMF said 24p, one of the editors confirmed it was 23.976 (which is what the camera was shooting at.) Then one of the other editors called me just to confirm that I was ND not drop frame. I told her that it would be however the OMF was given to me. After I hung up I realized that there is no such thing as 23.976 df. Back to FCP, I have no sync issues (OMF w/QT) after spotting picture to the head, but I figured that the OMF just read "24p" but was actually 23.976.

Hi, this might be a little off-topic, but I (and probably most of us) can see problems with exchanging OMFs to or from non Digi/Avid apps. Example: Omf from Avid, import to Logic - problems, wrong edits, renders and so on. Solution: open Omf in ProTools and export as OMF again. Result: Omf in Logic opened correctly. So, maybe you should try to open this Omf in Avid, and than export it again as Omf. I know that it is another conversion, but it might help. Best Kuba