Adobe Media Encoder CC and CS6 crash on startup.

Adobe Media Encoder crashes because it tries to load a bunch of After Effects plugins that it has in common, which it has no business dabbling in. The last thing I see before it crashes is Twixtor. How do I prevent this?

HI kasperxman ,
Can you please send me the following logs:
amt3.log oobelib.log and PDApp.log
Location: \Users\[user name]\AppData\Local\Temp
Mail them to [email protected]
-Pragya

Similar Messages

Why can't I download Adobe Media Encoder CC and I have the the Creative Cloud Suite.

Why can't I download Adobe Media Encoder CC and I have the the Creative Cloud Suite? (Windows)

It's not a separate program, it's automatically installed alongside the other CC apps which need it (Premiere Pro, After Effects, etc).

Uninstall Media Encoder CC and CS6?

After running the uninstaller in the drop-down menu for Adobe Media Encoder CC (OS X 10.10.2), I am still left with a the Adobe Media Encoder CC.app and a Configuration folder (1.89 GB). O.K. to just delete the whole thing?
I also have Adobe Media Encoder CS6 (721.4 MB), which if I remember correctly did not have an uninstaller. O.K. just to delete the entire folder too?
Thank you,
David

As I mentioned I did use the uninstaller for Adobe Media Encoder CC, although I don't think there was one for Adobe Media Encoder CS6.
Maybe Adobe Media Encoder is required for some of the other applications? (I only have Illustrator, InDesign and Photoshop installed.)
David

Adobe Media Encoder CS 5.5 hangs on startup

I've been using AME CS5.5 successfully for some time now, however, this week I was given a WMV file that used the GoToMeeting.com codec for video and AME (along with every viewer I had) couldn't open it until I'd installed GoToMeeting. After which, I could view the video with irfanview and windows media player, but AME would still not open it. So, I installed MS Expression Encoder 4 which COULD open it, and I encoded it with a standard VC-1 codec. I was expecting to then be able to open AME and encode it into FLV as I usually do. However, when I did that I found the program would no longer open. The splash image shows as it loads modules, but when it hits the quicktime one, it hangs. I've made a quick vidcap of the issue here:
http://screencast.com/t/cc8b6a7nJu
I rushed a little in the vidcap, but I've let it sit for up to an hour, and still got nothing.
I've tried deleting the AppData folder completely (C:\Users\[account]\AppData\Roaming\Adobe\Adobe Media Encoder\5.5) and got nothing and the files that are then contain no useful information.
Is it possible that MSEE somehow corrupted the ImporterQuicktime.pm module (seems pretty unlikely to me)? Couldn't have been GoToMeeting because I was able to start AME without any problems after I'd installed that.
My system is Windows 7 and I'm using CS5.5 (Design Premium)
Thanks!

HI
Please try this:
Delete everything in the following folders.
I see you did this for the first one.
See if deleting the other ones solves this issue.
C:\Users\[account]\AppData\Roaming\Adobe\Adobe Media Encoder\5.5
C:\Users\[account]\AppData\Roaming\Adobe\Common\AME
C:\Users\[account]\AppData\Roaming\Adobe\Common\Media Cache Files
AME doesn't have uninstaller. Since Design Premium installed it, the only way to uninstall it is to uninstall the entire suite.
I suspect one of these other applications you installed or modified Quicktime (which we do use) and in turn this is causing a problem for AME. You might also want to uninstall/reinstall Quicktime player again on your system and see if that solves this issue.
--Nariman

Adobe Media Encoder CS6 is a worthless piece of unstable trash

