From: Rendernyc <rendernyc@gmail.com>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Subject: Re: [AE] Quick AE Render question.
Message-Id: <476BE40F-FCA1-4E87-861A-F5930326EA7D@gmail.com>
Date: Mon, 28 Oct 2013 19:57:12 -0400
References: <list-5266360@media-motion.tv>
In-Reply-To: <list-5266360@media-motion.tv>
To: After Effects Mail List <AE-List@media-motion.tv>

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 se=
e what was the best speed and size format. 16b tiffs were ultimately used an=
d I know for certain that lzw worked back then as we could diagnose our rend=
ers based on file size.=20


On Oct 27, 2013, at 6:51 PM, Chris Zwar <chris@chriszwar.com> wrote:

>> Any ideas here?
>=20
> Is multiprocessing on?   Try turning it off.  I still think that MP is som=
ething 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 / sto=
rage bottleneck as they can get pretty big, pretty fast.  It might be that t=
he 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 l=
arger files that take longer to open.
>=20
> Also, things like motion blur and frame blending can really slow things do=
wn 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 o=
n for the layers, then that could easily account for the long time calculati=
ng the transforms and compositing.
>=20
> -Chris
> +---End of message---+
> To unsubscribe send any message to <ae-list-off@media-motion.tv>