No, has nothing to do with the out point. No renders out of Final Cut, we’re all accessing the same source.
I export an Automatic Duck XML which gets imported to an After Effects project. Source reconnects. The AE comp is the right length. There’s a lo res reference edit to confirm that everything matches to the frame. I go in and difference mode the reference edit to the hi res footage to make sure. I render out a QT movie import it into Final Cut and it lines up perfect.
I pass the shot off to an animator. They do their thing. If they render an image sequence of the comp it comes out the right number of frames. If they render a Quicktime about 50% of the time it imports into Final Cut a frame short. The shots are missing frames in Quicktime as well, which obviously makes you think it’s an After Effects issue, but I know there are people out there that have similar problems with Combustion too – even Color. Think it’s therefore a Quicktime/FCP issue.
If an animator renders out the shot on his machine sometimes it’ll come in a frame short… then I’ll tell him to add a frame to his comp and when he re-renders it it’ll come in a frame LONG. Like it got the missing frame back and another frame. Bizarre. Again, this has happened at numerous studios on numerous machines in numerous codecs. If the computer has FCS installed on it it does not seem to happen. It has happened on machines that don’t have FCS installed but have the Apple Pro Res codec installed, or Uncompressed 10 bit 4:2:2 installed.
I’m surprised that nobody here has run into it… all the editors I’ve talked to personally (that do a lot of fx heavy work) say they know about it but not why and just deal with it with handles.