| ||||||||||
| Since when does lzw not work with 16 bit tiffs? I worked in a project back in cs4-5 days where every output was tested to see what was the best speed and size format. 16b tiffs were ultimately used and I know for certain that lzw worked back then as we could diagnose our renders based on file size. On Oct 27, 2013, at 6:51 PM, Chris Zwar <chris@chriszwar.com> wrote: >> Any ideas here? > > Is multiprocessing on? Try turning it off. I still think that MP is something of a black art to get right. There are some cases where MP is slower than normal / single processor rendering and I guess it's related to memory. > If your source files are 16bit tiffs then it could also be a network / storage bottleneck as they can get pretty big, pretty fast. It might be that the drive with your tiffs on it can't keep up with multiple processors asking for multiple images. > Also, when using 16 bit tiffs make sure LZW compression is turned off. It only works for 8 bit tiffs, and having it on for 16 bit tiffs will create larger files that take longer to open. > > Also, things like motion blur and frame blending can really slow things down and you won't notice them until you're rendering at best quality. If you've been working and previewing without motion blur on, but have it turned on for the layers, then that could easily account for the long time calculating the transforms and compositing. > > -Chris > +---End of message---+ > To unsubscribe send any message to <ae-list-off@media-motion.tv> |
