Adobe Media Encoder CC renders do not reflect changes to Dynamically Linked After Effects Comps

When rendering a Premiere timeline with a dynamically linked After Effects composition, Adobe Media Encoder will sometimes use an older version of the linked composition (even after I have saved changes in the After Effects comp).
For example, if I correct a spelling mistake on some text in After Effects, save the composition, and then add the sequence to the render queue in Premiere, the final output from media encoder still has the old spelling.
If I do a straight export from Premiere instead of adding to render queue, the output is always correct. I've noticed this problem on several different Windows 8.1 systems.
All versions of the software are up to date as of today.
Why is this? Is it something to do with the disk cache in After Effects? Does media encoder have it's own cache that I need to clear?

Hi, I've been having this same issue.  Here are some additional things I've noticed about it:
Changes are reflected properly when played back on timeline in Pr CC 2014.
Happens regardless if the dynamic link file was rendered or not, thus deleting the render files does not fix the issue.
The issue can persist through saving, closing, and reopening both AE and Pr. 
I'm using OSX 10.9.4, so this is not just a PC issue.
Other than manually watching for every change to be reflected in the render, there is no way to know a problem has occurred.  Needless to say this can be incredibly costly.
Please address this quickly, it's completely unacceptable that what we render out could be a different version from what we see on the timeline.
PS Some additional things I will be testing:
Does the issue persist through closing all CC apps, including Media Encoder.
Does rendering directly out of Pr, i.e. not using Media Encoder, fix the issue.