8 gigs ram
Intel Core i7 950
Quadro FX 1800
Yadda yadda yadda. My comptuer should have enough juice to encode what I need it to (old NTSC home video footage). Unfortunately, regardless of my output settings, Adobe Media Encoder hangs and crashes when I try to encode a video with a length anywhere north of 10 minutes. It's infuriating. No logs, just an alert stating "Adobe Media Encoder has stopped working and needs to close".
This is a professional piece of software designed to do one thing and one thing well. The length/size of my source material shouldn't matter. I should not be having these problems. There should at least be a directory of comprehensive error logging so I can give a more useful description of my problem, but alas.
My questions are:
1. Are there any general tips you can provide to increase the stability of this useless product?
2. What are my alternatives, software wise? What can I use to actually get what I need done? Any recommendations?
Thank you.

What's the old saying, "You'll catch more flies with honey than with vinegar"?
Everyone hear loves to help other users, but attitude is important. The CS6 AME works perfectly for me and most other folks, which would indicate that there is something wrong in your particular setup or workflow. I understand you are frustrated, but let's take a deep breath and get this fixed for you ;-)
First off, Adobe always comes out with bug fixes after the intial release - are you using the latest 6.0.3 for Premiere? I don't know if there was an AME update, you can check that easy enough.
What is the workflow - how do you capture the clips, what are the Sequence Settings, and what are the Export settings?
Do you have a separate drive for video, or using C: for it all? Drives defragged, not too full?
Graphics card driver up to date?
Thank you
Jeff Pulera

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 CS5 Watch Folders

I'm not sure if this is the right place for this, but I couldn't find an Adobe Media Encoder forum, and since we purchased After Effects to get Media Encoder I figured this might be a good place to start.
Basically, we have a dedicated computer set up with Adobe Media Encoder, and we set up several watch folders on a network drive. We have several files that must be several different codecs, so Media Encoder is really an awesome solution to this problem. However, the only problem we've been running into is sometimes Media Encoder doesn't actually watch a folder. For example, we have a "For web" folder and a "For VOD" folder. The for web folder has had absolutely no problems as far as watching and pulling in goes. The "For VOD" will sometimes not pick up files, but if media encoder is closed and then reopened, it picks up all of the files in that folder, but then again, will not pick up additional files in that folder.
The Media Encoder machine is running on Windows 7 (due to one of the codecs being Windows only), while all of the other machines in the department are macs. I have tested setting up the same system on one of our macs and we get the same problem. We are using an SMB network, but also have DAVE clients on all of our macs.
My initial theories are that it's either: A.) Something with the network, or B.) Something on the computer interupting the network connection. One of the IT guys briefly checked out the situation, changed around some network settings, and concluded that it must be an issue within Media Encoder itself.
Also, as a side note, I did check for updates with Adobe updater and everything is up to date.
Any ideas would be fantastic! And sorry if I'm leaving out crucial information in order to solve our situation, I'm not sure what all would be relevant, but just let me know what you would need!
Thank you!

Typically, Adobe apps do not work as well in a networked environment. You might try moving the watch folders to a local drive on the Win 7 machine and see if that makes any difference. If it does, there's your solution.

Sizes In Adobe Media Encoder...

I make a PAL movie in Premiere Pro CS3 with clips from my Panasonic GS500 camera. Export to Adobe Media Encoder CS3 and it gives an output frame size (for FLV) of 1024 x 576.
I open the same sequence in Premiere Pro CS4 and Export to Adobe Media Encoder CS4 and the frame size becomes 1050 x 576.
Why the two different width sizes? I have not done any resizing or cropping.
If I do resize the video by half, so that 576 becomes 288 (keeping the proportion link checked) the size becomes 512 x 288. 512 is not half of 1050.
Also, why is there no Deinterlace button, as there was on CS3. Do we assume that the video is being deinterlaced by default? Or, as some others have complained when exporting to DVD, is the exported video remaining interlaced? This might account for why I cannot get the same FLV picture quality, using exactly the same settings, as I did with CS3.
Any help greatly appreciated.
Spok.

