CS4 Media encoder Has really sloooowed to a crawl

I have seen many posts in the past along these lines when comparing it to the rending process with CS3 but noticed that will all the update for CS4, the encoder is slower than I can ever remember it being.
Not sure if any of the recent updates have caused this or not but for a 1 hour 48 minute project with normal 4:3 settings standard MPEG DVD, close to 7+ hours seems a bit ridiculous.
I am using the hardware I've been using for some time and it has never taken this long. The encoder has been running for almost 40 minutes and I haven't even seen on bit of footage on the encoder monitor yet.
Has anyone observed this extended encoding time?
Intel Core 2 Duo 4 Mb RAM 3.0GHz processor SATA drives with Nvida SLE dual cards.
I think I have enough horsepower but CS4's encoder is running like a jet at take off with the brakes fully applied.
Much thanks for any assistance!!

Well I sure have.
One sure way to cut the encoding time is to render the timeline and then check the "Use Preview Files" in the "Export Settings" window.
In both cases below I did NOT export from Premiere. I closed Premiere and opened Adobe Media Encoder and under "File" I selected "Add Premiere Pro Sequence". This avoids using your C: drive as the source since I have a much faster RAID array for the project files
Without using the preview files on this extremely complex (editing-wise) one hour 18 minute video it took 6 hours 14 minutes to encode to MPEG2 DVD without using the preview files and it took only 42 minutes using the preview files!
This is an 8-core E5420 Xeon 2.67 GHz system

Similar Messages

Adobe Media Encoder has stopped working

I have Premiere version CS4, on windows vista 64 bit. All of a sudden the Media Encoder has stopped working, when I press problem details it says:
Problem Event Name: APPCRASH
Application Name: Adobe Media Encoder.exe
Application Version: 4.0.1.0
Application Timestamp: 4933bbdc
Fault Module Name: WatchFolder.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4933b879
Exception Code: c0000005
Exception Offset: 0000a7b3
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033
Additional Information 1: fd00
Additional Information 2: ea6f5fe8924aaa756324d57f87834160
Additional Information 3: fd00
Additional Information 4: ea6f5fe8924aaa756324d57f87834160
I have restarted the computer several times and it gives the same message
What can I do?
Thanks!

Did you set up a watch folder on an external or network drive, or any
other drive that isn't there any more?
-Jeff
I have Premiere version CS4, on windows vista 64 bit. All of a sudden the Media Encoder has stopped working, when I press problem details it says:
Problem Event Name: APPCRASH
Application Name: Adobe Media Encoder.exe
Application Version: 4.0.1.0
Application Timestamp: 4933bbdc
Fault Module Name: WatchFolder.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4933b879
Exception Code: c0000005
Exception Offset: 0000a7b3
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033
Additional Information 1: fd00
Additional Information 2: ea6f5fe8924aaa756324d57f87834160
Additional Information 3: fd00
Additional Information 4: ea6f5fe8924aaa756324d57f87834160
I have restarted the computer several times and it gives the same message
What can I do?
Thanks!
>
>

CS4 Media Encoder

Like many others, I have encountered a problem with CS4 Media Encoder upon start up. It quits unexpectedly.
I have a Quad-Core Intel Xeon Mac running 10.6.2.
Here are the problem details if someone understands it:
Process:         Adobe Media Encoder CS4 [299]
Path:            /Applications/Adobe Media Encoder CS4/Adobe Media Encoder CS4.app/Contents/MacOS/Adobe Media Encoder CS4
Identifier:      com.adobe.ame.application
Version:         4.1 (4.1)
Code Type:       X86 (Native)
Parent Process: launchd [113]
Date/Time:       2009-11-10 23:49:32.541 -0700
OS Version:      Mac OS X 10.6.2 (10C540)
Report Version: 6
Interval Since Last Report:          24036 sec
Crashes Since Last Report:           10
Per-App Interval Since Last Report: 505 sec
Per-App Crashes Since Last Report:   9
Anonymous UUID:                      9203213B-94A6-4772-A9E6-EFAC9F6ED5DE
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000c276e1a8
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
I have tried removing the ".pref" file without improvement. On another thread there is mention of removing an "Watch folder info.xml" file, which I can't find on a Mac.
Would appreciate any help
Kurt

