Hi Jannick, What you are seeing is a current limitation of Team Projects in After Effects and Premiere. Nesting of Premiere sequences in AE compositions and vice/versa is limited to one level only, and only the "containing" application can render the outer sequence or comp. There is a similar limitation to cross-application nesting between standalone Premiere and After Effects projects, though it's slightly looser. For example, if you place an AE comp into a Pr sequence in a Team Project, the sequence will render in Pr, but will appear as a placeholder in AE. Similarly, if you place a Pr sequence into an AE comp, AE will be able to render that comp, but it will appear as a placeholder in Pr. This limitation avoids circular references where each application might be waiting for the other to render a different part of the same Team Project. Only one level of cross-application nesting is allowed between standalone Premiere and AE project files, too. The difference is that, in a standalone project, Premiere will render an AE comp containing a Pr sequence via DynamicLink instead of showing a placeholder, and vice-versa. You still can't insert such a comp into a Pr sequence, though, so there's not much you can do with it beyond seeing what it looks like. Can you tell me more about the workflow that you are trying to accomplish? What would you do in AE with a Pr sequence that contained an AE comp, given the limitations that already exist outside of a Team Project? Thanks, -Peter
... View more