From: "Jim Curtis" <AE-List@media-motion.tv>
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\))
Subject: Re: [AE] Major Ae project corruption - and how I fixed it.
Date: Wed, 15 Aug 2018 19:54:35 -0500
References: <list-7134332@media-motion.tv>
To: After Effects Mail List <AE-List@media-motion.tv>
In-Reply-To: <list-7134332@media-motion.tv>
Message-Id: <529066F5-FD8C-49A8-B0B1-7CAC7D5A40B0@flash.net>

Thanks for the tip, Chris.  I was using the Smoother after every track, =
and deleting all but the Attach Point or Position KFs when that=E2=80=99s =
all I needed.

My Auto-Saves were taking 30 seconds, so I tempted fate and changed the =
frequency from 15 minutes to 60.  I save often usually anyway as I was =
raised on no auto-save and even one undo from early Ps days.


> On Aug 15, 2018, at 7:42 PM, Chris Zwar <AE-List@media-motion.tv> =
wrote:
>=20
> I=E2=80=99ve definitely seen the type of behaviour you=E2=80=99re =
seeing, when projects are very large with lots of keyframes.  It=E2=80=99s=
 happened to me on a few occasions when I=E2=80=99m importing .ma files =
and every frame has a keyframe for every property.  If you=E2=80=99re =
tracking in AE you might not have this problem.  I was generally able to =
get around it by deleting all unnecessary keyframes from the imports - =
most of the time there were keyframes on every frame for properties that =
didn=E2=80=99t animate.  This would generally make the projects smaller =
and faster to work with too.  There=E2=80=99s at least one script around =
which will clean up unnecessary keys - might be worth checking =
aescripts.
>=20
>> On 16 Aug 2018, at 9:45 am, Jim Curtis <AE-List@media-motion.tv> =
wrote:
>>=20
>> It works well in Premiere, too.  And sometimes, just creating a new =
Sequence and pasting the clips from the corrupt one into the fresh one =
works as well, and is faster than importing Sequences or whole projects.
>>=20
>> But in my case today, simply importing the entire corrupt Ae project =
was importing the corruption with it until I deleted 9 out of 10 Comps, =
and saved each Comp individually.  I=E2=80=99d never had that happen =
before. =20
>>=20
>> Anyway, more or less happy ending.  I was able to fix it and keep =
working.
>>=20
>> Until... I started having issues in Pr related to my Titan X GPU.  I =
wonder if the issues are related.  I reinstalled my GPU and CUDA =
drivers, to no avail.  Had to switch to CPU only in Premiere to get all =
my layers to show and render (ProRes 4444+ clips with alpha were showing =
as full black and turning every clip thereafter full black.).  That was =
also an issue I=E2=80=99ve not had before.
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>> On Aug 15, 2018, at 5:28 PM, Chris Zwar <AE-List@media-motion.tv> =
wrote:
>>>=20
>>> Yes, I remember Todd Kopriva explaining that when you import a =
project into AE, it is filtered/processed to check and remove =
corruption.  It=E2=80=99s definitely something to know.
>>>=20
>>>> On 16 Aug 2018, at 2:56 am, Henry Birdseye =
<AE-List@media-motion.tv> wrote:
>>>>=20
>>>> Importing troublesome projects has saved me many times.
>>>>=20
>>>>=20
>>>> On 8/15/2018 12:25 PM, Jim Curtis wrote:
>>>>> After working on this project for a week, my iStat menus are =
reporting that all 12 cores are at 100% when I just have Ae running and =
no comps even open.  Computer is correspondingly very sluggish and =
beach-bally (OSX).
>>>>>=20
>>>>> I deleted prefs and un- and re-installed Ae and it persisted.
>>>>>=20
>>>>> It only happens with one project that=E2=80=99s gotten pretty =
large - lots of tracking and 3D camera solves.  Keyframes galore.  Each =
save takes around 30 seconds.
>>>>>=20
>>>>> I think I fixed it.  It was laborious:
>>>>>=20
>>>>>=20
>>>>> I have 10 comps in the corrupt Project.
>>>>> Select Comp 01, Reduce Project, Save As =E2=80=9CComp 01-100=E2=80=9D=
 (100 is for my CPUs pegging at 100%)
>>>>> Create New Project.
>>>>> Import Comp 01-100 - CPU levels go back to normal: what I expect =
for an idling Ae Project.
>>>>> Save as "Comp 01 only.=E2=80=9D
>>>>>=20
>>>>> Repeat process after opening original 10-com corrupt project for =
all 10 Comps.
>>>>>=20
>>>>> I might import all 10 Comps into a master Project again, but only =
after I start feeling lucky again.
>>>>>=20
>>>>> Posting this in case anybody else runs into a similar issue.
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> Epilog / PS.  This didn=E2=80=99t work on one Comp.  So, I opened =
the Comp.  Select all Layers.  Copy.  Create New Project and Comp.  =
Paste.  Relink footage.   I got an error message telling my footage was =
tracked on a 360 x 180 layer (??? - Not true), but my tracking data was =
fine.  I just deleted the Mocha Pro plug-in that created the data, and =
all is well.  Save.
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> .
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> +---End of message---+
>>>>> To unsubscribe send any message to <ae-list-off@media-motion.tv>
>>>>=20
>>>>=20
>>>> +---End of message---+
>>>> To unsubscribe send any message to <ae-list-off@media-motion.tv>
>>>=20
>>>=20
>>> +---End of message---+
>>> To unsubscribe send any message to <ae-list-off@media-motion.tv>
>>=20
>>=20
>> +---End of message---+
>> To unsubscribe send any message to <ae-list-off@media-motion.tv>
>=20
>=20
> +---End of message---+
> To unsubscribe send any message to <ae-list-off@media-motion.tv>