Similar Messages

  • Both After Effects & Adobe Media Encode CC giving are not letting me export.

    Dear All,
    Both After Effects & Adobe Media Encode CC giving are not letting me export movies.
    Some times they will, but after one file both programs give me the following error messages.
    After effects:
    “[file path and name].mov. An output module failed. The file may be damaged or corrupted. (-1610153464)"
    AME:
    "Can't read from source."
    I've went through the forum and found threads & pages discussing the problem.
    E.g.
    http://blogs.adobe.com/aftereffects/2013/08/solutions-for-problems-with-quicktime-files-in -after-effects-cc-12-0-because-of-conflict-with-dvcprohdvideoout-quicktime-component.html
    http://forums.adobe.com/thread/1252092
    After following all the tips and suggestions (from deinstalling quicktime components & audio components to completely reinstalling CC) I'm still experiencing the problems.
    Which leaves me in a bit of a squeeze. I need to export over 144 movies in the coming 2 days and the only way to do this is to quit and open media encoder (or AE) after each single export.
    Not really an option.
    Both problems have the process Adobe QT sever in common, I took this from the console:
    9/26/13 1:02:44.517 PM com.apple.launchd.peruser.501[171]: ([0x0-0x42042].com.adobe.Adobe QT32 Server.application[331]) Job appears to have crashed: Segmentation fault: 11
    9/26/13 1:02:44.672 PM ReportCrash[354]: Saved crash report for Adobe QT32 Server[331] version 7.0.1 (7.0.1.0) to /Users/martijn/Library/Logs/DiagnosticReports/Adobe QT32 Server_2013-09-26-130244_martijns-MacBook-Pro-2.crash
    System information:
    Retina MacBook Pro (Mid 2012) (16gb ram)
    Mac OS X 10.8.5 (12F37)
    Running Adobe CC (for teams), all apps are up-to-date.
    I don't no why Adobe puts out such a buggy piece of software (I know it has to with Apple's poor 32bit quicktime implimentation, but hey, this was known information no?).
    Upgrading to CC has given our office nothing but problems.
    Hope someone can help to find a work around until Adobe realeases a proper update and solves this problem once and for all.
    All help is much appreciated.
    Kind regards,
    Martijn

    Hello Tim,
    Thanks for the really quick response!
    Regarding the crash log: it doesn't reference com.apple.audio.CoreAudio (though it did before, so I followed all the steps in your blog post before I posted to this forum).
    I've uploaded the crashlog to:
    http://martijnlambada.com/TMP/AdobeQT32servercrash.zip
    If you want to inspect it. It mentions the DXV codec (which I also uninstalled), but the crash keeps occuring. Also I need to export to DXV since it's the only codec the d3 media
    server accepts (http://d3technologies.com).
    I followed all the steps in the troubleshooting steps.
    Codecs used: I've tried everything from animation to Apple ProRes (including: h264/motion jpeg/uncompressed). With all codecs the Adobe QT32 server keeps crashing (though I can't always reproduce).
    Export destination: Internal SSD (same as where the OS is installed on) + External raid (via firewire & thunderbolt) + external HD via usb 3.0 (tried everything).
    When does the problem start: Really hard to specify, sometimes a day without crashes, sometimes every export for days on end. Sometime after restarting (tried logging out, restarting, switching off and on the computer). With other programs running and with out. Now checking every process active when exporting, and comparing log files.
    Can you export to other formats: See question 1, sometimes I can, sometimes not.
    When you launch AE and/or AME, is QT32 Server running? At what point does it stop running?  Still runing when I open the program. It crashes when exporting (ofter after finishing the first export).
    What component files are in your Library/QuickTime folder?: Currently the folowing:
    AppleAVCIntraCodec
    AppleHDVCodec.component
    AppleIntermediateCodec.component
    AppleMPEG2Codec.component
    AppleProResCodec.component
    DesktopVideoOut.component
    DVCPROHDCodec.component
    DVCPROHDMuxer.component
    DVCPROHDVideoDigitizer.component
    DVCPROHDVideoOutput.component
    DVCPROHDVideoOutputClock.component
    FCP Uncompressed 422.component
    iChatTheaterPreview.component
    IMXCodec.component
    LiveType.component
    Hope this helps.
    Cheers,
    Martijn

  • Adobe Media Encoder pausing rendering while working in Premiere Pro

    Hello everyone,
    So I am redering a video in Adobe Media Encoder and at the same time I am editing a new one in Premiere Pro.
    I noticed that AME is constantly pausing the rendering and did not know why. It turns out that while I'm editing a video in Premiere Pro, I am constantly pressing the space bar to start/pause the video I'm editing. While I do that, AME keeps pausing/unpausing the rendering. Somehow, pressing the space bar in PP has an effect in AME.
    I have no clue why it does that because the Premiere Pro window has the focus, not the AME one.
    Has anyone ever seen that?
    I use Windows 8 and Adobe CC.

    Hi Rallymax,
    Yes I do queue footage by having an Autowatch set up on the directories where the video is written to.  I rarely do a direct export unless testing new settings.
    Don't take this as gospel but I too had a feeling that GPU acceleration didn't happen with AME, only direct export.  Not sure where that came from, I did watch some of the recent Adobe TV Web Seminar's about new features of CC products etc, so maybe on one of those?
    I found this while trying to find out where I had seen it but it is from AMD site not Adobe so whether it's fully 100% correct I dunno:
    Adobe Media Encoder
    The Adobe Media Encoder (AME), with support for OpenCL™ and GPU acceleration, automates the production of multiple encoded versions of source files, sequences, and compositions in Premiere Pro CC. With the GPU-accelerated AME and AMD graphics technology, editors can quickly encode projects and output files for virtually any destination. AMD GPUs handle the heavy lifting, freeing the system’s CPU to perform other functions.
    I will try the same test as Jason, if I can find any AVHCD video and see what the results are.  Will be interesting.

  • AME Adobe Media Encoder Cuda GPU Acceleration not activated, How do I activate it

    Mac Pro Early 2009 4.1, Processor  2.93 GHz Quad-Core Intel Xeon, Memory  16 GB 1066 MHz DDR3 ECC, Graphics  NVIDIA GeForce GTX 680 2048 MB, Software  OS X 10.9.2 (13C64)
    Adobe CS6 suite up to date all programs as of 3-18-14
    NVidia Cuda Driver 5.5.47 installed, Open CL and GL capable
    I read this article http://blogs.adobe.com/kevinmonahan/2013/09/13/enabling-cuda-for-the-mercury-playback-engi ne-in-the-macbook-pro-retina/. it shows GPU acceleration through AME (see below). In my AME que window I do not see this

    Todd:
    (edit)
    Just reread - sorry, CS6 vs CC.
    What about AME CC?
    http://blogs.adobe.com/kevinmonahan/2013/09/13/enabling-cuda-for-the-m ercury-playback-engine-in-the-macbook-pro-retina/
    So, CUDA acceleration in AME and OpenCL is supported.  Anyway to monitor this?  I get FAILED when I try either (on a box with nVidia, or a box with AMD).
    Found this:  http://helpx.adobe.com/media-encoder/using/whats-new-media-encoder-7-1.html#gpu-accelerati on
    GPU acceleration
    Adobe Media Encoder now takes advantage of GPU for rendering purposes. Both CUDA and OpenCL are supported. The latest release of AME uses the GPU for the following renders:
    Scaling (HD to SD; SD to HD)
    Timecode filter
    Pixel format conversions
    Deinterlacing
    Aspect ratio changes
    All effects in the Effects tab
    GPU accelerated effects in Premiere Pro
    If you are rendering a Premiere Pro sequence, Adobe Media Encoder will use the GPU render preference you have set for the project. All GPU rendering capabilities of Premiere Pro are utilized.The limited set of GPU renderable tasks in Adobe Media Encoder is only for renders that originate in Adobe Media Encoder.
    If you are rendering a sequence with native sequence support, the GPU setting in AME is used and the project setting is ignored. In this case, all GPU rendering capabilities of Premiere Pro are utilized directly in AME.
    If your project uses 3rd party VSTs (Virtual Studio plugins), the GPU setting in the project is used. The sequence is encoded through headless Premiere Pro just as in earlier versions of Adobe Media Encoder. If Enable Native Premiere Pro Sequence Import option is unchecked, headless Premiere Pro will always be used and the GPU setting is used.

  • Adobe media encoder export error  "writer not found"

    When trying to export to wmv using adobe media encoder I get an export error of "writer not found". I did a search and found others having the same issue with no fix as far as I can see. Just wondering if anyone has any more iformation on this. I'm using Vista Ultimate and Premiere CS3.
    Thanks

    I registered the WMEncoderHelper.exe file with regserv, but I still get
    the "writer not found error". I wish I knew what codec it is trying to find and use.

  • Adobe Media Encoder CS5.5 does not preview video in Lion 10.7.3

    In response to a question in the Adobe Forums about this [ http://forums.adobe.com/message/4302817#4302817 ], Adobe said:
    Apple changed something in 10.7.3 and we thought we worked with them to find all the fall out.  This one slipped through.  We will work with Apple to determine how we can address this.
    Are there any updates on when this will be fixed? Not being able to preview video in AME5.5/MacOS 10.7.3 is a serious bug. I have to go back to an earlier version of AME on a Windows machine to encode FLVs.
    Adobe Media Encoder CS 5.5.1.12 (64-bit)
    Mac Lion 10.7.3

    I have the same problem since I update my mac book pro Mac Lion 10.7.3
    Adobe Media Encoder CS5.5 doesn't have a preview

  • I can't choose Adobe Media Encoder when rendering to video in photoshop

    I am trying to export an animation in Photoshop CC.
    Under Render to Video, the dialog box does not allow me to choose "Adobe Media Encoder" (it is greyed out)
    Why is that?
    I have Adobe Media Encoder CS6 and CC.
    Thanks!

    Unfortunately, photoshop cc doesn't support video on mac os x 10.6.8 and that's why you not able to export using the Adobe Media Encoder.
    At the bottom of this page under Product Level Changes:
    http://helpx.adobe.com/photoshop/using/whats-new.html

  • Dynamic link after effects and adobe media encoder

    Hello,
    I recently downloaded After Effects cc (yesterday). I am running a mac pro with OSX 10.9.3 2.3 ghz intel core i7 with 16 gb 1600 MHz DDR3.
    On previous versions of AE I was able to render straight out of AE, I know this is not the case with CC anymore. I am trying to use AME to export however I am having issues.
    When I try to send to AME from the Composition tab in AE it looks like it is doing something and then nothing happens. I then opened AME separately and tried to "add after effects comp" from the file menu in AME the error message displayed was "Could not connect to Adobe After effects. Please verify that Adobe After effects and Adobe Dynamic link components are installed".
    I have also tried to drag and drop my composition directly from AE to AME and the following message appears "Dynamic link error - Source is empty"
    I have read a multitude of threads on this issue and this is definitely not a firewall issue. Any advice would be GREATLY appreciated.

    > On previous versions of AE I was able to render straight out of AE, I know this is not the case with CC anymore.
    Why do you think that? You can still use the render queue in After Effects to render and export directly out of After Effects.
    That said, there are some formats that Adobe Media Encoder handles better.
    > and this is definitely not a firewall issue
    How have you determined that?
    Does exporting to QuickTime (.mov) format from After Effects work? How about the 3D Camera Tracker and Warp Stabilizer effects? The reason that I ask about these is that they use the same communication mechanism that Dynamic Link does, so if they also fail, then it tells us something about where the problem is.

  • Adobe Media Encoder CS5.5 crashing (not responding) when adding files

    Hello,
    I am running AME CS5.5 on a late 2010 MacBook Pro.  I have been trying to create some broadcast quality .mpg files for my local cable provider's Video On Demand service but AME keeps crashing on me whenever I add a .mov file to the queue.  I am using Final Cut Pro and Adobe After Effects CS5.5 to edit video and create animations.  I have been able to encode a few files into the required .mpg specs, but now I can't even add a file into the queue without it freezing up.  I then have to force quit the application to shut it down.  I have recently repaired my disk permissions and used DiskWarior to clean up and create a new directory.  Is this a known bug?  Is Adobe working on a fix.  I hope so because I have some projects due in mid-September and would hate to have to resort to using Apple's Compressor instead of AME since AME is faster.  Any help would be much appreciated.
    Here are my Mac specs:
    Model Name: MacBook Pro
    Model Identifier: MacBookPro6,1
    Processor Name: Intel Core i5
    Processor Speed: 2.53 GHz
    Number Of Processors: 1
    Total Number Of Cores: 2
    L2 Cache (per core): 256 KB
    L3 Cache: 3 MB
    Memory: 8 GB
    Processor Interconnect Speed: 4.8 GT/s
    Boot ROM Version: MBP61.0057.B0C
    SMC Version (system): 1.57f17
    Operating System:
    OS X Snow Leopard 10.6.8
    Software:
    Adobe Master Collection CS5.5
    Apple FInal Cut Studio 3
    Apple Final Cut Pro X
    Apple Motion 5
    Apple Compressor 4

    Is this happening with all files? Just QuickTime files? Just QuickTime files using a certain codec?
    I'm taking a shot in the dark, but any time that someeone mentions hangs and QuickTime, I suspect the problems described here:
    http://kb2.adobe.com/cps/857/cpsid_85711.html

  • Adobe Media Encoder... Not encoding

    So I got my video all said and done.
    I export the media.
    The encoder pops up, and I start the queue.
    ...and this is where my problem starts.
    The job will sit there and not start what so ever... I left it for an hour and came back to 00:00's...
    I notice PPROHEADLESS.exe is running and pretty much maxing out my cpu.
    When I kill it, the conversion job starts, but only for a few seconds.
    Then I kill pproheadless again, and another few seconds will convert.
    If I kill the process to many times, it stops converting all together...
    Help?!

    Here is a link to another recent POST on this issue. I'm doing this to keep references to recent PProheadless posts together.
    Good luck to all,
    Hunt

  • Adobe Media Encoder CC - I Can Not Download.

    http://www.adobe.com/support/downloads/product.jsp?platform=Windows&product=160
    JUST DOİNG UPDATE...
    CAN NOT İNSTALL....
    PLEASE HELP.....

    Without system information and otehr details nobody can say anything. Chances are you will have to run the cleaner tool and start from scratch.
    http://www.adobe.com/support/contact/cscleanertool.html
    Mylenium

  • Adobe Media Encoder Update for Mac not working?

    Hey!
    My Premiere says that there is an update available for the AME.
    When i open the PatchInstaller it says: "This Patch is not suitable for you."
    In a normal case AME is installed together with Adobe Premiere, isn't it?

    >> In a normal case AME is installed together with Adobe Premiere, isn't it?
    The above comment has been true for stand alone installation of major releases.  But when it comes to patch release, each product is on its own.  Generally speaking, PPro and AME products release patches on the same day.  There have been a few cases where PPro had a patch (like 7.2.1) and there was no AME corresponding patch.
    >> My Premiere says that there is an update available for the AME.
    >> When i open the PatchInstaller it says: "This Patch is not suitable for you."
    What versions of PPro and AME do you currently have on your system?
    What version does PatchInstaller wants to install on your system?
    The latest released versions of PPro and AME patches are 7.2.2.

  • Adobe Media Encoder CC 2014 would not be updated to 2014.0.1.

    The update has failed many times. I just uninstalled to it in order to reinstall

    In Mac OS, go to Username/library/Logs/AdobeDownload/DLM.log
    You'll find at the end of the file (corresponding hour and minutes) a string like so:
    2012-08-17T16:20:29: connecting to: = http://swupdl.adobe.com/updates/oobe/aam20/mac/AdobeMediaEncoderCS6-6/6.0.1/Setup.dmg
    2012-08-17T16:20:30: ThreadDownloadUpdates:: Need to download a .sig file for this dmg at: /Users/bahaelaila7/Library/Application Support/Adobe/AAMUpdater/1.0/Install/AdobeMediaEncoderCS6-6/6.0.1/Setup.sig
    2012-08-17T16:20:30: ThreadDownloadUpdates:: downloading .sig file from : http://swupdl.adobe.com/updates/oobe/aam20/mac/AdobeMediaEncoderCS6-6/6.0.1/Setup.sig
    2012-08-17T16:20:31: ThreadDownloadUpdates: ERROR: File Size Mismatch, between what is given in manifest and what is that of bob.
    2012-08-17T16:20:31: UCGetprogress : WARNING - Download failed due to file size mismatch at server.
    Copy the link and paste in Safari, download and manually install it.
    Now close the cc app
    Relaunch it and redo the same thing for all the errors.

  • Time-specific Image Overlay using Adobe Media Encoder

    Basically I just want to add a black screen at the end of my video. Is there a way to easily do this in Adobe Media Encoder without having to use other video production programs like After Effects or Premiere Pro?

    Thanks for the input. So just to confirm, you're saying that if I choose one of the Adobe Presets under QuickTime, that that setting should STAY visible in the selection box. Yes? Just like the others. Windows Media, Adobe Flash, etc...
    Because mine immediately changes to CUSTOM after I make a QuickTime selection. Also, it DOES NOT give me a file size estimate like the others. Does this make sense?

  • Media Encoder is rendering an older version of my Premiere timeline.

    This has happened to me on a few occasions, where I have a dynamically linked After Effects comp in my Premiere timeline, the changes I make appear as they should in the Premiere timeline, but when I queue it to Media Encoder or render directly through Premiere, it renders the older version of the AE comp, as if it thinks nothing has changed. This happens even after cleaning the cache, saving a new copy and restarting premiere.
    The only way I've managed to fix it, is by saving a new copy of the Premiere project file over the temp file submitted to Encoder.
    This is how it looks on my timeline (Correct):
    How it looks when I queue through Encoder (Incorrect):
    Any help on how to avoid this in the future would be much appreciated!
    Cheers,
    S

    I thought you had something working after you installed FFDshow tryout.
    It would be helpful if you could upload one of your files that you can't convert to a file sharing website. Then others can download the file and work with it on their machine to see if they can convert it.
    I use MediaFire's (http://www.mediafire.com) free plan to upload and share files. For example, http://www.mediafire.com/?uhpmob5nc1w6q is a link to one of my files: "Kodak Zi8 720 30p." It's not a direct link.

Maybe you are looking for