AE to Media Encoder slows when rendering multiple project files

So I'm trying to load in a bunch of compositions from various project files into Media encoder to render over night. I've noticed the first couple of projects render pretty quickly then it starts to bog down a lot. I mean very slowly chugging along through the renders. Is this a memory cache issue??? Any way to fix this? Is there a way I can clear the memory after a render finishes and before it moves on to the next?

See the known issue here about Adobe Media Encoder taking a very long time to open the first time on Mac OSX v10.10 (Yosemite):
After Effects with Mac OSX v10.10 (Yosemite)
Based on this, my suggestion is to open Adobe Media Encoder once, give it plenty of time to start because of this Mac OS bug, and then try again. My guess is that it'll work fine after that.

Similar Messages

  • Adobe Media Encoder crashes when I open a file

    Adobe Media Encoder crashes when I browse to open a file.
    I have a Creative Cloud subscription.
    I have uninstalled and reinstalled the program through the Creative Cloud service. No change.

    Thanks for responding.
    Yes, I am trying to utilize Photoshop CS (8.0) and I run Windows 7.1. I installed this from Adobe's Creative Cloud. The program opens, and I am able to open a Photoshop file with it, but then Windows tells me that there is a problem and is shutting down. I'm not sure would the problem might be.

  • Premiere Pro CC 2014 & Media Encoder Crash when rendering

    Every time I try and render something out of Premiere Pro CC 2014 it will crash before it completes the render. I have no idea why. I am on a windows 8 machine running the latest version of Premiere Pro CC 2014.Any idea what is going on?
    Here is the log from Event Viewer:
    Faulting application name: Adobe Premiere Pro.exe, version: 8.0.1.21, time stamp: 0x53c7b17f
    Faulting module name: mc_enc_avc.dll, version: 9.8.11.6624, time stamp: 0x536af65d
    Exception code: 0xc0000005
    Fault offset: 0x00000000000e7f80
    Faulting process id: 0x650
    Faulting application start time: 0x01cfb99562fe469a
    Faulting application path: E:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
    Faulting module path: E:\Program Files\Adobe\Adobe Premiere Pro CC 2014\mc_enc_avc.dll
    Report Id: f30f38a1-2589-11e4-bf2c-bc5ff467c039
    Faulting package full name:
    Faulting package-relative application ID:
    Here is the Report.wer that windows automatically generates: http://pastebin.com/hriEegkJ
    I have also tried rendering out of media encoder and I get a crash also (Report.wer: http://pastebin.com/Dpvk6bDb):
    Faulting application name: Adobe Media Encoder.exe, version: 8.0.1.48, time stamp: 0x53c99d97
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x000000002c2cce3d
    Faulting process id: 0xcf8
    Faulting application start time: 0x01cfb9906060796e
    Faulting application path: E:\Program Files\Adobe\Adobe Media Encoder CC 2014\Adobe Media Encoder.exe
    Faulting module path: unknown
    Report Id: 07096c20-2584-11e4-bf29-a0f3c1153ce7
    Faulting package full name:
    Faulting package-relative application ID:

    More hardware information might help someone give you an idea
    -Premiere Pro Video Editing Information FAQ http://forums.adobe.com/message/4200840
    or
    http://blogs.adobe.com/kevinmonahan/2014/01/13/computer-shuts-down-with-premiere-pro-or-af ter-effects/

  • MacBook Pro with SSD that has a limited disk space (120GB). Rendering in Project File (User/Movies/Final Cut Projects), it takes huge space and the limited disk space would not be enough for the whole editing.

    I'm using MacBook Pro with 128GB SSD that has a limited disk space. As we know, when rendering in Project File (User/Movies/Final Cut Projects), it takes huge space and the limited disk space would not be enough for the whole editing.
    My question is, Is there any method to get the rendering Projects file saved into an external hard drive which is connected with USB/ Thunderbolt/ Firewire, with huge disk space (eg. 500GB HDD).
    Now, new project created in my Mac is automatically saved in (User/Movies/Final Cut Projects) and my Mac has ran out of space to hold the files.
    Thank you.

    You have at least 3 different ways to show the project library:
    1) Go to WIndow->Show Project Library
    2) Click the button in bottom left of your window: 
    3) Hit the keyboard shortcut (Command-0)
    The project library will be shown, occupying the area where the timeline usually is.
    Your hard disks will be visible. Click the hard disk where you want the new project to reside and hit Cmd-N to create a new project.

  • Media Encoder crashes when exporting from Premiere Pro

    Media Encoder crashes when exporting from Premiere Pro. I am queueing multiple files for export and Media Encoder will crash. The computer system has 32GB of RAM and the videos export fine in Premiere, but that requires exporting each one individually. Each video file is being down converted and some can be quite long (upwards of 3-5 hours). Nothing else is running on the computer that would take up memory.
    Any idea why Media Encoder will crash?

    Try turning off GPU acceleration.

  • Adobe Premier pro running very slow when rendering a file

    Adobe Premier pro running very slow when rendering a file

    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
    The title of the Console window should be All Messages. If it isn't, select
              SYSTEM LOG QUERIES ▹ All Messages
    from the log list on the left. If you don't see that list, select
              View ▹ Show Log List
    from the menu bar at the top of the screen. Click the Clear Display icon in the toolbar. Then take one of the actions that you're having trouble with. Select any messages that appear in the Console window. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
    The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
    Please don't indiscriminately dump thousands of lines from the log into this discussion.
    Please don't post screenshots of log messages—post the text.
    Some private information, such as your name, may appear in the log. Anonymize before posting.

  • Media Encoder crashing when I try to batch a bunch of files

    I am trying to have the Media Encoder batch convert a bunch of files, but when I try to add the files, the whole program crashes, or when it's on the first few files, it crashes.
    Any suggestions?

    XP Pro (x86) SP3
    Quad Core (Q6600)
    4GB Ram
    Nvidia GeForce 8600 GT
    I installed the 4.02 update for Media Encoder, but before it was doing the same thing.
    Sometimes it would work, sometimes it wouldn't.
    I was trying to encode wmv files to avi.
    It could be there is something else running that is causing this, but I tried closing basically everthing else, and still not stable...

  • CS4 Media Encoder Crash after rendering - two files, help?

    I'm not a professional so I would appreciate any advice you can offer.  I was encoding a WMV HD video (edited in Premiere Pro from CS4) that was just under 2 hours long.  On an i7-920 with 9GB of RAM, it took just over 16 hours.  At the end of the encoding, the Media Encoder bar displayed 0:00:00 time left.  But it then froze at that point for about 30 minutes.  Then the program crashed.  I planned to take these WMV files and put them, via Encore, onto a dual-layer DVD with a few other special feature-related videos. 
    I now have two versions of the file in the destination folder, one that has the title I gave it and another that has a "._00_" before the title.  Both files are .wmv files and the one with the normal name is 6.64 GB whereas the one with the ._00_ before the name is 6.60 GB.  Both have problems if I try to play them beyond the 60% or so point.
    Is there a way to salvage these files without another 16 hour render? 
    How long should I expect, on a normal/successful render, for Media Encoder to continue to process the file after the countdown reaches 0:00:00?
    Thanks.  Any advice for this very untrained editor would be appreciated.

    On the topic of opening a project on the exact same version of Premiere Pro CC 2014 (yes it is definitely up to date, and the 2014 version), to overcome this export crash problem that ZachHinchy has brought up - you can't. Technically speaking, one should easily be able to open a Premiere Pro CC 2014 project from one system on another system running the exact same up to date, legitimate version of Premiere Pro CC 2014 without any kind of error. But for some reason, this has been disallowed(?) by Adobe. It has facepalm written all over it. Does anyone agree that this is at least a little bit silly?
    I have tried exporting a Final Cut Pro XML from my project to try and open the sequence at uni on a Mac, so I can render my project when I finish my edit. It half works - the clips are there, but the sequence is gone - i.e. 12 hours of painstaking sequencing and micro-edits that had me at several points in time wanting to insert my hand through my monitor with enough force to make a large hole. I really cannot afford redo this sequence, as my assignment is due tomorrow, and I have to work at 6 oclock in the morning, so I also cannot afford to stay up till the early hours of tomorrow morning. Wish me luck that some miraculous event has taken place overnight that will somehow allow me to just open my project, on the same version of Premiere, on a Mac, without hassle. (Apple OS is not friendly to anything but its own selfish nature, so I am having doubts).
    Adobe please, if you can do anything at all to help, you will save my assignment, and my faith will be restored. Otherwise, I'll just get my money back and buy Final Cut instead.
    I cant even
    If I find a way to fix either of these problems, I will post straight away.

  • Why is quicktime slower when using multiple mdat atoms

    Hi,
    I've been trying to generate a mov file and I noticed that the more mdat atoms I put in my mov file the more the file takes time to load on QuickTime, iTunes.
    Even worst, on the iPhone the file takes more than 3 minutes to load.
    If there are too many mdat atoms quicktime even says that the file is invalid ( error -2004 or -2002, I don't remember exactly).
    Why is quicktime/iTunes slower when using multiple mdat atoms ?
    Thanks,

    Yeah! Problem solved: It's a QT issue.
    Cause: Mac Update Software downloaded a faulty QT.
    Solution: Download QT from Apple's QT site.
    Great to have the Video back

  • How to install Adobe Media Encoder C6 when CC is all ready installed

    Hello
    I need to be able to publish flv files, but the new Adobe Media Encoder CC can't export FLV files, therefore I need to install an older version. But I can't find it anywhere. Not on Adobe.com or en the creatiev Cloud App under previous versions. Does anyone know where to find it?

    I hope this link helps.
    Install a previous version of any Creative Cloud application
    Media Encoder CS6 is bundled with some Video apps and cannot be installed by itself.  Installing Premiere Pro CS6, After Effects CS6, Flash CS6 or Prelude CS6 would install Media Encoder CS6.

  • FCPX 10.0.7 hangs when loading multiple projects - a non-destructive work around

    FCPX 10.0.7 hangs when loading multiple projects - a non-destructive work around....
    Hi Guys, I upgraded from FCPX 10.0.6 to 10.0.78 and discovered to my immense frustration that many of my 100+ FCPX projects would not load.
    Symptom:
    FCPX 10.0.7 appears to hang ("spinning beachball") with either high CPU% on a single core or  with 1-2% CPU busy (activity monitor.app) when a FINAL CUT PROJECT is selected. No logs error information in /var/logs ..hmm
    notices that the "status circle" spins around endlessly.
    Actvity Monitor.app shows "Final Cut Pro (Not Responding)
    and also I notice in some cases that an OEM filter ("NEAT VIDEO NOISE REDUCTION") is in progress to be loaded. FCPX V10.0.7 must be FORCED QUITtted to remove it from system.
    History: Upgraded FCPX from V10.0.6 to V10.0.07.
    "FINAL CUT EVENTS" and "FINAL CUT PROJECTS" on a single file system on SAS 16TB disk array (768MB/sec read via AJA system test) and 60% utilised capacity… FCP EVENTS has 400 events in it .. some 5.2TB of Prores essence etc .. all works fine! (i.e. the storage system is first class and is NOT the issue)
    32GB of RAM on MAC PRO 2009 Nehalem 16 x Vcore with ATI 5780 card and ATTO HBA's (i.e. plenty of resources!)
    As usual with any "upgrade" to FCPX 10.0.? all the EVENT objects need to be upgraded. In my case this takes an hour or two.. so I do that when asleep.
    After experiencing above, I restored the FCPX EVENTS LIbrary of that file system from LTO4 tape archive (BRU-PE ) and still had the same issues as above.
    WORKAROUND:
    FORCEd QUIT FCPX V10.0.7
    RENAMEd "/volumes/some_file_system_volume/Final Cut Projects" to "/volumes/some_file_system_volume/Final Cut Projects_original"
    created (make) a new "/volumes/some_file_system_volume/Final Cut Projects" (use finder)
    For each project !!! in "/volumes/some_file_system_volume/Final Cut Projects_original", (do one project at a time!!!)
    MOVE "/volumes/some_file_system_volume/Final Cut Projects_original/one_fcpx_projext_nnnn_folder" to "/volumes/some_file_system_volume/Final Cut Projects"
    Make sure you move ONLY one project at a time. If you have a subfolder of projects, please do each project one at a time (serially!)
    Launch FCPX V10.0.7 and BE PATIENT!!! .. DONT click or fiddle with the UI.. it seems when you intervene it locks up as well…
    Let FCPX V10.0.7 settle….
    select the project you just added above  and RELINK any objects it needs. Thumbnails and proxies will be rendered again.. just be patient
    wait until ALL the rendering as stopped.
    QUIT FCPX V10.0.7
    (now if FCPX locks up, just force it out and start again as above).
    repeat for all projects in "/volumes/some_file_system_volume/Final Cut Projects_original" (go to step 4 ad do until all projects moved)
    When all is COMPLETED MAKE SURE YOU ARCHIVE an instance (or make a backup ) of "/volumes/some_file_system_volume/Final Cut Projects"
    If this procedure has worked the folder "/volumes/some_file_system_volume/Final Cut Projects_original" will have zero (nill, none) projects in it.
    I have managed to restore ALL my  "/volumes/some_file_system_volume/Final Cut Projects" this xmas between drinking etc. I'm satisfied that its all ok.
    Other issues:
    use DISK WARRIOR or TT PRO 6 to make sure that the file system volume where your  "/volumes/some_file_system_volume/Final Cut Projects" are is physically ok. I noticed some entries in file system's  volume table that represented objects in  "/volumes/some_file_system_volume/Final Cut Projects" were at fault when I used these utilities… FWIW.
    SUMMARY: yes this took ages to d, however luckily I had everything in at least 3 instances in an archive which has saved me many time in the old FCP& and prior days… it was just a matter of time to put it back together.
    I put this outage down to may be my own impatience when I first fired up FCPX 10.0.7 after the upgrade.
    I'm interested if this workaround is helpful to others and in addtiion if others have a more satisfactory remedy.
    HTH
    warwick
    Hong Kong

    Hi Eb, yeah I could not see any "memory leak" or unusual consumption of REAL memory whose less availability would cause excessive PAGEing and SWAPping as seen in the Activty Monitor.app
    I watch this carefully especially the use of REAL MEMORY by 3rd Paryy apps. BTW there are a few that cause ALLOCATED but NOT USED memory (blue in the A.M.app UI). Simply a unix PURGE command can release that memory and help clean up the PAGE and VM swap files (its alleged!).
    Yes, you may be might with the element of "Luck" involved. I would add though, that having MULTIPLE project displaying in the STORYLINE window and loading always caused my FCP 10.0.7 jam up at startup with h symtoms and observations I described.
    TIP: I might also add that for a super speedy launch of FCPX one may also emply setting each PROJECT's UI to show only AUDIO thus negating the need to contstruct or reneder out a PREVIEW ui in each clip in the storyline.
    Your/Apples  suggestion of the movememt (rename) of "Final Cut Pro Projects" to "Final Cut Pro Projects Hidden" is similar to what I proposed above to stop FCPX 10.0.7 accessing and building it up at startup. This workaround has been useful inthe past as well.
    ALso one might also get the stick out and remove (delete/rm) the ~/Library/Saved Application State/com.apple.FinalCut.savedState in one's home ~/Library so that FCPX wont do such a neat job reinstating FCPX last time you crashed it... This has been helpful also in diagnosing my issues.
    Lastly I have noticed that:
    impatience clicking on the FCPX UI when in the unstable state causes it to lock up with NO visible CPU% busy.... as if its waiting on something which is usually me MEMTERMing it via FORCE QUIT and
    the projects where I have employed the NEAT VIDEO Noise Reduction OEM filter for FCPX seem to exasserbate the PROJECT loading issues when several PROJECTS are available at FCPX startup time.
    As of yesterday I have some 400+ EVENTS Final Cut Pro Events and 130+ projects of varying compexites in a single file system on Final Cut Pro Projects all working fine and as good as gold again!
    Oh and one more thing, I had to RE-RENDER many projects of them again... strange as the FCP PROJECT library was renstated from a recent LTO archive as of V10.0.6 FCPX.. strange that...I would have expected if the projects and events were 10.0.6/7 compatable as proposed by Tom, that this would not be necessary... hmm straneg that
    I'll monitor this thread.
    Thanks for your comments lads!

  • When rendering a project, FCPX did not stop at 100% but appeared to keep rendering - when it reached eleven thousand something, I quite FCPX (it allowed me to quit).

    When rendering a project, FCPX did not stop at 100% but appeared to keep rendering - when it reached eleven thousand something, I quite FCPX (it allowed me to quit).

    The background tasks indicator just kept going and going... 200, 300... 400... 600...800... When I opened the background tasks window, the only process it said was active was rendering. 
    I clicked on "stop" but it ignored me, kept counting on and on....  1000... 2000,,, 5000 I clicked Pause, it didn't ignore me but still kept counting...  7000... 10,000...
    I went to my activity monitor on my mac and from what it said (like, 97% or so idle), I surmised that it actually had stopped rendering.  So I quit FCPX - no problem, no "not responding" or "force quit" or anything. 
    My external harddrive was still whirring (that's where my project is stored) so with much trepidation I ejected it: no problem...
    After my question I (agian with much trepidation) opened FCPX, did some editing, rendered, exported, without problems. 
    But I'm concerned about what might have caused this bizarre behavior and what to do if it happens again.
    any thoughts???

  • Adobe Premiere CC crashes when opening a project file ....    error 3697 . [was:Adobe Premiere CC]

    Adobe Premiere CC crashes when opening a project file ....    error 3697 ....  have to close application with Task Manager.... media files open separately OK

    Just that one project, or any project?  Can you create new projects?

  • Can I link multiple project files together?

    I'd like to link multiple project files together so that they will play one after another. Can you do that in Captivate?

    Hey Leslie,
    Yes, you can create several projects in Captivate and publish them as Flash (SWF) format. There is an aggregator project in Captivate where in you can combine all these published projects (SWF) into a single output.
    Do you have any other requirement as well?
    Thanks,
    Anjaneai

  • GPU acceleration is grayed out in Premiere and AE, but not in Media Encoder. However, rendering is slow in all 3 programs.

    It worked fine in CS6.
    Now, everytime I open a project (Pr or Ae) I get the message: This project was last used with GPU Accelerated rendering. This happens with all projects, even with those that I created in Pr/Ae CC, with GPU Accelerated rendering already disabled.
    In Media Encoder, the GPU Acceleration is not grayed out, but still if I render a premiere sequence or an ae comp via ME, its very very slow. (takes 5 hours for a video that took 20 mins in CS6)
    Any thoughts?
    Thanks, Daniel

    I think I found the problem. On the website you linked, it says:
    The following notebooks are not compatible with this tool:
    Notebooks equipped with switchable graphics
    Toshiba® notebooks
    Sony® VAIO® notebooks
    Panasonic® notebooks
    And I have a Sony VAIO.
    When searching for drivers, I only found sites like these: AMD Radeon HD 7650M drivers
    Are these legit?

Maybe you are looking for