Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe After Effects merging projects and workflow performance

  • merging projects and workflow performance

    Posted by Anita Sancha on July 14, 2009 at 5:57 am

    Hi..

    Mac book pro 2 core and CS3

    I have a really “heavy” animation near completion. But it is in 2 projects.

    One project is the background and one the foreground, (which is a complicated conga salsa of vegetables.) I kept these as separate projects, because I have gotten into to the idea from somewhere that maybe AE performance would be better as separate projects??. However one of the characters needs to be in the other project as it interreacts with the main character (a pumpkin) in the background.

    so… 2 main questions.

    (1) how best is it to move a layer with all keyframes, effects… like the old clipboard cut n paste to the other project.

    (2) Does importing as merging one project into the other one make it even heavier, if only one of these comps is open as timelines?
    Then its easy to cut/copy/paste the relevant character to the background comp. BUT…..What happens to performance if both comps are open and the foreground salsa is nested into the background. I was going to tga out and import this as a sequence but I could nest it.

    This is not the first time I’ve made separate projects through fear of too many comps/nested comps open or closed, hogging performance, how justified am I in this?

    Thanks

    Thanks for all your help
    Anita Sancha.

    http://www.anitasancha.co.uk

    Adolfo Rozenfeld replied 16 years, 10 months ago 2 Members · 3 Replies
  • 3 Replies
  • Adolfo Rozenfeld

    July 14, 2009 at 7:49 am

    Anita:
    Performance will be more directly affected by the kind of operations you perform, and the kind of source files you use, than by having several comps living in the same project.

    In fact, Comps and source files which are part of the resulting project but are not open in a Comp viewer, they are there doing nothing. They don’t really affect performance in any significant way.
    You can import a project into an existing project – just use the Import feature instead of Open, as you normally do with projects. All Comps are source files from the imported will appear in a folder in the project panel.
    In any case, if you’re worried, you can try this and experiment for a few minutes without saving the resulting project, to see if you’re satisfied with performance. You can revert to the original project if you want.

    Adolfo Rozenfeld · Adobe

  • Anita Sancha

    July 14, 2009 at 12:02 pm

    Hi..

    Just to be clear on this… If I have 2 identical projects, each with a main comp and a nested com. .. and no interlinking references.

    Import both, and if I open as a timeline, the main comp from only one of these, AE will use the same performance as if I opened each of the projects separately as individual projects.

    If I leave open one of the main comps and then open the other main comp in the timeline as well, does this reduce the performance, even if there are no nested comps relevant to the other projects main comp.

    My sources are all image sequences taga or png (uncompressed with alpha) HD.

    You may well have answered this in the first response but just confirming I understand correctly as testing is difficult, as it is already slow and heavy, and I do want to combine large projects.

    Thanks a bunch for this help with my eco animations.

    Thanks for all your help
    Anita Sancha.

    http://www.anitasancha.co.uk

  • Adolfo Rozenfeld

    July 15, 2009 at 4:02 am

    [anita sancha] “Import both, and if I open as a timeline, the main comp from only one of these, AE will use the same performance as if I opened each of the projects separately as individual projects.

    If I leave open one of the main comps and then open the other main comp in the timeline as well, does this reduce the performance, even if there are no nested comps relevant to the other projects main comp.”

    Anita: Comps only use significant resources when you are working directly on them. They do not take that much CPU cycles or RAM when they are idle, even if they are open. Just so it’s clear, you could have 35 wildly complex Comps, and when you’re working on one of them, the others one barely exist. Unless one or more of these is nested inside, of course.
    This is an oversimplification, because RAM gets fragmented over time. You can fix this by purging (Edit > Purge) when things slow down, or re-launch the application.

    My sources are all image sequences taga or png (uncompressed with alpha) HD.”

    This will probably tax more your hard drives than your CPUs or RAM memory.

    Adolfo Rozenfeld · Adobe

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy