Dynamic link - AE render quality in PrPro

I'm a FCP switcher - and decided to check out dynamic link by sending a clip to AE for slow-mo.  In AE I turned on pixel motion and rendered the file - perfect - with new intermediate frames created giving a smooth slo-mo.  However when I rendered the clip in PrPro the new frames were merely repeats, giving that jerky effect. There was no pixel motion (optical flow) applied.  When I rendered out the clip from PrPro to disc, I got another result, this time the new frames were created by repeates and frame blending! 
Is it possible to render AE comps in PrPro - or do you have to render in AE and re-import into PrPro (which kind of invalidateds the dynamic link idea).
Thanks for any ideas.
Ken.
Mac Pro 2009 8 core
8 gigs RAM
Nvidia 8800 512Megs (no CUDA possible it seems)
PrPro 5.5.2
AE CS5.5

Ashe?
If yes, your problem is the result of bad karma.

Similar Messages

  • Problems with Dynamic Link and Render Farm

    We have a 10-node render farm that we use for all of our AE renders, and it works great, so we know the farm isn't the issue. But if we place a Premiere sequence into an AE file and attempt to send the After Effects file to the render farm, we get this error from every node:
    "aerender Error: After Effects error: Failed to connect to Adobe Premiere Pro Dynamic Link."
    Does anyone know of a possible workaround for getting an AE file using Dynamic Link to render to a farm? This is a very important workflow for us, and right now we're having to do local renders for any AE file that uses Dynamic Link.

    Why not ask such questions in the AE forum? Aside from that, using AE and PPRo DL at the same time can easily exhaust all your system resources and may cause any kind of issues, as effectively only one connection is meant to exist at any given time. So it's definitely in the way you use it, but not necessarily "wrong", just an unfortunate combination that makes things unworkable.
    Mylenium

  • Is anyone else having serious issues with Dynamically linked clip render times in CC 2014.2

    Short clips stalling and taking forever to render. Longer ones taking several hours???
    I've noticed arbitrary little fixes, such as re-opening the after effects window, then going back into the premiere window causes the render to instantly speed back up in some cases.
    A restart of the program I believe solves the issue too. As does simply rendering the clip out in after effects.
    The problem is that I have long, overnight renders set up that need to run automatically. In this case, 9 clips, all about 30 minutes long. And pretty much all one long dynamically linked comp (I created a picture in picture effect in after effects compiling 2 30-minute video feeds, and then added some color correction). When I left at night, the total time kept creeping up and up to about 2.5 hours for one video. Even THAT sounds like a lot to me, but I let it go. I return to the computer 13 hours later, to see only 3 videos completed, and the one CURRENTLY in the queue saying over 6 hours remaining. I cancel the render.
    I feel like there is some breakdown of communication between afx and premeiere happening here.
    Anyone have any experience with issues like this?
    Running PP CC2014.2 on a tricked out 2011 Macbook pro 17" OSX Yosemite

    I'm on windows 7, and similar dynamic issues were a result of having two versions of the same app on the machine, and not associating the files to use the latest version, etc, or a version mismatch. 
    Another workaround is to close PPro and import the project into AME, rendering it from there.

  • Maximum bit depth-maximum render quality when dynamic linking

    Hi
    A bit confused by the use of Maximum bit depth and Maximum render quality as used both in Sequence Settings and also as options when rendering in AME.
    1 Do you need to explicitly enable these switches in the sequence for best quality or, do you simply need to switch them on in AME when you render in Media Encoder?
    2 When dynamic linking to After Effects, when should you use an 8 bit vs 16 or 32 bit working space, and, how does this bit depth interact with the maximum bit depth, maximum render quality in PPro?

    Hi jbach2,
    I understand your confusion.  I'm like that most of the time I'm working. *chuckle*  The two settings you mentioned are two completely different parameters affecting (or is it effecting) your video. You do not need to enable them within the sequence itself unless you want to preview video on you program monitor at the highest quality.  I personally don't recommend it, as it's a tremendous resource hog, (the program even warns you when you try to click them) and unessecary for improving final output.  Again, do not enable these options in your sequence settings if you are only wanting a high quality export. Doing so will greatly reduce your editing performance unless you have a high-end system. ...and even then I don't think its worth it unless you're editing on a huge screen with a Director who wants to see everything at a maximum quality during the edit process.
    Keeping it simple...
    Resizing your final output video? Use Maximum bit depth.
    Starting or working with high bitdepth sources? Use Max Bit Depth.
    When/where do I enable these? In the AME only. ^_^
    Why?:
    Enabling the Max bit and Max render only needs to be done when you are exporting.  They both serve different functions. 
    Max Render aids in the scaling/conversion process only.  My understanding is that you never need to enable the Max Render Quality (MRQ) unless you are exporting in a format/pixel ratio different from your original video.  For example, when rendering a 1080p timeline out to a 480p file format, you'll want to use MRQ to ensure the best scaling with the least amount of artifacts and aliasing.  If you're exporting at the same size you're working with, DON'T enable MRQ.  It will just cost you time and CPU. Its only function is to do a high quality resizing of your work.
    Maximum bit depth increases the color depth that your video is working with and rendering to.  If you're working with video that has low color depth, then I don't believe it will matter.  However, if you're working with 32 bit color on your timeline in PPro and/or After Effects, using lots of graphics, high contrast values, or color gradients, you may want to enable this option. It ultimately depends on the color depth of your source material.
    The same applies to After Effects.
    Create something in AE like a nice color gradient.  Now switch the same project between 8,16,32 bit depth, and you will see a noticable difference in how the bit depth effects your colors and the smoothness of the gradient.
    Bit depth effects how different plugins/effects change your overall image.  Higher depth means more colors to work with (and incidentally, more cpu you need)
    Just remember that "DEPTH" determines how many colors you can "fill your bucket with" and "QUALITY" is just that, the quality of your "resize".
    http://blogs.adobe.com/VideoRoad/2010/06/understanding_color_processing.html
    Check out this adobe blog for more info on color depth ^_^  Hope that helps!
    ----a lil excerpt from the blog i linked to above---
    Now, 8-bit, 10-bit, and 12-bit color are the industry standards for recording color in a device. The vast majority of cameras use 8-bits for color. If your camera doesn’t mention the color bit depth, it’s using 8-bits per channel. Higher-end cameras use 10-bit, and they make a big deal about using “10-bit precision” in their literature. Only a select few cameras use 12-bits, like the digital cinema camera, the RED ONE.
    Software like After Effects and Premiere Pro processes color images using color precision of 8-bits, 16-bits, and a special color bit depth called 32-bit floating point. You’ve probably seen these color modes in After Effects, and you’ve seen the new “32″ icons on some of the effects in Premiere Pro CS5.
    jbach2 wrote:
    Hi
    A bit confused by the use of Maximum bit depth and Maximum render quality as used both in Sequence Settings and also as options when rendering in AME.
    1 Do you need to explicitly enable these switches in the sequence for best quality or, do you simply need to switch them on in AME when you render in Media Encoder?
    2 When dynamic linking to After Effects, when should you use an 8 bit vs 16 or 32 bit working space, and, how does this bit depth interact with the maximum bit depth, maximum render quality in PPro?
    Message was edited by: SnJK

  • Poor quality after timeline rendering of after effects dynamic link comp.

    One of my typical workflows involves dynamic linking AE comps into Premiere- Often I can playback the timeline in Premiere without rendering and achieve great results with no dropped frames. This scenario is ideal since I need to play out sequences in premiere passing them through a Matrox  MXO2 LE box to capture them on another system. However, I have noticed recently that if I need to render the Premiere sequences before playback because the dynamically linked AE comps are more complicated, I lose quite a bit of quality after rendering.I've searched around and read about different quality settings in both AE and PP and I can't seem to find any settings that affect this process. Pause and playback quality are both set to full, tried checking rendered maximum depth/quality in the sequence settings and I still can't get this right. I am perplexed since I would think that results would be better post-render.
    Dynamic Linked Clip Unrendered
    Dynamic Linked Clip Rendered:
    -A note about my settings:
    AE comps:
    720x480 (containing downscaled HD video)
    PAR: D1/DV NTSC (.91)
    29.97fps
    Resolution full 720x480 1.3 MB per 8bpc frame
    PP Sequences:
    720x480 (.9091)
    29.97p
    WINDOWS 7 - Adobe CC
    Intel Xeon(R)  12 cores 2.40ghz
    Nvidia Quadro 4000
    12g RAM

    The video preview settings were set to DV NTSC. I'm not sure why I didn't think to look at those settings. I went ahead and downloaded the Ut Video Codec Suite and things are now looking great - just like they do when I do not render the sequences. I am noticing now that my HD sequences usually are setup to use Matrox's Mpeg2 I frames only codec.
    Is the lossless codec choice always the best/most efficent choice to be used for the preview codec? I assume if I was not dynamic linking I should match this codec with the codec of the files in my sequence, is this correct?

  • Has CS6 fixed the PPro with AE dynamic links slow to render problems?

    I've got PPro with AE dynamic links slow to render problems similar to those discussed in this thread:
    http://forums.adobe.com/thread/904652?start=0&tstart=0
    As I understand it (and I could well be wrong), if I render a PPro project that has AE projects dynamically linked in (anything from simple lower thirds to color grading), during rendering the AE bits run as a service, which limits the AE bits to a single CPU and effectively stops simultaneous rendering of multiple frames. This is why I can get very high render times (essentially no parallel processing), and why messing with the number of CPUs allowed for simultaneous frame rendering, or the amount of RAM said CPUs can access, has little to no effect on total render time.
    Supposedly as some point AE was going to be changed such that it used Media Encoder to do it's rendering (same as PPro does), thus speeding up rendering for any PPro project that has AE parts dynamically linked in.
    Has this been done in CS6? If not, any idea when that's scheduled to happen?

    Jim Simon wrote:
    (I do wish Adobe staff would keep this distinction mind when creating their videos.  When I saw one about the new background rendering in PP, I was interested, only to learn that he was actually talking about background exporting, a feature PP has had since AME was introduced in CS4.)
    The distinction is not so distinct, and this is an industry issue, not really Adobe. After Effects has a render queue, which is used for exporting, but you can also export. Lightwave has this, even Avid. The terms do have their own distinct meanings, but of course context is usually required. So usually "rendering previews" or "rendering final output" serve as context-sensitive uses of the term.
    Terminology abuse is widespread, even people with video cameras now call themselves "filmmakers" and people who produce films never shown nor intended for a cinema call themselves "cinematographers." ENG video producers are called "photogs" and news photographers are called "photojournalists."
    Transcoding, encoding, rendering, exporting....mish-mashed unfortunately, but thankfully most people can figure out what's meant.
    Back to the OP - After Effects can be used with Adobe Media Encoder, it's just not the default. You can import any composition into AME from AE and render your encoded export.
    As for background rendering....I remember when Pinnacle Liquid was the first to the table with that feature back in 2004 or 2005. It seemed awesome, except that you needed a ton of spare hard drive space and lots of processing to keep the background rendering going...effecitvely your processor was in use 100% of the time. When you weren't scrubbing or playing back, Liquid was rendering previews. Of course, you could use those previews during export but you rarely would have wanted to do so, since it was better quality to reference the original data when compositing the layers and effects to output to a web file, for instance. Then  you had to keep cleaning up the preview cache.
    I rarely render previews at all, and when I do it's just a small segment at a time, just to get a full look at the final composite. Mercury Playback is usually more than capable of playing back most of my edits the rest of the time.

  • After effects CC on maverick slow render because of PP CC Dynamic Link Footage

    I put premiere pro CC edits in After Effects CC through dynamic Link every day. Since I upgraded my systems to Maverick and first installed the 12.0.1 and afterwards 12.1 the rendering of the After effects projects that have Dynamic Link Edits on the timeline slow down from 10 hours (in12.0 on Mountain Lion) to about 90 hours. When I replace the dynamic Link with a QT Movie, it renders about 10 hours again. It is normal that Dynamic link slows dow the rendering, but this is extreme and since this wasn't the case on Mountain Lion and 12.0 for the same project with the same dynamic link, not normal. I couldn't figure out what causes this. Is this Maverick on my 2008 Mac Pro ? is this a bug in 12.1 or dynamic link ? Or can I solve this with a simple setting somewhere in Maverick or AE ?

    I'm was having the same issues, turned off "app nap" for premiere and after effects which has mostly fixed things.
    The only thing now though is if I have a dynamic linked after effects composition within premiere and I have the after effects project open (that the composition came from) the dynamic linked comp within premiere won't play properly no matter what.
    Tried everything I can find on the net - app nap, full screen full res rendering within after effects - that composition just won't play and take ages to render if the after effects project that it came from is open.
    If I close the after effects project, the dynamically linked composition in premiere starts playing perfectly. Open the project in after effects and that dynamically linked comps stop playing. Any other dynamically linked comps from other AE sessions play fine within premiere (unless I open their original AE project!)
    This used to work fine before - it was great to be able to have AE and premiere open together and make changes in AE then switch to premiere to see the changes update, watch the sequence to get context, then flick back to AE, make more changes etc.
    Now I have to close the AE project, go to premiere, watch the sequence, open the AE project, make changes. When doing a few hundred adjustments over a week this can add considerable time to workflow!
    Any ideas? Is this happening for you guys?

  • Premiere-After Effects Dynamic Link render times vary wildly after minimal composition changes

    Here is something strange that happens a lot to me.
    I'll have a sequence in Premiere Pro CC 2014 that is entirely or largely an AE comp that I have dynamically linked.  I'll use a specific case as an example, but it's happened with various projects.
    In this most recent one the visual (but not audio) of my Premiere sequence is one AE dynamically linked comp of about 90 seconds.  It's more or less a fancy slide show- some photos with moves, some text, motion blur, masking, maybe a few filters.  Fairly basic stuff as far as After Effects goes.
    Anyhow, I like to render the sequence in Premiere and then watch it down with music to see if the timing works and make adjustments from there.  That's my usual workflow.  The strange thing is that when I render, the render times can vary tremendously.  With this particular project, one time rendered in about 2 minutes in Premiere.  I watched it down and I noticed a spelling error, which I fixed.  Just changing one word of text in AE.  This, of course, causes the entire linked comp to need to be rendered again in Premiere.  This time when I go to render, it took about 20 minutes and it only got about  70% of the way through.  A huge difference and all I changed was a couple letters, which shouldn't impact how intensive of a render is needed.  What I usually do is cancel the render when it takes that long, then quit Premiere, reopen, and render right away after I open.  When I do this, after the application restart, the sequence will then render in the faster approximately 2 minute duration.  Almost invariably this is true.
    So I end up quitting and restarting Premiere a lot to get the faster render times.  But of course that's annoying.
    What is going on here?
    I know that some might have critiques of the workflow and watching in Premiere and the fact that one letter change forces the entire sequence re-render.  I know I could break it up and there are ways around that.  But I am not interested in such critiques.  My work flow actually is quite efficient when the 2 minute render time happens.  Just not when it takes 10x more than that for the same thing.  Why are there these huge render time swings?
    My guess is that some cache gets filled up, so when the application is just started, and the cache is empty, the render works much better.  But I really do not know.
    Help please.

    There is currently a bug that causes Dynamic Link performance to be poor when the main After Effects application is running. (The underlying issue is that the main After Effects application is sending many more messages during Dynamic Link than it needs to.)
    The easy workaround is to quit the main After Effects application when using Premiere Pro to process a dynamically linked After Effects composition.
    This bug is fixed in an update due to be released in less than two weeks.

  • In CS6, why does my Ae dynamic link comp not stay rendered in Pr after render/save?

    I create a composition in Ae. Import the file and dynamic link to desired composition in Pr. Render a native timeline. Save it, then either go back a few minutes later or open the project again and the render preview is gone, requiring another full render to playback smoothly. Are my preview files being discarded or something of that nature?

    Try my workaround and let me know if it makes a difference:
    http://forums.adobe.com/thread/1144624?tstart=30

  • Dynamic Linked AE comp not using all cores in Premiere CS5 to render

    I have a project that is taking forever to render and am trying to troubleshoot it. It has an AE comp that is used several times and seems to be the culprit. If i load that into after effects and render with my "use 7 of 8 cores with 1GB ram each" setting in afx then my cpu usage is about 80-90% and it renders that segment in 50 seconds.
    Now when i link that into premiere and it is rendering along almost maxxing out all 8 cores until it hits that comp and then cpu usage drops down and only one core is at 80% and the rest are around below 20% and that segment takes almost 10 minutes for premiere to get through.
    Now obviously i can pre-render that and replace the comp and the problem will be solved but i would much rather see premiere render at full speed like it should. Am i missing something? With multicore systems this would make dynamic linking almost worthless if it wont use them (and i LOVE dynamic linking, it is a GREAT feature)
    system is win7, cs5, dual quad xeon (8 cores), GTX 460, and 20GB ram.
    thanks!

    > Am i missing something?
    No, you're not missing anything.
    This is a current limitation of using Dynamic Link between Premiere Pro and After Effects. When Premiere Pro calls the headless version of After Effects to render those frames, only one After Effects process is used.
    We're working on improving Dynamic Link. If you'd like to influence where we put our effort, please make a feature request so that the folks deciding what work to do can register your vote.

  • Dynamic Link Error (trying to render the Comp)

    Using Premiere Pro CC and After Effects CC:
    AE won't let me render a lossless video from a comp I created using Dynamic Link inside Premiere.  The workflow I'm currently trying to use is to lay out all my clips in Premiere, dynamic link to AE for denoise, grading, sharpening, add grain, stabilize, etc, render a lossless clip in AE, and then replace the dynamic link comp in the Premier timeline.  Unfortunately I get an error everytime I try to render my Comp from AE.  It will render a single frame using "Save Frame As" but it errors out with a sequence (.avi, .mov, and I even tried a targa sequence).
    I'm running a Windows 7 64 bit workstation.

    Can you create a comp from scratch not using the footage from Premiere and render a lossless video from the timeline? Can you create a simple comp in AE using your footage original footage without effects and render a lossless version? Can you apply the same filters applied to the comps that crash to any footage a successfully render?
    If the answer to question 1 is yes and the answer to question 2 is no then we need to know all about the original footage. What codec, frame rate, what camera. If the answer to question 3 is no then we need to know exactly what the filters are. An error message or crash report would also help.
    Without answers to these questions it's nearly impossible to tell what is going on because we don't have enough information.

  • Adjustment layer blur from AE to PP using dynamic link

    Hi there. I'm having trouble with a project I bring into PP from AE via dynamic link.
    Here's the problem. On my AE project, I have an adjustment layer with lens blur added to it. I also have a track matte assigned to that adjustment layer, because I have a specific shape in which I want the blur to be applied. Works fine in AE.
    However, when I bring the project into PP, the adjustment layer's blur is not applied to anything in PP. It does show up as a blur on animations I created in AE, but is not applied to any footage dropped under it in PP.
    Is this normal, or is there a workaround? At this point there it seems there is no benefit in using dynamic link over exporting the project as a clip with an alpha channel.
    If it helps to understand, the project is a lower third animation. The goal is to not only have it a little transparent but also slightly blur whatever footage is behind it, only in the area of the lower third.
    Any help is much appreciated!

    The export settings in PrPro should be ok, since they are the same ones I use for every other project. I did notice that the Max Render Quality checkbox was unchecked though. I just don't know why with the preview settings at max it still looks blurry. I have noticed that if I close down the project and reopen it, the problem might go away.
    I have tried exporting in AME, but sometimes the encoder just freezes up and won't render it. Again, another random issue. Not sure why that happens. (Though I recently learned about how to clean the cache and haven't tried exporting the project since then.
    I don't know if this will help or not, but what I do is align the footage up in PrPro and then use AE to import the footage. After getting everything the way it should, I use Dynamic Link in PrPro and pull in the AE file.
    I would assemble everything in AE, but the source material is P2 footage and AE doesn't have a viewer to differenate between all the clips.
    And to make sure for all clarity purposes, I can not reppplicate this problem. It seems to come and go as it wants, almost as if my machine is haunted.

  • After Effects Direct Link clips render slowly in Premiere

    I have a few clips I sent to After Effects from PPro via Direct Link and have noticed Premiere chugs along at a super sluggish pace when it gets to rendering or exporting those clips. Some clips take at least 5 times longer to render or export from Premiere than it does in After Effects which doesn't make sense to me. I have noticed in AE when I'm exporting my RAM is being utilized a lot but in PPro my CPU is maxing itself out while not using as much RAM – is there a way I can have PPro render utilizing the same system resources as AE?
    Direct Link is awesome in theory but right now I see two big problems with it:
    1) PPro takes forever to render Direct Linked clips so you might as well just export from AE and bring the clips into PPro
    2) I've read that when exporting from PPro, in order to get the highest quality export, it's best to not use render files which means even if you've rendered your Direct Linked in PPro in order to guarantee smooth playback you'll have to re-render them on export (please correct me if I'm wrong)
    Both of these issues makes me wonder what use Direct Link is other than a quick way to send clips to AE? Please help! I wan't this feature to be as awesome as it should be.

    Well that's a shame... If exporting from AE is required there should be a better method of getting the exported clip into PPro to replace the Dynamic Link clip. I was hoping I could point the comp in AE to use the lossless export as a proxy and therefore have PPro read the exported file rather than the AE comp but, unfortunately, that still produces stuttering playback.
    Fuzzy Barsik wrote:
    PrPro communicates with dynamically linked compositions via headless instance of AE, which limits processing to a single thread and, therefore, creates a bottleneck.
    I had high hopes for Dynamic Link, this is a sad revelation. Hopefully this is an issue Adobe is working to fix.

  • AE to PP Dynamic Link blurriness

    For some reason, every once in a while my dynamic links from After Effects to Premiere Pro come out slightly blurry. While the linked object is still useable, it is not crisp.
    I am using the latest verison of CC with all the updates installed on a Mac OS X 10.8.5. Upgrading the OS is not possible due to the IT guys not wanting to upgrade the company yet. As far as hardware goes, I'm using a Mac Pro with 2 x 2.66 GHx 6-core Xeon processor with 32 GB ram and plenty of hard drive space. The types of things pulled from AE are vector files (usually .ai files), jpegs, and text. When rendering out to a high quality H2.64 Quicktime movie with lossless output, this happens as well.
    These are random occurances. No way to explain or replicate why it happens.
    The first screen shot is with the blurriness. Look at the American Airlines part specifically.
    The second is without the blurriness.
    I know that this is just a minor issue. You might even have to blow the pictures up super big just to see the difference. Just looking if someone else has the same problem or even a fix.

    The export settings in PrPro should be ok, since they are the same ones I use for every other project. I did notice that the Max Render Quality checkbox was unchecked though. I just don't know why with the preview settings at max it still looks blurry. I have noticed that if I close down the project and reopen it, the problem might go away.
    I have tried exporting in AME, but sometimes the encoder just freezes up and won't render it. Again, another random issue. Not sure why that happens. (Though I recently learned about how to clean the cache and haven't tried exporting the project since then.
    I don't know if this will help or not, but what I do is align the footage up in PrPro and then use AE to import the footage. After getting everything the way it should, I use Dynamic Link in PrPro and pull in the AE file.
    I would assemble everything in AE, but the source material is P2 footage and AE doesn't have a viewer to differenate between all the clips.
    And to make sure for all clarity purposes, I can not reppplicate this problem. It seems to come and go as it wants, almost as if my machine is haunted.

  • Premiere Pro CS5.5 Dynamic Linking Broken

    I have a project in Premiere Pro CS5.5. Brough in all my greenscreen footage and did my edits. When I got picture lock from client I "replace with after effects comp" and did my keying in AE. This worked great throughout the project until yesterday when doing some final tweaks. Premiere would not load all the media, it got to 222 items reamaing and stalled, for hours! Then I moved the folder where all my graphics where and skipped the files when loading premiere and premiere then opened. I relinked all my graphics just fine, but when it came to relinking my AE dynamic link projects, got the spinning beach ball. I figured I would just let it spin overnight and see what happened in the am. 12 hours later it was still spinning. This is very frusterating and I can't think what I did to mess it up or if it's a dynamic link problem. I may have opened and edited the AE project without premiere open, maybe thats what messed it up. Any thoughts?
    Mac Pro 8-core 3ghz
    12 GB ram
    6TB fibre channel drive
    Mac OS 10.7.3
    Adobe Production Premium CS5.5 (all up to date)

    I've heard of other issues with DL from AE, but not this one... the problem I'm used to seeing is that you've got the wrong footage, and that's usually fixed by unlinking and relinking, which you've done. I rarely use AE myself, and when I do, I've generally found that I get better results by NOT using DL... but I know it should work, so perhaps someone else will have some answers for you. As long as you have the AE project still, you can always just render out your comps as lossless AVIs with UT or Lagarith and then import those to PrPro and replace the DL clips...

Maybe you are looking for