From CS4 Premiere, can't access Media Encoder

Yes I've un-installed Premiere and then re-installed. However I can not get past a message "Adobe Media Encoder CS4 has stoppe working." Not good. I have accessed Encoder via the "programs" file to see what would occure, same results. Of all things, I have a video that has to be completed by tommorrow afternoon. Any advise? The people who sold me the system are no help.
Chuck

Harm,
? I don't know what else to say.? The system was working fine until I downloaded the recent Premiere update.? That was too soon for the Matrox capture card, thus I had to go back to 4.0 and await Matrox's release of the new drivers.? Now, I can't get Encoder to function.? I just get the "stopped worked" message regardless of what file I'm trying to encode.? I have reloaded premiere from my CS4 disc which reloads, it appears, Media Encoder with it.? I dont' know what else to include here.
Chuck

Similar Messages

Can't access Media Encoder CC

I have been asking this question on these forums for about 2 moinths now, with no answer.
I know this is a community forum, but it is the only way I can access any support from Adobe.
I am in Australia. i am not willing to use the 800 number, and the 'chat' is not available to me.
When Adobe released the Cloud with much higher pricing in Australia they said it was because of the increased cost of support in this country. I am yet to find any support at all for my $50 per month.
So once again - here is my problem; </end rant>
I have Premiere CC and AE CC loaded via my CC subscription.
I can not access Media Encoder through either of these programs on my desktop, or as a stand alone app. I have fully removed and re-downloaded the apps a couple of times with the same result - ME does not install.
Can you give me a location where I can download ME so I can install it on my machine.

Hi Kevin,
thanks for that.
The problem on accessing the support was that i am in Australia and do not want to conatct an 800 number form here. No local number was available for me. The 'chat' function was also not available for me at any time, so i only had this forum as a point of communication. I am ceratinly aware that this is a user to user forum.
As a result of this matter I have seen the need for better support facilities to be available, so I determined to be a more active member of these forums, to help in some way. I don't want to just complain and not do something about it myself.
I do stand by my view though that a better method of direct support from Adobe is necessary. One of the reasons Adobe gave for the higher price of software in Australia prior to the Australian Senate Enquiry was the higher cost of support in Australia. While the cost did come down since then, I can find no form of support available to me unfortunately.
Thanks for listening to me,.

Premiere Pro and Adobe Media Encoder running slow

Hello everyone,
I'm having trouble with CS4, which is running significantly slower than CS3 did on a older machine. The CS4 suite is installed on a Dell Precision M6400:
Windows Vista 64-Bit
Intel Core 2 Duo CPU T9400 @ 2.53 GHz
8 GB RAM
NVIDIA Quadro FX 2700M Graphics with 512MB dedicated memory
The OS is running on a 57.5 GB HD (C:) and the Adobe suite is installed on a 298 GB Solid State HD (D:), except for Adobe Media Encoder, which is installed on the C: drive.
My project has 4 15-16 minute sequences. The sequences are in DV NTSC, 29.97 fps, My scratch disks are set to a folder on the C: drive. Media Cache Files and the Media Cache Database points to a folder on the D: drive.
These are some of the problems I'm having:
- Premiere Pro CS4 generates peak files every time I open a project
- It then takes 3-5 minutes to render before I can preview a 16-minute sequence
- Adobe Media Encoder takes 5 hours to render a 16-minute sequence (as flv) that has been previously rendered
- AME takes 1 hour to render every 15 minute sequence that has never been rendered before
Are my settings affecting their performance? Is there any way to improve it? Thanks.
(Premiere Pro is the only app that is slow)

