Rick Nweg
Forum Replies Created
-
-
Hey, the first thing i noticed after updating to 2015 was that the RAMPreview did not stop by clicking somewhere in AE (which it did before). In order to recreate your problem, i quickly generated a testscene with a lot of DOF, which usually takes a lot of time to render. As before “2015” the first run was slow, not realtime in order to render the frames into RAM. But as long as i did not change anything, it ran in realtime during the second runthrough. When i change something during RAMPreview (which was not possible before), AE needed to calculate again, resulting in a slow playback again.
Only sometimes i noticed the RamPreview not running in realtime during the second (or third) runthrough, although i did not change anything…
cheers,
kws -
i will try this. thx!
get back to you later…
-
-
https://dl.dropbox.com/u/2605990/20120621110205.png
as i sayd: the only effect i use is trapcode 3d-stroke. can’t find anything about ed stroke and mp…
thx
kws -
i can think of two possibilities: either it is done with a bit of motiontracking, some expressions and LOTS for manual work…
or it is done in a 3d-software (maya) with the text as textures or instanced paricles… and still a lot of work…
but actually, i have no idea…
hf&gl
kws -
but if you render it in 16bit you also need a container and a codec that supports 16bit, don’t you? or can you render 16bit in eg h264-codec?
-
ps: the ai footage is imported as comp with layers from a ill CS2 file…
the error messages come just at parts where this footage is used… -
well,…
you could find this out on your own,
but i tell you, i -
well,…
you could find this out on your own,
but i tell you, i