Return-Path: <dow.hanson@gmail.com>
Received: from mail-we0-f182.google.com ([74.125.82.182] verified)
  by media-motion.tv (CommuniGate Pro SMTP 4.2.10)
  with ESMTP-TLS id 5452458 for AE-List@media-motion.tv; Thu, 24 Apr 2014 19:30:19 +0200
Received: by mail-we0-f182.google.com with SMTP id q59so2591501wes.27
        for <AE-List@media-motion.tv>; Thu, 24 Apr 2014 10:30:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=+P4iYNQ7uW1ZLDhMwzruyBUYtjRZgWD7CmE53GEypUE=;
        b=kQ/gOjPGYKR8gOci9JBW/jWIQVTALS4Aji3ArDrq+Ab7lwxh/iYlAueBzfrdJvZ/Fo
         kRTp0gUpD1HEs3cBkyKyyWD2JSq+pTlom62hQArzi7XkJzWbZG3lrXLxa+LAyNYnjVBB
         wnuSgF4GPDImoo2fBSX9/e+nPvPGipzqWroPUStM0P8n3QtOfo6OnBBowAgsxpEqMYVF
         LchGv7A8dM0nYK4OX3Nj7M2APv0N308SWMMwx02gg3pEooX6lrhNNFUwlCdp9uEbqwAx
         XYg1D9ZvIkpOK3tph2ss2QTBjXaEg25zCUFqWeA5/YYFziE27URMXtfICNKEV5iPXBSc
         mqgw==
MIME-Version: 1.0
X-Received: by 10.180.109.69 with SMTP id hq5mr55716wib.30.1398360618951; Thu,
 24 Apr 2014 10:30:18 -0700 (PDT)
Received: by 10.217.161.68 with HTTP; Thu, 24 Apr 2014 10:30:18 -0700 (PDT)
In-Reply-To: <list-5452447@media-motion.tv>
References: <list-5452447@media-motion.tv>
Date: Thu, 24 Apr 2014 18:30:18 +0100
Message-ID: <CAP6LaPzeaJdvGsNzbGsGk5BQ07VaqZ9JZHAWmGW=Gu80A1SiPg@mail.gmail.com>
Subject: Re: [AE] render second output module as QC render: reliable?
From: D <dow.hanson@gmail.com>
To: After Effects Mail List <AE-List@media-motion.tv>
Content-Type: multipart/alternative; boundary=e89a8f3baa07f5eb2404f7cd33ce

--e89a8f3baa07f5eb2404f7cd33ce
Content-Type: text/plain; charset=UTF-8

If bad frames do occur you can just re-render the bad frames.


On 24 April 2014 18:10, scott.aelist <scott.aelist@gmail.com> wrote:

> I'm rendering some large 4k tiff sequences in the evening and I want to
> check them to make sure there aren't any errors. So I render a separate
> quicktime that is viewer-friendly so that I can check them. A coworker
> suggested to me that my quicktime may render fine, but that AE could write
> bad TIFF frames and I'd never know it. He things to be 100% safe I should
> first render my TIFF sequence, and then re-render that sequence as a
> quicktime. What do people think?
>
>

--e89a8f3baa07f5eb2404f7cd33ce
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">If bad frames do occur you can just re-render the bad fram=
es.=C2=A0</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote=
">On 24 April 2014 18:10, scott.aelist <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:scott.aelist@gmail.com" target=3D"_blank">scott.aelist@gmail.com</a>&gt=
;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>I&#39;m rendering some=
 large 4k tiff sequences in the evening and I want to check them to make su=
re there aren&#39;t any errors. So I render a separate quicktime that is vi=
ewer-friendly so that I can check them. A coworker suggested to me that my =
quicktime may render fine, but that AE could write bad TIFF frames and I&#3=
9;d never know it. He things to be 100% safe I should first render my TIFF =
sequence, and then re-render that sequence as a quicktime. What do people t=
hink?<br>


<br></div></div>
</blockquote></div><br></div>

--e89a8f3baa07f5eb2404f7cd33ce--