In CS3 on the PC. I have an image seq rendered out at 24fps. Final delivery will be an image seq at 24 fps.
But for review I built out quicktimes. I have imported the seq at 23.98 into a 23.98 comp to render a QT at 23.98fps.
In this comp frame one is slated text.
Frame two is when the image seq starts.
This rendered quicktime produces a stutter or random hold frames.
Now when I take the same comp but have the image seq begin on from one, the quicktime is flawless.
I have recreated this in AE7 and have no problems. Only in CS3.
Please see if you can recreate the problem.
My solution for now is to add a one frame handle on the head of the image seq. So the imported seq. starts on frame one and not frame 2.
I lost tons of time trouble shooting this, hope this helps, maybe someone else can chime in here.
Re: CS3 23.98 bug? by Dave LaRonde on Feb 9, 2008 at 1:40:33 am
[Anthony Dupsta]"Does it play back jerky. "
Right now, there's no no way to tell if playback will be jerky -- is this comp HD or SD? There's a big difference. A HUGE difference.
An SD file in Photo JPEG just might play back smoothly on most current hard drives, but I make no guarantees whatsoever.
An HD file in Photo JPEG definitely will NOT play back in real time: it's got at least five times as many pixels per frame, so the necessary bitrate is at least five times bigger. You'd definitely need a speedy striped array for that chore.
Re: CS3 23.98 bug? by Anthony Dupsta on Feb 10, 2008 at 4:25:26 am
Have you tried to re create it. In this case weather it is HD or SD is not the issue, it is not a bitrate issue. Again, the issue is what looks like a hold frame. When framing forward and watching your burn in counter, I can see the frame counter is moving but the quick time has a bunch of hold frames which give it that strobe feel. I think it is a bug in CS3. Again, just try to set this up SD or HD in AE8:
Comp is 23.98.
Image seq is imported at 23.98
23.98 Frame counter to help verify the frames.
Start image seq at frame 2 of comp.
Render QT photo jpeg.
Again, this same set up works perfect when the image seq starts at one, it only strobes when images seq starts at frame 2 of comp.
I have tested this on three diff systems, and one being a mac.
AE7 is the only one that will render out a 23.98 QT the way I have it set up.
I just want to verify that other people are getting this hic up.
Re: CS3 23.98 bug? by Dave LaRonde on Feb 15, 2008 at 6:44:36 pm
Here's a new thought on your render woes:
If you actually made an AE comp at a frame rate of 23.98, change it!!!! Right now!!!
Although many edit systems and even cameras refer to the NTSC film frame rate as 23.98, it's a misnomer. The actual frame rate they use is 23.976 frames/sec.
So why do so many things refer to 23.976 as 23.98? Shorthand, probably... or perhaps they think people will freak out when they see a frame rate taken to three decimal places.
In AE, on the other hand, 23.976 MEANS 23.976. AE has been around far longer than current editing software and gee-whiz cameras. It has always referred to the NTSC film frame rate as what it actually is: 23.976 frames/sec.
So if you rendered an AE comp at 23.98fps, AE obediently made a 23.98fps file. It did NOT make a 23.976fps file. With the 23.98-23.976 confusion, it's easy to make the mistake.
Re: CS3 23.98 bug? by Anthony Dupsta on Feb 15, 2008 at 9:24:28 pm
Dave or any other brave sole,
If you have a copy of AE8, do me a favor.
Make a comp at 23.98 or 23.976 it does not matter in this case.
IT can be SD or HD also.
Import an image sequence.
start the image sequence on the second frame in the comp. so the first frame is blank.
Render out a QT, lets say Photo jpeg.
Play back the QT and verify the hold frame or strobe playback.
Your image sequence will need some movement to see the hold frame.