The data rate for replay is one thing, the data rate from disk to memory then from memory to CPU and back the other way are different matters and ought not to be confused. It is well-established that for a computer to edit AVCHD you need top end components, and note that I said there were three tasks to distinquish with increasing hardware requirements, namely merely replaying the video, specifying edits in the editor and then the rendering. It is commonly accepted by all the industry vendors that to do remotely commercial AVCHD rendering you need a minimum Quadcore CPU then that eats data fast, in order to not let it go to waste you need a fast motherboard bus fast memory and in order for none of those to go to waste you need the fastest disk set-up you can manage. I in fact have a 4-disk RAID0 volume using SATA (I think the disk model is SATAII but I have to await return from the repair center before I can confirm). For this RAID0 volume I have run speed test software from BlackMagic because I have one of their HDTV capture cards. It recorded that this volume which remember is doing parallelised IO is just fast enough to receive a encoded HDTV stream from the BlackMagic card but too slow to receive an uncompressed HDTV stream, indeed when I tried both I found the volume did keep up with compressed but fell behind with uncompressed. Remember that with a RAID0 volume of 4 SATAII disks a given file gets spread over the four disks and hence IO is spread over those 4 3G/s data lanes. Also remember with these disks 3G/s is just a burst speed, for AVCHD we are interested in sustained serial IO which is much less.
Before my machine broke down, I found that it took 5 hours to render 33 minutes of HDTV albeit as it went along it transcoded from AVCHD to a Microsoft HD format for Vista-only. Another interesting thing is that I found that the longer this render ran the slower it became, the estimated time started at 3 hours but the actual was five and the last one third took maybe 3 hours. Because the machine broke after that run I couldn't figure the bottleneck. For my machine bear in mind that at the repair shop we found that the Quadcore had only half the necessary electrical power plugged in, the monitor software showed however that it constantly ran around 90% of whatever capacity that reduced power supply permitted. Now then we can puzzle over why it got slower and slower and yet CPU consumption remained consistent and near to full capacity, memory was not the bottleneck because that was constant at 6.4G. But you can say that this was maybe performing like a Dualcore and was hitting some sort of wall, if you had a 1 hour render with that rate of degeneration of performance factored in what would happen to the render time, and for 3 hours you could be running indefinitely. I hope when the machine comes back the correct power supply will make it behave like a Quadcore should for this type of application. Anyway I have two theories for the degradation. First is just that PrProCS4 was getting its knickers in a twist and thereby just doing more computation per minute of video to be rendered as time went by, maybe internal resource management related to OO-type programming maybe, or related to disk IO falling behind, both these theories have problems, for the latter the CPU usage should then have dropped also.
Anyways, you need really a Quadcore system and blazing fast disk to work fully with AVCHD commercially, we found an external SATAII disk so if I were you I would just go get one and move on with your life.
Message du 03/06/09 16:08
De : "Jim Simon"
A : "JONES Peter"
Copie à :
Objet : Premiere Pro and Adobe Media Encoder running slow
For AVCHD you MUST have FAST disks.
AVCHD actually has a lower data date than DV. You need lots of CPU muscle, but disk speed is really not a factor specific to AVCHD. Anything that works for DV will work just as well for AVCHD (and HDV as well).
>

Premiere Pro CS6 and Media Encoder CS6 Color shift on export

Hello,
I am working on an early 2008 Mac Pro with 2 X 3.2 GHz Quad Core Intel Xeon Processors 32 GB of RAM a NVIDIA GeForce 8800 GT 512 MB Graphics Card and I am running OS X 10.8.2.
I have the updated Version of Adobe Premiere Pro CS6 and Media Encoder CS6 through the awesome Subscription program that Adobe has started.
My footage is shot with the Canon 1D Mark IV shot 1920X1080 at 24 FPS
I am importing the camera files and then exporting them after I cut them up in to Quicktime Pro Res 422 HQ files
With the technical explination out of the way here is my problem. I have color right from the camera files that I like. and with out doing any thing to change the color I export the footage and get a dramatic color shift. The exported file looks desaturated and slightly green.
I have tried using Media Encoder CS6 to export my footage and that has the same result.
I started my career as a photographic retoucher and use photoshop and light room constantly so I am pretty confident that i know color. I also calibrate my Lacie 526 and Lacie 324i montiors monthly as well as have a sensor that will slightly shift the profile depending on the time of day.
I have attached three screen shots that show the color shift exactly. Now what I need is a solution. What I am not seeing is color settings for Premiere. I am totally open to any suggestions on what I might be doing incorrectly.
Ben

Benjamin Peterson wrote:
I started my career as a photographic retoucher and use photoshop and light room constantly so I am pretty confident that i know color. I also calibrate my Lacie 526 and Lacie 324i montiors monthly as well as have a sensor that will slightly shift the profile depending on the time of day.
I've been doing this for a few years now, and have come to some conclusions. Basically, the difference between still photography and video is like the difference between playing the trumpet and the sax. What you bring to the sax from playing trumpet is your ability to read music, what you know about composition, blending while playint with others, ect. But playing trumpet tells you nothing about how to physically play a sax. So it is with still photography and video.
For starters, your carefully calibrated computer monitor is just that, a computer monitor. It doesn't display the correct working space for video. What you need for WYSIWYG in video is a monitor that can show you the Rec.709 working space. Rec.709 has a different gamut, a different gamma, probably a different white point (D65), different phosphor colors, etc., etc., etc. Enought differences that it's difficult to make a computer monitor that can successfully display Rec.709. Yet there are a couple of computer monitors that can do this (a few Eizos, one HP). The vast majority of people doing serious color correction work in video use a production monitor for just this reason.
But a production monitor isn't enough. You also have to make sure that the signals you're sending the production monitor are correct. There's a sub-industry making signal converters for signals from NLE video cards (usually RGB based) -> signals for production monitors (usually YUV based).
That said, it is certainly possible to get a very good match between your NLE suite and a DVD / BD as displayed on an HDTV. But it's not as simple or easy as a calibrtated computer monitor for still photography use.
This is probably part of your problem. But Quicktime is probably the root of it. Quicktime is, well, I guess the polite way of saying it is that Quicktime is problematic. It gives all kinds of problems. Most people have abandoned it. You should too.

