Adobe Media Encoder freezes with one second left

Hi all,
All of a sudden now, when I export from Premiere CS4 to AME, regardless of what codec I use, AME hangs with just one second left to go. It will not finish encoding, no matter how long I wait. When I hit "Stop Queue" the program itself hangs, and I have to "Force Quit" to start over.
I have installed the 4.0.1 update for both Premiere and AME. Running on a Macbook Pro 2.5 GHz, 4 GB RAM. Anyone else have this problem and figured out a solution?

Sounds like the empty timeline or premiere's 'black video' freeze issue.
For some reason the encoder freezes when the timeline encounters any 'blank' frames. By blank I mean either an empty timeline, or any of the Premiere generated color mattes, title cards, bars and tone, etc. (if this is overlaid with 'real' video footage it does not seem to be an issue).
So if your project ends with a fade to black, or some black footage at the end, that may be the culprit. Is this happening in your case?
Solution: I've generated a black video file (i created and exported this in After Effects) that I have now laid on the first (bottom) layer of every Premiere project I start. I have a 5 second video file that I just stretch over the duration of the project before I render. This has solved the freeze issue for me. If you search the forum there is other mention of introducing opacity keyframes into your generated footage as another work around. I haven't tried this way myself, so I can't fully comment.
Good luck!

Similar Messages

Adobe Media Encoder Freezes

I am using Adobe Premiere Pro CS4 V4.2.1 on a Windows 7 64-bit system. I have an Intel Core i7 processor running at 3.1 GHz, 12 GB of DDR3 RAM running at 1413 MHz, an nVidia GeForce 260 core 216 graphics card, and a video disk consisting of 2 WD 7200 RPM HDD striped as a RAID 0.
Encore was crashing the computer everytime I selected the Build tab and clicked on the Blu-Ray button. This was solved by updating the Sonic Solutions PX Engine.
Now I have problems with the AME. I am working on a 2 Hr 39 Min project with .mp4 clips which Adobe's "Get Properties For" recognizes as XDCAM EX files NTSC, 1080i, 1920X1080 at 29.97 FPS. My preset is selected accordingly.
I have seen multiple posts about Adobe Media Encoder freezing but never found a definitive answer. I have gone as far as doing a clean install and reinstalling PrPro but nothing has changed.
The same thing happens when I try to build an H.264 Blu-ray disk image in Encore or whether I try to render the timeline in Premiere Pro CS4. The transcoding proceeds normally and the orange progress bar progresses for the first 3 - 3 1/2 hours. All 8 processor cores are running temps of 56-60 degrees Centigrade. After 3 - 3 1/2 hours the processor core temps fall to 36-40 degrees and there is no further progression of the orange bar over the next 3-4 hours. At that time the transcoding of Sequence 1 is about 30% complete. I then hit the cancel button and the busy ring spins and spins for about 10 minutes. Then a Windows pop-up says the program is not responding and asks if I want to close the program.
I had an almost identical project when I was using Windows Vista 64-bit and PrPro CS4 on the very same computer, but before the V4.2 update came out, and did not have any problems at all. I have been using Premiere Pro for about 14 years and have never encountered crashes like I am having now.
Hopefully somebody has the answer for this???

I am no expert but I had this happen also.
It turned out to be a bad video clip.
Have you rendered the project? (Sequence>Render Entire Work Area (Timeline must be your active box I believe))
Does it finish or hang?
If it hangs up you most likely have a bad clip or empty space.
The experts will be able to give you more to go on but that may get you started.
Also, I never trust the new Windows 7 "not responding" popup.
I always go to task manager and have a look, if I wait for something I know should take a long time it is almost always a false popup.
Watch for the ImporterProcessServer.exe *32 process. If it takes up a full core worth of processor percentage, you most likely have a problem with a clip. (I am willing to back off that “opinion” but it holds true for me.)

Firefox keeps crashing when I try to launch it. I uninstalled the program, but now when I try to download it from your website the download freezes with 1 second left. This has happened several times.

firefox keeps crashing when I try to launch it. I uninstalled the program, but now when I try to download it from your website the download freezes with 1 second left. This has happened several times.