HI Colin,
well, i used to be very happy with SorensonSqueeze, but for more than a year now, I'm just using Compressor (indeed from FCStudio).
It's VERY handy and lets you manage your settings in a way AME can't even think of in version 8... I mean nothing extraordinary, just the way it should, with possibility to move, edit, group, duplicate, rename, describe your settings...
And as for flv encoding (at the time of CS3, which I still have on my desktop machine) by installing the Suite, it would also install the codec for Compressor.. Excellent! Which CS4 doesn't do anymore... which forces us to use this terrible AME.. That's the scandale to my humble opinion!
But ok, via Compressor, you get the settings for flv... with the deinterlace box as on the attached image. Indeed with VP6 encoder.
And no, me neither, i'm not torn up, but it would have been nice Adobe gave us the info!
Compressor does also a great job in slomo. That's quite new but impressive. And Compressor is MUCH faster than AME.. AME takes ages! For a good result, I agree.
voila...

Adobe Media Encoder Issue

Hello,
I am using Adobe Media encoder CC and I do not see an option to export as FLV. Is it not supported in 2014 CC? please let me know.
Thanks in advance for your help.

The FLV export option was removed from the 2014 release of AME CC. Please see this blog post for more information:
removal of FLV and F4V export features from Adobe Media Encoder, After Effects, and Premiere Pro | After Effects regio…

Adobe Media Encoder needs update but no update available

Hey,
PP CS5 is prompting me to update AME everytime I try to encode timeline. WHen I go to help --> updates, AME is not listed.
Same thing if I go to adobe.com/go/updates
Says last AME update was put out in Sept. 2010
Anyone else getting this.
Thanks

yes that error message has no impact your AME will work fine...
If you are on Windows go to C:\Program Files\Adobe\Adobe Media Encoder CS5 and look for PCI-Version.txt file, all you need to do is change 5.0.0 to 5.0.1..

Adobe Media Encoder 5.5 - muxing independent stereo audio when i don't need it

Hi Adobe guys,
i seriously think this is a bug. Here's my problem.
Footage Format: Canon XF MPEG (mxf file extension)
Audio: 2 independent stereo channels recording different audio content on each channel left and right
Scenario 1 - export from timeline using the export media setting, i preserve the independence of my left and right channels of my audio
Scenario 2 - when i export the same footage using AME 5.5 via watch folder, it automatically mux (merges) the 2 channel audio, such that it is no longer independent of each other.
Its the exact same footage in both scenarios, and i am using the exact same preset settings. What is different in AME and the export media settings in Premiere Pro itself? Many small bugs like this is causing alot of unhappiness amongst loyal users like us.
Pls explain and offer a getaround before your next firmware upgrade comes along.
Regards
Mingsong

As Jim says, Adobe Media Encoder CS5 and later can import FLV files using the On2 VP6 video codec, not the Sorenson Spark codec.

Adobe media encoder 5.0.0.1?

i'm currently on 5.0.421 or something like that. it told me update take about 30 mins. anybody updated and can tell whats new about it?
the inconvienence i found with my current version is that it can't read flv files. so if i want to compress it i have to convert via Super and then go back to compress with AME. it just inconvenient. i wish AME can just read flv like Super can so i don't have to go through several apps to compress.
anybody else have similiar issue with AME?

As Jim says, Adobe Media Encoder CS5 and later can import FLV files using the On2 VP6 video codec, not the Sorenson Spark codec.

CPU Idling during encode in Adobe Media Encoder - why?

Wonder if anyone can shed some light on this for me.
Basically, just encoding a very short video in Adobe Media Encoder (AME) and it's not taking too long but I happened to notice that my CPU activity was a bit idle despite it performing this task. Surely, it should have devoted a bit more energy to the encode ad got the job done sooner?
Here's a screen grab to explain:
Anyway, if anyone can advise why this is the case and whether it is normal or abnormal behaviour it would be really helpful.
Many thanks,
Alex

This could depend on a lot things. Colorista and Looks, for example are processed on the GPU (using OpenGL, not CUDA), and can definitely create a bottleneck for the CPU.

Indesign CS5 and CS6 crash at start up!!!!!!

