>I am in the middle of 3 projects with tight deadlines and need your urgent help.
Shervin, in Adobe Media Encoder, can you render your Timeline if you add the project file manually via File > Add Premiere Pro Sequence?
Its not the permanent solution, but it might help you to meet your deadlines.
I'm having the exact same trouble with the same error on 64bit Vista. I've tried weeding out dynamic linking and things but with a simplified version of the file with raw linked assets (AVIs) I can't export media for my DVD. I can't link into Encore and get it to encode there. I can't link from Media Encoder and get it to encode from there either (as mentioned by Roger). I'm trying to reinstall CS3 on another machine and see if I can get it to work there.
If anybody finds a fix please let us know. It's funny how Adobe never comments on this stuff at all.
We are a hair away from dumping the Adobe stuff altogether and going to Final Cut, which is infuriating after buying a site license of Master Collection!
can you please mention the configuration of the system that you are using? Do mention if you are using any particular graphics card and also the RAM of the system.
did you have any history of CS3 on the machine that you are facing problems on? there have been problems with co-existence of CS3 and CS4. it is suggested that you install your CS4 on a separate and fresh system. i installed my CS4 on a fresh Vista 64 and never came across the issue that you have mentioned.
Yes, I did have CS3 Master Collection installed. I installed CS4 and had them both for a bit but then decided to remove CS3. As you might guess the best machine to run all of this on is my current machine which has too many other things on it to reinstall windows, so what I've done is to uninistall CS4 and reinstall CS3 (a test of my file with CS3 on a slower machine worked) which will hopefully solve the problem for the deadline I have. I hope Adobe fixes this seeing as it shouldn't have gone out the door with a global bug related to installing with an old version. I assumed it was a 64 bit Vista issue or something more obscure - not a cross-platform problem.
Testing Testing Testing is what they need to be doing. That is what we do at our company before software goes out.
I resolved the issue through a simple process of elimination. So simple in fact I wonder how I missed it. Since there has been no history of prior CS3 installation on this machine and every conceivable trick was applied to resolve the problem (refer to my original post earlier in the thread) ending in frustration, the problem had to reside in a factor or series of factors that were only present in this machine. Of the two remaining causes different in compare to other machines, I had to look into the possibility of any hardware and/or software conflicts. After all, this very same installation works perfectly fine on my colleague's Apple Macbook Pro and several Windows machines.
It turns out that I had installed Pro Tools on this machine that comes with all kinds of optional plug-ins in the so called ignition pack. One of these optional plug-ins is called IZOTOPE (three varieties include Spectron, Trash and another one that escapes my mind). They were all lite version licenses that would automatically pop up on their own when you would start a program where they had been residing. One such program where an association existed was indeed the Premiere. An annoying dialogue box directing you to buy the full version when you would start the premiere would refuse to go away. Sometimes it would even start on its own culminating in a a permanent dialogue box.
The cause of the problem was right before my eyes and I had overlooked it. Once uninstalled using IZOTOPE clean uninstaller on step 4, the problem was resolved. Projects are now loading very fast into the AME and encoding begins in earnest. I have never had any issues ever since.
Long story short, if you have any plug-ins specially the ones that are loading upon the start of any program or the ones that reside inside the premiere or the ones that start on their own independently, they could be one of the highly probable causes of this error. I have seen other similar posts complaining of plug in folders inside premiere that needed to be moved to resolve the issue for instance the ones that needed to be moved to AE folders. If you are a plug-in admirer, I would suggest to look into them seriously.
On the side note, many combination and causes may lead to the same error. I am not claiming that this is the solution for everyone.
It must also be noted that I applied the trick of creating a shortcut of Premiere (and naming it exactly as such) and dropped it into the Adobe Dynamic LInk folder (even though this was suggested for windows)and have changed the adobe Cache locations to an alternative folder on a separate drive. I haven't been able to establish conclusively if the latter steps are also essential in fixing the error on MAC but I can confirm that since the latter steps were taken before the uninstalling of Izotope plug-ins and i still had issues, probably uninstalling those plug ins or finding a way to move them to a place where they don't interfere (if you absolutely need to keep them) is the one essential step that solved the problem.
Hope this helps.
A solution which worked for me is posted at
just in case there is still anyone out there installing and reinstallign CS4
I had this problem using Premiere Pro CS4 on a MAC. The solution was as follows:
I uninstalled the Red Giant MAGIC BULLET PLUGIN. Go to their website to see how to manually delete the files. After I totally cleaned the system from all Magic traces, everything was back to normal. Media Encoder works again!
So be careful with third party plugins!
Did you have installed Knoll Light Factory?
If so please remove KLF from MediaCore folder and try to export again.
Welcome to the forum.
Yes, I do recall an issue with Knoll Light Factory, though have forgotten the details now. Would be worth a try.
I want to just say that I had the same problem. I got rid of the knoll light factory plugins and now ame works great.
I had the same problem. I removed KLF from my /MediaCore folder, and like magic, all is working.
I then move that folder back when I have to use KLF in AE.
I informed Red Giant about this, but of course, for them, they say this isn't an issue, so I don't expect an "official" fix from them anytime soon.
(I did send them a link to this very helpful thread.)
Whatever you do, better avoid Adobe Tech Support. These
people hardly know anything about Premiere. Yesterday I spent 5 hours on the phone with 5 different so called tech representatives. They badly damaged my OS and today everything crashes, from Premuiere to Encore etc...I Think it is now so polluted that I have to start with re-installing Win dows 7.
With the exception of S/N, licensing and some installation issues, I recommend that one goes to the forum, rather than to T/S. The answers are most often better, and come more quickly.