From: "Chris Zwar" Received: from mail-pf0-f195.google.com ([209.85.192.195] verified) by media-motion.tv (CommuniGate Pro SMTP 6.1.0) with ESMTPS id 6371197 for AE-List@media-motion.tv; Fri, 15 Dec 2017 04:04:18 +0100 Received: by mail-pf0-f195.google.com with SMTP id e3so5152549pfi.10 for ; Thu, 14 Dec 2017 19:08:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chriszwar-com.20150623.gappssmtp.com; s=20150623; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=NuRGuCeqnJxU22siw2O1v+O6/f8gAenH7q61kSF3gY0=; b=ykcwDuQiwGGzavvFOVwq6SuPrIvwb2AlkVlZSdFrJiyNWtF+8dohl52pJSrjJQTWiU Ij5PyYS5HfbMwf2SXgOZMWQPb9nAijnkKgkwbhna4hB1J+VNg2Fp8JPSLEzh5OrvXMIY 9HO6D2nvHReaI7WlQQ8qqTtor6VWRzEZalDWx/fhubhkaMTMG55ytBiy2FU8ZFgiW0w1 /ZzUh+VLDxtP5r38OlB8AUtV8/KbH+lLb+UT3vGvxcnSQasVD8qmKzAQx8t9Rxa2n7bd bn2HA+pGc13odpEbE7vk4KqpY8qI8VS6/LsoEH/MYSXkTTn9PlTTY0xNM97GpP/kyuD+ 4o4A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=NuRGuCeqnJxU22siw2O1v+O6/f8gAenH7q61kSF3gY0=; b=XZ2XoabZjyV/1Kqg8kJ4lMiGbJ0KqbT3ZN3wS0RphNZUpMmvmgsE5WKyxqwuoJ7P+d GVBNB+0huBkRM+vXBlmF8mSOLKEnpXLNcvyXJqS/20AwwFUnNcz8fThNI4Hdvo+1C7Uw NuAShN2lJJLrGNTLTCXUxiLjEqyGa4PGZ01b1jiwGfOp8awjj8FsLOVGtYKv8tXd2K4b gXOndD40FSy7M/gsQuf3S3UnTH0Fann0z7VHeXxB1lLoc3DBX4Z3Ti5Va5/oOdVYv3nf LEhUjxFneveRSAzLXu60nxouh99WA38RTAC1MLrsk94iJB0vssfL3C0SY56t0x9h+gHd kTaQ== X-Gm-Message-State: AKGB3mLXRYXo1CP6HFDoMPG1nfUrEOj5fHCWpuax+dw7S9JEKGQJknrS QsFESgVPMkLuhRRIX7igdiABsyVBFxg= X-Google-Smtp-Source: ACJfBotWR68aIqfvFDCjXKFYYfvLrEICboYIZnpGidfprcIBITiCWhUAGCPn9XgGIy7y6ijfDVPZvQ== X-Received: by 10.98.36.199 with SMTP id k68mr11666074pfk.236.1513307312424; Thu, 14 Dec 2017 19:08:32 -0800 (PST) Return-Path: Received: from [192.168.0.149] (7.130.233.220.static.exetel.com.au. [220.233.130.7]) by smtp.gmail.com with ESMTPSA id z5sm8639477pgb.6.2017.12.14.19.08.30 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 14 Dec 2017 19:08:31 -0800 (PST) Content-Type: multipart/alternative; boundary="Apple-Mail=_E0CF07C9-09DA-4EE3-8DB6-48A43589F0F5" Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: [AE] Cache bugs with expressions Date: Fri, 15 Dec 2017 14:08:26 +1100 References: To: After Effects Mail List In-Reply-To: Message-Id: <911E9967-0353-4453-85FB-161E96C0E83E@chriszwar.com> X-Mailer: Apple Mail (2.3445.5.20) --Apple-Mail=_E0CF07C9-09DA-4EE3-8DB6-48A43589F0F5 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hmmm. Yeah I've definitely had cache issues before, and I guess that=E2=80=99s = why the purge option exists, but I=E2=80=99ve never seen anything like = this, where AE seems completely oblivious to major changes in the = timeline. I do think there are some issues related to guide layers and = layers that are turned off but are still used for calculating = expressions. =20 I=E2=80=99ll try and pin it down further, but AE definitely seems to = fail when it comes to noticing that a layer should be updated because an = expression has been re-calculated. > On 15 Dec 2017, at 1:54 pm, Stephen van Vuuren = wrote: >=20 > Same here =E2=80=93 cache problems constantly and not real patterns or = easy to reproduce. Mostly on 2014/15 so don=E2=80=99t even both to file = bug reports. Just got to power through until film is done. > =20 > Best, > =20 > stephen van vuuren > 336.202.4777 > =20 > http://www.insaturnsrings.com/ > =20 > A film is =E2=80=93 or should be =E2=80=93 more like music than like = fiction. It should be a progression of moods and feelings. The theme, = what=E2=80=99s behind the emotion, the meaning, all that comes later. > =E2=80=93Stanley Kubrick > =20 > From: After Effects Mail List [mailto:AE-List@media-motion.tv = ]=20 > Sent: Thursday, December 14, 2017 9:52 PM > To: After Effects Mail List > > Subject: Re: [AE] Cache bugs with expressions > =20 > I've had numerous cache issues with 2014, 2015, 2017 (haven't pushed = 2018 yet). Not just with expressions either, it happens with plain = timelines, convoluted timelines. No rhyme or reason. It just loves to = hold onto old cache data. I can't replicate it, it just does it when it = wants to. I just learned to keep the Purge All Cache shortcut handy. = "Ctrl + Alt + /" on PC. >=20 > David Torno > 818.391.6060 > -------------------- > www.sydefxink.com (work history) > https://vimeo.com/davidtorno (work = samples & breakdowns) > https://gumroad.com/davidtorno > http://provideocoalition.com/dtorno = (tutorials) > =20 > "The most useless day is that in which we do not laugh" > -Charles Field >=20 > On Dec 14, 2017, at 6:12 PM, Chris Zwar > wrote: >=20 > I=E2=80=99m playing round with a project that is based on an = expression and I=E2=80=99m running into lots of cache bugs. I=E2=80=99m = currently using CC 2017.=20 > I=E2=80=99m just wondering if others have come across similar problems = and if there are any workarounds. >=20 > The project I have uses a fairly lengthy expression which is applied = to a text layer. The expression is also reading values from a slider. = Other layers are then reading the output text of the text layer (ie the = expression results) which controls their time-remapping values. >=20 > It doesn=E2=80=99t take much for AE to stop working properly. I can = move sliders around and nothing changes. I can completely change values = and yet the RAM preview will play the same thing over and over. I can = delete all keyframes, so in theory nothing should be moving at all, yet = scrubbing in the timeline still shows things moving around. >=20 > Basically, what I am trying to do is totally breaking AE=E2=80=99s = cache system. >=20 > While I will report my problems to Adobe and will send them a project, = I am wondering if there are some simple steps to avoid these issues. > Does anyone know if making layers shy, or setting them to guide = layers, effects the way the preview system works? In previous versions, = enabling motion blur has fixed cache bugs but this doesn=E2=80=99t seem = to be the case here. I can RAM preview something and set the same thing = off as a BG render and get two different results=E2=80=A6 >=20 > Any suggestions? >=20 > -Chris > +---End of message---+ > To unsubscribe send any message to > >=20 --Apple-Mail=_E0CF07C9-09DA-4EE3-8DB6-48A43589F0F5 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hmmm.
Yeah I've definitely had cache issues = before, and I guess that=E2=80=99s why the purge option exists, but = I=E2=80=99ve never seen anything like this, where AE seems completely = oblivious to major changes in the timeline.  I do think there are = some issues related to guide layers and layers that are turned off but = are still used for calculating expressions.  
I=E2=80=99ll try and pin it down further, but AE definitely = seems to fail when it comes to noticing that a layer should be updated = because an expression has been re-calculated.

On 15 = Dec 2017, at 1:54 pm, Stephen van Vuuren <AE-List@media-motion.tv> wrote:

Same here =E2=80=93 cache problems constantly and not real = patterns or easy to reproduce. Mostly on 2014/15 so don=E2=80=99t even = both to file bug reports. Just got to power through until film is = done.
 
Best,
 
stephen van = vuuren
336.202.4777
 
 
A film is =E2=80=93 or = should be =E2=80=93 more like music than like fiction. It should be a = progression of moods and feelings. The theme, what=E2=80=99s behind the = emotion, the meaning, all that comes later.
=E2=80=93Stanley = Kubrick
 
From: After Effects Mail List = [mailto:AE-List@media-motion.tv] 
Sent: Thursday, December 14, 2017 = 9:52 PM
To: After Effects Mail List = <AE-List@media-motion.tv>Subject: Re: [AE] Cache bugs with = expressions
 
I've had numerous cache issues with = 2014, 2015, 2017 (haven't pushed 2018 yet). Not just with expressions = either, it happens with plain timelines, convoluted timelines. No rhyme = or reason. It just loves to hold onto old cache data. I can't replicate = it, it just does it when it wants to. I just learned to keep the Purge = All Cache shortcut handy. "Ctrl + Alt + /" on PC.

