Skip navigation
Currently Being Moderated

After Affects CS6 comp do not update in Premiere Pro sequence

Jun 6, 2012 11:09 AM

Since CS6, if I change an After Effects project when the comp is already in a Premiere Pro timeline, the comp won't automatically update on the timeline, but it will update on the source monitor.

 
Replies 1 2 Previous Next
  • Currently Being Moderated
    Jun 6, 2012 11:16 AM   in reply to Proj.L

    Two things.

     

    1, Make sure you save the AE project before switching to PP.

    2. Make sure you're looking at the right comp in PP sequence.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 6, 2012 2:51 PM   in reply to Proj.L

    I have had the same issue

     

    Adobe Forums: Adobe Dynamic Link between Premiere Pro 6 and After Effects won't refresh

     

    I havn't had time to try any other workarounds. I thought I was the only one experiencing the problem.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 22, 2012 3:16 PM   in reply to Proj.L

    @Proj.L,  I just tested this with OSX 10.7.4 with multiple dynamic links and creating multiple changes between both applications.  I've had consistant updates on the timeline.  My only thought would be to clear your cache files, in AE and in Premiere, and see if that helps any.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 22, 2012 3:50 PM   in reply to RBemendo

    It happens to me when I render a preview of the DL clip, then change it in AE.  Pr keeps the original preview (green bar above) and doesn't update it.  I usually have to replace the clip manually - there is no option that I know of to disable/delete an individual preview file.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 22, 2012 5:08 PM   in reply to needles27

    @needles27 - okay, thanks, that's a good hint for where to look and for steps to reproduce.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 25, 2012 5:01 PM   in reply to Proj.L

    Regarding the original post..

    Dynamic Link CS5.5, is not compatible with Dynamic Link CS6. You can import an AE CS5.5 legacy project into PR CS6, or open a PR CS5.5 legacy project that contains comps from an AE CS5.5 project in PR CS6. But if you want to make changes in AE, and have the PR project update to reflect those changes, you need to overwrite the legacy AE CS5.5 project. For example, open the PR legacy project, in PR CS6. Select one of the AE comps, and choose edit original. When the AEP opens, save it using the same name, to replace the 5.5 version with a CS6.

     

    I'll address the work area preview topic separately, they appear similar, but are different issues.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 25, 2012 5:03 PM   in reply to needles27

    Needles27, What are you modifying in the AE comp, prior to bringing PR to the foreground?

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 25, 2012 8:31 PM   in reply to James Landy

    Just about anything, I think - I haven't tracked it.  But an example -

    I DL over a clip from the Pr timeline to AE.  I add a few filters such as Denoiser and Colorista - 2 pretty CPU/GPU intensive filters that need to be rendered in Pr to play back.  I also add a title.  I come back to Pr and render a preview.  Then, I go back to AE and change the title.  Then , finally back to Pr and the old preview is still there with the old AE comp.  I have to break the preview somehow to turn it back to a red bar, render again, and then I have my new AE changes in Pr.

     

    Does that help?

     

    MacPro4,1

    32GB RAM

    GTX 285

    CS6

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 1, 2012 2:44 PM   in reply to James Landy

    I'm having a similar problem. I have 2 Mac Pro machines that have recently been updated to CS6(Production Premium). This occurs on both machines. And is not specific to any one item being changed. It occurs to any changes being made AFTER rendering into PPro.

     

    If I link between PPro & AE comps/sequence, I can make changes in AE and it will update to PPro as long as it has not been rendered. However, if I render the sequence in PPro, and then go back to AE and make changes(and yes, I am saving it before returning to PPro), it does not unrender the PPro sequence, and will not update.  It remains rendered in the sequence as if nothing has changed. No matter what I do to the imported AE comp in PPro, it will not unrender. (short of adding an adjustment layer with an effect above it all in the sequence to force it to unrender - this is my workaround for the moment).

     

    I've gone so far as to delete the linked comp out of PPro, and re-import the AE comp, and if I drop it on the same sequence it pops immediately back up as rendered.  My guess is it has something to do with the global cache.

     

    This is not a legacy issue, as this project was created from scratch in CS6.

     

    Here's the workflow

     

    Create PPro Proj  -> import footage -> edit video -> save.

     

    Create AE Project -> edit composition to desired effect/graphics etc... -> import or drag comp from AE to PPro -> Lay AE comp on video layer above base footage -> Go back to AE make any desired changes and Save -> return to PPro, and project is updated -> Render ALL in PPro ->  realize something needs to be adjusted in AE -> go to comp in AE, make adjustment & save -> return to PPro and find that it will not update/refresh/unrender.

     

    I can duplicate this exactly on the other machine as well, so it's not a specific issue with a specific machine.

     

    Am I missing something short of clearing out the entire render folder in PPro?

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 1, 2012 3:17 PM   in reply to jesmo71

    When the area in the timeline in Premiere is not pre-rendered, then all of the edits/preview output is playing from media files, various cache files, Metadata, Project files, and audio conformed files. This allows the Dynamic link to immediately adjust any of those files as needed from the other applications such as AE. However if you render out a portion of the timeline, then you are now playing back from a preview file just like playing any media file in a media player. Since this file was created before the changes were made in AE then they will not adjust realtime. You have to delete the render files for that portion of your work area ( BTW you can do that under sequence settings) and then re-render that area. This is by design and not a bug.

     

    Eric

    ADK

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 1, 2012 5:31 PM   in reply to ECBowen

    I'm aware of how sequences are affected when they are not pre-rendered. However, I'm specifically talking about once the file is rendered there is an issue that did not exist before CS6. In CS5 & CS5.5 I could render in PPro, make changes in AE, and the rendered timeline would become unrendered, and show the updated information from AE without having to manually delete any render files. I've done it thousands of times, and until CS6 it was not an issue. That is the point of dynamic linking.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 31, 2012 8:01 AM   in reply to ECBowen

    [Antagonistic comment deleted]
    Dynamic link is designed so whatever changed you make in After Effects are immediately reflected in Premiere, without the need of having to render anything in between, that's the way it worked in CS5 and CS5.5, it's not how is working in CS6, Premiere Pro is just not becoming aware that something changed in the linked AE comp so all of us users in this forum have to find ways to make PPro aware that we changed something in our linked AE projects, Me, I drag the clips across the timeline, I get the beach ball for a few seconds and then the green line turns to red, so I re render and my latest changes are reflected.

     

    As some other have pointed out already, I'm also working from freshly created projects in CS6, nothing I'm using was created in CS5 or below.

     

    @ James Landy and/or Eric Sanders, the changes in AE can be as little as scaling up a layer or deleting keyframes or as big as adding new precomps or reanimating a camera. None of it will be detected by Premiere.

     

    I'm on a Mac, Snow Leopard running PPRO 6.0.1 and AE 11.0.0.12

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 31, 2012 7:49 AM   in reply to David Cabestany

    it's not how is working in CS6

     

    It is for me.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 31, 2012 8:04 AM   in reply to Jim Simon
     
    |
    Mark as:
  • Currently Being Moderated
    Aug 31, 2012 8:03 AM   in reply to David Cabestany

    Well, it means that the "bug" is not easily replicated, and may be more difficult to track down and fix than something that affected everyone.

     

    It also means it may not be a bug with PP, but a system error common to those having the issue.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 31, 2012 8:09 AM   in reply to Jim Simon

    I think the number of affected people is large enough to safely call it a bug, but that's my opinion.

     

    I still have CS5 and CS5.5 installed on this machine, I just can't replicate the issue with those, whereas in CS6 I get it every single time, is not a random thing that happens sometimes and sometimes it doesn't.

     

    While searching for answers I found this thread plus another one also in the Adobe forums and one more in Creative Cow I think, this is not an isolated problem.

     

    I can send specs of my system to the Adobe engineers if they think this could be related to something particular on my computer if they think that would be helpful.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 31, 2012 8:15 AM   in reply to David Cabestany

    Are you work/media drives Formated HFS+ Journaled or Non Journaled for this project? Also where is your Media Cache located right now for this project?

     

    Eric

    ADK

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 31, 2012 8:18 AM   in reply to ECBowen

    HFS+Journaled. The cache is located in an external drive which also contains the media. The software runs in a separate solid state drive

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 31, 2012 8:29 AM   in reply to David Cabestany

    The Journaled Meta data has been causing issues with 3rd party applications it seems quite abit lately due to the meta-data added for the journaling. Can you move your media/project files/preview/media cache files files to a drive formatted non jounaled. Make sure you change the primary directory name that you copy those files into. Move the Media Cache folder to the same Non-jounaled drive and delete the current files there. Re-render the timeline where the AE comp is and then make an adjustment. See if Premiere will recognize where the comp preview files are located and then auto delete them.

     

    Eric

    ADK

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 31, 2012 8:31 AM   in reply to ECBowen

    Thanks, will do that, not right now because I need to finish the project and I do not have a non journaled drive available so I need to re format one or buy a new one, as soon as I can try that will do it and post my results here.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 31, 2012 11:51 AM   in reply to Jim Simon

    I disagree that this bug is not easily replicated. I can do it on both of my editors, and I've gotten two other local production facilities to replicate it as well. This is an Adobe Dynamic Linking in Mac issue. Although you may have no problem with it on a PC, the programming does not apply in the same manner on Macs. This has specifically to do with when a layer has been rendered; dynamic linking is not updating the rendered portion with changes. As was pointed out by David, it is quite obvious that this is happening to multiple Adobe/Mac users. It is a bug, and I'm sure it will be addressed at some point. It's annoying at worst, and easily overcome with a simple workaround.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 31, 2012 12:13 PM   in reply to jesmo71

    This is an Adobe Dynamic Linking in Mac issue.

     

    That's possible, 'cause it works fine for me on both Windows machines.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 31, 2012 12:23 PM   in reply to Jim Simon

    Jim Simon wrote:

     

    This is an Adobe Dynamic Linking in Mac issue.

     

    That's possible, 'cause it works fine for me on both Windows machines.

     

     

    Well, while I appreciate that you're trying to contribute, commenting about a bug that is Mac specific (and has been stated as such since the beninning of the thread) when you're using Windows is just adding unhelpful chatter to a conversation where people are looking for informed ideas.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 31, 2012 9:19 PM   in reply to jesmo71

    (and has been stated as such since the beninning of the thread

     

    Sorry, I missed that.  I just normally click the "Last Post" time, which takes me to the most recent post.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 1, 2012 12:06 PM   in reply to Proj.L

    Well, there goes that idea.

     

    Does everyone having the issue also have any missing sequence presets?  Can you properly do a Replace with AE Comp?

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 6, 2012 5:56 PM   in reply to Jim Simon

    Regarding: Render Work Area in Premiere doesn’t get deleted when modifying linked comp in AE.

    I can’t reproduce the issue on Mac 10.8.1 or Win 7 64-Bit SP1 running Production Premium CS6 with all of the current updates. It works 100% of the time. In order to fix the problem, we need to be able to reproduce this in-house. It sounds like a legit issue. The question remains, why does it work for me, and occurs for other users. Based on the comments in this thread, I think we can rule out user error. So what is the common denominator that all of the users who are encountering this issue have in common? That is what we need to define next. I think ECBowen may be onto something, with the idea that it has something to do with where the Premiere preview files are being stored. Is anyone who is encountering this issue storing his or her preview files in the default install location?

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 7, 2012 6:02 AM   in reply to James Landy

    James,

     

    Both of my systems are on 10.6.8 - Planning to upgrade to Mountain Lion soon. I just wanted to wait until everyone had a chance to make sure the drivers were updated before pulling the trigger. It is something we can reproduce here 100% of the time.

     

    I'm not 100% sure which versions of OS X the other two local facilities are using, but I'm pretty sure one could be as old as 10.5

     

    Also, I am not using the default location as my preview save location.

     

    Message was edited by: jesmo71

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 7, 2012 6:11 AM   in reply to jesmo71

    @James/ECBowen - And just to clarify - Yes all the drives we used are HFS+ (Journaled) - No, we can't switch to non-journaled because we have about 5Tb of data (most of it video), and it just would not be feesible. If the drive being Journaled is the issue, that equates to a programming issue, and is something that needs to be addressed by Adobe. I do, however, appreciate that you've worked at finding the solution to the problem.

     

    @Jim SImon - My apologies, when I told you this was a Mac thread, I thought we were in the other thread that is having this exact same conversation.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 7, 2012 7:55 AM   in reply to jesmo71

    If you could get an external HDD of some type to test and use as backup later that would help see if the Metadata added by Journaling is causing Adobe's File manager from detecting the file locations correctly. If you have a card reader and a blank media card we could try the same thing it would just be slower.

     

    Eric

    ADK

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 7, 2012 12:57 PM   in reply to ECBowen

    A media card is a great idea. I'll try that first chance I get and post the results here.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 7, 2012 2:37 PM   in reply to jesmo71

    Regarding: Render Work Area in Premiere doesn’t get deleted when modifying linked comp in AE.

    After further investigation, although it is still a possibility, I think the drive/location of the preview files is not the problem. I’m back onto the idea that this is an AE comp/project settings/parameter not flushing the hash cache. We need to figure out if the issue is with AE or PR. Once a modification has been made to the comp in AE, AE sends a notification to PR. We need to determine if AE is sending the updated information, if not the bug is in AE. If PR is receiving the information, and not updating, the bug is in PR. I need someone who can reproduce this problem 100%, to send me their project and source files, or set up a connect session with me, so I can observer the workflow in greater detail. We also have some debugging tools we can walk you through.  Any volunteers?

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 7, 2012 2:45 PM   in reply to James Landy

    James,

     

    I can do this with you on Monday - I'll have to set up a connect session with you, because all the files are too large to send. You can contact me at my email address in my profile. Let me know if that will work for you.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 28, 2012 12:07 PM   in reply to jesmo71

    i also have this problem regularly.  it is very annoying and can not wait till it is fixed.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 26, 2012 1:37 PM   in reply to Proj.L

    The only solution I have found is to force Premiere to re-render the linked footage. I put a white solid below the footage and dropped the oppacity.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 26, 2012 2:05 PM   in reply to AudioBrad

    I have a couple of ideas.

     

    After Effects recently made some changes to the cache memory area of the app. Those changes are in AE 11.0.2, which is available as a live update. I've had reports from other users that after upgrading, they can no longer reproduce this issue.

     

    I found a bug recently where the work area preview does not get invalidated in Premiere if you modify the composition in AE while the preview is being created in PR. Here is the workaround;

    1. After you have made your modifications to the comp in AE, bring PR to the foreground (the work area is not deleted).
    2. Bring AE to the foreground, and then click in the comp viewer panel to bring it into focus.
    3. Bring PR to the foreground. The work area gets deleted.

    Note: You might have to repeat step 2 and 3. This issue only occurs if the AEP is in 16/32bpc mode.

     
    |
    Mark as:
1 2 Previous Next

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points