CS4 Premiere Won’t Encode Videos..

[Jamie Hurt]

Try running Repair Disk Permissions on your start up volume from Apple’s Disk Utility to be certain that there is not an issue with the directories Adobe Premiere/Media Encoder are trying to access/write to.

I ran mine a couple times until it did not get an error.

You can also “Get Info” on your directories/volume to look at the “Sharing and Permissions” attributes – that should have your login ID as a user with read/write privileges set.

Remember Premiere and Media Encoder – are dropping cache files in a few places (on my set up that was scattered over 2 internal eSATA drives, and sometimes an external volume)- It could be worth a trip to the preferences in each Adobe app IF you don’t get a working result from the above test. If it ain’t broke don’t mess with it…Also, test your changes systematically and one at a time. And minimize any drastic changes you make until you run out of the simple options.

That solution, as simple as it was, caused my issue. I had clean install of my Leopard and a clean install of CS4 when I got the “Encoding Failed” error from Media Encoder.

I did not have a previously installed copy of CS3 on this system. So that wasn’t my issue.

If that doesn’t work, you can try creating a New User with Administrator privileges from your System Preferences/Accounts set up. That could help you test if there is something wonky about your user folder.

Yeah – I hate the idea that we are beta-testing software for a multibillion dollar corporation. I usually wait until a few of the bugs are worked out, before buying Adobe software. I wasn’t able to do that on this specific release tho. I lost 12 hours or more on a Saturday rebuilding my system. Pain in the royal *ss.

Hope this helps – holler back if it works, or if you find a better answer.

Imagination is more important than knowledge. Knowledge is limited.
– albert einstein

[Bill Clark]

OK, believe it or not, 5 mins after I posted my rant I managed to solve my problem. It had nothing to do with all the stuff that everybody on the web was suggesting about re-installs and clean scripts. Something much simpler. I have a few plug ins on AE – Sapphire, Magic Bullet etc and I realised that every adobe programme was loading them on start up. And I kept getting an error message from Premiere Pro and Media Encoder about Magic Bullet looks – that it wasn’t registered. It was driving me nuts because it is. I reinstalled everything twice, and during this process spotted that Adobe is now putting all the plug ins in a central folder – which it refers to as media core. This on a Mac is at Macintosh HD/Library/Application Suport/Adobe/Common/Plug ins/CS4. (There might also be a CS3 file as well)

It occurred to me that this might be causing confusion – Media Encoder trying to load plug ins that it doesn’t understand and might not be licensed for in the XML file. So I pulled them out of there and put them straight into the AE CS4 plug in folder. Bingo. All the plug ins run fine – AND SO DOES MEDIA ENCODER! And now, no problems at all with the dynamic links between AE, Premiere Pro and ME.

I’m not saying this is the solution for everyone – but it’s worked for me. Hope it helps somebody.

Over and out.

Bill Clark
Origami Films
Slate612

[Jeff Klein]

I found a solution that worked for me:

I had upgraded from CS3 Master Collection to CS4 Master Collection by installing CS4, and then uninstalling CS3. I was then running into the same Premiere encoding problem described in this thread. I found a solution that worked for me.

I noticed that even though I had uninstalled CS3, there were still CS3 folders in program files/adobe. In other words, inside the Adobe folder there were two folders for every program (ie. a Premiere CS3 folder and a Premiere CS4 folder).

My solution was to just erase all the CS3 folders, knowing that those programs had been uninstalled. After doing so I immediately tried rendering from Premiere CS4 and it worked. Hopefully this will solve some problems, good luck.

[Joel Morales escobar]

I found this, and it totally solved my issue:

Solution: Create a shortcut to the Premiere Pro executable file, rename the shortcut to Premiere, and move the shortcut to C:\Program Files\Common Files\Adobe\dynamiclink.

As dumb as it may sound, it worked! And I didn’t had to uninstall or reinstall nothing. I kept both my CS3 and CS4.

Good luck!

Source: https://kb.adobe.com/selfservice/viewContent.do?externalId=kb407106&sliceId=2

[Baldur Helgason]

[Bill Clark] “I reinstalled everything twice, and during this process spotted that Adobe is now putting all the plug ins in a central folder – which it refers to as media core. This on a Mac is at Macintosh HD/Library/Application Suport/Adobe/Common/Plug ins/CS4. (There might also be a CS3 file as well)

It occurred to me that this might be causing confusion – Media Encoder trying to load plug ins that it doesn’t understand and might not be licensed for in the XML file. So I pulled them out of there and put them straight into the AE CS4 plug in folder. Bingo. All the plug ins run fine – AND SO DOES MEDIA ENCODER! And now, no problems at all with the dynamic links between AE, Premiere Pro and ME.”

Wow Bill, you truly are a genius! This totally worked for me, the Media Encoder is encoding as we speak! 😉 Thanks for sharing!

[Jeff Cooper]

WOW, what an easy fix – Thanks for the KB search Joel!

I run Vista, had CS3, uninstalled CS3 and installed CS4 and immediately had the Media Encoding error when encoding from Premiere. I also saw a “Adobe Dynamic Link error” when I tried to load the adobe sequence from my Premiere project directly from Media Encoder, so this solution makes sense.

I wish all serious bugs were this easy to eliminate.
Jeff

[James Brady]

[Joel Morales Escobar] “Solution: Create a shortcut to the Premiere Pro executable file, rename the shortcut to Premiere, and move the shortcut to C:Program FilesCommon FilesAdobedynamiclink.”

This absolutely worked for me! What a kooky hat trick… How anyone would think to do this as a solution is beyond me, but I’m glad it’s published here. Joel, you’re my encoding hero!

[Eddie Lotter]

[James Brady] “How anyone would think to do this as a solution is beyond me”

It’s published in an Adobe Technical Support document. 😉

Cheers
Eddie

[Joel Morales escobar]

heheh… no problem! Im glad my research helped more people.

[Ronald De heer]

Solution: Create a shortcut to the Premiere Pro executable file, rename the shortcut to Premiere, and move the shortcut to C:Program FilesCommon FilesAdobedynamiclink.