Return-Path: <walter@keenlive.com>
Received: from mail-oa0-f44.google.com ([209.85.219.44] verified)
  by media-motion.tv (CommuniGate Pro SMTP 4.2.10)
  with ESMTP-TLS id 4945724 for AE-List@media-motion.tv; Wed, 09 Jan 2013 20:47:48 +0100
Received: by mail-oa0-f44.google.com with SMTP id n5so1452563oag.31
        for <AE-List@media-motion.tv>; Wed, 09 Jan 2013 11:52:50 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:x-gm-message-state;
        bh=ANiYMyElGMp25H5bOtrBERoK0zH0AajVcqiCiotGuL0=;
        b=gRamTEGk+vMrRRi8SQr3QJbLsMq5whleXQlXx6bVIpA0ASOP/Kx5fZQZ0RnZ03Gw3n
         PJstba6ntqztzUAZUFGwlS1HYst6ZATyg4ONVKblpFeHURDtZcEzhPueR2e9cFNn6M83
         bN/MD2/ft2aeDoKlor5aczRmEmzL8CInVR9i46FsGci4Qf3EofHR/atJ0t0NZGYFpGKt
         IsLqoUWFbmwRLW0WKh6z8/KSPZBISmFuwA1B9ZBH2NHbd9TkB92jIQRgdLlru6nswBNU
         PJhnNMygHwTUatnwRL/fSqoA/ppkI4Iu08EHg1SnSiTGKwWhijdbeIuMG44lyGX3/EFN
         sURw==
Received: by 10.60.0.165 with SMTP id 5mr40717971oef.128.1357761170201; Wed,
 09 Jan 2013 11:52:50 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.171.137 with HTTP; Wed, 9 Jan 2013 11:52:30 -0800 (PST)
In-Reply-To: <list-4945675@media-motion.tv>
References: <list-4945675@media-motion.tv>
From: Walter Soyka <walter@keenlive.com>
Date: Wed, 9 Jan 2013 14:52:30 -0500
Message-ID: <CAEcMUeT4mJeQ+vYXxdQ_EUjiT2rvmQgycPHP3HpobXd=x2MgJw@mail.gmail.com>
Subject: Re: [AE] Comparing speeds from CS4 to CS6
To: After Effects Mail List <AE-List@media-motion.tv>
Content-Type: multipart/alternative; boundary=e89a8ff2535c3d5dc704d2e06845
X-Gm-Message-State: ALoCoQm2icXvuPe6rXznCXISyM1t5NNie4xqZsv/eoLsnaHXn2cmo3+Vjl0yqii4FrSsNfstjzjn

--e89a8ff2535c3d5dc704d2e06845
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Jan 9, 2013 at 2:01 PM, mike cardeiro <mcardeiro@yahoo.com> wrote:

> I am still experiencing bugs with the new cache system (but I love it and
> am still using it).  The bug I am encountering is ae displaying
> pre-rendered frames from the cache even though tiff sequence frames used in
> the sequence have been revised (the workaround is you have to erase the
> disk cache and purge all).


Mike, I'm curious -- are you reloading the footage in Ae (right-click on
the sequence in the project panel, choose Reload footage), or just relying
on Ae to pull the new files from disk?

*Walter Soyka*

--e89a8ff2535c3d5dc704d2e06845
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Wed, Jan 9, 2013 at 2:01 PM, mike cardeiro &lt;<a href=
=3D"mailto:mcardeiro@yahoo.com">mcardeiro@yahoo.com</a>&gt; wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-=
width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;paddin=
g-left:1ex">

I am still experiencing bugs with the new cache system (but I love it and a=
m still using it). =A0The bug I am encountering is ae displaying pre-render=
ed frames from the cache even though tiff sequence frames used in the seque=
nce have been revised (the workaround is you have to erase the disk cache a=
nd purge all).</blockquote>

<div>=A0</div><div style>Mike, I&#39;m curious -- are you reloading the foo=
tage in Ae (right-click on the sequence in the project panel, choose Reload=
 footage), or just relying on Ae to pull the new files from disk?</div><div=
>

<br></div><div dir=3D"ltr"><div class=3D"gmail_extra"><div><div><b>Walter S=
oyka</b>=A0</div></div></div></div></div>

--e89a8ff2535c3d5dc704d2e06845--