CS4 Premiere: Can't open due to inaccessible to Importer Process Server

CS4 Premiere: Can't open due to inaccessible to Importer Process Server:
Dear Guru:
After subject:
I uninstalled it;
Re-installed it;
Reopen it,
No luck, same error message ...
A friend's wedding reflash is set on 12/22, I have yet to open my Premiere?!!! Heeelp... Please...
Appreciate !
Forest

Hi, Jeff:
My system is XP; before the premiere worked well.
More detail story: Premiere could not open 3 days ago, no fix, some one sent me a crack software, I used it, no luck. Another nice guy told that is for non-legal Premiere, surely it won't work.
I tried to remove Premirere; difficult; some one suggested me to use Adobe CS4 cleaner from Adobe. Then it was removed. I re-install Premiere; During the process, abnomal thing I remember was: I can't input product S/N, so I had to use 30-day trial.
During the installation, it was stopped by Windows Installer issue, I restarted Windows Installer, then the process continued...
I have two log files, don't know how to attach into this message. But, can't find any problem therein.
Heverever, when I tried to open newly installed Premiere, error message says: ---can't open, reason is exactly same with very beginning: Can't communicate with Inporter Process Server....
Appreciate!
Forest
<Removed by Moderator>

Premiere now freezes on Media Encoder Queue

After updating to the Oct 2014 CC Update, upon exporting media using the Media Encoder queue, Premiere freezes on the "Preparing Data for Export" box. It launches Media Composer, but it never makes it out of Premiere.
Just exporting from the application works, as well as importing sequences straight into Media Encoder. But I need the queue to work.
On a Windows 8.1 PC
24b 1333 mhz ram
3.2 ghz Intel Processor
NVIDIA Quadro FX 3800
R

I am having the same problem (see Premiere now freezes on Media Encoder Queue)
I am on 2014.1 of both programs (8.1.0 on premiere, 8.1.0.122 of AME). I know an update just came out today, but it seems to be just a RAW photo update.
Mine hangs when premiere is "Preparing Media for Export..." It launches AME and AME boots up fine... so from where I sit, it looks like a Premiere problem as it's compiling the project file to export.
Neither "import natively / non natively" or GPU acceleration help. However, I wouldn't expect them to, given this seems to be a premiere problem, not an AME problem.
That thread does not apply re: nView.
R

I cannot import .mov files to Premiere Pro or Adobe Media Encoder.

I cannot import .mov files to Premiere Pro or Adobe Media Encoder.
How do I around this problem?

We need to know a lot more if we're going to help you.
What happens when you try? Do you get an error message? If so, exactly what does it say?
What version of Premiere Pro? Have you installed the recent updates? What operating system?
Does this happen for all .mov files or just some? Has this ever worked before? What version of QuickTime do you have installed?
Here's a page written for After Effects, but the information is relevant to Premiere Pro and AME, too:
http://blogs.adobe.com/toddkopriva/2011/02/troubleshooting-quicktime-errors-with-after-eff ects.html

Can't run (Media Encoder or Encore) and Premiere Pro

I finished a sequence, started up Media Encoder, then began editing a new sequence with Premierer.
The result was that after a while, Media Encoder "Not Responding".
I started Media Encoder again and this time I left the room to watch TV.
Media Encoder built the AVI file correctly.
Also Encore died when I tried to use Premiere at the same time.
Is that the rule with CS4 applications?

Harm
In EN once I click on the Build button to begin building a DVD it will take more than 30 minutes before the DVD comes out.
In the mean time I would like to fire up PR to start editing some other project.
If that is not something I can do then I can use my KVM switch to go to my old PC and produce artwork for the DVD case.
On another topic, I am in the process of making a BluRay DVD with Encore and when I clicked on the Preview button, instead of getting the neat little window that allows me to run a simulation of the DVD menu, I got a huge version of that menu that I could not manuver to get to the controller buttons.

