Mailing List AE-List@media-motion.tv — Message #64339
From: Jim Curtis <AE-List@media-motion.tv>
Subject: Re: [AE] Major Ae project corruption - and how I fixed it.
Date: Wed, 15 Aug 2018 18:45:48 -0500
To: After Effects Mail List <AE-List@media-motion.tv>
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.

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’d never had that happen before.  

Anyway, more or less happy ending.  I was able to fix it and keep working.

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’ve not had before.






> On Aug 15, 2018, at 5:28 PM, Chris Zwar <AE-List@media-motion.tv> wrote:
>
> Yes, I remember Todd Kopriva explaining that when you import a project into AE, it is filtered/processed to check and remove corruption.  It’s definitely something to know.
>
>> On 16 Aug 2018, at 2:56 am, Henry Birdseye <AE-List@media-motion.tv> wrote:
>>
>> Importing troublesome projects has saved me many times.
>>
>>
>> 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).
>>>
>>> I deleted prefs and un- and re-installed Ae and it persisted.
>>>
>>> It only happens with one project that’s gotten pretty large - lots of tracking and 3D camera solves.  Keyframes galore.  Each save takes around 30 seconds.
>>>
>>> I think I fixed it.  It was laborious:
>>>
>>>
>>> I have 10 comps in the corrupt Project.
>>> Select Comp 01, Reduce Project, Save As “Comp 01-100” (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.”
>>>
>>> Repeat process after opening original 10-com corrupt project for all 10 Comps.
>>>
>>> I might import all 10 Comps into a master Project again, but only after I start feeling lucky again.
>>>
>>> Posting this in case anybody else runs into a similar issue.
>>>
>>>
>>>
>>> Epilog / PS.  This didn’t 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.
>>>
>>>
>>>
>>> .
>>>
>>>
>>>
>>>
>>> +---End of message---+
>>> To unsubscribe send any message to <ae-list-off@media-motion.tv>
>>
>>
>> +---End of message---+
>> To unsubscribe send any message to <ae-list-off@media-motion.tv>
>
>
> +---End of message---+
> To unsubscribe send any message to <ae-list-off@media-motion.tv>

 
Subscribe (FEED) Subscribe (DIGEST) Subscribe (INDEX) Unsubscribe Mail to ListMaster