| ||||||||||
| 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 |
