|
|
Posted by Martin Heffels on 10/06/41 11:33
On 1 Dec 2005 10:16:47 -0800, "etrenkamp" <etrenkamp@yahoo.com> wrote:
>I still find it disconcerting that FCP keeps doubling it's estimate
>every time I cancel the render. And even if the render time estimate
>is accurate, it still shouldn't take four days to render a 40 minute
>sequence.
That is quite long. Sounds like you FCP is very screwed up. I don't know if
it keeps track of previous render-times (I know for instance Combustion
does remember how long the previous render was, and uses that as an
estimate), and uses that as base to calculate the render-time.
Not that this which I write now, brings you anything, so just for fun :)
With Combustion 4 I recently rendered a 21 minute sequence of DPX-still
images, uncompressed, full size PAL SD, 10-bit, with colour-correction,
1:85 mask and some vertical shifting (reframing), to an uncompressed
QT-file, on a Pentium mobile 1.7 with 1GB to an external firewire-drive, in
17 hours. So, I would say double the time for you, and your computer is
probably faster than mine, so that should be shorter.
>Is there anything else anyone can think of that would be causing this
>problem?
As was already mentioned, erase all the render-files with the media
manager, and restart the rendering. In general it is a good idea to erase
all the previous render-files anyway, before you do a final render, because
sometimes you can stack codec-errors on top of each other, leading to
errors in your finished product. This will increase your render-time
though, as FCP can't smart-render anymore.
cheers
-martin-
--
"If you go through life convinced that your way is always best,
all the new ideas in the world will pass you by." Akio Morita
Navigation:
[Reply to this message]
|