From: "Chris Zwar" <AE-List@media-motion.tv>
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: [AE] autosave function
In-Reply-To: <list-5499364@media-motion.tv>
Date: Thu, 12 Jun 2014 11:58:22 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <454357B0-327A-4F56-85A5-C55ACEBBCFA2@chriszwar.com>
References: <list-5499364@media-motion.tv>
To: "After Effects Mail List" <AE-List@media-motion.tv>

On 12/06/2014, at 4:41 AM, rendernyc <AE-List@media-motion.tv> wrote:
> I have had this happen many many times over the years. i had reported =
it in the past but i have never been able to nail down why or when it =
stops.

Well I mostly use CS6 and it still sometimes stops working.  I have =
always had a hunch that it was to do with memory and maybe =
multiprocessing but no proof.

I don't know if it still happens in CS6, but in earlier versions of =
After Effects if it ran low on memory then the composition motion blur =
settings would be reset to 2 samples, which would then effect all new =
compositions.  A real pain.  The often commented bug "Ram preview needs =
2 or more frames" also seems related to low memory.  So if those two =
quirks/bugs are memory related then it's a reasonable guess that when AE =
runs low on memory, the autosave trigger also gets reset or something.

Before CS5, when we had to "purge all" regularly to avoid the stupid =
memory buffer error, doing a "purge all" would also stop autosave from =
working.  I haven't had to "purge all" since CS5 - which is over 4 years =
old now - so I don't know if that still happens.  But that was =
definitely something I noticed with CS3.


-Chris=