[Ali Jassim] "you can prevent that by selecting the option "Preserve frame rate when nested". It means that if you nest 60fps comp into 24fps comp, its layer will stay at 60fps, where any other layers in the final 24fps will run at 24fps. I saw that many times, I've attached a video link on YouTube to see by yourself... He nested three comp (60fps, 25fps and 8fps) into 25fps comp. All nested comps were running at the same frame rates been sett for them in their original comps. They didn't get effect by the final 25fps comp. "
You cannot escape the frame rate of your output comp. It is the rate at which the precomps will be sampled in time. What the "preserve frame rate when nested or in render queue" switch changes is HOW that resampling occurs. When checked, Ae will treat the comp like footage, pulling only "existing" frames from the comp as if it were rendered media, and displaying them at the output frame rate. When unchecked, Ae will re-evaluate the contents of the comp at the time of the containing comp, without being subject to the precomp's frame rate.
In the demo you showed, the 60 fps precomp will show 25 frames in one second with minimal motion blur, but it is skipping 35 other frames every second to get down to 25 fps. The 25 fps precomp will show precisely 25 unique frames in one second with normal motion blur. The 8 fps comp will show 25 frames with lots of motion blur in one second, and it is repeating 17 frames every second to make up the difference between 8 and 25.
Check out this demo, where I expand upon the demo you showed:
10693_preserveframerate.aep.zip
Again, maybe this would be easier to explain in the context of your practical question.
Walter Soyka
Designer & Mad Scientist at
Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive [twitter] |
RenderBreak [blog] |
Profile [LinkedIn] 
