From: "Teddy Gage" Received: from mail-yk0-f170.google.com ([209.85.160.170] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 5500660 for AE-List@media-motion.tv; Fri, 13 Jun 2014 16:33:40 +0200 Received: by mail-yk0-f170.google.com with SMTP id q9so2088014ykb.15 for ; Fri, 13 Jun 2014 07:33:39 -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=80TZF2391uOp4oCsiCl/ruf6RLlrCduAERZInVX9Uxs=; b=XeMfmkqxIEzX33+reE4/QAWhYhGP3BRaM6SCzDet91YoBAGo5H0LURcM0yn6sH7Nr0 YpDNCP5u3i+Sd1QWGsdnkOjOd7GzS83FzEXx1scOZY7V3OpFYTXH8LKtoST0v6/QrSZb 6sZKolKhFNXiAtojc7Y9Sff9Kh3wm5hK8FAlGWr4zrnDELyE2DaFQx0J7n9aibvdo5uK UaphzSHZtQuzpYedz5mrgiPzABvYnL42lOONVC9quan8uCAOr4nx/k9StArgRQ24wKQS c8Dle6fVjaQVRRu3AzoV+Uul7KZdsLM4N2SSZgxdJfg9VkqWQ/k/T1AMWQtrjJrI+XgE r5qA== MIME-Version: 1.0 X-Received: by 10.236.66.139 with SMTP id h11mr5162560yhd.30.1402670019428; Fri, 13 Jun 2014 07:33:39 -0700 (PDT) Received: by 10.170.76.134 with HTTP; Fri, 13 Jun 2014 07:33:39 -0700 (PDT) In-Reply-To: References: Date: Fri, 13 Jun 2014 10:33:39 -0400 Message-ID: Subject: Re: [AE] autosave function To: After Effects Mail List Content-Type: multipart/alternative; boundary=001a1133cb6c3f829f04fbb89057 --001a1133cb6c3f829f04fbb89057 Content-Type: text/plain; charset=UTF-8 Really? I purge the RAM constantly, especially before ram previews or rendering. It seems to make a significant difference in speed and / or stability. Could just be old habits die hard On Wednesday, June 11, 2014, Chris Zwar wrote: > On 12/06/2014, at 4:41 AM, rendernyc > 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 > +---End of message---+ > To unsubscribe send any message to > > -- _____________________________ VFX & Motion Graphic Artist teddygage dot com --001a1133cb6c3f829f04fbb89057 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Really? I purge the RAM constantly, especially before ram=C2=A0previews or = rendering. It seems to make a significant difference in speed and / or stab= ility. Could just be old habits die hard

On Wednesday, June 11, 2014= , Chris Zwar <AE-List@media-m= otion.tv> wrote:
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. =C2=A0I have al= ways had a hunch that it was to do with memory and maybe multiprocessing bu= t no proof.

I don't know if it still happens in CS6, but in earlier versions of Aft= er Effects if it ran low on memory then the composition motion blur setting= s would be reset to 2 samples, which would then effect all new compositions= . =C2=A0A real pain. =C2=A0The often commented bug "Ram preview needs = 2 or more frames" also seems related to low memory. =C2=A0So if those = two quirks/bugs are memory related then it's a reasonable guess that wh= en 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 stu= pid memory buffer error, doing a "purge all" would also stop auto= save from working. =C2=A0I haven't had to "purge all" since C= S5 - which is over 4 years old now - so I don't know if that still happ= ens. =C2=A0But that was definitely something I noticed with CS3.


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


--
________= _____________________
VFX &= ; Motion Graphic Artist
teddygage dot com

--001a1133cb6c3f829f04fbb89057--