[Tyler Williams]

I think that may have been the case with the quicktime that I exported for the sound editor. I sent it through Compressor but left it as current assuming that Final Cut would actually do it’s job. How silly of me. Running it through Cinema Tools afterwards got it working properly as 23.976 in ProTools.

Now a similar thing is happening with the OMF export, where ProTools interprets it as 24. I’m seeing lots of similar posts describing this being a problem with OMF’s sent out of 23.98 FCP sequences. Next time I’m in session I will have her try importing it as 24 and then changing the session to 23.976. It will then have to be transferred into our existing session with all of our ADR work, but I imagine that shouldn’t be a big deal.

I’ll try to keep the thread updated with my results.
Thanks.

[Tyler Williams]

Thanks, Robert.

I’m on 7.03 as well. My sequence is 23.98 but when I export the OMF and bring it into ProTools it opens as 24fps. Very frustrating. Strangely, this happened when I exported my timecode screener for them as well. ProTools thought it was 24 when it wasn’t. I had to run it through Cinema Tools and conform it to 23.98 before ProTools would accept it. Unfortunately I can’t do the same for my OMF export.

It’s definitely some kind of miscommunication between FCP and ProTools I just can’t figure out how to fix it. I’ll keep trolling the forums.

Thanks again.

Mac Pro 2 x 2.93 GHz Quad-Core 14GB RAM
NVIDIA GeForce GT 120
Matrox MXO2 LE
Firmware V 24.0
Software V 1.8.1.0009

OSX 10.6.2
Final Cut Pro 6.0.6

[Tyler Williams]

I am having this exact problem right now. Did you ever find a solution?
Thanks.

Mac Pro 2 x 2.93 GHz Quad-Core 14GB RAM
NVIDIA GeForce GT 120
Matrox MXO2 LE
Firmware V 24.0
Software V 1.8.1.0009

OSX 10.6.2
Final Cut Pro 6.0.6