Adobe Community: Encoder not working

Currently Being Moderated

1. Curt Wrigley,

Oct 29, 2008 7:11 PM in reply to (dsharvey)

Report

Did you click "Start Queue" in AME after it launches?

|

Mark as:

Currently Being Moderated

2. (kdpruett),

Oct 29, 2008 7:39 PM in reply to (dsharvey)

Report

I have a similar problem with CS4 on the Mac in that the Encoder does not work. I get an error message "Null pict handle for id 2004". After watching the spinning beach ball for a couple of minutes I get another message "an Adobe dynamic link error occurred". I can click on the ok button to clear this message, however I can't click on the first error message to clear it. You basically have to force quit Encoder. Even after doing so the error message remains on the screen. The only way to get rid of it is to reboot.

So I am not able to use Encoder which sort of makes the software pointless. I am able to edit in Final Cut Pro, go to After Effects, and back to FCP without any problems. So it looks like I'll be sticking with FCP.

|

Mark as:

Currently Being Moderated

3. (Mark_Shumard),

Nov 5, 2008 1:08 PM in reply to (dsharvey)

Report

The same thing is happening to me, exporting from Adobe Premiere Pro CS3. When I click "start queue" the "loading" progress bar appears and "Elapsed Queue Time: 00:00:00" appears. That's it. No matter how long I wait, nothing changes.

Am using an Acer e700, 2GB RAM, Intel quad core 2.4GHz, Intel mother board, Windows Vista service pack 1. I've downloaded the software again, re-installed twice, updated drivers and other software, tried tracing paths down. Have tried different project settings with lots of different sources on the timeline (sequence) including DV, DVAVI, HDV, Quicktime, AVCHD, and have tried to export to FLV, QT, MOV, DVAVI, and many more. Source file in "C:\users\users\ ... etc" that Adobe Media Encoder references (in the queue) acutally appears in that location, and I can open in Premiere Pro CS4. (I have kept PP CS3 on my computer. Am afraid to remove it, because I will have nothing that works once I do.)

As a test I installed Premiere Pro CS4 on a three-year-old Windows XP machine and export (With Adobe Media Encoder) works well. Have been on the phone with Adobe for an hour.

I have been using Premiere for 15 years. My upgrade is worthless.

Wow something new. I let AME cook while I was writing this and got a message (in the log) Could not read from the source. Please check if it has moved or been deleted.

|

Mark as:

Currently Being Moderated

4. Curt Wrigley,

Nov 5, 2008 2:06 PM in reply to (dsharvey)

Report

Well it works on one machine and not the other. Its an install problem of something local with your pc. You're doing the right thing by utilizing adobe install support to work it out.

|

Mark as:

Currently Being Moderated

5. Eddie Lotter,

Nov 5, 2008 3:14 PM in reply to (dsharvey)

Report

>Please check if it has moved or been deleted.

Did you change your user folder's location?

Cheers
Eddie

PremiereProPedia ( RSS feed)
- Over 300 frequently answered questions
- Over 250 free tutorials
- Maintained by editors like you

Forum FAQ

|

Mark as:

Currently Being Moderated

6. Aurobi,

Nov 6, 2008 6:42 AM in reply to (dsharvey)

Report

Hi Mark,

if you launch AME and then from File>Add Premiere Pro sequence, you choose the Premiere Pro CS4 sequence and add it to AME batch and try to encode, does it work?

Thanks
Aurobinda.

|

Mark as:

Currently Being Moderated

7. (Mark_Shumard),

Nov 11, 2008 10:07 PM in reply to (dsharvey)

Report

Thanks. Am just getting back to this.

Short answer is it doesn't work at all. For comparison I tried it on my XP computer, and it worked great. When I clicked on the appropriate .prproj file in the import window, "sequence_1" appeared in the sequence window, and a few clicks later it rendered in AMECSD4.

On my Vista computer, I clicked on file>Add Premiere Pro Sequence, surfed to the file in the import window, and clicked on the appropriate .prproj file. Waited. Eventually got a (Not responding) message and the spinning donut.

Soooo ... either PPCS4 is making a corrupt file, or AMECS4 isn't able to recognize the file. Or maybe Vista is doing something wierd! Wouldn't be the first time ...

(By the way, the .prproj file mentioned above opens and plays in PPCS4. And if you drag a DVAVI, AVCHD, or other files into the AMECS4 cue window, the software converts it.)

|

Mark as:

Currently Being Moderated

8. Deemac1965,

Nov 12, 2008 5:18 AM in reply to (dsharvey)

Report

I have the same problem. I was told that if you uninstall CS3 first then install CS4 things should run smoother (I have a suspision we are still beta testing for adobe here!!) My work round was to render movies using CS3 (AVI or uncompressed) then load them into CS4 media exported and create the files that way. What a faff . . (as they say in Scotland)

PS I'm on A PC

|

Mark as:

Currently Being Moderated

9. Aurobi,

Nov 18, 2008 7:37 AM in reply to (dsharvey)

Report

Hi Mark,

if you have CS3, CS4 installed on the same system and you had un-installed CS3, you might see the problem. Please refer to http://kb.adobe.com/selfservice/viewContent.do?externalId=kb407106&sl iceId=2 for the solution.

Thanks
Aurobinda

|

Mark as:

Currently Being Moderated

10. (Mark_Shumard),

Nov 18, 2008 2:13 PM in reply to (dsharvey)

Report

Thanks to everyone for your help in this matter. When I bought my computer about a year ago it came with Vista. Over the last year the operating system has caused many problems with my software and with my computer. Over the weekend I installed XP. Now Premiere Pro CS4 and Media Encoder are working well.

|

Mark as:

Currently Being Moderated

11. Hobbyist22,

Apr 13, 2009 2:41 PM in reply to (dsharvey)

Report

I had this problem too -- I originally had CS3 installed, the installed CS4 and uninstalled CS3. Things started getting strange when I uninstalled CS3 -- lost my file associations, had this encoder problem and a bunch of other things. Finally I completely UN-installed both CS3 and CS4, deleted everything out of c:\program files\adobe (the uninstaller left lots of DLLs there), and reinstalled CS4 from scratch. Now everything works great, including the encoder.

|

Mark as:

Currently Being Moderated

12. digabyte,

Apr 25, 2012 5:48 PM in reply to Aurobi

Report

Hi Mark,

if you launch AME and then from File>Add Premiere Pro sequence, you choose the Premiere Pro CS4 sequence and add it to AME batch and try to encode, does it work?

Thanks
Aurobinda.

I am having the same problem (when I click ctrl-M to open AME for render, then click "start queue" AME goes into hang and eventually states "Not Responding"). I just tried the method above, and when I got the window for selecting the project file to import, the same thing happened (unrecoverable hang). I am running Win 7 64 bit (edit: just remembered this is a Vista machine, all current service packs and updates though), and my machine is 8 core with 12GB Ram and a dedicated vid card, so plenty of power and speed.

Edit: running Premiere CS4.2.1 (AME is CS4, but I can't tell you which one, but it is currently hanging... like most of the time)

|

Mark as:

Premiere Pro CS4 & Earlier

Encoder not working

Oct 29, 2008 2:03 PM

More Like This

Bookmarked By (0)