David Torno
818.391.6060
--------------------
www.sydefxink.com (work history)
https://vimeo.com/davidtorno (work samples & = breakdowns)
 
"The most useless day is that in which we do not = laugh"
-Charles Field


On Dec 14, 2017, at 6:12 PM, Chris Zwar = <AE-List@media-motion.tv> = wrote:

I=E2=80=99m playing round with a = project that is based on an expression and I=E2=80=99m running into lots = of cache bugs.  I=E2=80=99m currently using CC 2017. 
I=E2=80=99m = just wondering if others have come across similar problems and if there = are any workarounds.

The project I have = uses a fairly lengthy expression which is applied to a text layer. =  The expression is also reading values from a slider.  Other = layers are then reading the output text of the text layer (ie the = expression results) which controls their time-remapping values.

It doesn=E2=80=99t take much for AE to stop = working properly.  I can move sliders around and nothing changes. =  I can completely change values and yet the RAM preview will play = the same thing over and over.  I can delete all keyframes, so in = theory nothing should be moving at all, yet scrubbing in the timeline = still shows things moving around.

Basically, = what I am trying to do is totally breaking AE=E2=80=99s cache system.

While I will report my problems to Adobe and = will send them a project, I am wondering if there are some simple steps = to avoid these issues.
Does anyone know if making layers = shy, or setting them to guide layers, effects the way the preview system = works?  In previous versions, enabling motion blur has fixed cache = bugs but this doesn=E2=80=99t seem to be the case here.  I can RAM = preview something and set the same thing off as a BG render and get two = different results=E2=80=A6

Any = suggestions?

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


= --Apple-Mail=_E0CF07C9-09DA-4EE3-8DB6-48A43589F0F5--