Me too. Sometimes it works. Sometimes, even the smallest file will crash the ENTIRE COMPUTER and it will force restart itself. I have tried it with h.264 and MPEG2-DVD, and both have crashed it.
I thought it might be overheating my MacBook Pro, so I have been watching the temperatures. The CPU gets almost to 200f. The process viewer shows encoder process average around 167%.
It is unfortunate because when it does work, it actually makes very pristine encodes.
I also tried updating the licensing through a FLEX update, as the console was reporting the same message over and over again. That message has stopped, but the crashing has not.
My fans run constantly when watching training videos on Adobe's site, and the computer never crashes. So I assume it is not a heat problem. That said, I don't know whether the CPU or the GPU are responsible for video playback. In other words, if the GPU does playback, and the fans go on, it isn't getting hot enough to shutdown. If the CPU does does playback, and is causing the fans to go on, I would think that the computer would shut down just as it does when Media Encoder is encoding and causing the CPU to get hot.
At this point my hunch is that Media Encoder is causing some sort of kernel panic, causing the computer to restart. But this is just a stab in the dark.

Premiere CS4 & Media Encoder CS4 didn't work..

i just install Premiere Pro CS4 & Media Encoder CS4..
i finished editing my videos in Premiere, but when i want to encode it in Media Encoder, it says "please verify that adobe premiere is installed in your computer"..
what should i do?
tnx..

Welcome to the forum.
Do you have the full-paid version, or the trial?
It sounds like your installation is not complete, or has become corrupted. This is a general CHECKLIST for installing most Adobe programs. Look over it, to see if perhaps you missed something.
If you did everything in the checklist, then I would attempt a Repair Install. Did you install from media, or from a download?
Good luck,
Hunt

The Adobe product that installed Media Encoder has not activated

My Adobe Media Encoder CS4 was working perfectly.
I even exported a video one morning and that same afternoon it refused and gave me the following message:
"Thank you for using Adobe Media Encoder CS4. The Adobe product that installed Media Encoder has not activated.
Please launch and activate that Adobe product before continuing to use Media Encoder"
I reinstalled a couple of times, but nothing changed.
I uninstalled and installed CS5, it launched once then gave me the same message all over again.
I even tried to install it on another computer and it's giving me the same result.
I have been working on this video more a month, and I can't even export it.
Can anyone help ? I have a deadline to meet
Thanks a lot

Hi, I've just been having the same problem but on my mac!
I have been trying to use XDCAM EX converted Mov files on my new MacBookPro with CS6. I have just completed the installation of ProRes Quictime codecs, but when I went back to try to re-open my Adobe Media Encoder, (that I was using without problem around an hour ago), I now get the same message that The-Jade was getting
"Thank you for using Adobe Media Encoder CS4. The Adobe product that installed Media Encoder has not activated.
Please launch and activate that Adobe product before continuing to use Media Encoder"
Any ideas?
Thanks,
JAK

Does The New CS4 Media Encoder Seem Slow?

I selected some B-Roll that was shot in P2 1080i and brought it into a standard definition project. I scaled it to about 44% and sped up one timelapse segment by about 900%. The resulting length was about 8 minutes.
Transcoding this 8 minute sequence into 720x480 NTSC With the CS4 Media Encoder is taking over 3 hours! This is on a system with an Intel Q6600 processor.
Has anyone else noticed that the new Media Encoder seems slower? I don't think it uses existing render files like previous versions of Premiere.

