Adobe MEdia Encoder Crashes with big files inputed

Hello,
There isn't a forum for the Adobe Media Encoder, so I thought this would be a good spot. I am an after effects and Premiere user who likes the idea Adobe seems to have of using the media encoder to cover all my encoding needs.
My typical workflow, especially since these days I'm doing more shorter form animations, is to render out to a Quicktime Animation codec file as my main archive file. From there, output all the various different web versions, flv, etc from that core archive file. Since my projects usually aren't running more than 5 minutes, this leaves me with a nice 3 - 7gig file.
Problem: I'm running CS4 and the media encoder crashes when I input files that are in this file size range. The program locks up when I push start que, and then eventually crashes. Works fine with smaller size files that are about under a gig.
I can run a render out of after effects, which seems to be more stable. But I'd love to be able to use this great new tool.
Here's my machine specs if it helps:
PC
Intel Quad Core Q9550 @ 2.83 ghz
4gB RAM
Windows Vista 64 bit ultimate
All updates current for CS4 apps as of 01/30/08
Running Adobe Media Encoder V 4.01.078
Hard drives are nothing special. 7200 rpm western digital internal and external. I've tried all sorts of hard drive configurations, where the input is coming from, where it's going, etc. No difference.
I have been experimenting with using Lossless AVI's as my "uncompressed" archive file. Works well, but same crashing with the Media Encoder.
Also tried experimenting with frame size alterations during encoding, no difference there. Also, whatever the output codec is, be it FLV, H264, etc. no difference.
Anyone have any thoughts or have experienced similar issues? I hope all my MAC friends aren't right, seems like all my attempts to streamline my workflow with this CS4 and beefy PC combo are crashing and burning.
Anyone else feeling this pain, or have recommendations?
Thanks,

Thomas, thanks for your suggestions on Vista optimization. That Sheer Codec looks nice, but hard justify the cost when I've been working for years with essentially uncompressed codecs that work well. Will play more though to see if the cost would actually pay off in the long run though.
In general I made a decision that it was too early to throw in the towel on my old uncompressed codecs. The Quicktime animation codec has always been for me the safest, most universally accepted, and most reliable "uncompressed" codec. It's always worked in the past, not gonna give up just cuz media Encoder CS4 has troubles.
Mylenium, thanks for the reminder about the silly platform wars. I've always felt the same as you, but when I'm stressing sometimes the silly propaganda can get to me. Makes me forget that no matter what system ya got, it never works perfect!
Here's an update. I have trying my best to learn more about the bug and have come to some interesting realizations. The AME does work with larger files, just not the larger files that I had been using at the current moment. Older files of mine as big as 20GB can be inputed into AME with fine results.
This being said, it scratches out most of the RAM overload thoughts with AME.
The difference with my current files that were causing AME crashes: larger than a few GB, came from AE, had the 1.21 pixel aspect ratio metadata.
When I re-interpreted the file in AE into a square pixel aspect ratio, exported it, it was then successfully inputed into AME.
I have read just now that there were changes in After Effects widescreen pixel aspect ratio interpretation in CS4. Can this change be causing problems in my AME. Not positive, but I'm now thinking after many days of testing that the bug could have its roots somewhere in this ball park.
If anyone from Adobe is reading this, I would love any ideas you might have on this issue. In general, there is really no support for the Adobe Media Encoder itself. This is not good, considering how it is so necessary for AE and Premiere users like myself.
Thanks,

