Return-Path: Received: from mail-yh0-f51.google.com ([209.85.213.51] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 5424219 for AE-List@media-motion.tv; Fri, 04 Apr 2014 00:58:14 +0200 Received: by mail-yh0-f51.google.com with SMTP id f10so2417131yha.38 for ; Thu, 03 Apr 2014 15:59:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=H9OF6030VHdvMdoSIxdwyD20PpLtT3O+6hzNQD8qkQg=; b=unkXjNq2g0SAEshHNJisuCv4MxNngYyy7/UP4ZhN4DBktEIP4gDgTXwU4Bu73rW4XE 7GthIVUxrdCiQXvv/Uv9xY9oMcNrS3jYoce7hTTf35olY5H5dts1Eg0uuJTR6JwRBb/1 LnUEFpL2/SnQR+8XpvfwcN8c5YVNwxGVDhz0bB/W/P6rdN6Tra3yvSn32JnXkUlYGrKj nmOBs9HZv4geri1qyMRJzvbUyM0SLdCfGbzjc4LGQJ6pYKlExu88EjetuCFRST2NFZf+ JjxcyJQQ1Op6c8Uy5H52sLeGC5WB0YL3srGoZqcjOJrIwH2ndR3YqooV9/NrZjZxlw29 N2Nw== X-Received: by 10.236.141.113 with SMTP id f77mr4919089yhj.128.1396565981126; Thu, 03 Apr 2014 15:59:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.170.160.6 with HTTP; Thu, 3 Apr 2014 15:59:01 -0700 (PDT) In-Reply-To: References: From: Teddy Gage Date: Thu, 3 Apr 2014 18:59:01 -0400 Message-ID: Subject: Re: [AE] Which output codecs are full 64bit? To: After Effects Mail List Content-Type: multipart/alternative; boundary=20cf303dd22835e3c604f62b5b61 --20cf303dd22835e3c604f62b5b61 Content-Type: text/plain; charset=ISO-8859-1 Looks like .tif sequences actually rendered slower on the benchmark than the raw QT 422 exports, so it doesn't look like a bottleneck after all. Something to consider if you render a lot of sequences. -TG On Thu, Apr 3, 2014 at 11:32 AM, Teddy Gage wrote: > So Stephen Van Vuuren ran the AfterBenchCCbenchmark and came up with a good question, one I had not considered. He > wasn't sure whether the 8 bit 422 raw quicktime export I have set as > default output in the benchmark was actually 64 bit enabled, as AE has had > issues in the past with quicktime libraries. I thought those had been > resolved but maybe not. > > So I have two questions: > > - Is there a better default codec to render to within AE? I wanted to > avoid image sequences because the "render and replace usage" feature is > used several times, and also because it's a bit more complicated for the > end user. I was trying to keep things as idiot proof as possible. > > - What render codecs provide the least bottleneck in terms of output? i.e. > What outputs are fully threaded and 64 bit enabled? Is the QT 8bit 422 > sufficient? One would think that because the renders do seem to use 100% of > available resources when exporting that it is, in fact, 64 bit. > > I am going to be doing some tests with image sequences and DNX export to > see what happens > -TG > > -- > _____________________________ > VFX & Motion Graphic Artist > teddygage dot com > -- _____________________________ VFX & Motion Graphic Artist teddygage dot com --20cf303dd22835e3c604f62b5b61 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Looks like .tif sequences actually rendered slower on the = benchmark than the raw QT 422 exports, so it doesn't look like a bottle= neck after all. Something to consider if you render a lot of sequences.=A0<= div> -TG


On Thu, Apr 3, 2014 at 11:32 AM, Teddy Gage <teddygage@gmail.com&g= t; wrote:
=A0 =A0 =A0So Stephen Van Vuuren ran the AfterBenchCC benchmark = and came up with a good question, one I had not considered. He wasn't s= ure whether the 8 bit 422 raw quicktime export I have set as default output= in the benchmark was actually 64 bit enabled, as AE has had issues in the = past with quicktime libraries. I thought those had been resolved but maybe = not.

So I have two questions:=A0

- Is th= ere a better default codec to render to within AE? I wanted to avoid image = sequences because the "render and replace usage" feature is used = several times, and also because it's a bit more complicated for the end= user. I was trying to keep things as idiot proof as possible.

- What render codecs provide the least bottleneck in te= rms of output? i.e. What outputs are fully threaded and 64 bit enabled? Is = the QT 8bit 422 sufficient? One would think that because the renders do see= m to use 100% of available resources when exporting that it is, in fact, 64= bit.

I am going to be doing some tests with image sequences = and DNX export to see what happens
-TG

=
--
_______________________= ______
VFX &= amp; Motion Graphic Artist
teddygage dot com



--
=
_____________________________=
VFX & Motion Graphic Artist
teddygage dot com
--20cf303dd22835e3c604f62b5b61--