"DV project. If you have three clips AND THE 2ND ONE is color corrected then you do a 'preview render' that 2nd clip is rendered to dv so it will play real time in your timeline. Then when you render out to DVD clip 2 is rendered yet again to Mpeg-2. It has been rendered twice, it a second generation image unlike CLIP 1 AND 3 WHICH are still first generation before the Mpeg encoding"
Sorry typing faster than my brain. Sorry trying to get work done and help people got the better of my fingers brain. The above is corrected with the corrected in CAPS.
In a nutshell when you use preview files your telling the computer to use files that have already lost a generation to make your edit faster.
If you edit DV the preview renders the effect (or whatever) to whatever is set in the sequence files. So a new DV file is made, which is rendered into an MPEG (or quicktime, Blu-ray whatever).
"But if you are saying that re-render renders the already rendered preview clip, I believe that you may be in error. I thought re-render ignored the previews and looked to the source file(s) again. Am I wrong?"
Yes your wrong because your assuming the preview render was done in the format your outputing in AME. If re-render 'ignored the previews and looked for the source file(s) again' there wouldn't be any render to 're-render'.
The Preview render renders a new file based on your media codec (dv to dv, HDV to i-frame. dvcpro to dvcpro). It has no way of knowing what your final setting in AME are going to be. So preview files are double rendered.

Windows 7, CS4 Media Encoder freezing and crashing upon clicking "Start Queue" - every sequence!

Windows 7, CS4 Media Encoder freezes when queue starts with sequences from Premiere. However, sequences opened from Media Encoder's "Add Sequence" export fine. Have re-installed (without first un-installing), issue is ongoing. I have several important deadlines fast approaching, please help! Media cache has been cleared (both automatically and manually), computer has been defragged and scanned for disk errors... I am absolutely stumped!

I've checked the anti-virus (I didn't think of that!), but it doesn't seem to make any change.
I've had Window Task Manager running while trying to export, it would seem that the problem occures when PProHeadless.exe opens. If I manually close it right before clicking "Start Queue", AME doesn't freeze until PProHeadless.exe re-starts once more.
Any information on forums regarding PProHeadless.exe seem more to do with an error message, not that the application itself is causing problems. I've tried multiple different sequences, all with different footage, different types of files and all with the same result.
Would a complete reformat or Windows and CS4 be the only answer? I dread the thought but I'm getting desperate.

AME CC 2014: "Adobe Media Encoder has encountered an unexpected error and cannot continue."

Adobe Media Encoder CC 2014 on MacPro "mid-2012" (MacPro5,1) running OSX 10.9.3 and getting this error when trying to launch Adobe Media Encoder CC 2014:
Adobe Media Encoder Error
Adobe Media Encoder has encountered an unexpected error and cannot continue.
Have uninstalled, reinstalled. Checked and fixed permissions numerous times. Tried removing all plugins and that didn't fix. Also tried editing the text listings within the .app for OpenGL and CUDA to remove all cards listed - that didn't fix anything either.
At this point it's uninstalled and "hopefully" everything will point to CC (non-2014 version). Adobe Media Encoder CC works fine. Adobe Media Encoder CS6 works fine.
Cannot find any other reports of this issue.

Progress in trying to fix. This workaround was NOT successful on previous attempts, but now appears to be working. Seems like the trick was to have AME CC 2014 started and open BEFORE doing any of this? As always, make sure all of your permissions are set properly - had done that numerous times previously. My issue was NOT directly permission related.
Navigate to the following folder:
You may see a file SHORTCUT that is invalid called "Presets":
Remove/delete this file. It's a broken shortcut.
Move a folder of .EPR files into the "8.0" folder. Call it anything except "Presets". Go to AME CC 2014 and quit. (I was greeted with another crash message.)
Open AME CC 2014 again. Your presets will not be loaded yet, but you should see an XML file that was created in your new folder like this:
Delete this file.
You should see a new folder also created by AME called "Presets". Move your .EPR files into this folder and delete the original folder. Quit AME CC 2014. (I was greeted with ANOTHER crash message.)
Open AME CC 2014. Your preset files should be there at the top under the preset browser:
Probably a good idea to keep a copy of those .EPR files elsewhere

