The PProHeadless.exe Error

[Dumeyni Arnaud]

Hello,
Do you have any CS3 products installed ?
If you have Premiere CS3 and CS4 on the same system, Media Encoder becomes instable and can’t export compressed footages from Premiere properly.
I had to export in AVI uncompressed and then compress it with another software.

The metadatas are detailed information ( take, bitrate, comments, etc ) about your medias.
When you export those within a file you can see and edit those info with any CS4 product. The fact that Media Encoder can’t read this data doesn’t make your file damaged.

[Gary Olsen]

Good information. However, this is a totally clean and brand new platform, so no legacy software was ever on it! I wonder if it has something to do with the fact that all of my video content (AVI comes from a hard drive (Sony) that is integrated with my camera, the HV1U. Maybe there’s something imbibed in the format of those videos that are causing the inconsistencies? I’ve got to do more testing of other files and imported footage. The list of possibilities is still quite long, and I am no closer to narrowing the field or figuring out any single cause. IS THERE AN ENGINEER OR CONTACT AT ADOBE I CAN CONTACT WITH MY LOG FILES SO WE CAN HAVE AN EDUCATED ANALYSIS? Can anyone help me with a contact person, and email, a wonklist or a phone number (that would be great)?

[Eddie Lotter]

If you want to contact Adobe directly, see the support page for contact numbers. Open a ticket with them and you will be able to work in real-time with a technician.

Cheers
Eddie

[James Brady]

Hello,

While researching a similar encoder problem, I came across this article about PProHeadless.exe…

https://digitalcontentproducer.com/affordablehd/newsletter/cs4_64bit_1222/index.html

It may help you identify whether you have a memory issue.

[Gary Olsen]

A (final?) followup on the problem of the PProHeadless.exe error. It has, for all intents and purposes, disappeared! Everything is working normally. But how can I rest without wondering if it will return to vex me? One who respondend to this thread suggested I had corrupt video clips. That may have been the cause. You see, I use hard drives and flash memory on which I record my video. No tape, no capture… just straight file transfer. You would think that such files would be pristine, and for the most part, they are. But if you don’t occasionally reformat your drives, you may impart a corrupt tag onto files that will not affect the video… which will play, and you can import it, put it on the timeline, slice it, dice it, and fry it in the pan, but when you attempt to output the finished project, you get the dreaded PProHeadless.exe error. I examined the file importation data log when I was importing clips, and I noticed there was trouble. The data log reported “problems” with certain clips. In Premere CS4, it’s a little window in the lower right hand corner of the time line. Subsequently, more care and frequent re-formatting steps on my camera’s hard drive and flash memory is my routine. Takes no time at all, and the result is clean files, and the problem disappears. Okay, I know what you’re thinking. How doI fix the corrupted files? Well, on my cameras I have tape backup, so I keep that source file and injest(capture) it the old fashioned way, and the result is a clean file. Hope this helps someone out there who encounters this problem. Ironically, this may not be the cause or the solution. But it worked for me, so if it’s a coincidence, a fix is a fix.

[Nezih Kanbur]

Sorry for the late response.
I ve had the same problem together with several other cs4 software errors. This happened to me before also, but this time after setting up an old version VGA driver (to operate my stereoscopic gaming devices)

Some of he messages were about the newly introduced GPU acceleration or something like gpu sniffer, so I thought this might be a VGA driver related issue. I have an NVIDIA 8600 GT graphics adapter. Setting up the latest drivers againe, solved my problem in all adobe applications.

Although your adapter is ATI, it may well have similar problems with adobe’s gpu acceleration.

[Jens Jensen]

I have the same problem. I found this tip :

"hi,
To solve this bug:
Pproheadless increases its memory buffers up to the limit of the RAM and stops the export in ame.
Just select in Ppro: Edition preference general
Optimize the memory render =
(sorry if the text is not exatly the same of the english version, but I use the french version…)
I also increase the ASIO buffer memory to 4096 and selected "32 bit" to avoid the "jkl" bug…
Xavier "

I have tested at all is fine 😉

[Tyrone De guzman]

Hi! i have the same problem PProHeadless.exe has encountered a problem and needs to close.. how come this is happening, i check the source file in the encoder it says c:/documents/locals/temp…etc but my status says could not read from the source check if it has been moved or deleted, but my source is in an external hard disk and not in c: howcome? =( im becoming desperate could not solve it by myself, sir/maam, please help thanks!

[Tyrone De guzman]

hello Jens, where will i find the PProheadless settings? thanks:)

[Gary Olsen]

If you read back on my posts, you’ll see the difficulties I had with this problem. It is likely you have a bad video file, but there is a workaround. If your video file plays from a tape, camera, or disc device attached to the camera, try recapturing it from your source footage.

To determine where the problem is, you will notice during rendering and just prior the error, there’s a clip that can be identified as responsible for the error depending on where the rendering stopped and the message appeared. Recapture that footage and create a new file. Import the new clip into your project and delete the old one. Then try rendering your project again.

I shoot direct to disc, so I usually transfer the files directly from my camera’s hard drive or flash memory card to Premiere. If like me you do it this way, try something different in capturing your footage… say through the HDMI connection, Firewore (iLink) or through your component video cable.

This has worked for me. Adobe has not come forth with a problem analysis or a fix for me. This is something I worked out with fellow users of the product making suggestions via posts to Creative Cow.