This content has been marked as final. Show 8 replies
removing RAM till 8GB left and try again rendering, maybe its faulty RAM.
if you have apple care protection plan you have "Techtool Deluxe" for maintenance incl. RAM Test.
running Applejack in auto-mode
Ok, Thank you very much Todd, this is very interesting to me, but let me have a serious question: what will happen in the nick of time to eliminate these flaws?
Thanks for the feedback, I have a follow up question,
Is their a reason why the comp is able to export in hallf resolution without multiprocessing shutting down but is unable to at full resolution?
You are using a large blur, glow or similar effect somewhere that dilates/ expands the buffer beyond what the RAM assigned to the background instances can hold. Since the BG instances are solely controlled by the AE process manager, they have no way of directly requesting more RAM (or disk swap memory) from the operating system and thus shut down. The single remaining instance of the main program doesn't suffer from this limitation. At half resolution it naturally works, as the processing of the effect(s) that make everything go *poof* at full res is naturally also based just on teh half res version, hence it may be just enough.
Rest assured that solutions to these issues are being worked on and in weird and wonderful ways everything shall be much better in CS5. It has been stated from many sides that CS5 will bring the transition from Carbon to Cocoa for all major Adobe products and as a Mac-addict, you can take a guess at which additional benefits there may be to working with a 64bit API... ;-)
Thanks for the responses, i really do hope these issues are resolved in CS5 because it's a little frustrating to find out I won't get the full kick from my ram when working on heavier comps which is a norm for me now.
Thanks again for the feedback
b everything shall be much better in CS5.
shall? bad excuse for those who already spent money whilst upgrading.
at least i'd expected a huge progress for CS4.
I'm just asking myself why adobe did not rather took their time, developing their stuff for a two year period considering all the main feature requests from anno 2000 and we'd mostly be fine.
I'm working in a huge agency and ALL machines are still supplied with CS2, i mean, we have 2009. Somethings definetly wrong with the upgrade prices vs. progress that would be worth menitoned by the IT-Head ofs to the CEO considering the future investments into software upgrades.
Sorry and by all respect, but i still feel like beta testing a major release :(
I think Todd's post on features which disable multiprocessing was not followed properly.
There are features which by their very nature do not get along well with simultaneous multi-core rendering. This is not specific to AE, and actually AE does the right thing in turning off multiprocessing in these cases, given that otherwise things would end taking much longer. This is the case for things like Particle Playground, many time-based effects and some third party plug-ins. This kind of highly time-dependent tools work in a way in which a frame is not really an independent entity from other frames and thus feeding separate frames to the different cores would make things worse, not better.
This is of course very different from the cases Lutz explained, in which a switch to 64 bit processing would definitely change everything.