CS4 Media Encoder doesn't render Quicktime at all

The CS4 Media Encoder will render H.264 and FLV, but doesn't render any form of Quicktime at all.
The Queue loads the project, pretends to render, but does not show progress frames. Seconds later (way too early!) there is a green checkmark that the render completed successfully. The log file looks successful with essentially the same content as for H.264 and FLV.
For example this log file shows a 1-minute sequence "rendered" in 30 seconds -- normally takes 3 minutes -- and no .mov was created.
10/29/2008 7:09:16 AM : Queue Started
- Source File: C:\DOCUME~1\MARATH~1\LOCALS~1\Temp\happyValleyBeijingMoreHighlights_5.prproj
- Output File: C:\Documents and Settings\Marathon Runner\Desktop\china\finished\happy valley beijing\more highlights\Sequence 01.mov
- Preset Used: NTSC DV
- Video: 720x480, 29.97 [fps], Lower, Quality 100
- Audio: 48000 Hz, Stereo, 16 bit
- Bitrate: DV/DVCPRO - NTSC
- Encoding Time: 00:00:00
10/29/2008 7:09:45 AM : File Successfully Encoded
10/29/2008 7:09:46 AM : Queue Stopped

>always save the project before you export
Very good advice.
I would also say, save your project after any edit that you feel you can't afford to lose.
Cheers
Eddie
PremiereProPedia (
RSS feed)
- Over 300 frequently answered questions
- Over 250 free tutorials
- Maintained by editors like
you
Forum FAQ

Media Encoder saying "The Adobe Product that installed Media Encoder has not activated"

I'm using Captivate 6 and one of the applications installed alongside this is Adobe Media Encoder. I've recently moved to a new Laptop. I de-activated Cap6 on the old one and sucessfully reactivated it on the new one. However, when I try to run Media Encoder on the new laptop I get a dialog box stating that "The Adobe Product that installed Media Encoder has not been activated". Does anyone know how I can resolve this?
Mike

nominder,
Start by making sure your products are updated to the latest versions. Launch Premiere Pro and choose Help>Updates. Do all the updates (if any) and restart the computer.
As far as AME is concerned, you were one click shy of your desired goal - hitting the start button on AME. AME works in the background so you can keep working in another Adobe application. So the workflow is thus.
within Premiere Pro - file>export media
choose correct settings for your output type and click ok
AME launches and ques up the render - click start...
Hope this helps,
Dennis

CS4 Media Encoder Presets

Does anyone know if CS5 Media Encoder Presets are compatible with CS4 Media Encoder?
http://blogs.adobe.com/ktowes/2010/10/new-encoding-settings-for-multiple-screens-using-ado be-media-encoder-cs5.html
Thanks

The solution! :)
Now I only have one of these two folders containing all presets. The "other folder" is a symbolic link to this folder using this tool:
http://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html
Now it doesn't matter whether I am defining a preset in Premiere or in AME. It works fine!
Carlos

Pro CS4 Media Encoder vs Sorenson Squeeze Quality?

