CS4 Premiere Won’t Encode Videos..

[Mike Velte]

[Anthony Parker] “Source File: C:UsersanthonyAppDataLocalTempSuperman Spoof 1.3.prproj”

What is your Premiere Project file doing in a temp folder?

[Anthony Parker] “Could not read from the source. Please check if it has moved or been deleted.

The Superman Spoof 1.3.proproj is not your source video, it is a Project file. Can you play your timeline all the way thru? I doubt it and suspect that at 7;50 in the timeline is an Offline clip…orphan.
—————————————————————————–“

[Jerry Riojas]

@mike velte

Well, I am having the same problems. You asked why his project files were in temp folder?, well, In CS4 when you go to export and want to render your file, they took Adobe Media Encoder out of premiere and made it a seperate application. Now when you go to export your movie, it automatically transfers the job to Adobe Media Encoder, and this is where the problem is….

When the job opens in Media Encoder…. the path already says “temp” folder. My projects actually are in the “Documents/Adobe/Premiere Pro/4.0/” folder. Why does it put the path as the temp folder? I don’t know and have been thru every setting in Premiere and Media Encoder…. I read on the Adobe forums, that there is a known issue if you had CS3 installed before and un-installed CS3(and that it is a win-only problem). It said to un-install and re-install CS4, but that hasn’t worked for me. I tried that 3 times. I am at the point of reverting back to CS3.

[Tim Kolb]

[Jerry Riojas] “When the job opens in Media Encoder…. the path already says “temp” folder. My projects actually are in the “Documents/Adobe/Premiere Pro/4.0/” folder. Why does it put the path as the temp folder?”

Why don’t you change the path?

The Media Encoder is actually looking at the PPro sequence, which probably puts some sort of a cache file in temp until you’re done encoding…then it goes away I would guess (I’ve never looked).

The Media Encoder being a separate app has lots of possibilities…I really like being able to cue up a PPro sequence, an AE comp, source clips…all in the same cue, each with a separate output filetype and location…serious timesaver.

TimK,
Director, Consultant
Kolb Productions,

CPO, Digieffects

[Mike Velte]

This might be a fix;
https://www.adobeforums.com/webx/.59b6d73a/0

[Jerry Riojas]

@Tim Kolb

With changing the path…. that is what I was talking about in my other reply when I said I went thru all the settings trying to figure out where I could do that. In the Media encoder, the path is is grayed out and can’t be changed…

But yes, I also like the fact that the media encoder is it’s seprate app now, I just wish it would work.

@mike velte

That is the exact forum post at adobe I was referring to in my initial reply. I also stated that I tried that 3 times already, make that 5 now, haha. And every time I unistall, I run the CS4 Clean Script that is available at Adobe. But it still doesn’t help. This error took my entire weekend away from me. Unistalls took roughly 40 mins and installations were 45-50 mins. And it isn’t my machine being slow…. I have a AMD Quadcore 9550 and 6GB Dual Channel RAM, CS4 is just so beastly…

[Anna Haas]

I am having the same problem. I worked around this by opening the Premiere Project in After Effects as a comp then rendered the comp to an Avi file. You can bring it back to the encoder and it will do the conversion. Stupid way to do things but it worked. Especially when I had to pay too much for the suite upgrade I was hoping for more.

Frustrated in Seattle

[Rodrigo Polo]

After a long research and many tests I found that the final solution is to make a full and clean Windows install.

I did a clean install on a virgin virtual windows and everything works.

The typical installation method for Adobe products consist in uninstalling the previous version and then installing the new version, but again like CS3, there are many problems (if you remember the CS3 Clean Script).

In Mac OSX there is no problem upgrading, I did an uninstall of the CS3, and an install of CS4 and everything works great!

I already try uninstalling and reinstalling many times, I lose the count, and I also try the CS4 Clean Script which doesn’t work, so the current solution is to expend your weekend making a backup of all your disk, installing a fresh Windows copy, and then the CS4. (if you have another computer, you can just move all the folders on the C: drive to a backup folder in the same disk “c:\backup\” and then install windows, save a lot of time).

I recommend a x64 system, like VistaX64 or XPx64. For Photoshop x64 to use more than 4GB ram. (Right now OSX is x64 if you have a x64 processor, but because Apple don’t want to make Carbon for 64bits you will have a Photoshop 32bits, lol.)

[Anna Haas]

I went to the white papers at Adobe and found their recommendation on the problem. I did have to uninstall as you said. It seems that if you have Premiere CS3 on your machine when you install the CS4 version and then uninstall the CS3 version after wards then it does some magical twisting of the program. This requires that you uninstall CS4 and then go through a large pot of coffee and a box of doughnuts while you put CS4 back on the machine. What fun! Now it is working very smoothly and I still have a fair amount of my hair left as well…

Frustrated in Seattle

[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.

[Bill Clark]

Premiere pro CS4 to Media encoder works on my Macbook pro but not on my Mac Pro. I’ve followed ADOBEs work around, uninstalled CS3 re-installed CS4 yaddda yadda and still nothing!

This is unacceptable – we’ve all paid GOOD MONEY for CS4 – isn’t there anybody out there from ADOBE who can fix this!!!!

Bill Clark
Origami Films
Slate612