Queuing from Premiere Pro to Adobe Media Encoder no longer working? CS6

Hi there,
Just very recently adobe media encoder has stopped accepting que's from premiere. I choose export in premiere, setup the export details and hit que, adobe media encoder launches, but then it flashes once (like disappears reappears, very quickly) and then it just simply does nothing. No item appears in the que. I have tried opening the premiere sequence directly from adobe media encoder but it does nothing either. If I drag the premiere project directly onto a preset in adobe media encoder, it crashes every time. (though not sure if it would of done this previous to my problem arising)
Anyway, very frustrating as I usually work on a different project whilst media encoder is rendering something out. Now i'm stuck with huge down times as I wait till the render is finished.
Recently updated to Mac OSX 10.8.3 - I think this is when the problem began.
Just updated the CUDA driver to 5.0.45 but this has not changed anything.
Working on a Mac Pro 5,1, 2x2.4Ghz 24GB RAM, EVGA GTX 660 FTW,

Some suggestions and answer at least the 16 questions at the end of the Wiki article.

Soundbooth CS4 - does it include Adobe Media Encoder

Hi there,
i am especially interested in Adobe Media Encoder, to setup an encoding workstation.
My question is, if Adobe Media Encoder is bundled with Soundbooth CS4, and if it is available as a standalone program or if AME can only be opened through Soundbooth directly.
I would be happy if someone can give me an answer to this. AME doesnt seem to be available as a standalone purchase in the Adobe Store.
Kind Regards,
Sascha

Hi Sascha,
Adobe Media Encoder is bundled with Soundbooth, but is only available from within Soundbooth when saving files. It is available as a stand-alone application when installed with Premiere Pro CS4, but I'm not aware of any plans to sell it as an individual product.
Durin

PP CS4 Crashes when sending to Media Encoder

I've used PP CS4 since it came out, have had no problems like this. I have spoke to the techs at Adobe really no help they do a bunch of stuff and the next time I use it crashes. PPro crashes when sending to Media Encoder if it gets to Media Encoder in time I can still render the file I've sent. There's only one thing I can think of that could be causing this I use an external drive and it nearly full I'm getting a 2T and coping over to there is there a possiblity that the drive that only has 3 gigs left could be causiing this?
Or do you think it's something else?

This is my solution to the crashing start Media Encoder before exporting from Premiere Pro CS4 I've had no problem since. It has something to do with the exporting the fonts or that's what come up in the crash report. I hope this is a remedy for those that experance this problem.

Premiere, After Effects, Speedgrade, Media Encoder and... the dynamic link

