Skip navigation
marq5.1
marq5.1
Currently Being Moderated

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

May 18, 2012 9:18 AM

Tags: #premiere_pro #cs6 #after_effects_cs6

Hi,

 

I needed to make changes to a recently finished 5.5 project. It was my first attempt at using the Adobe Dynamic Link function which basically treats a Ae composition as if it were a sub comp (or nested sequence) in Pr. This worked pretty good in Pr 5.5, all changes I made to the Ae 5.5 comp were quickly updated (or refreshed) in the nested sequence in Pr 5.5.

 

Unfortunately, in the mean time I had updating to Pr 6 and Ae 6. There were several issues with the converted Ae 6 project (previous animation presets were not working anymore). I fixed these fairly easily by adding the presets again from the the effects pallet, the key frames worked still miraculously.

 

The more annoying issue was that the refreshing of changes made in Ae were not showing up in the Pr project. They where there, but not visible. When exported the exported sequence's changes matched those from the Ae comp.

 

I couldn't find a command to empty the render cache in Pr, so I just trashed the render files from the finder level (the folder with the render files is in the same path as the project file). That worked. I had to rerender everything, but at least the changes from Ae were visible. I have reported this as a bug.

 

Cheers,

 

DK

2115 Views   8 Replies   Latest reply: jesmo71, Aug 21, 2012 11:31 AM
 
Replies
  • _techkid123_
    Currently Being Moderated
    1. _techkid123_,
    May 18, 2012 5:04 PM   in reply to marq5.1
    Report

    Hi,

     

    Make sure you SAVE in AE before toggling back to PrP.

     

    Delete the render files and re-rendered the entire sequence.

     

    or try to use http://helpx.adobe.com/x-productkb/multi/startup-screen-hangs-premiere -after.html

     

    Hope it helps

     
    |
    Mark as:
  • marq5.1
    Currently Being Moderated
    2. marq5.1,
    May 23, 2012 3:54 AM   in reply to _techkid123_
    Report

    Hi Techkid,

     

    Thanks for the suggestions. I do save before toggling (mainly because if you don't and then quit the Ae project without savinging you have a big mess on your hands), even though in Pr 5.5 with Ae 5.5 that wasn't realy necissary. The changes just updated like magic.

     

    The workaround for this problem is to manually delete the render files and rerender everything. I think the idea was that you would just need to render the changes.

     

    I'm guessing that the new "global performance cache" funktion is causing the problem. It looks like Pr is not getting the information about the changes from Ae. A classic case of a good function turning into a good headeche. The function is causeing exactly the type of delay it was designed to eliminate.

     

    It would benice to know if others are having the same issue. It could be just me... ...!

     
    |
    Mark as:
  • Jim Simon
    Currently Being Moderated
    3. Jim Simon,
    May 23, 2012 9:17 AM   in reply to marq5.1
    Report

    Test again in a new project, not one created in 5.5.

     
    |
    Mark as:
  • James Landy
    Currently Being Moderated
    4. James Landy,
    Jun 25, 2012 4:55 PM   in reply to marq5.1
    Report

    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.

     
    |
    Mark as:
  • jesmo71
    Currently Being Moderated
    5. jesmo71,
    Aug 1, 2012 2:48 PM   in reply to marq5.1
    Report

    Here is another workaround that may be a bit easier.

     

    Add an adjustment layer above your AE comp in PPro, and add an effect to the adjustment layer (three-way color corrector is a good one that won't make any actual changes to the adjustment layer, unless you actually change settings). This will force the layers below to unrender, and allow you to see the updated AE comp.

     
    |
    Mark as:
  • David Cabestany
    Currently Being Moderated
    6. David Cabestany,
    Aug 10, 2012 12:11 PM   in reply to marq5.1
    Report

    I'm too seeing this issue.

     

    However I found a faster workaround than deleting the files fro their actual locations, if you close the sequence and open it again, the revised parts will show unrendered.

     
    |
    Mark as:
  • ~joris
    Currently Being Moderated
    7. ~joris,
    Aug 21, 2012 11:27 AM   in reply to marq5.1
    Report

    I have experienced this issue as well.

     

    My workaround so far has been to change the opacity value of the clip in question and then reset it to its original value. Way faster than deleting and relinking any files and seems to do the trick for me.

     
    |
    Mark as:
  • jesmo71
    Currently Being Moderated
    8. jesmo71,
    Aug 21, 2012 11:31 AM   in reply to ~joris
    Report

    ~joris, I agree it's easier to just make an adjustment like opacity or adding an adjustment layer. I'm sure we'll see this addressed in some sort of update.

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Incoming Links

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