Who says it's an AE bug? You're looking at this in Quicktime player. What happens if you take the clip into editing application?
Taking it into FCP, I see similar mixed results:
- In the bin, it shows 23.98 fps framerate (correct), just like CMD-I in QT Player shows the correct framerate.
- Opening the clip and watching its timecode or frame number display while stepping through it, it still appears as base 30 with missing frame numbers. The actual frame numbers that are skipped in FCP are different from those skipped in QT Player, though -- so it does seem to be an attempt to correct the timecode to keep up with the framerate.
Exporting the movie from QT Player strips the timecode track, but the frame numbers are made correct. Recompressing through Compressor fixes the timecode track and frame numbers.
Seems like a problem out of AE to me.
Were the Time Display units in the AE Comp set to 24. or if it's available, 23.976?
Comp is 23.976. Project Settings can be 24 or Auto -- same result.
If the comp is set to 24, the rendered movie comes out right -- base24.
I don't have CS5.5 -- does this not happen in the newer release?
That wasn't really the question. Despite the a comp's frame rate, the time display units can be set to 30. In the comp, does the frame before the 1-second mark read 29 or 23?
Aye, that's the Project Settings option, isn't it? Can be set to 24 or 30 (no decimals, as it's just the time base) with the same result.
Timecode display in the AE comp before 1:00 properly shows 0:23