Hello Deb,
Something fishy going on with those particular files. But without looking at them directly I couldn't say what. Usually in a case like this the problem is some of the metadata that is attached to the file. Where did these files come from? A camera, a scanner, the internet?
An explanation about the Watched Folder function: It looks for changes to a folder, not just automatically grabbing whatever files are in it. Generally, you want to select an empty folder as a Watch Folder. Once this has been set up, as you add files to this folder they will be imported into the Organizer. If you start with a folder full of images, those will be ignored, any new items will be added.
-Brett

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,

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

Export problems!!! Freezes with 5 SECONDS LEFT!!!

My Adobe Premire Elements freezes when I go to Share>PC>MPEG>Save, but only after most of it is done and it says it will be done in 5 seconds. This is really important because these videos are for a local video station and are broadcast weekly. I just got Adobe Premiere Elements two days ago and this is my first project on it. Can someone help?

After you have followed Steve's advice and insured that everything is good there, take a good, long close look at the end of your Project. Use the horizontal zoom to get the Timeline greatly magnified. Step slowly through the Assets near the end of your Timeline (remember, the 05 sec. is for the total Export operation, so look beyond the last 05 sec. on the Timeline.) with the PageUp and PageDn keys. Look for things like gaps in your Video Tracks. You do not want any gaps. Also, study the exact Assets at the end. Do they differ from the rest, i.e. different format/CODEC for a video, or maybe a very large still image. Is there any difference near the end? Go slowly and look very carefully.
Good luck,
Hunt

Latest Update of Adobe Media Encoder Issue with C4D Source

Updated Media Encoder to Build 8.0.0.173 this AM when the Adobe notification came through and it now refuses to encode any project with C4D source. The issue is codec agnostic. Tried with both C4D R15 and R16. No joy. Any clue? Would like to roll back to the previous version but not sure that option is available within the uber-slick CC Adobe world.

I'm confused. You say that you updated ths morning, but then you give the version number for the previous version (8.0), rather than the current version for AME (8.1).
I just tried rendering and exporting an After Effects composition containing a .c4d scene file through AME 8.1, and it works fine for me on Windows and Mac OS.

Adobe Media Encoder Error with MPEG2 Formats [../../src/Command.cpp-2519]

I am trying to use some of my presets using MPEG2 format and it is giving me this error: [/Volumes/BuildDisk/builds/ame602_mac/main/app/frontend/prj/mac/../../src/Command.cpp-251 9]. I try the system presets that use MPEG2 and I get the same error. I notice if I try to make a new preset, I do not even have the option to choose MPEG2. I only get MPEG4 or MPEG4 (Legacy). I am using AME 7.0.2; if anyone has an idea on why I can't use MPEG2 please let me know.
Thanks,
Mike

Hi mboory,
Please mention the exact version of Media Encoder CS6 that you are using and also the version of operating system. Please check the below link as well.
http://forums.adobe.com/message/4402558
Regards,
Vinay

Adobe Media Encoder Streaming with Mac

I really want to use a mac to broadcast internet radio. I
notice that the streaming media encoder only seems available for
PC. Am I missing something? I have Flash CS3 and other Adobe CS3
software. Is there anything I can do to stream Flash Media from a
Mac.
I suppose I could use a Windows computer just to handle the
stream, but how do I get the stream from the mac to the Windows
computer if I do that.
I'm planning on using a Streaming service for the actual
streaming but I'm just trying to get it from my computer in the
best possible way.

how about connecting an audio cable form the mac to the pc?
But seriously, it's a shame that FME isn't available to OSX.
if you have an Intel Mac, you could use bootcamp or Parallels
desktop (just an example) to run Windows apps on top of OSX (we've
done this)

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.

Adobe Media Encoder won't start