Help, Indesign CS 5 and CS6 crash at startup- on Mac OS 10.9.5 Mavericks
Seems to crash at starting registry
I have installed all the updates and patches, comes up with a long error log
Can anyone help

Ask in the ID forum and provide exact info like the actual error log/ crash report and what Mac.
Mylenium

Adobe Media Encoder CS6 Random Crashing Mid-Render

Hello -
I've been dealing with this issue for enough months and across enough computers to finally seek out some advise here, hope it works out...
Basically I've got a 2 hour long film that I've been trying to export using Adobe Media Encoder CS6. It's never made it all the way through. I can usually skim through the generated quicktime file up to the point where the crash occurred. I've tried using that as a reference to check out my sequence in Premiere but there is never anything suspicious going on there. Most frustratingly the crash occurs randomly. Sometimes it will go through 10 minutes of the film; sometimes an hour. Regardless I get a crash with a report that has no specific information.
Footage:
r3d - Various resolutions, all being cut in a 2048x1152 sequence.
Quicktime mov - ProRes4444 for the most part.
Machine(s):
I had been attempting to render this for the past few months with a Macbook Pro running OSX 10.8.4 w/ 16GB RAM, 2.7 GHz Intel i7, NVIDIA GeForce GT 650M 1024MB - never made it through a render longer than 50 minutes of the 2 hours.
We recently got one of the new 2013 Mac Pro systems running OSX 10.9 w/ 16GB RAM, 3.5 GHz 6-Core Intel Xeon E5, AMD FirePro D500 3072 MB
The hope was that this new powerful machine would overcome the issues we were running into with these renders. Since I'm posting this now you can probably figure out that it didn't really work out that way...
Software:
AME- 6.0.2.81
Premiere - 6.0
I know there are updates to be used here, but whenever I update Premiere from just 6.0, the project itself becomes a buggy mess, crashing constantly. I also run Creative Cloud and have tried to just jump over to Premiere CC hoping all my problems would vanish, but instead, I again get a buggy project that constantly crashes. The only version of Premiere that seems to work with this project is 6.0, so general updates have not been useful (and instead damaging, I've wasted several days trying everything I possibly can to make the project work in the updates).
Any help appreciated. Thanks.

Thanks for the reply MMeguro.
Last night I was able to get my first full render through by doing a combination of things (so I'm not sure what did the trick in the end).
To answer some questions first, never attempted to do the FULL render directly out of Premiere, always switched over to AME for that, so that potentially could work too. Smaller renders have worked directly out of Premiere Pro, but they've also worked out of AME.
The initial render attempts that had been failing for the last few months were on the MBP which did not support GPU accleration due to an incompatible graphics card. I assumed the issue must be tied to something else because of this and was using it on the renders with the new 2013 Mac Pro. Using the workflow of Pr6.0, AME 6.0 and GPU rendering turned ON, I was failing to render to both Quicktime h264 and ProRes 422.
What worked for last night's render:
1. Convert Pr6.0 project to PrCC project (when I've done actual editing in CC after converting this project it tends to crash, but I figured just generating the project itself without doing any editing in it might satisfy what I was attempting to do).
2. Open AME CC and import PrCC Sequence. Used custom ProRes 422 setting.
3. Turned OFF GPU acceleration.
So as long as I the PrCC project I create stays stable long enough to save it (without crashing, which has been a problem with that Pr6.0 to PrCC conversion) then it seems like this will work. Kind of an annoying couple extra steps but I'm just out of my mind glad that I can actually render this thing finally. We're still in the rough stages so being able to turn around a review version within a day is very important.
Wish I could do more tests to figure out exactly which combination actually made this work for the benefit of others, but can't afford to do multiple 10 hour+ renders with random crash times.
Anyway, thanks again for the reply MMeguro much appreciated.

Adobe Media Encoder CC and CS6 crash on startup.

Similar Messages

Maybe you are looking for