-
Pproheadless.exe error results in extra m4v file, what exactly is happening?
I’m editing a large amount of H.264 videos via Premiere 5.5, then exporting via Adobe Media Encoder.
Lately been getting the “Pproheadless.exe has stopped working” error at the end of each encode, but I can close the popup error window and the video file is still created. However alongside the regular finished file “filewhatever.mp4” is a similar-sized one called something like “3933_3222_14608865.m4v” – this appears to have the same content but I’m unable to seek via the progress bar in any media player.
Can anyone explain the mechanics going on here? What is this second & seemingly identical file? Is the error damaging affecting the quality of my encodes in some way I’m not noticing, or can I safely ignore it if it doesn’t totally crash Premiere or AME?
Also, any suggestions to prevent that error? I’ve tried everything in https://greenwoodworx-media.blogspot.com/2012/01/error-adobe-premiere-cs4-cs5.html with no luck.
FWIW, I’m encoding in h.264, single pass variable bitrate.
Thanks in advance.
-
5 Replies
-
The error is pretty vague, so there would have to be a lot more info to troubleshoot it.
The file you’re seeing is a temp file that is created during the transcode. If the final file had been completed properly, that temp file would have been gone.
TimK,
Director, Consultant
Kolb Productions,Adobe Certified Instructor
-
Thanks for the reply Tim!
So that temp file isn’t a remnant of some unfinished process (aside from its own deletion)? I guess my worry was that it was data that needed to be integrated into the main video file somehow, but not doing so due to the error. If it’s just extra due to deletion begin aborted I can live with that.
-
I’m not sure if the error might actually have been a result from the temp file not being able to be deleted…if you target a different destination for the output file, does the issue persist?
TimK,
Director, Consultant
Kolb Productions,Adobe Certified Instructor
-
Yup, no matter the directory I choose for the video to encode to, that m4v populates right there beside it.
-
The fact that the file exists at the end of the process is proof enough that something is going wrong at the end of the decode…that temp file should be gone as it would only exist until the destination file is properly written and closed.
I’d at least try to reinstall the software…does this happen on all your projects? Any type of media?
TimK,
Director, Consultant
Kolb Productions,Adobe Certified Instructor
Reply to this Discussion! Login or Sign Up