Not OP, but I have the same problem. AME just won't run. Double click, it's loading, I can see the process in Windows Task Manager but it just goes away again. Tried deleting that watch folder .xml but not working. Here's my spec from the FAQ:
What version of Adobe Media Encoder? Include the minor version number (e.g., Adobe Media Encoder CS6 with the 6.0.1 update).AME CC from premiere cc 7.0.1
What other Adobe applications do you have installed, and what application are you using Adobe Media Encoder with?Premiere Pro. Premiere Pro
Have you installed the recent updates? (If not, you should. They fix a lot of problems.)Used creative cloud to update to latest version
What operating system? This should include specific minor version numbers, like "Mac OSX v10.6.8"---not just "Mac".Windows 7. All update patch installed.
Are you using Adobe Media Encoder through a Creative Cloud Membership subscription?Yeah
What kind(s) of source footage? When telling about your source footage, tell us about the codecs, not just the container types. For example, "H.264 in a .mov container", not just "QuickTime".N/A. App won't launch
If you are getting error message(s), what is the full text of the error message(s)?No error message
Is the problem only occurring with a specific output format or encoding preset? If so, which one? If this is a custom preset not included with AME, then upload the preset file to a file-sharing site and provide a link.No.
What were you doing when the problem occurred?Booted up the computer. Launch AME.
Has this ever worked before?Yes.
What other software are you running?Google Chrome
Do you have any third-party codecs installed?Avid DNxHD, Cineform Studio
Tell us about your computer hardware. Be especially certain to tell us about third-party I/O hardware (e.g., AJA, Matrox, Blackmagic, MOTU).Regular desktop
Are you using Mercury Playback Engine GPU Acceleration in Premiere Pro?Yes.

