[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

[Jamie Hurt]

Also if you’re on a Mac, run Apple’s Disk Utility to Fix Permissions.
I had the same error and was able to fix it by doing that.

I had just installed a clean copy of my Mac OS, and a clean copy of CS4 – so the CS3 issue wasn’t the cause. It turns out my internal drives (job folders) were still assigned to the user from the previous OS…I thought I ran Disk Permissions earlier, but maybe it didn’t complete the process or ran into some error I didn’t pay enough attention to.

-0

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

[Jamie Hurt]

Hello,
I’m on a Mac running a clean install of Adobe CS4 Master Collection – and I have the same behaviour from Adobe Media Encoder CS4 refusing to render/compress any clips from Adobe Premiere Pro CS4.

It puts the “source file” in a temp folder -and the error log says “Could not read from the source. Please check if it has moved or been deleted.”

During my troubleshooting I’ve restarted the machine, moved the cache file, output files and changed caching preferences. I’ve fixed “permissions” on the Start up disk (a Mac-only phenomenon)

No luck.
I don’t have and have never installed CS3 on this system – so it doesn’t have that issue uninstall CS3 issue.

I DID, however, run an update from adobe that seems to correspond with this issue. My version of Premiere is 4.0.1 – and the Adobe Updater claimed that update would fix issues with the Media Encoder – I didn’t give it much thought until now.

— WORK AROUND ANSWER —
Since I don’t have a lot of time to beta test the Adobe Software, here’s what I did to work around the stubborn issue today. Open up your Premiere Sequence in Adobe After Effects CS4 and use it’s Render Que instead. — For the most part, it looks like this will solve my issue, but check your work. Audio levels, transitions, CG might get all whopper-jawed from this approach. Fortunately, the project I have today is a simple video edit.