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