[Tad Newberry]

yep, i was having the same problem with a single clip. figured it was corrupted or something. i had already tried everything mentioned in this thread. another thread mentioned making sure there were no clips above the one i was trying to process.

there were!

i moved them off the clip, hit “analyze”, and away it went! even while it was analyzing, i moved the other clips back into position (on top of my clip that was being analyzed), and it still kept cranking away! i don’t recall having this problem before, so i’m guessing it’s a new bug with some recent upgrade.

thanks for helping out a bonehead!
__________________________

FCS3 / Adobe CC
3.33 GHz 6-Core Intel Xeon Mac Pro
24GB RAM
ATI Radeon HD 5870
…and a few TeraBytes o’ storage
(then it’s on to PetaBytes, ExaBytes and MosquitoBytes!)

[Tad Newberry]

David,

I’ll give that a try. Thanks! (never done it before, so hopefully i find the right file!) 😉

I was on an online chat for 2 hours+ yesterday with Sandeep from Adobe. He took control of the computer. Uninstalled 2014, reinstalled..twice. Nothing. Then we looked at my BlackMagic card. saw that they released a driver update last month. Installed it and the thing screamed away for the rest of the day. Then last night, upon trying to do a “save as” to another project name, back to the same old same old. Very mysterious! I reopened my case with Adobe and we’ll see wazzup…

Also, i started a brand new (though audio only) project yesterday, too, and that one is still working fine today.

thanks for helping out a bonehead!
__________________________

FCS3 / Adobe CC
3.33 GHz 6-Core Intel Xeon Mac Pro
24GB RAM
ATI Radeon HD 5870
…and a few TeraBytes o’ storage
(then it’s on to PetaBytes, ExaBytes and MosquitoBytes!)

[Tad Newberry]

so far, i only see two solutions: go back and render out all the AE projects as rendered videos with their alpha channels like pre 2014 OR leave the linked sequences in the PP sequence, but render out the video with the layer turned off that has all the linked AE sequences. That one will render pretty quick, and then bring that rendered video back in to a new sequence and bring the AE layer over there and render. a little more work, but will save HOURS of render time…especially if you might have to render several versions of that original sequence (i.e., a different set of graphics, or no graphics – clean version, etc.)

thanks for helping out a bonehead!
__________________________

FCS3 / Adobe CC
3.33 GHz 6-Core Intel Xeon Mac Pro
24GB RAM
ATI Radeon HD 5870
…and a few TeraBytes o’ storage
(then it’s on to PetaBytes, ExaBytes and MosquitoBytes!)

[Tad Newberry]

so is it the linked AE sequences that are bogging down the system? ya…terribly slow here. i have a 22:30 show with about 10 linked AE sequences and it’s taking about 5 hours to render to ProRes HQ. does that sound normal to the rest of ye? also, i’m on Mavericks, no Yosemite yet.

thanks for helping out a bonehead!
__________________________

FCS3 / Adobe CC
3.33 GHz 6-Core Intel Xeon Mac Pro
24GB RAM
ATI Radeon HD 5870
…and a few TeraBytes o’ storage
(then it’s on to PetaBytes, ExaBytes and MosquitoBytes!)

[Tad Newberry]

ah, the magic of simply asking the question here leads me to the answer (well…at least, AN answer). i went back to AI and chose “export” instead of “save as”. voila. a working png in PP 2014.

thank you for listening.

😉

thanks for helping out a bonehead!
__________________________

FCS3 / Adobe CC
3.33 GHz 6-Core Intel Xeon Mac Pro
24GB RAM
ATI Radeon HD 5870
…and a few TeraBytes o’ storage
(then it’s on to PetaBytes, ExaBytes and MosquitoBytes!)

[Tad Newberry]

ah, back on this, and your advice is working GREAT. THANK YOU! just gotta rename the comps in the project bin since it defaults to calling them by their location, but no worries, this will be a template so only have to do it once. thanks again!

thanks for helping out a bonehead!
__________________________

FCS3 / Adobe CC
3.33 GHz 6-Core Intel Xeon Mac Pro
24GB RAM
ATI Radeon HD 5870
…and a few TeraBytes o’ storage
(then it’s on to PetaBytes, ExaBytes and MosquitoBytes!)

[Tad Newberry]

Thanks, Paul!

😉

thanks for helping out a bonehead!
__________________________

FCS3 / Adobe CC
3.33 GHz 6-Core Intel Xeon Mac Pro
24GB RAM
ATI Radeon HD 5870
…and a few TeraBytes o’ storage
(then it’s on to PetaBytes, ExaBytes and MosquitoBytes!)

[Tad Newberry]

oops! mine installed 14.2…so we’ll see! so far, so good! those imbedded AE graphics (lower thirds, mostly) are pretty darn slow though…

thanks for helping out a bonehead!
__________________________

FCS3 / Adobe CC
3.33 GHz 6-Core Intel Xeon Mac Pro
24GB RAM
ATI Radeon HD 5870
…and a few TeraBytes o’ storage
(then it’s on to PetaBytes, ExaBytes and MosquitoBytes!)

[Tad Newberry]

thanks for the reassurance, Herb. i’ll give it a go today.

thanks for helping out a bonehead!
__________________________

FCS3 / Adobe CC
3.33 GHz 6-Core Intel Xeon Mac Pro
24GB RAM
ATI Radeon HD 5870
…and a few TeraBytes o’ storage
(then it’s on to PetaBytes, ExaBytes and MosquitoBytes!)

[Tad Newberry]

Thanks for the replies, guys. What i was worried about was when 2014 first came out, it was pretty buggy, and we had tried it and had problems, but that was almost a year ago, so just checking. i’ve been using CC 6 and CC 7 and they’ve both been pretty stable, but based on these responses today, it sounds like i should make the move to 2014. i hear you can actually modify things like AE lower thirds right on the PP2014 timeline, which would be great.

thanks for helping out a bonehead!
__________________________

FCS3 / Adobe CC
3.33 GHz 6-Core Intel Xeon Mac Pro
24GB RAM
ATI Radeon HD 5870
…and a few TeraBytes o’ storage
(then it’s on to PetaBytes, ExaBytes and MosquitoBytes!)