Similar Messages

  • Adobe Media Encoder - Issue with exporting file

    When I send a file to Adobe Media Encoder and I hit queue I get an error, "could not read from source file, please check if it has been moved or deleted".
    The source file location that the AME is trying to use is C:\Users\User Name\AppData\local\temp\file name.prproj
    Is this file location correct?
    Why is not using my scratch disk file?
    How do I change the file that AME is trying to use?
    I have not been able to export a video since I have purchased Premiere CS4.
    Any help with this would be greatly appreciated.

    If you want a quick work-around do not try exporting from Premiere, just save and exit the project after you are through editing.  Open AME and under File, select Add Premiere Pro Sequence, browse for your project file and click on it once--have patience Adobe's feedback here is lousy--your sequence will finally appear in the Sequence window, click on it and then click on OK.  Select your Format,.Preset and Output location.  If you want to tweak your settings just click on the Settings button.  Then hit Start Queue.
    Do you have the project on an external removable drive?

  • 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.

  • Premier Pro CC and Media Encoder crashing on long file export.

    Please forgive the length of this inquiry. But it is complicated and has a lot of variables.
    I have an hour long mixed format timeline both Red 3K footage and Black Magic ProRes 1080P footage that I want to make a DVD from and it takes forever and crashes half way through. I have tried doing it every way possible and the only way I was able to get even a partial export was using the "MPEG 2 DVD" export option in Premier CC. It goes fast at first telling me it will take about 2 hours but even though it starts quickly doing about 15 fps it slows down to less than 1 fps and finally just stops and crashes my Cuda Core enabled Macbook Pro Laptop.
    I really don't know who to ask about this since there are so many different variables. I never had a problem like this on my MBP with PP6 on a 4K timeline exporting to DVD or Blue Ray or to H-264 or Even Prores. But I wasn't mixing formats either. But on this project the first 20-30 minutes of footage goes through fine in a couple of hours but something seems to be bogging down the system on longer projects. My work around was to break the project up into multiple exports and combining them on the DVD timeline but I can't do this on every project. I thought maybe it was a corrupted clip somewhere in the timeline but when I broke the timeline up into several parts I had no problems.
    I did notice a dramatic variance in the time it took to export footage based on the sequence settings. A one minute timeline comprised Red 3K footage and ProRes 1080P footage Here are some sample export results:
    From a Red raw 3K timeline 2880x1620  with 1080P Prores footage upscaled 150%)
    to .m2v Mpeg 2 720x480 format    1:48 Minutes ***
    to .mov  Prores 422HQ  1080P                         22 Minutes
    to .mov H.264  1080P                    22 Minutes
    to .m2v Mpeg 2 1080P                                                22 Minutes
    From a 1080P timeline Prores footage at 100%  (Red footage downscaled to 67%)
    to .m2v Mpeg 2 720x480 format                         13 Minutes
    to .mov  Prores 422HQ 1080P                             13 Minutes
    to .mov H.264  1080P                                                             14 Minutes
    to .m2v Mpeg 2 1080P                                                            14 Minutes
    Since I am going to DVD,  I chose the fastest option  Red to m2v Mpeg 2 720x480 format which only took 1:48 per minute. Why? I have no idea. Maybe someone here knows the answer. But again these numbers are for a ONE MINUTE clip when I tried to convert the whole hour timeline to  the 720x480.m2v DVD File the Red timeline froze my computer after several hours even though I had set sleep mode to “Never” and turned the display off manually and I had to convert it in multiple chunks. In 20-30 minute chunks it did go fast about 1:48 per minute like the test indicated. But I would like to be able to convert the whole hour and not to have to try to stitch the clips together in my DVD authoring program.
    I don’t want to have to avoid using multiple formats on the same timeline or waste time transcoding everything to the same format.
    Can anyone give me any suggestions as to why the computer is crashing or bogging down in long exports and what timeline settings I should be using?
    I have plenty of room on my Scratch Disk and 8 Gig of RAM and according to my Activity Monitor during the export process  have about 800 Meg of System Memory during export but the CPU Usage is 98% and in my Activity Monitor I see under “Process Name” ImporterRedServer flashing up at the top of the list about every second during export.
    Why .720x480 mpeg DVD setting is so much faster than all the other export codecs?
    And if there are any other settings I can use to get higher speed exports in HD? 14x1 seems a little slow especially since every time it crashes I have to start over.

    Hi,
    Since a long time I did not encounter the crash of Media encoder with
    long file export.
    But I take care of a lot of details before the export :
    - clean up Media cache and Media Cache Files within PP CS6 and/or CC,
    - delete all render files with Preview Files,
    - rendering of sequences until the rendering is completed,
    - PP CS6 and/or Pp CC opened during export to AME and/or Encore CS6,
    I guessed to leave Adobe but this company remains the last with a
    serious authoring software (Encore CS 6).
    I tested :
    - Avid Media Composer, Final Cut Pro X, both are very good software but
    no really authoring software for these video editing softs.
    Th only way is to "flood" Adobe with "bug reports" and "wish forms"
    which are not very easy to use.
    And also to call the Adobe support day by day until they send they
    escalate the bug.
    Le 16/05/2014 16:51, alainmaiki a écrit :
    >
          Premier Pro CC and Media Encoder crashing on long file export.
    created by alainmaiki <https://forums.adobe.com/people/alainmaiki> in
    /Premiere Pro/ - View the full discussion
    <https://forums.adobe.com/message/6384665#6384665>

  • Really need help with AME Adobe Media Encoder crash on startup.

    Hey all, this is my first time posting in these forums.
    I have Adobe Design Premium and need to use the included Media Encoder for a project I'm working on.  It opened well the first time, and I started converting a file - at which point it crashed.  Since then, when I start it, it shows the startup / loading image, but once finished opening disappears and closes itself.  I've tried reinstallig, no dice.  I also read the plugin log files (My Documents > Adobe > Adobe Media Encoder > Log Files) - nothing out of the ordinary.
    Very stuck and very frustrated - any suggestions would be really appreciated.
    Thanks!

    Hi Michael. Without more information about output settings, the project, the computer, etc, I can't speculate on the cause of the initial crash. I can, however, offer a suggestion as to why the app is now failing to launch: the initial crash may have corrupted the application settings. If you delete those settings, or otherwise hide them from AME, then the app will create fresh settings on the next launch.
    Windows Vista & Win 7: C:\Users\<<yourUserName>>\AppData\Roaming\Adobe\Adobe Media Encoder\<<yourCreativeSuiteVersion>>*
    Windows XP (from distant memory): C:\Documents and Settings\<<yourUserName>>\Local Settings\Application Data\Adobe\Adobe Media Encoder\<<yourCreativeSuiteVersion>>
    Mac: <<partition>>\Library\Preferences\Adobe\Adobe Media Encoder\<<yourCreativeSuiteVersion>>
    *On Windows 7 & Vista, if you can't see the App Data folder, you'll need to set Windows Explorer to show hidden files and folders: Tools>Folder Options>View tab.
    If this does the trick to get AME running again, and if it again crashes on you, please provide as much information as you can about the project, export settings, system, etc.

  • Using Adobe Media Encoder CS4 for MTS files

    Hey everyone, I did some searching on this topic to no avail so here I am.
    Anyway, I recently got an HD camcorder that records in 1080i AVCHD.
    I have no problems getting the MTS files off of my camera but as I'm sure you can imagine, working with those files is a whole other issue.
    I've found that Adobe Media Encoder CS4 works great in encoding these files to QuickTime format (.mov) but the problem is that the resulting file size is actually bigger than the original MTS file which is unacceptable, especially considering I'm encoding the files from 1920x1080 down to 1280x720.
    Does anyone have any experience using AME CS4 to convert MTS files to a more workable 720p format for uploading to YouTube?
    I've tried a number of different custom settings to no avail (where you see an "or" is where I've tried different options):
    Format: QuickTime
    Video Codec: MPEG4-Video or H.264
    Quality: 100
    Width: 1280
    Height: 720
    Frame Rate: 29.97 or 23.976
    Field Type: Lower First or Upper First or Progressive
    Aspect: Square Pixels (1.0)
    I won't list the audio options because I don't think that has any bearing on my problem.
    Any ideas as to why the encoded file sizes are actually larger than the MTS file sizes?  Maybe AME CS4 is not what I should be using for this task?
    Thanks for your help,
    Tom

    I figured it out.
    If you select H.264 as the format you can then select YouTube Widescreen HD for the preset.
    This will set everything up to convert your MTS file to 720p and reduce the file size by around 30% with little quality degradation in my experience so far.
    The only problem I encountered was the video was kind of choppy when the camera panned but that was remedied by upping the frame rate from 24 to 29.97.
    Hope this helps someone and if anyone has any suggestions to improve efficiency or reduce file size post it in here.

  • Adobe media encoder crash

    its not a show stopper but getting a crash in C++ (virtual function call?)
    after rendering in media encoder 6.0.3.1 (32-bit).
    Its being sent from premiere, and rendering h264, 720 50p.
    Encoder than stops responding.
    In fact even if encoder has not rendered anything - if I just start it up and close it again - it crashes on exit
    I'm on windows 8 64 bit.  I just dowloaded microsoft C++ redistributable 2010 and was told there was a newer version on the machine. Could this be the issue? (that  media encoder doean't like the new C++?)
    Error stuff from application event log:
    Faulting application name: Adobe Media Encoder.exe, version: 6.0.3.1, time stamp: 0x5057aebb
    Faulting module name: MSVCR100.dll, version: 10.0.40219.325, time stamp: 0x4df2be1e
    Exception code: 0x40000015
    Fault offset: 0x0008d6fd
    Faulting process ID: 0x2ae8
    Faulting application start time: 0x01ce3be758479a67
    Faulting application path: C:\Program Files (x86)\Adobe\Adobe Media Encoder CS6\Adobe Media Encoder.exe
    Faulting module path: C:\Windows\SYSTEM32\MSVCR100.dll
    Report ID: 98ae627c-a7da-11e2-be70-e0cb4e2c4d27
    Faulting package full name:
    Faulting package-relative application ID:
    Fault bucket -1113903016, type 1
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0
    Problem signature:
    P1: Adobe Media Encoder.exe
    P2: 6.0.3.1
    P3: 5057aebb
    P4: MSVCR100.dll
    P5: 10.0.40219.325
    P6: 4df2be1e
    P7: 40000015
    P8: 0008d6fd
    P9:
    P10:

    Hello!
    Try this:
    First Disable the UAC, on Editing machines i dont like to use it:
    Press WinKey + R
    and paste this :   useraccountcontrolsettings
    Enter and put the slider down to end and apply.
    Reboot.
    next reset the Encoder Settings
    go to Windows Explorer
    in the Bar paste
    %appdata%\adobe
    find the folder   Adobe Media Encoder
    and rename it to Adobe Media EncoderOLD
    Try export again!
    i hope this help something as did to me.

  • After Effects + Adobe Media Encoder + Flash = Most Random File Sizes Ever

    Asking this question in this AE forum because I think more would have knowledge on the topic here than the Flash Forum. 
    I've heard that video compression is more of an art than a science...  Could someone provide me some insight on the following?
    -Created a 12 second, 30 FPS, 300x250 banner animation inside of After Effects
    -Exported for FLV/Flash to be placed inside of a 300x250 .FLA
    -Comps rendered directly from Adobe Media Encoder standalone instead of Render Queue in AE (for 2 pass .FLV's, and heard from various that .FLV's from render queue are not the prettiest at times). 
    I've always been under the impression that I would get smaller file sizes with SWF's externally linking to an FLV.  If I do it this way, I end up with: 
    41 KB .SWF  + 668 KB .FLV = 709 KB
    However, if I EMBED the same 668 KB .FLV to the FLA's timeline (not using the flvPlayback component) I end up with a 381 KB file size!
    I am just confused on the logic here, could someone explain the reasons for this?  I always thought my file size would be bigger if it was embedded to the timeline. 

    Actually I think it's the tons of extra AS code that make linked players fatter. Never could make sense of the why and how myself, but you can find enough alternate free players/ skins (nonverblaster for instance, which I use) that are a lot leaner.
    Mylenium

  • Adobe Media Encoder Crashes when launched

    Hello, friends on the forum!
    I am using a PC with a Windows XP (Home Edition) o/s.  It has an Intel Pentium 4 cpu @ 2.80 GHz and 2.5 gb or RAM.  This problem just developed: when I try to export a CS4 project, AME hangs and crashes.  I then get a message saying "Adobe Media Encoder CS4 has encountered a problem and needs to close.....yadda, yadda, yadda!"  It then, by itself, tries to launch again with the same dismal result.  Any suggestions as to how I might fix this?  Many thanks in advance!
    Lewis Beck

    Work through all of the steps (ideas) listed at http://ppro.wikia.com/wiki/Troubleshooting
    If your problem isn't fixed after you follow all of the steps, report back with ALL OF THE DETAILS asked for in the FINALLY section, the questions at the end of the troubleshooting link... most especially the codec used... see Question 1

  • Adobe Media Encoder crashing system

    I  am experiencing crashes whenever I use Adobe Media Encoder for a file 2  min. or more.  It seems no matter what format I save in flv, quicktime,  etc. or size – NTSC, Custom, 1080p the same results..  Please advise as  I cannot use program until fixing this problem.
    I am using Premiere CS4 on Windows Vista, quad core 3.2 AMD processor, 16 gb RAM
    Don
    Also; earlier this year when I had this similar problem, I  needed to upgrade my power supply and it completely fixed the problem.   Since it has started again, I;ve upgraded the power supply  substantially, but this time no change.

    When a system crashes, there is often a breadcrumb trail left behind. This ARTICLE will give you tips on finding clues in that trail.
    This ARTICLE will give you tips on setting up your computer for an editing session.
    Good luck, and hope that helps,
    Hunt

  • Adobe Media Encoder CS4 converted FLV files have sound but no picture

    Hi,
    It would be great if anyone can help - I am using the latest trial version of Flash CS4. I have used the Media Encoder to convert mpg4 files to FLV however the resultant files play with sound but no picture - just a black screen. Is there a solution to this issue?

    mostly this problem is caused by lacking of
    some nessery codec. Which means when reencoding your video to flv, it can not generate the video.
    Does Riva FLV encoder needs any extra codec? I am using Moyea Flash Video MX 6. It do not need any extra code. It needs in the former versions but in version 6 it can convert nearly any video format now.

  • Adobe Media Encoder bug with Cineform .avi

    I encoded an HDV m2t file to Cineform intermediate in Sony Vegas. I added that file to Adobe Media Encoder's render cue. No matter what export format I choose, AME fails to recognize the source file's pixel aspect ratio of 1.33:1 and produces a horizontally squashed image.
    Even the source window incorrectly shows the file as having a PAR of 1:1. Premiere Pro CS4 won't load the source file properly. I can import it into AE CS4. From there, I exported it to the same Cineform intermediate, and then it works fine in AME.
    Why can't AME and Premiere Pro recognize the proper PAR in the Vegas-encoded Cineform file?

    I'm not even sure if this qualifies as a "bug". The only thing at issue (if I understand correctly) is that AME is failing to recognize the PAR of the file. AFAIK, there is no "standard" for flagging PAR in AVI files (aside from DV footage, which can have simple boolean 16x9 flag).
    Adobe has their RIFF headers -- but this is by no means a standard across the entire industry. There is no indication that your file contains any PAR information whatsoever.
    If you open the file in Premiere, you should be able to right-click on the clip in the Project window, go to Interpret Footage and select the correct PAR of 1.333.
    The problem is that the standalone version of AME does not have an "Interpret Footage" option to override PAR assumptions for AVI files, etc. that are added to queue. This is a good idea for a feature request for future versions of AME.

  • Adobe Media Encoder Crash / hang

    I have exported a few vids in my 30 day trial of Pro CS4 BUT last night I paused a vid that was encoding (it got pretty late) and this morning if I try to open Media encoder then it loads up to the point at which the screen would normally appear and be active and it hangs.. vista comes up and says "a problem has caused the program to stop working" etc.. I am forced to close the window..
    I have tried the export from cs4 route and the same happens.. please help I have called cust support but they cant help as its only a trial..
    thanks
    g
    (i have tried the update..)

    Hi Geoff,
    try removing the AME preferences from
    C:\Users\username\AppData\Roaming\Adobe\Adobe Media Encoder\4.0
    before relaunching AME.
    Thanks
    Aurobinda

  • Media Encoder crashes with Bluescreen

    I'm using Adobe Premiere CS4 w/ Windows XP to edit some MPEG2-Videos. All I do is importing them, doing some edits and exporting them back as MPEG2. Everything worked just fine with Premiere CS2. But since I upgraded to CS4, everytime I try to export a file with Media Encoder, my system crashes.
    In about half the cases, there's a Bluescreen 000000B8 "A wait operation, attach process, or yield was  attempted from a DPC Routine". In the other cases, the BSOD errors vary (PFN_LIST_CORRUPT, PAGE_FAULT_IN_NONPAGED_AREA), the system just freezes or restarts without warning.
    What I've tried so far:
    Updating mainboard/chipset drivers
    Upgrading BIOS to latest version
    Switching graphics accelerator
    Trying different hard disks
    Changing RAM
    Checking Syslog for errors
    Lightning a candle on Sunday :-)
    Reinstalling Apple Quicktime
    Deinstalling all Adobe Software and reinstalling them from scratch
    All Adobe programs and Windows itself are up to date
    Any more advises?

    Often these problems can be caused by a faulty PSU or by heat problems. Use Speedfan or HWMonitor to check these and please post a link or screenshot to the results. Can you give some more details on the hardware side? Mobo, processor, RAM, PSU, video and disk setup, etc.

  • Adobe Media Encoder crashes when borders are applied to the "barn doors" effect.

    Pproheadless.exe stops working. End of story. Doesn't matter what kind of clip I try to apply this to. Barn Doors works; Barn Doors with a border doesn't.

    Ah, sorry about that. It's what happens when I post in frustration at 5:00 in the morning. But thanks for the response.
    Windows 7 64-bit
    Premiere Pro 5.5.1
    Combined Community Codec Pack
    K-Lite Codec Pack
    Not sure if Mercury Playback is enabled. The crash only happens when creating a file in Media Encoder. I've isolated the problem to rendering as a DVD-Mpeg with "Render at Maximum Depth" checked. When it is unchecked, the files render without a crash.

Maybe you are looking for

  • Where did my pro go?

    I ordered and paid for QT Pro a little over a year ago. Since, I have used it to edit several videos w/o a problem. BUT recently when I load QT, I can not access the PRO settings. I try to re-register but do not know where to find the reg. key. It is

  • How to output results to a file?

    If there is no Debug capability, how to output test results to a file?  Are there any other ways to do this? Thanks!

  • Creating Properties and Methods for an exe built in LabVIEW

    Hi all, How do we create properties and methods for an executable built in LabVIEW. I know when building an exe, the "Enable ActiveX server" option in advanced has to be enabled. But after that how do we create Properties and methods for the activeX

  • Cursor Disappears After I Return From VIewing Web Video In Full Screen Mode

    After I view a video from a web site in full screen mode using Safari v6.0.1 or Firefox v15.0.1, I escape to normal screen mode. When I then try to move the cursor using the built-in trackpad, I am unable to see the cursor anywhere on the screen. I d

  • 1 GB Promotion Error...Need help!

    I received and activated my iPhone 6 Thursday.  Unfortunately, the extra 1 GB of data did not show up on it's own.  I called Customer Service Friday and both the Rep & Supervisor said there is no way to fix this because the system automatically adds