From: "Py Fave" Received: from mail-ot0-f181.google.com ([74.125.82.181] verified) by media-motion.tv (CommuniGate Pro SMTP 6.1.0) with ESMTPS id 6399600 for AE-List@media-motion.tv; Sat, 03 Feb 2018 18:25:39 +0100 Received: by mail-ot0-f181.google.com with SMTP id l5so17188613otj.11 for ; Sat, 03 Feb 2018 09:28:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=aWvB/XEVpOE0XBBYiCdZxm1ibVf2J1JpJpQPyxPzwYU=; b=TPAszGg8FkDBtuopWhumCKMGN5rnUc42VxU8Ipt0g3QxpKK9s5iKdBUz0pLIYu7dM8 t2BFiKV727Q1aDBqhzUIbwPYqBeBLuUfq04w9lg1shu/Z0Cqm72Hogz+0KvbYm18qmO7 wIi1cWNX+gVAj8dryvg5lwJRq0o1jqQP2NvDOnSq3wd8pqTNo2WMiw1K3OrtXLmimoMk OmaatD33uWpldi9bAfidA2th+xADTnPOMiS5Yfpy5FzP4undfHwgtCcEpyNwa7igNbjU qj03vO2E/qPgT4GVoMzvFP7eFy6lcBcwrB5m1h6syltKgkzDYK+o1lu84Kc4KA+MX7f/ BtWA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=aWvB/XEVpOE0XBBYiCdZxm1ibVf2J1JpJpQPyxPzwYU=; b=gt7QpYn4GXM/KcQc1dpq7el2i2/1+PFq6FMs/H2fGqKtlA5BcbkFl2/FWnmW1KwBsD j32gfgS7gsURoNxivvpKFHJHMrzZz2S+85bo72dwgSvKxEPpCsxBdCasFTta90HJ9fPH WJDnUkSaLji51+OcdFjTZ02bTMscpkBxM1Oc60feZ1nBK/DqCSRxCVJ7jyIUrKoBD1Gb /pT9kwCtXnxOjNzwAeLDKtTj2K6Ql3MQ+Z7BpibfaTJQy09KRiGjtDoOEadse7D4J9+G kHrySQY6Q/Htlp+ALDCAivpprknJStfUHY5ooCjip7MUf42zQzO/nD7gISMaRzeoicPj 4dLQ== X-Gm-Message-State: APf1xPCKbGOyrHkijYCaALq2XrFSG7gxNcDzSF4nTOslMc6gMwLWy6HR 93cwUzPcOieRe2gToM7mctR7bTOIRXwnu36U9Sk= X-Google-Smtp-Source: AH8x226m+dducXHyuF/1rI73HxrYmtSS3mGrR8cQ3fVk6Ipunr9wDu0YxEAk/Tf3pE4afPkfY7z4YCqPU+aFgoguCvo= X-Received: by 10.157.27.145 with SMTP id z17mr8683223otd.285.1517678923190; Sat, 03 Feb 2018 09:28:43 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.14.162 with HTTP; Sat, 3 Feb 2018 09:28:42 -0800 (PST) In-Reply-To: References: Date: Sat, 3 Feb 2018 18:28:42 +0100 Message-ID: Subject: Re: [AE] AE not clearing image cache To: After Effects Mail List Content-Type: multipart/alternative; boundary="001a1144fa861994af0564522947" --001a1144fa861994af0564522947 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable i had problems with caching of precomps with different fps. was on 2017.2 i solved it by using proxies. but it's bad and never happened on previous versions. (i mean 2014 and cs) check for time remapping keys, or keys wich are note at the exact frame time (this occurs when changing framerate,f.i.) 2018-02-01 15:45 GMT+01:00 Jarret Langmeire : > Thanks Chris. I've checked all pre-comps and unfortunately all checks out > and is as it should be. I've not yet made the move to 2018 either but am > wondering whether now's the time. > > On 1 February 2018 at 11:16, Chris Zwar wrote: > >> Sorry but no. I can only sympathise. Sometimes you just have to wait >> for a while and then it figures it out after a few minutes. >> The cache has been driving me nuts lately, I haven=E2=80=99t started usi= ng CC >> 2018 yet but 2017 has been really problematic. I actually wonder if it = is >> just the cache or if there are deeper issues with the playback system. >> Sometimes it feels like AE is running two or three things at the same ti= me >> and they=E2=80=99re all out of sync. >> >> I have a project for sale on videohive that seems especially good at >> breaking the cache system. For a while it was so unreliable I wondered = if >> I could even offer it up as a retail product. >> >> FWIW I don=E2=80=99t use a disk cache. >> >> Of course there=E2=80=99s always the possibility the one-frame is meant = to be >> there. Check for shy layers you=E2=80=99ve forgotten, effects that refe= rence other >> layers, motion blur (this is a biggy for artefacts that only show up in >> final renders) , check things like composition shutter angle and phase. >> Frame blending can also cause funny results for 1 frame. >> >> -Chris >> >> > On 1 Feb 2018, at 8:31 pm, Jarret Langmeire >> wrote: >> > >> > This is driving me batty. I've got a massive comp and there's a >> one-frame glitch appearing at the same spot. When I go through each of t= he >> pre-comps there is absolutely no reason for the glitch. When I drop in a >> 1-frame black solid, that solid doesn't show in the RAM preview nor in t= he >> render ie. for some reason that 1 frame is persisting in AE's image cach= e. >> > >> > I've cleared the cache via the menu (including the disk cache) and hav= e >> also manually deleted all disk cache files but that damn glitch persists= . >> Does anyone have any idea what might be going on? >> > >> > Many thanks >> > >> > >> > -- >> > >> > Jarret >> >> >> +---End of message---+ >> To unsubscribe send any message to >> > > > > -- > -- > > Jarret > --001a1144fa861994af0564522947 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
i had problems with caching of precomp= s with different fps.
was on 2017.2