I have a problem like this:
Anybody HELP?
Process:         Adobe Media Encoder CC [16188]
Path:            /Applications/Adobe CC/*/Adobe Media Encoder CC.app/Contents/MacOS/Adobe Media Encoder CC
Identifier:      com.adobe.ame.application
Version:         7.2.0.43 (7.2.0)
Code Type:       X86-64 (Native)
Parent Process: launchd [253]
Responsible:     Adobe Media Encoder CC [16188]
User ID:         501
Date/Time:       2014-02-05 01:15:39.418 +0100
OS Version:      Mac OS X 10.9.1 (13B3116)
Report Version: 11
Anonymous UUID: 7E5DC048-8DD8-5DA9-CFD0-539F29161D59
Sleep/Wake UUID: D2BBCDCA-68C3-4C86-B34D-57E4C884FDD8
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
terminating with uncaught exception of type dvacore::filesupport::dir_create_exception: $$$/dvacore/filesupport/DirCreate=The directory '@0' could not be created. Please check the parent directory protection or permission rights.
abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib                  0x00007fff8a1c2866 __pthread_kill + 10
1   libsystem_pthread.dylib                 0x00007fff8998835c pthread_kill + 92
2   libsystem_c.dylib                       0x00007fff8f10dbba abort + 125
3   libc++abi.dylib                         0x00007fff95124141 abort_message + 257
4   libc++abi.dylib                         0x00007fff95149aa4 default_terminate_handler() + 240
5   libobjc.A.dylib                         0x00007fff9413c322 _objc_terminate() + 124
6   libc++abi.dylib                         0x00007fff951473e1 std::__terminate(void (*)()) + 8
7   libc++abi.dylib                         0x00007fff95146e6b __cxa_throw + 124
8   com.adobe.dvacore.framework             0x000000010022814d dvacore::filesupport::DirHelper::Create() + 813
9   com.adobe.AMEAppFoundation.framework          0x0000000104f285e9 AME::foundation::AppUtils::GetUserPresetDir(bool) + 425
10 com.adobe.Batch.framework               0x0000000105c0a842 AMEBatch::Initialize() + 2194
11 com.adobe.ame.application               0x00000001000273cb AME::app::AMEAppInitializer::AMEAppInitializer(exo::app::AppInitArgs&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >&) + 811
12 com.adobe.ame.application               0x000000010000ad6a AME::app::AMEApp::InitApplication(exo::app::AppInitArgs&) + 2426
13 com.adobe.exo.framework                 0x000000010513e77a exo::app::AppBase::Initialize(exo::app::AppInitArgs&) + 1066
14 com.adobe.ame.application               0x00000001000141a8 AME::RunTheApp(exo::app::AppInitArgs&, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&) + 1576
15 com.adobe.ame.application               0x0000000100056a38 main + 424
16 com.adobe.ame.application               0x0000000100003f74 start + 52
Model: MacBookPro11,3, BootROM MBP112.0138.B02, 4 processors, Intel Core i7, 2.6 GHz, 16 GB, SMC 2.19f3
Graphics: Intel Iris Pro, Intel Iris Pro, Built-In, 1024 MB
Graphics: NVIDIA GeForce GT 750M, NVIDIA GeForce GT 750M, PCIe, 2048 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x134), Broadcom BCM43xx 1.0 (6.30.223.154.49)
Bluetooth: Version 4.2.1f2 12982, 3 services, 23 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM1024F, 1 TB
USB Device: Internal Memory Card Reader
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 17.1

Adobe Media Encoder CS5 doesn't work anymore (WHY? WHAT's WRONG?)

The system I use is Adobe Production Premium CS5.
I have often used Adobe Media Encoder CS5 started from the export of a film sequence in Adobe Premiere Pro CS5.
On the 31st of December 2013 my computer crashed and dumped more or less at the end of a process of Adobe Media Encoder CS5. There was no complete output.
Since then this program Adobe Media Encoder CS5 cannot start up anymore.
It stops at the start-up saying that the program does not work anymore and that there will be looked for a solution. But then it finishes saying that it will be reported if a solution becomes available in the future.
I have tried the following:
- Run Adobe Media Encoder CS5 (exe) from directory C:\Program Files\Adobe\Adobe Media Encoder CS5 => same problem.
- Stop security control AVG while not online with internet => run Adobe Media Encoder CS5 => same problem.
- Reinstalled complete Production Premium CS5 suite => same problem.
- Removed complete directory C:\Program Files\Adobe\Adobe Media Encoder CS5 and then reinstalled Adobe Premiere Pro CS5 => the full directory C:\Program Files\Adobe\Adobe Media Encoder CS5 with contents was there after the install, but subsequent running of Adobe Media Encoder CS5 => same problem.
- Removed complete contents of D:\mediacache\database\Media Cache and D:\mediacache\Media Cache Files => same problem.
What more can I do ??????
I would be very grateful for a solution.
Regards, Arie de Jong, Rotterdam

Hi Jim,
Thank you very much for the suggestions for a solution. First I considered
re-installing Win 7 Pro, because I did not have a fall-back point
predefined. So I could not try to reload a previous system environment. But
for your information the following.
Yesterday my son suggested that there could be some corruption in a control
file of Adobe Media Encoder, because re-installing that program did not
give a solution. Obviously that then would have to be a file which is not
affected by a program re-install.
What he then did for me is to remove directory
Users\owner\ AppData\Roaming\Adobe\Adobe Media Encoder (he actually
renamed it to hide that directory for Media Encoder).
Thereafter we ran program Media Encoder from Premiere. The result was that
a new directory ......\ Roaming\Adobe\Adobe Media Encoder with proper
control files was automatically generated and the problem was solved.
Regards from Arie de Jong

Adobe Media Encoder CS4

Adobe Media Encoder CS4 has one Filter ... Blur , is it
possible to add another and are there any available, specifically
for adjusting gamma.
Thanks

Georges, please provide
these details to help us help you.
Cheers
Eddie
PremiereProPedia (
RSS feed)
- Over 300 frequently answered questions
- Over 250 free tutorials
- Maintained by editors like
you
Forum FAQ

Adobe Media Encoder Install Problem

Hi-
I am encountering some problems when trying to start Adobe Media Encoder. It jumps to two successive "Adobe Media Encoder" install screens (one for the exporter, one for the importer) After some loading time, it displays an error message "Installation was unsuccessful. Restarting Adobe Media Encoder will trigger the installer again. Please contact Adobe Technical Support if this problem persists." It then goes to the Adobe Media Encoder screen.I can load files, and export them, but I am unsure what is wrong that makes it complete this "install/installation unsuccessful" sequence every time I try to open the program or export in Premiere Pro.
I have tried re installing Premier Pro and Adobe Media encoder, and it does not work. Also, I have tried updating, to no avail.
I attached pictures of the install screen, and the error screen.
I am currently using a student liscence of Adobe Production Premium, Windows version.
Thank you for the help
Sam

Please contact Adobe Technical Support if this problem persists.
Good advise.

Adobe Media Encoder freezes with one second left

Similar Messages

Maybe you are looking for