Guys,
When outputting a video to Flash (for this discussion, let's assume Flash V8, medium size.....with the Web as the target audience), does anyone have experience using both PProCS4 Media Encoder and Sorenson Squeeze---being able to comment of the quality of each? Is CS4 Media Encoder doing as good a job (apples to apples) as Sorenson Squeeze would do? For general info, they want SD video in 4:3 ratio.
I've want to provide the best quality video I can to a client who is selling web training for a professional methodology. They are using video to provide additional visual support to their audio segments.
TIA,
jd

I purchased Squeeze after the release of CS4, the Adobe Media Encoder was fine in CS3. I noticed after installing CS4 that the end product (usually Quicktime, AVI, Mpeg-2 DVD and BluRay for me) was soft and fuzzy. I dug around various forums and found that many had this issue with the AME in CS4 and saw Sorenson Squeeze highly recommended. It should be noted that I use a Matrox RT.X2 card with my CS3 and now CS4 environment. I now export out an uncompressed i-Frame Matrox AVI and bring it into Squeeze and it works great.
I am finding the same issue in a non-Matrox project. We are doing a spot now that was shot in DVCPRO-HD. The image is gorgeous in PP, however when I use the AME, the resulting file is soft and dull.
Question to anyone who can help. In a non-Matrox project, what can I use to get it into Squeeze? With my Matrox projects, the uncompressed Matrox export bypassed the AME and gave me a clean image to bring into Squeeze. In my current non-Matrox DVCPRO-HD project I tried uncompressed AVI but it reduced my size to 720x480, and it reduced the quality. How do I get my footage out of Premiere and into Squeeze without using the AME?
Thanks,
Marty

CS4 Pro Export to Media Encoder has Audio, Titles, w/out Video

My Sequence is complete and looks great in the Program playback. I am exporting through Media Encoder and all goes well. I Media Encoder the Output looks great as well! The encoding takes about three minutes ends successfully. Yet, when I open the movie I have sound, titles all without video (black screen). I have tried many output formats including quitcktime & h.264 and different presets all with the same result. What's up?

Thanks for the assist! My Export Settings for my latest attempt:
Format: Quicktime / Preset: NTSC DV
Video: 720x480, 29.97 (fps), lower, quality
Audio: 48000 Hz, Stereo, 16 biy
DV/DVCPRO - NTSC
Anything else?

CS4 Media Encoder- Two Pass CBR settings?

I have come across something strange in the stand alone Adobe Media Encoder CS4 (Windows and Mac) when attempting to encode an FLV with on2vp6.
There is an option under CBR that allows for a two pass, however it also has the minimum bitrate, maximum bitrate and bitrate variability options. This makes sense for VBR, but why are they there for in CBR? Are they inactive for CBR? Shouldn't they be dimmed? Are you supposed to set to 100% and leave it? Is it a bug? I know H.264 only has one pass, and it acts the same way as FLV/on2vp6 One Pass.
One of the whole points CBR is that you have a defined bitrate with no variation, used predominantly for HTTP Pseudo Streaming or Streaming. I have a bitrate limit imposed on a server, so I add video and audio bitrates together and get the total bitrate and I want a steady stream. With minimum and maximum settings it would vary depending on your content hence the term VBR which seems contradictory to CBR...
Can anyone please shed some light on this?
Thanks in advance.
Jon

Thanks again for the reply. The next question would be, is One Pass CBR then the only true CBR (or best for streaming/pseudo streaming)?
Adobe's Docs skipped right over that (2 Pass and CBR)...seems pretty important, maybe they figure most will just use One Pass for CBR.
The funny thing is you can't find any real references on the web to Two Pass CBR either. Even Google wants me to change it to VBR Two Pass in my searches :-)
The reason I ask is that when we ran Two Pass CBR, it flagged an error on the HTTP Psuedo Stream server (similar to Xmoov PHP) because it exceeded the bitrate limit at a portion of the video (evidentially) and stopped it in its tracks... Unless maybe it was a coincidence but it was tried several times supposedly. I didn't witness this, because we don't have access to the client's Intranet/VPN (long story). I built a JWPlayer/Xmoov PHP setup at our site to replicate, but it doesn't have the bandwidth throttling enabled to test that theory. I will try to run some more tests and post back here if I find the anomaly.
I much prefer VBR 2-Pass anyway for quality but you can't really stream it effectively.
-Jon

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.

CS4 Media encoder Has really sloooowed to a crawl

Similar Messages

Maybe you are looking for