i solved it by us= ing proxies.
but it's bad and never happened on previous versi= ons. (i mean 2014 and cs)

check for time remapping keys, or ke= ys wich are note at the exact frame time (this occurs when changing framera= te,f.i.)

2018-02-01 15:45 GMT+01:00 Jarret Langmeire <AE-List@media-motion.tv>:
Thanks Chris. I've checked all pre-comps and unfor= tunately all checks out and is as it should be. I've not yet made the m= ove to 2018 either but am wondering whether now's the time.

= On 1 February 2018 at 11:16, Chris Zwar <AE-List@media-motion.tv= > wrote:
Sorry but no.=C2=A0 I = can only sympathise.=C2=A0 Sometimes you just have to wait for a while and = then it figures it out after a few minutes.
The cache has been driving me nuts lately, I haven=E2=80=99t started using = CC 2018 yet but 2017 has been really problematic.=C2=A0 I actually wonder i= f it is just the cache or if there are deeper issues with the playback syst= em.=C2=A0 Sometimes it feels like AE is running two or three things at the = same time and they=E2=80=99re all out of sync.

I have a project for sale on videohive that seems especially good at breaki= ng the cache system.=C2=A0 For a while it was so unreliable I wondered if I= could even offer it up as a retail product.

FWIW I don=E2=80=99t use a disk cache.

Of course there=E2=80=99s always the possibility the one-frame is meant to = be there.=C2=A0 Check for shy layers you=E2=80=99ve forgotten, effects that= reference other layers, motion blur (this is a biggy for artefacts that on= ly show up in final renders) , check things like composition shutter angle = and phase.=C2=A0 Frame blending can also cause funny results for 1 frame.
-Chris

> On 1 Feb 2018, at 8:31 pm, Jarret Langmeire <AE-List@media-motion.tv> wrot= e:
>
> This is driving me batty. I've got a massive comp and there's = a one-frame glitch appearing at the same spot. When I go through each of th= e pre-comps there is absolutely no reason for the glitch. When I drop in a = 1-frame black solid, that solid doesn't show in the RAM preview nor in = the render ie. for some reason that 1 frame is persisting in AE's image= cache.
>
> I've cleared the cache via the menu (including the disk cache) and= have also manually deleted all disk cache files but that damn glitch persi= sts. Does anyone have any idea what might be going on?
>
> Many thanks
>
>
> --
>
> Jarret


+---End of message---+
To unsubscribe send any message to <ae-list-off@media-motion.tv>



--
--

Jarret

--001a1144fa861994af0564522947--