My feeback after working with the dynamic link these days. Basic project. Editing, color correction, animated titles.
I'm using a 3.5Ghz iMac 24GB Ram and a GTX 780 4GB. (2014 versions & last updates).
Rendering the timeline in Premiere is sometimes extremly slow (with AE comps). Need to quit and reload the project to get a good speed.
Too long delay of refresh for the AE compositions inside Premiere (with the dynamic link). Need to go in AE then back to Premiere to get the refresh.
When i export to media encoder i need sometimes to save then send it 2 or 3 times to get the last edits in the export.
Even worse with the AE compositions. If i change something in AE then export from Premiere i need to quit and reload Media Encoder to get the last changes.
Really fast export from Premiere to Speedgrade and from Speedgrade to Premiere.
But !!! Lumetri fx is not compatible with AE. And Speedgrade doesn't support BlackMagic but only this nVidia Sdi thing.
And why we could not export h264 from AE anymore ???
Quiet disappointing :-(

Using Premiere Pro CC 2014.0.1 (build 21) and Media Encoder 2014.0.1 (build 8.0.1.48) on OS X 10.8.5
If I Export a video from Premiere, I can continue using Premiere, but if I Queue an export, returning to Premiere produces the beach ball of death. If I give it time, the beach ball goes away and the arrow returns, but trying to click anywhere in Premiere simply returns the beach ball. There is nothing to be done but Force Quit Premiere. I can leave Premiere and run any other application, but if I leave to execute the Media Encoder queue, I cannot return to Premiere and use Premiere. I can visit Media Encoder (call it to the foreground) and return to Premiere after the queue is done.
My current workaround is to use Export from Premiere and not use Queue from Premiere.

Can't reinstall media encoder CC (Windows)

Hello There & Help!
I deleted media encoder cause it was working incorrectly, now it no longer is there.
Reinstalling Premiere pro CC dose not reinstall media encoder.
Really? Why no seprate download.
Any way to reinstall it?
P.S
Samuel

Yes, I wouldn't recommend deleting that folder. You should restore it from Recycle bin if it's still there.
Here is how you can get AME back on your system if AME folder is no longer in recycle bin:
- Copy and paste the AME folder from another computer that has AME (you can install the trial)
------------- or --------------------------------------
-   Deactivate PPro and other apps through Help -> Sign out (this way you don't lose your license)
-   Uninstall PPro, AE, InDesign, and Flash Pro
-   Run the CC Cleaner Tool (find it here: http://www.adobe.com/support/contact/cscleanertool.html)
-   Install PPro again.
Good luck

Published .avi from Captivate is shorter in Adobe Media Encoder

I published 8 slides from Captivate 4 to .avi video format. When I play the .avi in Windows Media Player, it works great. I'm using Adobe Media Encoder to convert it to .flv file to use in my Flash project. When I import the .avi to AME, it's shorter and the audio on the last slide is cut off. I tried inserting a duplicate slide with silent audio in Captivate to extend the duration by 10 seconds. Still, the .avi is 2:57 in length and when I import it to AME it's 2:47. It makes no difference if I extend the last silent slide to even 25 seconds.
Is this an issue with AME or with Captivate 4? How do I fix it?
Thank you!

Here's the info I can provide at this time:
Yes, it seems that this only affects .avi files published from Captivate. Other .avi files reflect the correct length when imported to AME.
Using AME CS4 4.2.0.006.
Using Captivate CS4 4.0.0.1596.
Yes, it happens with every .avi file published from Captivate. I've tried the following and still the last slide (#8) was cut off at the end including its audio:
extended last slide (#8) for more than a minute after the audio stops
extended the audio on the last slide (#8) by inserting silence for additional 30 seconds
added another slide (#9) after the last slide
added another slide (#9) after the last slide with 30 seconds of silent audio
I did find a temporary solution, however. I added a transparent object (rectangle) a few seconds after the audio ended on slide 8 and when I published to .avi, Captivate recognized the added object and published the video to include the added animation.
You may download a zipped file containing the Captivate project and the published .avi from here:
http://www.warnerdevelopment.com/Adobe_d7g8b9/files.zip
Thank you,
Artur

Premiere CC and/or Media Encoder audio bad renders

Occasionally, but not always, when I export a timeline to Media Encoder queue, the video renders out with no audio.
I have not found a repeatable way to replicate this, but when it happens, it really blows up my workflow.
Typically I:
Import a ProRes 1080 clip into a fresh timeline, and only trim down the ends. Audio and Video playback great in premiere. I then, without changing anything, export to media encoder queue in h.264 1080p OR 720p (vimeo preset).
The queue runs and bang, video file with no audio.
My extended workflow is as such - once the h.264 file has arrived in the folder (it is a watchfolder), there are presets set to create OTHER Files - wav for CD, mp3 for podcast, DVD for distro, mp4 for podcast. So, as you can see, it snowballs into a trainwreck. I would also automate/schedule the podcast postings, but obviously I can't rely on media encoder/premiere to do it's job.
Has anyone experienced any lack of audio render issues? Is it tied to hardware at all, or is it just freak randomness? I even got to point to where I reboot the machine right before each original capture begins, but the error is always in the first render out of premiere.
I have checked for any muted tracks and such, and there are none. As I said, it is VERY random. For instance, this week, I dropped the capture into a timeline, exported as usual, and got a bad render. Did it again, this time moving the audio down a track. Still a bad render. Rebooted the Mac, tried it all again, and finally got a working render. This is the first time it has happened TWICE in a row, and I'm getting tired of it, as these renders are fairly long.
Any help would be much appreciated.
- Ben

Ben, I'm having the same issue. Never had it before yesterday.
I'm editing on CC with R3D's. I have 8 tracks of audio. When I'm exporting (either through Encoder or through Premier) I'm getting a final product that has no audio, and in its place a loud clicking sound. I performed a number of reboots and got it to export once. But I've tried dozen's of times now and can't get audio to export through this sequence.
When I go to render the project I'm getting an "Error Compiling Movie. Unknown Error" message. I suspect that's related. Not sure what's happening. I'm going to keep testing. I'll let you know if I discover anything. But it is VERY FRUSTRATING:( Deadlines are looming.
-Brian

From CS4 Premiere, can't access Media Encoder

Similar Messages

Maybe you are looking for